A Shock­ing Mis­take

Who Do You Think You Are? Magazine - - LETTERS -

Like C Glenn, I also had a shock on An­ces­try. I found that a per­son liv­ing in Amer­ica had posted a fam­ily tree stat­ing that my grand­fa­ther’s place of birth was Bre­con. I in­formed this per­son that this in­for­ma­tion was in­cor­rect via An­ces­try, as I had my grand­fa­ther’s birth cer­tifi­cate in my pos­ses­sion.

My grand­fa­ther was born in Port Tal­bot. He lived in the house he was born in un­til his

mar­riage to my grand­mother, and had no con­nec­tion at all with Bre­con. This per­son did not al­ter their find­ings, which made me very an­gry. So, af­ter An­ces­try stated there was noth­ing they could do to al­ter in­cor­rect in­for­ma­tion, I ended my sub­scrip­tion with them as I could not cope with this in­cor­rect fam­ily tree be­ing on pub­lic view on a daily ba­sis. El­iz­a­beth Kift, Swansea

Edi­tor Replies: Clearly the is­sue of in­cor­rect trees, and peo­ple un­will­ing to change them, con­tin­ues to an­noy many of you. MyHer­itage has a ‘con­sis­tency checker’ for its trees, or al­ter­na­tively Fam­i­lySearch just has one big shared tree so there can only be one ver­sion. Per­haps it’s time for An­ces­try to have a re­think about how it tack­les this prob­lem.

Newspapers in English

Newspapers from UK

© PressReader. All rights reserved.