In addition to what I already said earlier, this one I sent to product manager. The announcement has to be dumbest I have ever received. Read my replies to understand why. Consider this case this afternoon... Harriet A. Day LZYG-DFV or is it Minnie Day or is it Jane Ella Day or is it Statia Bell or is it Stacy Lucinda Bell? (take a peek in nFS for yourself.) Whose ordinances are hers, or is hers, or is hers, or is hers, or is hers. Bottom line, the lady I was working with, said these ordinances are split betwwen Harriet, Minnie and Jane. She had the paper copy she kept to keep track so she know whose ordinances are. Only way to deal with this is to continue KB 106612 and eliminate the "borrowed ordinances" and other identities. On 6/11/2013 5:35 PM, Steve Kelsey wrote: > Comments please. > Steve Kelsey > > ----- Original Message ----- > From: <Support@FamilySearch.org> > To: <undisclosed-recipients:> > Sent: Tuesday, June 11, 2013 1:06 PM > Subject: Separating or Combining Individuals in Family Tree > > >> Dear FamilySearch Patron: >> >> Thank you for contacting FamilySearch. We appreciate your diligence in >> maintaining accurate family history records. You have asked us to correct >> information in new FamilySearch or Family Tree. Often, correcting >> information in new FamilySearch or Family Tree involves combining or >> separating records in new FamilySearch. Currently, combining and >> separating records in new FamilySearch causes the records in Family Tree >> to reset to what is in new FamilySearch. This has the potential to reverse >> any changes made to the records in Family Tree. In order to preserve the >> work that you and other patrons have done in Family Tree, we are no longer >> separating or combining records in new FamilySearch. >> When you find incorrect information in Family Tree, (including multiple >> individuals in one record), do one or more of the following: >> 1. Correct the incorrect information in Family Tree, including all >> genealogical and relationship data. If you need to view the details of the >> record, go to new.FamilySearch.org, and display the combined record. >> 2. In Family Tree, check the possible duplicates, and merge duplicate >> persons. >> 3. Indicate persons who are not a match to prevent the records from being >> merged incorrectly in the future. >> 4. Create a new record for the individual(s) whose information did not >> come across from new FamilySearch, linking the new record(s) to the >> correct family. >> Family Tree is continuously being improved to allow patrons to >> independently resolve data inaccuracies and issues in their family >> pedigree, part of this improvement is better tools to help us assist >> patrons in resolving data challenges they are not able to address >> themselves. We are currently waiting for the tools in Family Tree to be >> fully developed in order to assist you. We ask for your patience as we >> wait for these to be completed and available to our team. We wish you >> success in your family history endeavors. >> >> Sincerely, >> FamilySearch >> Support@FamilySearch.org >> 866-406-1830 >> > > > Please send the one word message SUBSCRIBE or UNSUBSCRIBE to LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM > ------------------------------- > To unsubscribe from the list, please send an email to LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message >