new merging system, cannot see when each possible duplicate ID was added to Family Tree
LegacyUser
✭✭✭✭
Carol Hutchinson said: you cannot see which record was added first [chronologically] to Family Tree, this is a very horrible downgrade from the previous merging system. You used to be able to see WHO added the ID, and WHEN the information was added to Family Tree by just clicking on the data you wanted to check when comparing the 2 records you are trying to merge.. This is all gone. At least I cannot figure out how to do this.
It was nice to be able to see when a record [or individual data such as name, birth, christening, burial, etc.had been added, and which user ID had added it] to Family Tree. You could be certain to merge the brand new 2020 files into the older files, which have the history of changes which can contain VERY important data.
Now, new patrons will just merge the established, well sourced records to their new, possibly flawed files, and all history of changes will vanish. There are so many more things wrong with this new merging system, there is not enough room to list them all
I would suggest everyone copy all the ID numbers of people from Family Tree that they care about, so that if their data disappears because of "bad" merging, they will have a better chance of correcting it bu restoring [undoing the merge]
Another problem is that you used to have to scroll down to the bottom of the page before you could continue a merge, THIS WAS A GOOD THING. Because you had to look at everything, person, etc. that you were merging. Now all you have to do is keep hitting the continue button on the top of the page, without every looking at all of the data [and yes, most people will just do that,] Have you seen the horrible merges that happen on this webiste?, You now have to add a reason for the merge before the merge will happen.However, all you have to do is type in one letter, like s and the program lets you complete the merge. So, that step is mostly useless, and no better than the previous merging system, where you could add a reason, but didn't have to.
It was nice to be able to see when a record [or individual data such as name, birth, christening, burial, etc.had been added, and which user ID had added it] to Family Tree. You could be certain to merge the brand new 2020 files into the older files, which have the history of changes which can contain VERY important data.
Now, new patrons will just merge the established, well sourced records to their new, possibly flawed files, and all history of changes will vanish. There are so many more things wrong with this new merging system, there is not enough room to list them all
I would suggest everyone copy all the ID numbers of people from Family Tree that they care about, so that if their data disappears because of "bad" merging, they will have a better chance of correcting it bu restoring [undoing the merge]
Another problem is that you used to have to scroll down to the bottom of the page before you could continue a merge, THIS WAS A GOOD THING. Because you had to look at everything, person, etc. that you were merging. Now all you have to do is keep hitting the continue button on the top of the page, without every looking at all of the data [and yes, most people will just do that,] Have you seen the horrible merges that happen on this webiste?, You now have to add a reason for the merge before the merge will happen.However, all you have to do is type in one letter, like s and the program lets you complete the merge. So, that step is mostly useless, and no better than the previous merging system, where you could add a reason, but didn't have to.
Tagged:
0
Comments
-
Jeff Hawkins said: I like your idea about knowing when a record was created. That does help to know which record is more mature.
In step 2 of the merge, you can see the dates and attribution by expanding the conclusion using the chevron.0 -
Aaron Allen said: The new merge is much more confusing and adding the additional steps is much more time consuming.0
-
Paul said: If "more time consuming" equates to users dedicating more attention to this extremely important activity, I believe this change will prove to be highly positive. Up till now, it has been rather too easy to say, "Yes, that appears to be a match," without having to give too much thought to the comparison process.0
-
gasmodels said: second your comments Paut, I spent several hour in the past few days undoing merges of parents living in Utah having children christened in England in the 1850/60's just because the parents names matched.0
-
Tom Huber said: I also agree with Paul's thoughts.
But this particular discussion does make a point. I haven't used the new system, so I don't know what is presented in the Change Log, but if a merge is not noted in both the merged record and the surviving record, then that needs to be remedied.
We must be able to see if and when a merge takes place that impacts persons (their PIDs) involved in the merge.0
This discussion has been closed.