Hints

Do you use the hinting system found on some of the genealogy websites? Or, are you one that only searches for specific information?

When I first started researching my family history, my process was centered around locating specific information. In reality, this research involved locating specific types of records and then using those records to search for my famiily.

Today, I am spoiled. Even though I will search for a particular set of records or county histories, I spend most of my research time following those hints. Since I primarily use Ancestry, those leaf hints often take me to obvious sources such as census records, Find a Grave memorials or vital records. Sometimes, they lead me to a record that I wouldn’t have thought to research.

That is the case with a hint for my great grandmother, Josie Winifred Hammond Crawford. I had already done quite a bit of research on Josie. Thus, when I saw a new hint, I thought it would be to another Ancestry member tree. Instead, I was surprised to find the hint leading to an obituary.

Since I live in Kansas, I have access to a wonderful newspaper collection at the Kansas State Historical Society. Thus, I had already found my great grandmother’s obituary in the Dodge City Daily Globe. This find was in my early days of research, when I transcribed portions of the obituary and took notes on the other parts.

Even though many of the Dodge City newspapers have been digitized, the 1954 issues have yet to be digitized. Thus, I was surprised to find that the Ancestry hint led to a copy of Josie’s obituary. This obituary was published in The Wichita Eagle (Wichita, Kansas) on 28 Sep 1954.

Pioneer of Kansas Dies at Dodge City

(Special to the Eagle)

Dodge City, Kan. Sept. 27 – Mrs. Josie W. Crawford, 79, widely known resident for many years here, died Monday morning in Trinity hosptial where she had been a patient briefly for treatment. She had been active until her final illness.

Born Feb. 9, 1875 in Know County, Ill., she came with her parents, Mr. and Mrs. Richmond F. Hammond to Pratt County. Two years later the family moved to a farm in Ford County southwest of Dodge City and later moved to Dodge city.

Miss Hammond was married to Judson F. Crawford Dec. 24, 1890. Mr. and Mrs. Crawford celebrated their golden wedding anniversary in 1940. Mr. Crawford died in February , 1949.

Mrs. Crawford had been active in Methodist work since girlhood and received her 50 year pin several years ago. Among her many public services Mrs. Crawford helped organize and was an active member of the East Side Bible Class organized in 1917 and still active.

Final rites are slated for w p.m. Wednesday in the First Methodist Church here with the Rev. Alvin W. Murray officiating. Burial will be in Maple Grove Cemetery here.

“Pioneer of Kansas Dies at Dodge City,” The Wichita Eagle (Wichita, Kansas), 28 September 1954, page 11; digital image, Newspapers.com (www.newspapers.com : viewed online 5 September 2021).

Without the Ancestry hinting system, I doubt I would have found this particular obituary for my great grandmother. Thus, I will continue to work thru these hints.

Panic

(Note: This was written on Thursday, August 5th – the morning after my panic.)

Do you ever read about some software update or change on an Internet site and think I need to do something NOW? Having been a building technology coordinator for over 20 years, implementing software updates sometimes required an immediate reaction. Thus, when I hear about a bug fix or a major change in an often used website, I tend to respond immediately.

On Wednesday of this week, there was a blog post written about a change in Ancestry’s terms and agreements. The post, One Big Change at Ancestry, by Judy Russell captured my attention. And I reacted – or looking back I panicked.

My thoughts were along the lines of

Ancestry is going to sell my pictures. I don’t want Ancestry to sell my pictures.

So, I started looking at how to take down my pictures. I don’t know why I was so concerned. I have had a genealogy website for years. And my genealogy work, including images, has been out there for others to see and use. I would guess that some of the family photos have been so widely spread that even though I have the originals in my possession, I probably can’t claim ownership. Because I shared them freely, they now belong to the greater family.

But, I panicked.

And I had over 670 screens of images in my media gallery on Ancestry. With 24 images on a screen, that is over 16,080 images.. Many of those images are of census records and other Ancestry sources. Buried in that multitude of images are the family photos. So in my panic, I started scrolling thru and deleting the photos and stories.

Knowing that there was no way I was going to be able to go thru 670 screens of images, I started looking for the ‘easy’ button to remove those images. And the only ‘easy’ way to delete the images is to take down the tree and put up a new one without the images.

