I have I haver importes the ancestors of P6Y1-S8M into an fresh and empty database
Around 3500 people were read in.
Fatally, 370 people have double parents.
The parents are identical in both FSIDs. On FS, only one parent couple bid
Does it seem to be a mistake by RM11?
I know that under Couples, I can manually unleft the double marriages.
With 1090 sitations, I’m busy for days.
How can I eliminate the problem?
BG
It may be helpful to post example FSID’s for people that have double-parents, to avoid helpers having to navigate backwards through ancestors. Just a thought.
Just a note that this might only be 70 families… where every child of large families has doubled parents.
If you are comfortable in running a SQLite query, I can give you one to do it. It’s so trivial that it should be a simple feature to incorporate in the RM app. But that’s an enhancement request you could wait a long time for it to be fulfilled.
hallo Tom sehr gerne
I’ve posted two queries to the following page. one to identify the children and their duplicated parents, the second to delete the duplicate child-parent links. I hope that addresses your problem and that there are no other issues that have arisen in your FamilySearch imports.
das Schlimme ist ja dass in FS keine doppelten Eltern vorhanden sind; sie tauchen nur in RM11 auf. Ich habe dort eine Gruppen-Regel “doppelte Eltern” Siehe meinScreenshot
Duplicate posts on this. I mentioned on the other one to turn on RINs instead of the FSID. Then you can determine if you have duplicate people or duplicate links.
danke
wo soll ich die RINS aktivieren?
ich habe aber offensichtlich 1070 doppelte links
Wie kann das überhaupt passieren?
Ein Fehler in RM11 !!!
danke Tom
das werde ich machen
besser wäre es, wenn dieser Fehler in RM gar nicht auftreten würde 
Renee makes a good point. The RootsMagic RIN is guaranteed to be unique but it’s possible the FamilySearchID might get duplicated. To turn on the RIN to display with the name:
ok nun sehe ich statt der FSDI die RIN, die jeweils identisch ist
übringens auch die Spouses sind doppelt bei identischen RIN / FSDI
sehr ärgerlich, dass RM dies nicht korrekt importieren kann 
This is hilarious. I just came across this exact issue in my file a couple hours ago, where a set of parents had double relationships between them and their children, and a couple of the children’s family’s had it as well. Yes, they were the same RM people with the same RIN and FSID. My gut tells me it was from a previous FS import just looking at the state of the people, but I couldn’t give you an exact before/after of how or when I did that.
What I have noticed is that if an FS import process runs into someone that’s already imported into RM, there seem to be 4 different possibilities of what happens:
Is this a new behavior? I’ve only been using RM for about 6 months but up until recently, I noticed that it seemed to always stop if it found a person that’s already imported. It’s nice when it creates the new relationship for me, not so much if it keeps going
Actually, since BOTH her Parents and Spouses are DOUBLE, my first guess is the possibility of two separate FS downloads of portions of this person’s trees.
I agree. @thburkhart click on the heading of the FSID column of the People list and look for duplicates. If there are, they most certainly have unique RINs and have been doubly imported. That means my SQL query will not fix that issue.
I’ve not quite got my head around this but I proceeded to create a new database file from a FamilySearch download of the default number of ancestors and descendants of P6Y1-S8M which was identified as @thburkhart 's download starting point in the first post in this topic. I got fewer people but it was enough to be able to replicate the screenshots he posted for Catharina Dieterich:
She appears only once in the People List but twice in the Couples List, corresponding to the duplicate Marriage events to Georg.
The double entry in the Couples List means that they have two FamilyIDs (two separate records in the FamilyTable). Therefore, there is a Marriage event for each of the two FamilyIDs and there is a record for her as a Child of each of the two Couples.
I checked the sorted People List and did a query of the FamilySearchTable table and confirmed that there are no duplicate fsIDs. The number of records in the latter corresponds to the number of people in the database (2493).
My sense of this outcome is not that there has been a second download from FamilySearch but that there is indeed a bug in RM11.5 or in the API or at the FS server, possibly related to the handling of Family events. The fact that the problem can be replicated by me means that Support can, too. @rzamor1
Meanwhile, to clean out these duplicate couple and child links and associated Family-type events is more complex than I had previously imagined and my earlier solution is indeed not going to help.
I wonder how long this has been going on, is it an issue with all FS downloads or only those that traverse certain parts of the one big tree…
Great approach to isolating the part of the schema affected!
ja genau es war nur ein erster download in eine frische Datenbank.
Wir sind uns also ziemlich sicher, dass ein Fehler von RM 11.5 vorliegt.
Ich denke, dass viele User das Problem gar nicht entdeckt haben, da sie die Gruppenregel
“more then 1 parents”
gar nicht kennen, angelegt und ausgeführt haben haben .
doppelte Elterpaare können per se gar nicht vorkommen; es sei denn, es handelt sich um Adoptionen etc.
@razmor1 RM sollte dem nachstellbaren Fehler auf den Grund gehen und beseitigen.
das Verhalten von RM ist schlicht fehlerhaft..
Die Gefahr, dass mehrfache Verlinkungen entstehen ist zu groß.
Das Verhalten von RM, bereits bestehende FSIDs zu ignorieren ist prinzpiell ok.
Nicht aber, dass Verlinkungen dupliziert werden.
Wie ich nun verifizieren konnte (und andere das ebenfalls nachstellen konnten), passiert dies selbst bei frisch angelegten Datenbanken
Ich hoffe, dass der Fehler bald behoben wird
I do not know how the API through which RM interacts with FSFT actually works. For a download, does RM simply tell FSFT the starting person and the number of generations of ancestors and/or descendants, just as we enter them into the form? If so, then FS traverses the tree and transmits each person’s data and linkages to RM in bulk. If so, it’s possible that there is a problem on the FS side that RM is faithfully reproducing.
It’s also possible (and from the download progress reporting very likely) that RM asks for each individual’s data sequentially through the tree following the linkages it receives for spouses and parents. That leaves open the question whether FS is sending some duplicate linkages or RM is mistakenly adding them.
Whatever the cause, the result is a problem for end users. I’m making progress on a set of SQLite queries to identify and fix the duplicate couples, child-parent relationships and duplicate couple-type events. One wrinkle that I’ve just found is that there can be children of the duplicate couple that are not linked to the primary couple (smallest FamilyID). I want to check if the opposite is also true and whether all of the children for that couple shown on FamilySearch are accounted for by the union of the duplicate families and that there are no rogue children. The same needs to be done for couple events such as Marriage.
Even so, there is the fundamental question of how faithfully RM has reproduced a tiny chunk of the big, beautiful FSFT.
I’ve been exploring my downloaded database within RM11.5 and with SQLite queries and am seeing some shape of a pattern. It begins with an end-of-line ancestor but not all and ends around the 3rd or 4th generation. One of the end-of-line ancestors gets a duplicate spouse (duplicate couple in the family list). The 2nd generation gets duplicate parents and duplicate spouses. The 3rd generation gets only duplicate parents. But that’s a generalisation that is not always the case and is derived mainly by color-coding in RM and visual inspection. Here’s an example with an exception:
These were done with RM’s Advanced Search, Grouping and color coding in the order Orange, Yellow, Red as observations led to the end-of-line supposition. Then any Reds with no colour-coded descendants were manually cleared of colour. Thus, it’s not necessarily a perfect representation of everyone with either duplicate spouses or duplicate parents but it does suggest that the end-of-line is a demarcation between faithful reproduction of the ancestral lineage and the beginning of duplication of child-parent and spousal links and of family-type events. This is amplified by the Fan Chart (set to 11 generations=root person + 10gens):
Notable is that its only the paternal ancestry that exhibits the problem.
An exception to the generalisation that 3rd generation gets only duplicate parents is Hans Georg Kienzle-591 with also has duplicate spouses so he is orange. What’s curious here is that only 3 of his and Anna’s 5 children get duplicate parents (or are themselves duplicated by the same ChildParent linkage) while 2 do not.
Those two are both shown as 5th great-grandfather of the root so it would seem that pedigree collapse (multiple lines to the same end-of-line) might be a contributing factor to the problem.
