Why Was new.FamilySearch.org Turned Off ?
by Jim Greene of FamilySearch, January 15, 2015
The following is highly informative. We encourage all uses of familysearch new and old to read this information and use it to help yourself and others.
The new.FamilySearch.org website was recently closed down because, among other things, it no longer allowed us to provide the best possible service and data resources to our users. The few users who were still using the new.FamilySearch.org site were redirected to the current FamilySearch Family Tree website. However, several people have asked questions about why FamilySearch migrated away from new.FamilySearch.org site to the FamilySearch Family Tree. Below are some of the most commonly asked questions regarding this transition and answers to those questions. . .
The following is highly informative. We encourage all uses of familysearch new and old to read this information and use it to help yourself and others.
The new.FamilySearch.org website was recently closed down because, among other things, it no longer allowed us to provide the best possible service and data resources to our users. The few users who were still using the new.FamilySearch.org site were redirected to the current FamilySearch Family Tree website. However, several people have asked questions about why FamilySearch migrated away from new.FamilySearch.org site to the FamilySearch Family Tree. Below are some of the most commonly asked questions regarding this transition and answers to those questions. . .
This section contains 9 of the most frequently asked questions along with the answers concerning the closing of new.FamilySearch version.
Q #1 -Why have the engineers decided to shut down new. FamilySearch.org before it and Family Tree are separated.
A: The new.FamilySearch database and Family Tree have always been separate databases. We cannot shut down one and start the other, especially when they are so different. To address this issue, we’ve allowed a period of time where the two databases are synchronized. This means that data can be entered in one and it will show up in both databases. This is a very complex and costly process, so we allowed it only as a temporary solution. When we got to a point where the majority of our users were using Family Tree, we decided that it was time to close down the new.FamilySearch.org site.
The new.FamilySearch program was shut down in phases to make the transition as easy as possible. It was well planned and totally directed toward easing the transition for our users. The decision to move to a new system and a new database was made years ago, and was necessary in order to realize the goals of FamilySearch. The new.FamilySearch system had limitations that made it impossible for the system to keep up with the needs and demands that the public was asking of it. An important part of our long term goals is and always will be to provide our users with the easiest and most efficient access to records and information that will allow them to uniquely identify their ancestors and help rebuild their ancestral families. This transition from new.FamilySearch to Family Tree makes that possible.
Q #2 - With new.FamilySearch no longer operational, we will not be able to view records that were merged incorrectly. How can we “unmerge” mismatched records?
A: 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.”
Q #3 - Why is the Combined Records Search feature not available in Family Tree?
A: Family Tree does not combine records. Family Tree keeps a single copy of the best conclusions. It keeps a history of how that data got there, and allows any action to be undone.
Q #4 - Many people have numerous PIDs that were incorrectly combined/merged in new.FamilySearch.org. What can we do about that?
A: They will be able to go to 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.
Q #5 - I heard that records that were merged in new.FamilySearch cannot be un-merged in Family Tree. Is that true?
A: Not true. See above. It is a different process, but it can be done.
Q: #6 Shutting down new.FamilySearch leaves users with no way to know what mis-merges have occurred.
A: Mis-merges in new.FamilySearch should be left alone. There is no way to correct them even in new.FamilySearch. Learn the new tools and techniques to use in Family Tree, and you will be much more satisfied with the results and the overall experience.
New.FamilySearch was constructed from Ancestral File, Personal Resource File, and the International Genealogical Index. It is important to review the original data to understand the actual persons that were originally created and then combined incorrectly later. To help users identify the actual individuals who were combined in new.FamilySearch, we are planning to create sources on each person in Family Tree that refer to the original AF, PRF, and IGI records. This will allow users to go back and view the original data that was used when creating a combined record. By using these sources, users should be able to accurately determine all of the individuals who were mis-merged in new.FamilySearch.
Q: #7 Why can't new.FamilySearch remain as a read only database rather than getting rid of it?
A: Over time, much of the data in this database became badly flawed and incorrect. Using new.FamiySearch, even as a viewable source, could easily confuse people and lead to even worse conclusions in Family Tree.
Q: #8 Does this mean that valid temple ordinances that were done in the old system are now being thrown out?
A: No, ordinances are never thrown out. The same ordinance database used in new.FamilySearch is being used in Family Tree. All ordinances are connected to ancestors as they have always been.
One concern we have is when someone manually creates a new record in Family Tree for an ancestor that was originally mis-merged in new.FamilySearch. When that happens, the newly created ancestors will not have the original ordinances showing on their record. We recognize that this is a problem, and we are working to provide the ability for members to search the ordinance database to find the correct ordinance information and attach them to their ancestor. Until that search capability is available, some people may need to call our online support folks and ask them to move ordinances to the correct person based on good evidence. One call to the FamilySearch Support team should help you resolve that issue quite nicely.
Q: #9 How will the accomplishment of the 2016 milestone impact long-standing subscribers who are not members of the Church of Jesus Christ of the Latter day Saints?
A: New.FamilySearch was not open to those who aren’t members of the LDS Church (except a few select Family History Center workers). It will have zero impact on those who aren’t members of the Church. In fact, it will lead to many positive things for them that they never had available before.
A: The new.FamilySearch database and Family Tree have always been separate databases. We cannot shut down one and start the other, especially when they are so different. To address this issue, we’ve allowed a period of time where the two databases are synchronized. This means that data can be entered in one and it will show up in both databases. This is a very complex and costly process, so we allowed it only as a temporary solution. When we got to a point where the majority of our users were using Family Tree, we decided that it was time to close down the new.FamilySearch.org site.
The new.FamilySearch program was shut down in phases to make the transition as easy as possible. It was well planned and totally directed toward easing the transition for our users. The decision to move to a new system and a new database was made years ago, and was necessary in order to realize the goals of FamilySearch. The new.FamilySearch system had limitations that made it impossible for the system to keep up with the needs and demands that the public was asking of it. An important part of our long term goals is and always will be to provide our users with the easiest and most efficient access to records and information that will allow them to uniquely identify their ancestors and help rebuild their ancestral families. This transition from new.FamilySearch to Family Tree makes that possible.
Q #2 - With new.FamilySearch no longer operational, we will not be able to view records that were merged incorrectly. How can we “unmerge” mismatched records?
A: 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.”
Q #3 - Why is the Combined Records Search feature not available in Family Tree?
A: Family Tree does not combine records. Family Tree keeps a single copy of the best conclusions. It keeps a history of how that data got there, and allows any action to be undone.
Q #4 - Many people have numerous PIDs that were incorrectly combined/merged in new.FamilySearch.org. What can we do about that?
A: They will be able to go to 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.
Q #5 - I heard that records that were merged in new.FamilySearch cannot be un-merged in Family Tree. Is that true?
A: Not true. See above. It is a different process, but it can be done.
Q: #6 Shutting down new.FamilySearch leaves users with no way to know what mis-merges have occurred.
A: Mis-merges in new.FamilySearch should be left alone. There is no way to correct them even in new.FamilySearch. Learn the new tools and techniques to use in Family Tree, and you will be much more satisfied with the results and the overall experience.
New.FamilySearch was constructed from Ancestral File, Personal Resource File, and the International Genealogical Index. It is important to review the original data to understand the actual persons that were originally created and then combined incorrectly later. To help users identify the actual individuals who were combined in new.FamilySearch, we are planning to create sources on each person in Family Tree that refer to the original AF, PRF, and IGI records. This will allow users to go back and view the original data that was used when creating a combined record. By using these sources, users should be able to accurately determine all of the individuals who were mis-merged in new.FamilySearch.
Q: #7 Why can't new.FamilySearch remain as a read only database rather than getting rid of it?
A: Over time, much of the data in this database became badly flawed and incorrect. Using new.FamiySearch, even as a viewable source, could easily confuse people and lead to even worse conclusions in Family Tree.
Q: #8 Does this mean that valid temple ordinances that were done in the old system are now being thrown out?
A: No, ordinances are never thrown out. The same ordinance database used in new.FamilySearch is being used in Family Tree. All ordinances are connected to ancestors as they have always been.
One concern we have is when someone manually creates a new record in Family Tree for an ancestor that was originally mis-merged in new.FamilySearch. When that happens, the newly created ancestors will not have the original ordinances showing on their record. We recognize that this is a problem, and we are working to provide the ability for members to search the ordinance database to find the correct ordinance information and attach them to their ancestor. Until that search capability is available, some people may need to call our online support folks and ask them to move ordinances to the correct person based on good evidence. One call to the FamilySearch Support team should help you resolve that issue quite nicely.
Q: #9 How will the accomplishment of the 2016 milestone impact long-standing subscribers who are not members of the Church of Jesus Christ of the Latter day Saints?
A: New.FamilySearch was not open to those who aren’t members of the LDS Church (except a few select Family History Center workers). It will have zero impact on those who aren’t members of the Church. In fact, it will lead to many positive things for them that they never had available before.