Now, I knew I didn’t want to mess with my tree. I knew I didn’t want to mess with my tree!

  • My tree is linked to 4 DNA tests and I didn’t want to loose those links
  • My tree is linked to my RootsMagic file via TreeShare
  • I knew that a new tree on Ancestry is virtually invisible to other users until it is indexed. Indexing trees does not happen very often.
  • I like getting the light bulb hints in RootsMagic that are only possible because my RootsMagic file is linked to my Ancestry tree.

I knew all of this and I still panicked.

  • I uploaded a new gedcom file without images to Ancestry.
  • I connected that new file to my DNA kits.
  • I tried to delete my original tree. Fortunately, Ancestry’s slow response saved me!
  • I even disconnected my RootsMagic file from Ancestry.

Then, I realized that those light bulb hints in RootsMagic were gone. And, what I thought at the time, the only way to get those light bulb hints back was to create a new tree by using RootsMagic to upload my file to Ancestry.

I didn’t like my options. And I totally regretted my panic!

Then, out of curiosity, I wondered whether I could restore a backup to my RootsMagic file and restore the RootsMagic connection to my original tree. So I dug in my folder for backups to RootsMagic 7 for the most recent file and restored it.

AND the light bulbs were back!

Since I am in the habit of backing up RootsMagic several times a day – with unique file names, I didn’t loose much. This is especially true since I have been spending most of my time in the preview version of RM8. Restoring the backup file undid most of my panicked reaction. I was even able to restore my RM8 file and get it connected to my Ancestry tree.

There were a couple of voices of reason out there that I did not read until after my panic. The first one I read was a Facebook post from Michael John Neill.

The second voice of reason was from Randy Seaver. His post, Ancestry.com and Your Ancestry Member Tree, provides a good perspective on the issue.

As I was deleting images last night, I found that I had the exact same image of an individual in my media gallery multiple times. It made me wonder whether deleting the images would help Ancestry reduce their server load.

Hopefully, I have learned my lesson from this panic. Hopefully, the next time, I will sit on an issue for 24 hours before proceeding.

I am VERY thankful that I had recent backup files for both RootsMagic 7 and RootsMagic 8.

I am VERY thankful that my backup file restored my link between RootsMagic and Ancestry!

Making Connections

#CousinBait #52Ancestors

I know I’m going to date myself, but I remember the joy of finding Everton’s Genealogical Helper in our mailbox. I would pour through each issue looking for an ad that might connect me with a genealogical cousin. Finding such an ad would cause me to compose a letter with a pedigree chart or family group sheet attached and send it off with a SASE (Self Addressed Stamped Envelope). I would then wait for a reply. Sometimes, I would be the person posting such an ad. Again I would anxiously await any replies to my ad. [See article: Pre-Internet Cousin Bait}

Thru time, mailing lists, surname lists and message boards replaced the ads in the Helper. Even though those resources may still exist, I rarely use them. Browsing Anestry’s message boards and seeing fewer and fewer messages posted and many with no replies, it is obvious that others are not using this resource either.

So, what is being done to connect with cousins. My husband has successfully used Facebook groups for his ancestors to connect with living cousins. Even though I have befriended a lot of cousins on FB, I have not had the success that my husband has had. That is likely due to the fact that he is very active in his groups and tends to ignore anything and everything else on Facebook while I’m not very active in my family groups.

Instead of Facebook, I’ve been concentrating on this blog. I’ve shared photos, ancestral biographies, lists of descendants, sources and analysis of local records in my various blog posts.

In terms of sharing my genealogical data, I concentrate on my Ancestry tree, Heartland Genealogy. I am also adding sources and memories to the FamilySearch tree. Since I’m using RootsMagic 7 for my genealogical research, I also have a free site thru RootsMagic for my data.

Another way in which I try to connect with cousins is thru DNA. My Ancestry tree is connected to the four DNA tests I manage on Ancestry. To help make connections with DNA cousins, I am researching descendants of my 2nd and 3rd great grandparents. By doing this research, I’m hoping to provide a connection between my tree and a DNA match’s tree.

In order to connect with cousins who may have tested their DNA on a different site, I have transferred my Ancestry DNA to GedMatch, MyHeritage and FamilyTree DNA. Thanks to the use of GedCom, I have transferred my genealogical data to these sites. Thus, I have a tree connected to DNA on MyHeritage, GedMatch, and FamilyTreeDNA.

