Incorrect designation of paternal grandparent when mother's parentage is undefined
Merged a mother from a baptism where the mother had the married surname and the tree already has the maiden surname.
As usual an entry is created for the mother on the child's page with the same ID as the mother who is married (shown above this new entry), and the child from this entry, who has a different ID. No father is given (yet). This child already has an entry with a different ID
Merging the child (by ID) is Not Recommended because of a high degree of inconsistency.
The inconsistencies include " The paternal grandfathers' first names are different." but this is untrue. The mother's father is being confused here with the father's.
Comments
-
I have left this in place for review at: https://www.familysearch.org/en/tree/person/merge/verify/MMTH-7BF/MB7V-1TC
1 -
The merge is based on this record: https://www.familysearch.org/ark:/61903/1:1:NKR3-V6X?lang=en. It contains the mother but not the father (although the underlying image, obtained from other sources) has both mother and father.
The entry is from a well-researched family. I am not in doubt about the accuracy of the merge itself.
0 -
Considering how many women have been entered with a married name in the World Tree, it's really important for the merge function to recognize they may be the same as entries with a maiden name!
0 -
Yes, that's certainly true. In this particular case, however, it seems to be an error in the algorithm.
" The paternal grandfathers' first names are different." was stated as reason but is untrue.
It seems that in this case the mother's father is being confused with the father's father.
(Or I'm missing something here.)
0 -
@FrankLittle Thanks for letting us know about this bug. We believe we have this fixed now. Please let us know if you see anything else odd.
Thanks again!1 -
My thanks.
0