Family Tree Two Generations Repeated ad infinitum
Here's an odd family tree. https://www.familysearch.org/tree/pedigree/landscape/9MPD-78T
Thomas Smedley 1796-1796 and his father Thomas Smedley 1759-1836.
His father Thomas Smedley 1796-1796 and his father Thomas Smedley 1759-1836.
His father Thomas Smedley 1796-1796 and his father Thomas Smedley 1759-1836.
His father Thomas Smedley 1796-1796 and his father Thomas Smedley 1759-1836.
I followed this chart back 20 generations with the same pattern. Does it go on forever?
Best Answer
-
I agree with A van H: mistaking the "direction" of the tree is a relatively common error, causing people to add a parent when they want to add a child, or vice versa, and resulting in this kind of recursive relationship that causes an endless loop in the charts.
There already is a check that prevents a person being entered as his or her own parent or child; I can't imagine that another generation of checking would be particularly difficult, even if should result only in a warning rather than a hard "no" (because of the unlikely but not impossible scenario of a later marriage making a parent into a [step-]child of his or her own offspring).
0
Answers
-
It does continue infinitely, as the elder Thomas is both the father and the son of the younger Thomas.
I have fixed this by removing one of the relationships. I hope it is now correct.
0 -
Robert
I am just another 'lowly' User/Patron ...
Just in passing ...
IF, you have a 'look' at the "Pedigree", the "Image", that you attached; THEN, you will notice the "Data Problem" [ie. 'Red' "Exclamation Marks"], of ,"Reoccurring Person"; and, "Looping Pedigree".
Plus ...
IF, you "look' at the individual/person, Thomas SMEDLEY ( KZGS-X5L ), who is reported, as being, an Infant, who Died in the SAME Month, that he was Born, you will notice the following DISCREPANCES:
▬ "Data Problems" = Child Born before Father. The child's birth year is listed before the father's birth year.
▬ A Spouse has been added, with the "Event", left "Blank"
▬ His OWN actual Father added; as, his Child, with the Spouse
And ...
Apart from the matter, of a Spouse; being added, to a Child, who Died; as, an Infant ...
The "Patent-Child" Relationship, of having his OWN actual Father; as, his Child, is the REASON, for the problem/issue, of the "Infinite Loop" ...
Both, those problems/matters need to be addressed/fixed.
Good Luck.
I hope, that this may help/assist, somewhat.
Brett
0 -
Isn't the problem in the code that generated the infinite regress?
0 -
Robert
Just in passing ...
Short Answer: 'No', NOT directly ...
The Problem/Issue, in this instance, lies, with the "Patent-Child" Relationship, of having his OWN actual Father; as, his Child, that is the REASON, for the problem/issue, of the "Infinite Loop", that can be addressed/fixed ...
The "Infinite Loop", is just a byproduct, of the INCORRECT (and, the IMPOSSIBLE) "Patent-Child" Relationship ...
Whereas ...
As to whether, the "System", can be "Coded", to prevent a Parent, from being recorded/associated; as, a Child, of his own Child, most possibly, it CAN; but, the NEED, to spend valuable time, coding for such, is NOT necessary.
As, the "System", ALREADY clearly indicates, that the are a number of "Data Problems", that CAN be rectified.
[ Which, would rectify the situation ... ]
Please be, aware; and, advised, that ...
There are MANY "Priorities", in the "Family Tree" Part (and, the OTHER Parts) of 'FamilySearch'; and, there is LIMITED "Resources" (eg. "Funds") available to 'FamilySearch'.
"FamilySearch', was created; and, is maintained, by the Church ...
'FamilySearch', is FREE to ALL ...
'FamilySearch', is NOT, a "Commercial" Website (ie. NO, Payment; or, Subscription; or, Fee, is required) ...
Just my thoughts.
Brett
ps: All, that needs to happen, is to address/fix, the INCORRECT (and, the IMPOSSIBLE) "Patent-Child" Relationship ...
..... Oh, and, of course, "Removing" the Spouse ...
..... [ It is as SIMPLE; as, that ... ]
.
0 -
With all due respect to FamilySearch, I think they should not permit users to add a parent of a profile if the parent is also a child of the profile. It's relatively simple from a coding perspective to iterate through the profile's children, and stop and return a warning to the user if any of them match the person being added as a parent. To be clear, I'm talking about instances where the parent being added is an existing FSFT profile, so you'd only need to check the IDs. I'm not suggesting the system should check that the parents and children could be the same person in a similiar manner as to how potential duplicates are flagged.
1 -
All
FYI
Just in passing ..
I agree, that the "Coding", is possible ...
I just DO NOT, want 'FamilySearch', to spend, its LIMITED "Resources", on such a MINOR problem/issue.
Especially, one, that can be EASILY addressed/fixed, by Users/Patrons.
Plus, due to ALL the OTHER, more IMPORTANT matters, that need either, implementing; or, addressing/fixing.
Simple as that ...
Brett
1