Thanks to my brother agreeing to do a yDNA test, his results are part of the CRAWFORD yDNA project. This project has a fantastic administrator and an associated Facebook group. I am also participating in the GedMatch project for Germanna descendants. Both of these projects are helping me connect to DNA cousins with ties back to the 1700s.

So cousin, if you find a connection to your research in my research posted on my tree or in my blog or via my DNA results, please contact me. I can be friended on Facebook as Marcia Crawford Philbrick, messaged in Ancestry or reached via email using mcphilbrick at gmail dot com as my address.

DNA Stats

Do you track your DNA statistics? At times, I’ve tried keeping track of these statistics but got frustrated when the way the information was reported would change. Thus, it became difficult to compare current data with previous data.

After seeing Randy Seaver’s post, Randy’s Autosomal DNA Test and Analysis Summary – 29 Dec 2020, I decided to compile my own DNA statistics.

ANCESTRY DNA

MeBrother 1Brother 2Parent
Total Matches110,981125,144115,18274,618
Immediate Family3333
1st Cousins (As defined by Ancestry)1114
2nd Cousins (as defined by Ancestry)4839
3rd cousins3340936
4th cousin sharing 64 cM or more1113713
Close Matches – at least 20 cM3701464139142709
Distant Matches 6-20 cM107,280120,503111,26871.909
Distant Relative group (6-8 cM)67072743746840544670

When it comes to ‘common ancestors,’ I couldn’t find the number reported by Ancestry. Since I don’t want to have to try and count them, I’m going to guesstimate. I recently posted my ThruLines Summary thru my 4th great grandparents. For my ‘guesstimate,’ I’m going to use 1/2 of the total number of ThruLines thru my 4th great grandparents. This isn’t an accurate calculation.

MeBrother 1Brother 2parent
1/2 ThruLines thru 4th Great Grandparents10651013926787

MY HERITAGE

MeBrother 1Brother 2
Matches14,72510,74610,281
Theory of Relativity283031
Smart Matches354

GEDMATCH

MeBrother 1Brother 2Parent
64 cM or closer12131117
34 cM or more959170127

FAMILY TREE DNA

  • Total autosomal matches to my DNA – 6257
  • Total autosomal matches to brother 1’s DNA – 1677

FAMILY TREE DNA – yDNA results for brother

  • yDNA matches at 111 markers with genetic distance of 4 – 1
  • yDNA matches at 111 markers with genetic distance of 6 – 8
  • yDNA matches at 111 markers with genetic distance of 7 – 4
  • yDNA matches at 111 markers with genetic distance of 8 – 6
  • yDNA matches at 111 markers with genetic distance of 9 – 3
  • yDNA matches at 111 markers with genetic distance of 10 – 1
  • Big Y R-^88686 haplogroup matches – 3

With over 100,000 matches for one DNA test, there is NO WAY I’m going to be able to document all of those matchers. However, I’m using the ThruLines matches to help support my paper research. Thus, all of those matches are important to me.

ThruLines Summary

It’s approaching that time of year when on reflects on the past year and looks forward to the next. Like most people, I’m ready for this pandemic to be over. However, I do like to look back on my genealogy to see how much progress I’ve made. In order to do that, I have to collect data for future comparison.

Thus, I’m going to collect data on my Ancestry DNA Thrulines. I am MC, my siblings are DC and TC and my parent is RC.

Great-Grandparents

AncestorMCDCTCRC
Judson Crawford888
Josie Hammond888
Hiram Currey333
Winnie Hutchinson333
Edward Briles8888
Frances Ricketts8888
Charles Mentzer9999
Nettie Wells9999

2nd Great Grandparents

AncestorMCDCTCRC
Washington Crawford111211
Mary Foster111211
Richmond Hammond101010
Sarah Ralston999
Hiram Currey878
Angelina Burke878
Albert Hutchinson252222
Julia Harding252222
Noah Briles10101010
Sarah Thompson10101010
James Ricketts9999
Rachel Christy9999
George Mentzer14141314
Emeline Minnick14141314
Thurston Wells16141516
Salome Crandall13131213

3rd Great Grandparents

