Case 2:
A. Import 11 gen Ancestors of KHR5-7J1 from FSFT into RM11.5 fresh database
versus
B. Import same into Ancestral Quest, export to GEDCOM, import into fresh RM database
FAN CHARTS
Both colorcoded to highlight duplicate couples: Blue=child of duplicate couple, Red=Father in dup couple, Green=Mother in dup couple
And I tested for the first time my deduplication procedure. While it did clear out the duplicate couples and child-parent links, it also lost the linkage that tied the root person’s parents as second cousins. So it’s not quite right, yet!
That’s an insane collection! Surely not from just one download? If so, it seems that RM had a really difficult time reconstructing the lineage data it got from FSFT. There’s a vestige of it still.
Now that I’ve got a grip on the current situation, I’d be curious to see what my colour-coding shows. Are there patterns that are different from the second-cousin couples I’ve come across so far? Are there lineage screwups that it does not reveal? And does my deduplication work effectively on this strange database?
Here’s my post that attempts to consolidate a statement of the problem, its analysis and workarounds to avoid it in new downloads from FamilySearch or to cure it in previous and new downloads within RootsMagic until such time as RM eliminates its bug:
Thank you for sharing your old, large FamilySearch download that you did with RM8 back in 2022 which, according to your recollection, took over 3 days and was incomplete because it maxed out at so many generations. You did a subsequent import to extend it.
I can confirm, as you have already suspected, that the RM database exhibits the duplicate-couples syndrome that we are seeing with RM11 downloads from FamilySearch, in spades. Therefore, we can conclude that every download of an ancestral branch of FamilySearch Family Tree from RM8 to RM11.5 is afflicted with duplicate-couples syndrome if the branch includes parentage involving two relatives of each other.
One couple, at the top of the tree, is duplicated 376 times with the same children who are espoused to each other 189 times. Right, that’s Adam and Eve and RM shows them with 189 or 190 parents each. From a SQLite query:
What this duplication suggests is that between the root person in the download and the end-of-line there may be 190 different direct lines, caused by inter-related parents. As RM reconstructs the tree it gets from FS, it traverses many of the same couples repeatedly, and, for whatever reason (that’s a bug), there are some that it does not recognise as being already in its FamilyTable and it creates duplicate records for the identical couple. No duplicate people are created; the same pair are repeatedly added to the Couples List.
While I’ve not attempted a download of this scale, I did do a much smaller one (16 gens) from a person identified in your big 2022 RM8 download as having parents who were half-2nd-cousins-once-removed, leading to the duplicate-couples|duplicate-parents syndrome in her line. My new download produced identical results as far as I checked up the line confirming that this bug that we’ve identified now existed then.
The good news is that the cleanup utility that I referenced in an earlier post eliminated all but the primary FamilyID for every unique couple in your file - no more duplicate spouses|duplicate parents|duplicate family-type events. It took about 13 minutes. Here are the basic stats:
Before
After
People
121,866
same
Families
165,126
57,662
Events
308,479
276,175
I can’t speak to other issues reported in this topic by @int13h in April. The author has noted “duplicate processing” which sounds related to the duplicate-couples|parents|events syndrome. The Marriage events issue might be related - not something I’ve noticed or been looking out for. You may pick up on some of those in people with which you are familiar.
@RootsMagicRootsMagicRootsMagicRootsMagic Support / Development
Mit diesen zusätzlichen und eindeutig auf einen Fehler von RM hinweisenden Informationen bitte ich RootsMagic um Stellungnahme, wie mit diesem Fehler umgegangen wird.
Bei der Gelegenheit kann der Fehler, dass nur in frischen Datenbank einigermaßen fehlerfrei importiert werden kann, beseitigt werden.
Es solle doch möchlich sein, dass man mehrfach Importe über FSID vornimmt, und dies ohne Duplikate und doppelte Link´s
Der Fortschritt könnte ja hier im Forum kundgetan werden.
RM11 ist diesbezüglich für mich erst dann wieder benutzbar, wenn dieser Fehler behoben ist.
