Sunday, November 13, 2022

Notating AncestryDNA Matches

Sunday morning is suppossed to be the day when I work on my DNA matches. 

Today it was my AncestryDNA matches who had the workout.  I began by filtering my match list by unviewed recent matches.


Today's matches were all in the predicted 4th-6th cousin range, with the highest cM totals being 27cM.

I went through each match by first opening up the match by clicking on the name.  Many had no public family trees or had trees that were not very complete.  I then selected the Shared Matches tab to see who we both shared DNA with.


Remember, AncestryDNA will only show you a match who shares 20cM of DNA with both you and the match.

Once I opened the shared matches between us, I scrolled down the match list to see what notes I may have already entered for the shared matches.  

If I notice a pattern of shared matches notes which might indicate descent from a particular line, I consider that a clue and add a note to the current match for further reference.  For example, if the shared matches indicate descent from the Crockett-Hedge lines, I would put a note in this new matches profile that indicates they have ICW (In Common With) matches on the Crockett-Hedge lines.



Until I do further research on this line, there's no guarantee that this match descends from my ancestral Crockett-Hedge line, but at least I have a clue where to start.

When AncestryDNA predicts a Common Ancestor between us, I indicate that by notating that we have a Predicted MRCA (Most Recent Common Ancestor) and indicate the ancestral couple.  Later, I can work the match filters by Common Ancestors and verify the path of descent.  When I verify the descent, I indicate the Relationship (ie. 2C1R for 2nd Cousin Once Removed) and add each generation in the notes down to the match.



On those occassion where AncestryDNA is telling me that the match and I descend from a couple in my ThruLines that has not been verified yet, I simply note that match as "Hold for further review".  There are a few ThruLines predicted for me that are very speculative.

Today, I had a couple of matches that appeared with shared matches that I had no notes indicating any identified relationships.  Those I simply marked as "Hold for further review".

I've used this method to weed through the matches in a fairly quick fashion.

Saturday, November 12, 2022

Multi-generational Birthday Photo

LeMaster family, Evansville, Indiana, 5 Nov 2022


A week ago, I was able to spend my birthday in a manner that I don't believe has ever happened - with not only my daughter and grandchildren, but with my parents as well.  As we gathered for a breakfast in Evansville, I was able to convince the waitress to capture the moment and create a memory - a four-generation photo.

Likely it has been twenty years since my daughter and I have been together on my birthday.  The fact that we were able to meet on the actual day and have all of us together makes the family historian in me smile.  Bonus for me was to see my daughter on her birthday weekend, as her birthday is two days after mine.  I enjoy a lot of mileage out of the corny 'dad joke' that she has been my favorite present.

We were able to spend some time together, enjoy a meal, spend some time shopping and hearing all about school with the grandkids before returning home.

I've always been intrigued by multi-generation photos and now I have a pretty good one to capture a moment in time when we were all together.
 

Tuesday, May 10, 2022

Locality Guide Planning

Writing out locality guides as an aid for future research projects has been another project goal for my genealogy research this year.  Using a locality guide to document where a particular record set exists not only helps keep you on track but also can point to potential new sources.

Excellent resources for building a locality guide can be found at FamilyLocket or GenealogyPants.  

I started out by taking my pedigree chart and making a Google sheet of my surnames, their location (county/state), year settled, any notes and an indicator of whether or not I'd created a guide.  My paternal LeMaster line, for example, starts with me currently residing in Grant County since 2001.  Prior to that, my direct line had been in Madison County since 1968, was in Delaware County in 1967, and Jay County since 1854.  My maternal Wright line has been in Madison County since 1867. Anywhere it was possible to have created genealogical records should have a research guide.  

My Indiana roots go back quite a ways, particularly on the maternal side, but as I chart out these localities that I can use for later research, it didn't take long to list out places in Ohio, Virginia, New Jersey, etc.  The great thing about the locality guides is by understanding the history of the local area you can get a better feel for where your ancestors lived and what records they might have created.

Even those counties where there was not much family activity will have locality guides because eventually they might come in handy when a new branch is discovered or when I've helping someone else out research a particular area.

I'm modifying the templates and suggestions used by others to make the locality guides relevant.  Including maps of the townships and neighboring counties has been helpful in getting a sense of how the area was settled. Documenting the hours and locations of the libraries and archives will make my future research trip planning easier and not such a 'shotgun' approach.

Noting any record loss that occurred in the county will be quite helpful in understanding limitations on research in those counties.