AncestorMCDCTCRC
Nelson Crawford121511
Martha Smith121511
Zebulon Foster151919
Caroline Ostrander151919
Horatio Hammond202827
Louisa Fisk202827
James Ralston303430
Nancy McCormick293329
Hiram Currey17718
Rachel Harris17718
Henry Burke878
Elizabeth Bland878
Aaron Hutchinson242121
Sarah Merry252222
William Harding514056
Elizabeth Fowler493753
Alexander Briles18191721
Sarah Rush19212023
William Thompson10131112
Polly Evans10131112
John Ricketts11111012
Orilda Reed11111012
Samuel Christy16161420
Lyda Gallmore12141114
Phillip Mentzer21262225
Orinda Miles3333
John Minnick16151417
Elizabeth Jones16151417
Ozias Wells26212333
Mary Kennedy26212333
Lewis Crandall16161216
Almira Nafus16161216

4th Great Grandparents

AncestorMCDCTCRC
James Crawford252418
Sarah Smith272921
_____Smith121511
Hannah _____121511
Richard Foster434845
Rachel Browning434845
Edward Ostrander303125
Margaret _____303125
Jason Hammond273438
Rachel Hale273438
Jonathan Fisk252627
Mary Arnold13712
David Ralston464739
Hannah Barr464739
James McCormick444
Sarah Hall283126
Hiram Currey211425
Sarah Reagan211328
Peter Harris16617
Rachel VanArsdale16617
John Burk454233
Elizabeth Graves514737
Eli Bland9129
Sarah Anderson9129
Aaron Hutchinson211919
Hannah Nettleton211919
Whiting Merry222020
Elizabeth Peabody222020
William Harding664876
Elizabeth Flewelling664776
Thomas Fowler453750
_____ _____453448
John Briles15012057200
Nancy Beckerdite14712057196
Noah Rush8210284112
Sarah Clark8210184111
John Thompson13222539
Sarah Iglehart13222539
James Evans14202632
Sarah Garret14202430
Edward Ricketts109810
Sarah Story109810
John Reed39272442
Mary Buckles59473766
Ebenezer Christy29282941
Rachel _____29282941
Isom Gallimore70664697
Judith Bentley69664696
Phillip Mentzer18221821
Isabella Motes18221821
Oliver MIles24232226
Sarah Joslin24232228
_____ Minick5345
Esther Schiedel18151516
Henry Jones17162124
Catherine Bovey17162124
Green Wells33292737
Abigail White33292737
John Kennedy26242335
Anna _____75710
Hampton Crandall34343234
Freelove Butler34343234
William Nafus30301432
Salome Carpenter28271328

Alternate Names

Have you learned thru the years that spelling matters when doing an Internet search? On the other hand, have you found that spelling of names varies — and thus a specific spelling doesn’t matter any more? That need to be able to search for various spellings of a name was behind the development of the Soundex code.

Soundex code was very valuable in pre-Internet days for locating census records. It can still be used today with searches of Ancestry’s databases. Unfortunately, this concept isn’t used when Ancestry’s computers compares the trees of people who have a DNA match to identify the common ancestor. Instead, the computer is looking for an exact match.

As I’ve started researching an ancestor that Ancestry identified as a potential match, I’m running into spelling issues.

This new ancestor is a revolutionary war veteran, Major Simon Van Arsdale. In addition to his revolutionary war service, Simon Van Arsdale was part of the Low Dutch Settlement that migrated to Kentucky.

The discovery of Simon Van Arsdale as a potential ancestor is opening up doors to other potential ancestors and a lot of interesting history. Unfortunately, the spelling of the Van Arsdale name is making it difficult to locate records and to identify DNA matches. So far, I’ve identified the following spellings for this surname:

  • VanArsdale
  • Van Arsdale
  • Van Arsdalen
  • Vanarsdall
  • Vannarsdall
  • Van Artsdalen
  • Van Osdol
  • Vanosdol

For the most part, clicking to also use Soundex when searching Ancestry databases will help me get around the many spellings of the name. However, that option isn’t available when working with DNA matches. I recently learned that I should use the ‘alternate name’ fact to add variations on the spelling of a name.

This morning as I was thinking about the need to add ‘alternate name’ facts for Simon Van Arsdale, I saw a Facebook post questioning why Ancestry’s computers can’t find common ancestors when both parties of a DNA match have large trees. I believe the same post also talked about how changing the spelling of a name (Fannie to Fanny) caused the number of matches on a ThruLines to drop. In the comments on the post was a suggestion to add an ‘alternate name’ fact for the different spelling of the name. (Unfortunately, I haven’t been able to find this post back. Thus, I can’t give credit to the parties who wrote the post and the comment.)

