The delete button caution says: "It is recommended that you delete people only if you added a person by mistake or if the person never existed." I think that is a good option because I have seen where people have added names and information in by mistake before really searching and verifying the person (and listing the wrong person/information)- only then to figure out they made a mistake and can't figure out how to get rid of that wrong person once they figure out the right person. Additionally it should be helpful in deleting out the people listed with the incorrect gender- as one cannot merge individuals of different genders. As for the uncombine option- don't wait for that appear. With the new merging, that option is not possible. In new.familysearch.org all information merged was kept in separate "little files" and so it was easy to uncombine or separate those files out. With the merge in Family Search- there are no "little files" to easily separate out, only the selected information is saved and put in one record/file. The unmerge button will only appear until changes have been made in that newly created record. Once changes have been made, the computer doesn't know to which of the records the changes apply.... so it cannot uncombine. The option is to make separations manually. Here's a link to the white paper about how to separate people who have been incorrectly combined in new.familysearch. http://broadcast.lds.org/eLearning/fhd/Community/en/FamilySearch/FamilyTree/ pdf/familyTreeNotMyAncestorWhitepaper.pdf The issue there still remains, that in creating a new person, the ordinances will show as available- and probably have already been done (multiple times in some cases.) There is supposed to be a "Fix" in the works for an ordinance assignment option, but it hasn't been released yet. If changes are well sourced and documented, it is hoped that others will not come back in and change those records. Dive into Family Tree- it really does have a lot of great options! Not perfect, but I think superior to new.familysearch in the ability to really correct errors! And sourcing, stories and photos are amazing! Tammy Stevenson ______________________________________________________ Message: 3 Date: Thu, 30 May 2013 19:21:38 -0400 (EDT) From: JCBrooks@aol.com Subject: [LDS-WC] Delete button To: lds-ward-consultant@rootsweb.com Message-ID: <71b04.50d1a8db.3ed93902@aol.com> Content-Type: text/plain; charset="US-ASCII" Is anyone as concerned as I am about the delete button? We should be merging first before deleting as I believe ordinances could well be lost. Plus there is so much disagreement in some families, particularly non-LDS lines, about research. Frankly Family Tree is embarrassing to me when I look at what a mess they and others have made of simple pure, well documented families. Like others, I am waiting until they straighten out more before I spend any great amount of time fixing things. It is so frustrating and we only have half the tools. Uncombining is sure more important than delete!! Michele ______________________________________________________________

Thanks for the link to the document. I experienced a problem the other day where two brothers, Bernard Henry Stueve and Henry Bernard Stueve were combined by FamilySearch. The only thing I could do was make sure that Bernard Henry's information was correct and then re-add Henry Bernard to the family. This meant that Henry Bernard no longer had his temple ordinance info associated with him. I was able to sync with nFS and upload the "unofficial" ordinance records from my file. Now his record says "Complete" but no information is listed as to when and where the ordinances were done. Miles Meyer Jacksonville, FL "Unless someone like you cares a whole awful lot, nothing is going to get better. It's not." - Dr. Seuss, The Lorax On Fri, May 31, 2013 at 9:08 AM, Scott and Tammy Stevenson < sstevenson@safelink.net> wrote: > The delete button caution says: "It is recommended that you delete people > only if you added a person by mistake or if the person never existed." > I think that is a good option because I have seen where people have added > names and information in by mistake before really searching and verifying > the person (and listing the wrong person/information)- only then to figure > out they made a mistake and can't figure out how to get rid of that wrong > person once they figure out the right person. Additionally it should be > helpful in deleting out the people listed with the incorrect gender- as one > cannot merge individuals of different genders. > > As for the uncombine option- don't wait for that appear. With the new > merging, that option is not possible. In new.familysearch.org all > information merged was kept in separate "little files" and so it was easy > to > uncombine or separate those files out. With the merge in Family Search- > there are no "little files" to easily separate out, only the selected > information is saved and put in one record/file. The unmerge button will > only appear until changes have been made in that newly created record. > Once > changes have been made, the computer doesn't know to which of the records > the changes apply.... so it cannot uncombine. The option is to make > separations manually. Here's a link to the white paper about how to > separate people who have been incorrectly combined in new.familysearch. > > http://broadcast.lds.org/eLearning/fhd/Community/en/FamilySearch/FamilyTree/ > pdf/familyTreeNotMyAncestorWhitepaper.pdf > The issue there still remains, that in creating a new person, the > ordinances > will show as available- and probably have already been done (multiple times > in some cases.) There is supposed to be a "Fix" in the works for an > ordinance assignment option, but it hasn't been released yet. > > If changes are well sourced and documented, it is hoped that others will > not > come back in and change those records. > > Dive into Family Tree- it really does have a lot of great options! Not > perfect, but I think superior to new.familysearch in the ability to really > correct errors! And sourcing, stories and photos are amazing! > Tammy Stevenson > ______________________________________________________ > Message: 3 > Date: Thu, 30 May 2013 19:21:38 -0400 (EDT) > From: JCBrooks@aol.com > Subject: [LDS-WC] Delete button > To: lds-ward-consultant@rootsweb.com > Message-ID: <71b04.50d1a8db.3ed93902@aol.com> > Content-Type: text/plain; charset="US-ASCII" > > Is anyone as concerned as I am about the delete button? We should be > merging first before deleting as I believe ordinances could well be lost. > Plus > there is so much disagreement in some families, particularly non-LDS lines, > about research. Frankly Family Tree is embarrassing to me when I look at > what a mess they and others have made of simple pure, well documented > families. > > Like others, I am waiting until they straighten out more before I spend any > great amount of time fixing things. It is so frustrating and we only have > half the tools. Uncombining is sure more important than delete!! > > Michele > ______________________________________________________________ > > > > 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 >

