MORE MyHeritage to FSTree Duplications; use cautiously!
LegacyUser
✭✭✭✭
Robert Wren said: Today, I was browsing my FS synched tree in MyH and viewed "Instant Discoveries" and regrettably clicked on what on "Review" which I NOW see was just another "People Discovery."
Hence, 12 people were added to John Thurber 1700-1791 to my MyH tree, AND when (or if) I once again sync to FS (WHICH I DO NOT PLAN TO DO!) many of these 'additions' would be changed in, or added to, FS Tree LK32-9ZQ family. At least 5 of the 12 would be duplicates, likely more - and the parents are different (which I need to resolve).
They were basically added 'automatically' from another person's tree. There was NO WAY to stop the process once started and the process took over 20 minutes, no monitoring of what is happening - other than 'still working' - when I clicked to the previous page I was unable to return to the download page.
I still have 19 other similar MyH "discoveries" with a couple hundred other potential problems. So once again I will spend time repairing, rather than researching.
At some point someone in the 'family history business' needs to realize that copying other folks trees may be quick - but not necessarily CORRECT!!
I've contacted the FS employee in a private email with more details who 'partially' solved the problem last time: https://getsatisfaction.com/familysea...
I suggest extreme CAUTION in using the FS/MyH sync procedure, et al, and to use similar caution with any and all other trees unless they are 'proven' and well sourced.
It may be EASY and increase your 'numbers' but it may do little to help in records "Worthy of All Acceptation."
Hence, 12 people were added to John Thurber 1700-1791 to my MyH tree, AND when (or if) I once again sync to FS (WHICH I DO NOT PLAN TO DO!) many of these 'additions' would be changed in, or added to, FS Tree LK32-9ZQ family. At least 5 of the 12 would be duplicates, likely more - and the parents are different (which I need to resolve).
They were basically added 'automatically' from another person's tree. There was NO WAY to stop the process once started and the process took over 20 minutes, no monitoring of what is happening - other than 'still working' - when I clicked to the previous page I was unable to return to the download page.
I still have 19 other similar MyH "discoveries" with a couple hundred other potential problems. So once again I will spend time repairing, rather than researching.
At some point someone in the 'family history business' needs to realize that copying other folks trees may be quick - but not necessarily CORRECT!!
I've contacted the FS employee in a private email with more details who 'partially' solved the problem last time: https://getsatisfaction.com/familysea...
I suggest extreme CAUTION in using the FS/MyH sync procedure, et al, and to use similar caution with any and all other trees unless they are 'proven' and well sourced.
It may be EASY and increase your 'numbers' but it may do little to help in records "Worthy of All Acceptation."
Tagged:
0
Comments
-
Jordi Kloosterboer said: MyHeritage should program an undo option.0
-
Paul said: The FamilySearch Possible Duplicates algorithm comes to mind! Okay, you are not directly (inadvertently) doing something yourself, but the resultant workload - to correct the mess created by other users - seems to have been no worse than many of us encounter regularly, even without having a "synched tree".
I know there are mixed feeling on this, but I think it is far better to search for duplicates / records manually than have a computer routine do it for you. Perhaps I'm not comparing like-with-like here, but I can't see I would have gone anywhere near the MyHeritage routine, as I would always expect possible, negative consequences.0 -
Jeff Wiseman said: MyHeritage is NOT supposed to be allowing bulk copying of records from other trees into the FS specific tree in MyH accounts! This is for the very same reason that loading GECOM files into those FS specific trees is not allowed.
MyH is not doing a very good job of protecting those FS Specific trees the way they said they would.0
This discussion has been closed.