In thinking about this question as to why the computers aren’t finding the common ancestors, I realized that spelling of surnames and name variations could be a big issue with my tree. I have a lot of places in my tree where the name I have could be slightly different from the name another person might have in their tree. However, I have one surname where this could be a big issue: CURREY.

Over the years, I have found that when the name is spelled with the ‘e’, the record is usually for someone in my line. I have also found records using the CURRY spelling that are for individuals in my line. Thus, the name could be spelled CURREY or CURRY. Since I only have the CURREY spelling in my direct ancestral line, I’m going to experiment with adding CURRY as an alternate name to see what happens to my ThruLines.

Below are the number of ThruLines matches for each generation of my CURREY line:

  • Hiram Currey – Dodge City – 1866-1943 —– 3 matches
  • Hiram Currey – Leavenworth – 1835-1901 —– 7 matches
  • Hiram Currey – Peoria – 1787 – ? —– 16 matches
  • HIram Currey – Ohio –? – ? —– 22 matches
  • Thomas Currey — Ohio — ? – ? —– 16 matches

I will add the ‘CURRY’ alternate name for each ancestor and their children. Then I will re-check my numbers in a few days. Hopefully, I will see the number of matches increase!

Small cM DNA Matches

Do you remember having conversations with your parents similar to ‘Why can’t I? Everyone else is doing it.’ Well, that is how I sometimes feel when it comes to my DNA research strategy. In other words, I often haven’t had a specific strategy, but was following the ‘crowd’.

That was at least true when I submitted my spit to Ancestry to have an autosomal DNA test completed over 4 years ago. At the time, I didin’t know much about DNA but was hoping that it would help break down the numerous brick walls in my family tree.

It was only after getting my results back that I started learning about the perceived limitations of these results.

Since my tree was already complete thru 5 and 6 generations and mostly complete thru 7 generations, my hopes of using my Ancestry DNA results to prove a new ancestor were dashed.

Then came the summer of 2020 when Ancestry announced that it had plans to remove the 6 and 7 cM matches from our lists of matches. Since Ancestry had also recently announced that over 18 million people had had their DNA tested by Ancestry, I knew that these smaller matches were adding to the data load. Thus, I looked at this move for what it was – a cost saving measure.

That was until I looked at my own ThruLines data and realized that I had ‘brick wall shattering’ information in my ThruLInes that utilized quite a few of these smaller matches to build these connections.

Thus, I started working to tag these smaller matches — starting with those identified as having a common ancestor. In working thru these matches, I found matches to support my paper research identifying Rachel Harris, daughter of Peter Harris as my third great grandmother. These matches helped me identify Peter’s wife along with the parents of Peter Harris and his wife, Rachel Simonse VanArsdale. This discovery led me to three revolutionary war ancestors and a very rich family history going back to the 1600s.

Knowing that there had to be other ‘yet to be identified’ common ancestors lurking in this pool of 6-7 cM matches, I decided I was going to try and tag as many of these matches as I could. Roberta Estes provided some guidance on how to do this in her blog on July 16: Ancestry to Remove DNA Matches Soon – Preservation Strategies with Detailed Instructions. So, I started by searching these matches for some of my surnames and then tagging them. Since this was a slow labor intensive process, I knew that I wasn’t going to be able to save very many of these matches.

Then I saw a post by Roger Froysaa on the Facebook group, Ancestry DNA Matching where Roger shared a script that could automatically tag these 6 and 7 cM matches. Roger not only shared several versions of his script but also wrote a script to cause the list of matches to scroll to the bottom. These scripts worked — to a point. I would either get an ‘Aw Shucks’ your browser crashed OR a message from Ancestry that their backend servers were overtaxed. Charles Updike shared changes to the script, including a different script to scroll to the bottom.

This morning, I saw another post on the AncestryDNA Matching group about these scripts. This post was by Kay Simpkins where she shared a script written by Earl Haiks. I found the script in one of Kay’s comments on her post and copied/pasted it into Notepad.

After reading all of the comments on Kay’s post, I realized that I didn’t have to sort out the 6-7 cm matches, I just had to run the script. I renamed my ‘6-7 cM Matches’ group and called it ‘Distant Relatives’ so that I wouldn’t have to edit the script shared by Kay. I then ran it on my matches — and it was QUICK and I didn’t get any of those error messages. In about 4 hours early this morning, I was able to run this script on five tests. I still have one test to run the script on but am waiting until tonight when it should run faster than midday.

Below are the stats for these five kits:

