tag:blogger.com,1999:blog-1527613590529958801.post3769146339293543699..comments2024-03-21T19:08:05.737-07:00Comments on Genealogy's Star: More information about FamilySearch Family TreeJames Tannerhttp://www.blogger.com/profile/02989059644120454647noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1527613590529958801.post-91591439980194110062012-09-12T14:25:56.117-07:002012-09-12T14:25:56.117-07:00The current plan is to release the first version o...The current plan is to release the first version of the merge/unmerge feature the end of September or early October, at which time combine/separate from new.familysearch will be disabled. The plan also has new.familysearch going away in early 2013.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1527613590529958801.post-29585056075021442402012-09-04T19:14:22.329-07:002012-09-04T19:14:22.329-07:00As you have previously pointed out, the biggest is...As you have previously pointed out, the biggest issue by far at this point is that changes made in Family Tree are overridden when records are combined and separated in nFS. It's hard to justify spending a lot of time cleaning up Family Tree since all your work is lost when someone combines a record in nFS. One other issue I haven't heard talked about is that it is very easy to "hijack" a record in Family Tree. You can take a record that is incorrect and "fix" it by entering the corrected name, birth/death dates, etc., but then the temple work at the bottom of the form may well be for a completely different person! The users's manual talks about needing to review the "qualifying information" and if the temple work is for the wrong person that will have to be corrected as well. That sounds like a very tedious task when you have thousands of people in your tree.Anonymousnoreply@blogger.com