This is the first of two posts on Ancestry‘s ThruLines regarding an issue I
have had with the new feature.
Access to ThruLines™ Beta is available to customers without an Ancestry subscription for a limited time.
Unfortunately, hundreds of user trees on Ancestry cannot be taken into account when building ThruLines. The Legal Genealogist went ballistic last Saturday and wrote How do we know? It’s an excellent post with an example of a user tree which cannot be taken seriously. Judy G. Russell recognized the errors in the tree but can a computer program do the same? I think not.
This is not meant to provoke negative comments concerning Ancestry and the features offered by them. This is about giving feedback concerning a known problem in hopes of getting positive results.
Sunday, April 7, 2019
I have given feedback several times before [concerning the reason I am not satisfied with ThruLines] and will try to be more detailed as there is a bug in the system which has not been fixed.
I realize, at this time, ThruLines is a free tool on AncestryDNA. However, your long-time customers’ experience in family history research should be taken into account. We can work together to get this fixed.
The problem is a known bug in the system as other users have complained about it on social media. Some users who gave feedback say their ThruLines were “fixed” within days. I do not believe Ancestry has taken the step to go into one user’s ThruLines to fix this bug. I strongly believe it was a coincidence the users’ ThruLines were corrected after feedback. It is more likely another user’s tree, which was being used to build the connection between the ancestor and the match, had been corrected and this resolved the issue.
This is the issue I have with ThruLines’ “step bug”
I am seeing a step-parent as the parent in the ThruLines. The information is correct in my tree. No other tree is being used to create this ThruLines ancestor. Along with this step-parent, I am seeing all of her ancestors, unrelated to my line, as my ancestors in ThruLines. Not as POTENTIAL ancestors with a dotted borders – they are being shown as ANCESTORS.
- The ancestor who is showing up incorrectly in ThruLines is:
- The pedigree of the incorrect person in my tree:
I’ve added images to her ancestors showing they are NOT the ancestors of the home person and/or test person. [This is so that I can quickly recognize them on ThruLines.]
- This is her husband, my 2nd great-grandfather, in my tree. His information is correct and includes his two wives and their respective children:
- This is the pedigree of his first wife, my 2nd great-grandmother, who along with all of her ancestors are NOT showing up in my Thrulines. There are many DNA matches for people who descend from her PETERS, LIVELY, PROFFITT, and COCKRAM lines, on the match list, but they are being ignored by ThruLines.
I want to stress that ONLY entries in my tree are being used for this (incorrect) ThruLines ancestor. No other user tree is being used to make this connection between the half-cousin matches whose relationship is incorrectly calculated to full cousins.
I understand the idea of ThruLines and believe it could be a powerful tool. One problem will always be the hundreds of trees which are incorrect due to sloppy research, i.e. accepting hints without looking at dates, places, names, etc.
However, in this case, the tree being used is correct and ThruLines is overriding my information and picking the wrong person in the tree. I have no experience in programming. I can only tell you where I am seeing the bug. I’m fully aware of the fact that detecting the source of the bug may be more difficult.
Thank you for your time. In hopes of a quick resolution to this problem,
I wrote the above last Sunday but didn’t want to post it on my blog without giving Ancestry had a bit more time to fix the issue. This was the first time I included links to the specific areas where the “bug” was detected. Will this kind of feedback help resolve the issue I have with Ancestry‘s ThruLines?
Don’t miss part two tomorrow.
© 2019, copyright Cathy Meder-Dempsey. All rights reserved.