Ancestry Thrulines connects to the aunt of same name

[Biggles50]

When I look at any Thruline I always start at the top.

Evaluate is the key, simply do not accept it as correct, I accept it as Not Proven and then I look at how the person has been included.

I click on Evaluate then look at the top tree from which the Ancestry algorithm has determined the relationship.

Those presented are in a pecking order determined by what supporting information they have in their tree.

In many cases the parents of the person are different from what is in our own tree.

I then look at the next one down and evaluate them.

In this case the dates look straight off wrong, to large a number of years separate them.

I then go back to the person in our tree who is the suggested MRCA and undertake another look to see if they have had more children than I have included in our tree.

It is a bit like X-Files, trust no-one!

[alan o]

Alas I too find so many of the tree suggestions are copied from others with no checks so errors perpetuate.  I check every suggestion with the primary source and refuse to accept any one else's tree at face value.  However in this case when there are over a dozen DNA links to Portland ancestors who Ancestry DNA suggests is Scottish rather than a Dorsetman, I suspect it is the Ancestry DNA region suggestion, rather than the trees that is wrong. 

There is always the possibility of illegitimacy or an affair outside marriage which could explain an unexpected regional result but as the Thru lines go back several generations before my great grandfather, that explanation does not hold water.