Very interesting. I am concerned this might happen to baby brothers who die as infants and receive the same name one after the other. What would have happened if you had found the "possible match" before the records were combined and marked them as "not the same person"? Would FT still have allowed them to be combined? > From: milesmeyer@gmail.com > Date: Fri, 31 May 2013 09:25:10 -0400 > To: lds-ward-consultant@rootsweb.com > Subject: Re: [LDS-WC] Delete button > > Thanks for the link to the document. I experienced a problem the other day > where two brothers, Bernard Henry Stueve and Henry Bernard Stueve were > combined by FamilySearch. The only thing I could do was make sure that > Bernard Henry's information was correct and then re-add Henry Bernard to > the family. This meant that Henry Bernard no longer had his temple > ordinance info associated with him. I was able to sync with nFS and upload > the "unofficial" ordinance records from my file. Now his record says > "Complete" but no information is listed as to when and where the ordinances > were done. > > Miles Meyer > Jacksonville, FL > > "Unless someone like you cares a whole awful lot, nothing is going to get > better. It's not." - Dr. Seuss, The Lorax > > > On Fri, May 31, 2013 at 9:08 AM, Scott and Tammy Stevenson < > sstevenson@safelink.net> wrote: > > > The delete button caution says: "It is recommended that you delete people > > only if you added a person by mistake or if the person never existed." > > I think that is a good option because I have seen where people have added > > names and information in by mistake before really searching and verifying > > the person (and listing the wrong person/information)- only then to figure > > out they made a mistake and can't figure out how to get rid of that wrong > > person once they figure out the right person. Additionally it should be > > helpful in deleting out the people listed with the incorrect gender- as one > > cannot merge individuals of different genders. > > > > As for the uncombine option- don't wait for that appear. With the new > > merging, that option is not possible. In new.familysearch.org all > > information merged was kept in separate "little files" and so it was easy > > to > > uncombine or separate those files out. With the merge in Family Search- > > there are no "little files" to easily separate out, only the selected > > information is saved and put in one record/file. The unmerge button will > > only appear until changes have been made in that newly created record. > > Once > > changes have been made, the computer doesn't know to which of the records > > the changes apply.... so it cannot uncombine. The option is to make > > separations manually. Here's a link to the white paper about how to > > separate people who have been incorrectly combined in new.familysearch. > > > > http://broadcast.lds.org/eLearning/fhd/Community/en/FamilySearch/FamilyTree/ > > pdf/familyTreeNotMyAncestorWhitepaper.pdf > > The issue there still remains, that in creating a new person, the > > ordinances > > will show as available- and probably have already been done (multiple times > > in some cases.) There is supposed to be a "Fix" in the works for an > > ordinance assignment option, but it hasn't been released yet. > > > > If changes are well sourced and documented, it is hoped that others will > > not > > come back in and change those records. > > > > Dive into Family Tree- it really does have a lot of great options! Not > > perfect, but I think superior to new.familysearch in the ability to really > > correct errors! And sourcing, stories and photos are amazing! > > Tammy Stevenson > > ______________________________________________________ > > Message: 3 > > Date: Thu, 30 May 2013 19:21:38 -0400 (EDT) > > From: JCBrooks@aol.com > > Subject: [LDS-WC] Delete button > > To: lds-ward-consultant@rootsweb.com > > Message-ID: <71b04.50d1a8db.3ed93902@aol.com> > > Content-Type: text/plain; charset="US-ASCII" > > > > Is anyone as concerned as I am about the delete button? We should be > > merging first before deleting as I believe ordinances could well be lost. > > Plus > > there is so much disagreement in some families, particularly non-LDS lines, > > about research. Frankly Family Tree is embarrassing to me when I look at > > what a mess they and others have made of simple pure, well documented > > families. > > > > Like others, I am waiting until they straighten out more before I spend any > > great amount of time fixing things. It is so frustrating and we only have > > half the tools. Uncombining is sure more important than delete!! > > > > Michele > > ______________________________________________________________ > > > > > > > > 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 > > > > 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