MyHeritage to FSTree Duplications

LegacyUser

Robert Wren said: Jimmy, one partial 'solution' to these duplicate/similar 'sources' would be to allow the duplicates to be 'nested' and allowing the BEST one (with the actual source IMAGE showing, with a good transcription) to be 'on top.' Then all would be available but the others less 'visible.'

It must be remembered that the primary purpose of hints, indexes, & transcript is to lead to an image of the actual source! The source itself is the documentation of the genealogical information that is being "proven" - not the hint, index or transcript. And that actual source IS evidence to prove whatever data is being attempted to be added to the PID.

LegacyUser

Jeff Wiseman said: Great idea. But since there are multiple copies of images of the same paper from different places/owners, being able to "Stack" any source citations that are ultimately derived from the same PAPER copy would be pretty cool. e.g., an index made directly from a paper copy of a Census, and an index made from an image of that census, and an index made from a different image that is not available but known to be the same image would ALL be in the same stack.

One of the problems that we have is the differences between citations, index sources, and image sources. People tend to view them all as the same thing and as a result, they frequently can get confused over it all.

This would allow a person to very quickly evaluate the same index data between all the sources for comparison purposes. But I don't know how difficult it would be, given a set of maybe 80 source citations attached to a given person record, to go through and group them by determining what the original paper record was. You also would have to deal with things like "is the paper record index of another paper record in the same "group" for stacking purposes?"

It seems that it could really get out of control, especially when you consider custom sources that are coming from different places as well.

It might be easier to limit the benefits a bit and only stack citations to index sources which are referencing the same image sources. You could end up with multiple stacks for the same logical image that way, but it would help when multiple indexes have been drawn from the same images.

In any event you should still have only a single citation per source, even if you are "stacking" them for display purposes.

LegacyUser

Tom Huber said: The problem is really one that MyHeritage needs to deal with. It will take a lot of programming effort on their part, but if a record, such as a census enumeration, exists on both sites and MyH has imported that source into the tree from FS, then regardless of how the source is set up in both sites, MyH must prevent a duplicate source from being written into the MyH and subsequently transferred back to FS as a duplicate.

I have "played around" with the MyH site and find that the duplication of the FS tree on the MyH site and they concept behind its synchronization feature is not a good one. Back when the site overwrote the FS material when it was initially introduced, one of the concepts was that the one-by-one synchronization is too much work for the MyH customers, so they came up with the sync process that avoid the one-by-one approach. To me, that is a major flaw and if MyH is still maintaining that philosophy, then I think FS needs to sever its synchronization relationship with MyH.