A quick note to all family finders. The new Thru Lines feature at Ancestry is definitely worth setting up (including tagging of known relatives who appear as dna matches). If one can add one or more family dna results to the mix then the process is even more powerful. And if Ancestry would allow raw tranfers from other labs the we'd really be getting somewhere. This feature harnesses the power of all those amazing Ancestry trees (the number and depth of Ancestry trees dwarf FTDNA abd 23 in this department) and enhances it with dna matching-- a sharp and straight arrow for the quiver.
--
Adam Cherson

I set up Thru Lines on Ancestry awhile back, but I must say I've been disappointed, as it has errors that apparently can't be corrected.

For example:  Thru Lines identifies my grandmother's paternal aunt as potentially my grandmother's maternal grandmother.  The error results in Thru Lines misidentifying subsequent ancestors.
The FAQs for Thru Lines state: "If a potential ancestor does not support what you know about your family's history, you may contact the family tree owner associated with that person to correct any errors or make changes." 

But the family tree owner doesn't even have my grandmother listed in her tree; there's nothing there to correct.  Moreover, the error is not based on a DNA match (although I DO match a descendant of my grandmother's paternal aunt... which isn't even reflected here!).  I wish there was a way I could click "Ignore" as I do with some of the hints Ancestry provides for people in my family tree.

Ellen


--
Ellen Morosoff Pemrick 
Saratoga County, NY

Researching WEISSMAN/VAYSMAN (Ostropol, Ukraine); MOROZ and ESTRIN/ESTERKIN (Shklov & Bykhov, Belarus); LESSER/LESZEROVITZ, MAIMAN, and BARNETT/BEINHART/BERNHART (Lithuania/Latvia); and ROSENSWEIG/ROSENZWEIG, KIRSCHEN, and SCHWARTZ (Botosani, Romania)

I have a similarly frustrating problem with this new "tool". Thru Lines identifies my aunt's granddaughter as my aunt! The granddaughter has the correct relationship in her tree so the blame for this error obviously lies with Ancestry!
--
Vivian Kahn, Santa Rosa, California
Researching families including:
BERKOVICS/BERKOWITZ/ROTH/GROSZ. Avas Ujvaros, Hungary/Orasu Nou, Romania
KAHAN/JOSIPOVITS/DUB, Sziget, Kabolacsarda, Nagyvarad, Hungary/Sighet, Ciarda, Oradea, Romania
KOHN/Zbegnyo/ Zbehnov, Tarnoka/Trnavka, Slovakia; Cleveland  LEFKOVITS/Kolbasa/Brezina, Slovakia
MOSKOVITS/Honkocz, Szobranc, Osztro, Kassa, Hungary/Chonkovce, Sobrance, Ostrov, Kosice, Slov., Nyiregyhaza, Hungary
ELOVITS/Hornya, Hungary/Horna, Slovakia
NEUMANN/Szeretva, Kereszt, Nagymihaly, Miskolc, Hung./Sobrance, Kristy, Stretavka, Michalovce, Slov. 
POLACSEK/Hunfalu, Hungary/Huncovce, Slovakia
SPITZ/Nikolsburg/Mikulov, Prosnitz/Prostejov, Moravia/Czech Republic; Kismarton/Eisenstadt, Hungary/Austria; Hunfalu,Hungary//Huncovce, Slovakia

I spoke with Ancestry about someone on my throughlines and who'd done their tree also, they put the wrong relation in their tree and so it made mine appear wrong when in fact I'm the decendant so I would know!... Ancestry told me to reach out to this person to let them know it wasn't correct. I think this needs to be changed by Ancestry, I know it's in small print somewhere that it may not be 100% much like our matches on there, but this can offend. 

Mandy Molava 
Researching mainly Krakow Russia Brest Slovakia 

These anecdotes show that no tool is perfect and any process is only as good as the input data. Still,  I hope none of these experiences prevent everyone from trying.
--
Adam Cherson

Sometimes it is accurate and other times not.  I was looking at it where it had a woman and her daughter with identical names and no data for the other side of my "match".  I did have success once at removing a completely erroneous match.  

--
Sarah L Meyer
Georgetown TX
ANK(I)ER, BIGOS, KARMELEK, PERLSTADT, STOKFISZ, SZPIL(T)BAUM, Poland
BIRGARDOVSKY, EDELBERG, HITE (CHAIT), PERCHIK Russia (southern Ukraine) and some Latvia or Lithuania
https://www.sarahsgenies.com