SUCCESS AT LAST!

Now, I just have to continue researching ancestors / descendants on my tree so that Ancestry’s computing power can figure out the common ancestor for these distant matches.

None of this would have been possible if others had not been willing to share via a blog post or Facebook community. Thank you Roberta Estes, Roger Froysaa, Charles Updike, Kay Simpkins and Earl Haiks for your contributions to this conversation. Also a shout out to Jason Lee for creating and administering the AncestryDNA Matching Facebook group.

Help Needed!

As with many other genealogists, I’m struggling with the upcoming loss of small matches from my Ancestry DNA match list. I have no idea how many of these matches I have but I’m guessing it is in the thousands.

Since I will never have the time to work thru thousands upon thousands of matches to figure out how we connect, I’m hoping to use Ancestry’s computer technology to help me. Thus, I’m concentrating on my ThruLines matches, including the “potential ancestors”.

I have done a lot of descendancy research which I believe is helping Ancestry’s ThruLines technology connect me to DNA matches who have very small trees. Seeing the words ‘No Tree’ or ‘Unlinked Tree’ in my list of matches means I will scroll right past the match and will never take the time to figure out our relationship.

Thus, I need my over 100,000 matches to have a searchable tree attached to their DNA test(s).

PLEASE help me figure out our DNA connection by attaching a tree to your DNA results.

Completeness Part Two

Have you seen Ancestry’s recent news that they will be dropping smaller matches from our list of DNA matches? (Ancestry to Remove DNA Matches Soon) With over 100,000 matches on my list, I’m not sure I will miss most of those small matches.

However, I decided to look at my ThruLines and Common Ancestors matches to see what the impact might be. Since I have four DNA tests to manage, including my mother, I decided to start with the 5th great grandparent ThruLines. My goal is to add color coding dots and notes for ALL of the matches for each match listed on ThruLines.

As I’ve worked my way thru all of these 5th great grandparent ThruLines, I observed some matches with very small trees where the common ancestor was identified.

After finishing the 5th great grandparent ThruLines, I then looked at 6-7 cM matches who have an identified common ancestors. Going thru that list, I again observed quite a few small trees showing up as having a common ancestor.

Since I have done a lot of descendancy research, I’m guessing that all of that research is helping Ancestry’s computers to make these ‘common ancestor’ links between these small trees and my larger tree.

Unfortunately, there isn’t a magical report to ‘grade’ me on my research of descendants. However, seeing these DNA matches with small trees showing up with common ancestor connections is enough validation for me.

Thus, I will continue to work on my descendancy research — after I get done marking my 6-7 cM matches that appear to have a known connection.

For more information on how to do descendancy research, check out Crista Cowan’s video: What Is Descendancy Research.

ThruLines Error

Recently Jason Lee posted a Facebook poll asking whether readers agree or disagree with the statement, “All ThruLines errors are because of errors in trees.” As of today, 802 people agree with that statement, while I am in the minority of 120 people disagreeing.

The reason, I disagree with the statement is that the ThruLines for my 2nd great grandfather, James Crawford. This ThruLines suggests that William Monroe as a child of James Crawford based on a DNA match with a known 3rd cousin once removed.

Even though this match has a very small tree, she has enough in her tree that our trees should connect. Eugene Beggs, son of Walter Beggs and Ethel Anita Lighter is in both of our trees. My match’s tree includes Eugene Beggs’ father, Walter, but not his mother, Ethel Lighter.

Thus, our common ancestors are Washington Marion Crawford and his wife, Mary Foster. Not only is ThruLines suggesting an incorrect connection on the Crawford line but also on the Foster line. This time, it is suggesting Margaret E. Jordan as a daughter of Zebulon Foster.

In hopes of getting the algorithm to correct these ThruLines, I added this cousin to my tree several months ago. Unfortunately, I haven’t observed any change in the ThruLines. Not only do I have Eugene Beggs and his link to Washington Marion Crawford and Mary Foster in my tree, I have also researched these families and attached sources.

I keep hoping that the computer algorithm for ThruLines will discover this connection and show the correct way our lines connect.

Although I haven’t researched all of the suggested connections thru ThruLines, I haven’t found other errors. For the most part, I have been able to document the suggested connections. Because the ThruLines tool helps me see connections between myself and my DNA matches, I appreciate the information provided. However, I wish there was a way to report this ThruLines error to Ancestry. Unfortunately, I haven’t found such ability.