This particular blog post answers, in-depth, many of the questions that are raised continually by the adoption of FamilySearch Family Tree as a replacement for the.FamilySearch.org. After reading through the blog post, I have chosen not to reproduce large portions of the blog post here. I think the information provided is valuable and explains many of the problems and issues raised by the transition. There is however one reference that I think is important to be disseminated further. The question is asked, "How can we "unmerge" mismatched records?" Here is the response:
The new.FamilySearch system combined records in such a way that even though you think it is showing you what was combined, it was not a clean view and could be very flawed. That is one of the reasons we needed to move away from new.FamilySearch to Family Tree. Data in new.FamilySearch was becoming jumbled and unreliable. Family Tree keeps a history of merges and allows users to unmerge an incorrectly merged record. To learn how to properly unmerge a record, refer to the help article titled, “Undoing a Merge.”One of the main issues in migrating from new.FamilySearch.org to Family Tree is the issue of the combined records in the new.FamilySearch.org database, many of which have been wrongly combined. The resolution of this issue is somewhat complex but involves simply correcting the information in Family Tree and, to some extent, ignoring the previously mis-combined records.This particular issue is addressed in the FamilySearch blog post as follows in response to the question about incorrectly combined records in new.FamilySearch.org:
They will be able to go a person’s records and put only the best sourced information there. If multiple people were incorrectly combined or merged in Family Tree there is a process to follow to clean up these incorrect merges. In many cases, it is easier to fix this problem in Family Tree. Using the data in new.FamilySearch to provide you with a roadmap to cleanup your data is not a good choice since many individuals were not correctly merged in the first place.This blog post answers some of the more difficult questions which I am faced with answering on a regular basis. In many cases, it will take me anywhere from an hour to two hours to adequately explain to people who are caught up in trying to correct the errors in Family Tree inherited from there.FamilySearch.org the reasons for the difficulties they are facing. Blog posts such as this one are extremely helpful in facilitating the transition process I appreciate the explanations given by Jim Greene. If you have anything to do with Family Tree, I would suggest carefully reading and noting the implications of the explanations given.