Genealogy Do-Over: Plateau

This series of posts are based on the Genealogy Do-Over Workbook by Thomas MacEntee. I highly recommend it. 🙂 I just want to say there are parts of this workbook that I am not posting about, so if you would like the full set of tasks, then visit Thomas’ page or purchase the workbook.

If you haven’t been able to tell by my lack of posts, I’ve hit a plateau in my Do-Over. It doesn’t have to do with a brain block, a brick wall, or lack of information. I have plenty to do, and I know exactly what I’m supposed to do next. I’ve even ordered some new records. For some reason, I’m just struggling to get moving on any of it. I’m unsure if it’s just a little bit of burnout, the holidays, or just an overall tiredness.

Current Status

Current Status

The screenshot above shows my public DNA tree at Ancestry.com. It’s the easiest way to show the progress I’ve made in my Genealogy Do-Over. As I move through my list, I delete or update people in the public tree. It’s quite obvious that I’m on the John Mays/Celia Slusher section of the tree. I have been uploading documents and pictures to all the trees that are public on any of the DNA websites.

This takes quite a bit of time. There are days that I only work with one record.

Are there any big changes that you’ve had to make?

Ohio Department of Health, Division of Vital Statistics, death certificate 639 (1927), Harmon Mays; digital image, FamilySearch (http://www.familysearch.org: accessed 5 Dec 2017).

Though it’s not a big change, I did change John Mays’ name from John Harmon Mays in my database to John Mays. This death certificate is the only official document I’ve found referring to this man as Harmon. The only other instance was the cemetery plot records. Notice that his son Harmon Mays is the informant on this record. That leaves the possibility of “operator error” when asked Full Name at the top of the document. For now, Harmon is just an alternate name in my database and no longer an accepted form of his name.

The second change was John’s birth date. Its unclear to me if it was my error at the time or if I just trusted the transcription. I believe I had this record in a paper copy before it was put online, so I think it was probably me. Most online trees even agree on the original date of 4 Sep 1872. However, upon reviewing this again, I do believe it is 24 Sep 1872. Which doesn’t seem like a huge deal, but it just goes to show I’m paying much closer attention to details now.

I hope everyone is enjoying their holiday seasons. I hope to have another DNA entry up in the new year!

DNA Matches – Notes Section

After my previous post, some of you may be wondering what goes into the Notes section of my Excel spreadsheet. This is actually the first time I’m writing down this process, so I’m hoping it makes sense to someone other than myself!

Step One

My DNA Matches – Step One

My first step is to take a visual look at my matches. The results you see above are my matches closer than 4th cousin. With my working knowledge of the family tree, I’m able to tell just by looking at these matches who 50% of them are. That’s including my father. I’ve obviously edited out the pictures and names of the matches to protect their privacy.

As you can see, most of my close matches aren’t sharing any kind of public tree. Except, of course, some of them are sharing unlinked trees. Right away, when I’m going through my fourth cousin matches, I will add a note if my third cousin shares that match. For example, if I share a match with my 2nd cousin then I put, Shared match with 2nd cousin. Using their member name in place of the relationship.

Step Two

My DNA Matches – Step Two

My next step is to go through each match and see who we both share a match with. The screenshot above shows that this 3rd cousin match is a match shared with my father and two other 3rd cousins. One of those third cousins is already on my known list. From that match alone, it narrows down where this match comes in significantly. Not only for the match who I am looking at but for the other unknown third cousin match.

For this match in her Note section would read, Shared match with ‘3rd cousin’ and ‘3rd cousin’. I don’t add that my father is a match because I already have a box for that in my excel sheet.

Step Three

My DNA Matches – Step Three

My next step shows how even an unlinked family tree can help determine which section of your family tree a match comes from. This third cousin match has a small family tree that’s not attached to their DNA results. That means I have no idea if the DNA results are for the home person on this family tree. I can’t know without asking. I’m not ready to ask yet because I’m still rebuilding my core family tree. The two surnames that are shown above (Theademan, Moyer) are very familiar to me though. My great-grandma was a Moyer. That means I’m comfortable making another change to my list.

Re-Visiting my List

Making Progress on my DNA Match list

Okay, so now I know where eight out of my ten matches are coming from. I used a different symbol to denote that while I think I know where the match comes from, I’m still not sure. This is still a clue to identifying someone in my 4th cousin match list. If any of these third cousins come up as a shared match, then it goes into my notes section.

The last two matches

My last two matches are the most difficult ones. The first one has a public tree, but nothing that looks familiar. The second match has a tree but it is private. The one thing going for me is that when I look at the shared matches for each one, the other is listed. That means all three of us match. That doesn’t mean we match at the same spot, but that we are all related to people in common somewhere.

Breaking the 4th cousin barrier

When looking at the matches, I realized not only did we have each other all in common. We all had a fourth cousin in common. That fourth cousin also has a public tree up. I recognized the Slusher name from this match. The funny thing about the Slushers is that I usually match with them as double cousins. There were 3 Mays siblings that married 3 Slusher siblings. That means we could all descend from different Mays/Slusher couples or the same one. One of us might not even be connecting through the Mays/Slusher mess but somewhere else. Without knowing those other two people, it’s difficult to say. As if DNA matches weren’t hard enough!

So now if I match with these third cousins and that particular fourth cousin, I add in the fourth cousin to my notes section. This gives me a starting point for my next level of analyzation. I sure am good at analyzing things to the point of exhaustion!

The Final List

My Final List of 2nd and 3rd cousins

Okay, the above screenshot shows my final list of 2nd and 3rd DNA cousin matches. The ‘i’ symbol on those last two matches shows that I just don’t have enough information on them. Now that I have a general idea where a lot of my matches come from, it doesn’t seem so overwhelming. That’s not the end though. There is one last thing I have in my Notes section.

What happens when there are no second or third cousin matches?

Yup. I have quite a few of those as well. There are many types of notes that aren’t using a cousin match.

  • Descendant of … : Usually, if they have a public tree that I see familiar names on.
  • Descended through: This one is if they are descended through a known sibling of my ancestors.
  • Only 1 shared match: There are 16 matches that only have one shared match.
  • Possible Surname connection: If I see a pattern or surnames that I’m familiar with.
  • DNA Circle: I only have a few DNA circles and they come and go depending on my cousin matches opening and closing their public trees. Though I feel like a lot of my sorting and organization is leading me to create my own DNA circles.
  • Unknown Connection: 213 of my cousin matches are still a mystery to me. I have 493 charted. That means about 43% of my matches still need more work. In the grand scheme of things, I think that’s a good start. That means I will probably be able to figure out over 50% of my matches without too much hassle.

Regret Nothing

  1. It is 9:24 PM on Thursday night and I am neck deep in Samuel Redfords.
  2. I deleted my Twitter account months ago because I never used it.
  3. I don’t want to bore my family with Genealogy stuff on my Facebook all the time.
  4. That means I have nowhere to post except for here.
  5. 3 Birth Certificates, multiple possibilities, and still no answers.
  6. I love this stuff.

Sucked into the DNA Trail

Here I am again, after another absence. This one was partially on purpose. Sometimes you just need a mental break from genealogy. It’s not a bad thing. Over the years, I’ve learned it helps me to focus better if I just walk away from it for a week or two. The rest of my break, I have been working on learning about DNA. Oh, man has that been a journey! I’m obviously still learning and probably will never fully understand.

During Amazon Prime Day this year, I purchased three 23andMe DNA tests. I had previously tested myself and my Dad on Ancestry. I thought since I had never used 23andMe before, I might want to go ahead and re-test my Dad to see the differences between the companies. In addition to testing my Dad, I also tested my mother and her brother.

Information Overload

The biggest thing I’ve gotten from DNA test results is information overload! Learning from my fellow genealogists, I know that the cure for information overload is learning and organization. The overload comes from not understanding what you are looking at. That means I have to learn more and I have to find a better way for my brain to process it. Okay, that’s definitely something I can do!

My Dad’s Ancestry DNA matches

The image above is the Excel spreadsheet that I made to wrangle my DNA matches. This is after I watched about 10 DNA webinars, and some of them I watched twice. The main problem I have found from a research standpoint with Ancestry DNA matches is you have to go into each tree and click on multiple things to see all the information. From a research perspective, that’s a lot of wasted clicks and time.

Before carpel tunnel sets in, I wanted to have a way of pinpointing a focus subject without having to click 3,987 times. The following are my headers and the reason.

The Explanations

  • Username: Ancestry uses its own messaging system for DNA matches, so I made sure to put down the username of all my matches. In the case of someone who has a manager of their DNA test, I put Username (managed by Username).
  • Predicted Relationship: This is the relationship that Ancestry thinks I share with the person. I have 473 4th Cousin or closer matches and my Dad has 223. That’s a lot. Not only is that a lot but there are hundreds of pages of more distant matches. I chose to stick to the 4th cousin and closer matches except for the case of Shared Ancestor Hints. If I had a distant cousin match but we also shared an ancestor hint, I added them to my spreadsheet.
  • Shared Hint, Common Ancestor: This is my favorite column. This one shows me who is already showing as having an ancestor match with me. Before I actually started tracking these matches, I didn’t realize I had so many on my Dad’s side. I always assumed most of my matches came from my mother’s well-documented side.
  • Public or Private Tree?: This one speaks for itself. I’m able to tell at a glance if the tree is public and might hold a lot of clues, or if I’m going to need some caffeine and my thinking cap. Probably some patience too.
  • Unlinked Tree: This is one of those hidden, but wonderful clues into those Private trees everyone is so upset about. Sometimes, if you are lucky, someone has an unlinked family tree on their account. In Ancestry, you have to go in and link test results to a tree. People don’t always do that and they certainly aren’t required to. However, sometimes they might have a tree already online and just haven’t linked their results to it. Of course, you can never be sure unless you ask them if those results go with that tree, but it’s better than no information at all.
  • Shared cM: This is the section I know the least about. This number is how Ancestry determines that Predicted Relationship. Mostly what I know is the higher centi-morgans you share, the closer your relationship. There are tons of tools and charts out there that break this down much better than me!
  • Confidence Level: Ancestry gives every match a confidence level. It was pretty interesting to compare my results with my Dad’s. Some of those High results were Extremely High for him or even the other way around.
  • Shared Matches: A simple yes or no. There aren’t many no answers but now I’m able to see them with 1 click of my mouse.
  • Contacted: This column is for if I’ve contacted the person yet or not.
  • Matched with Kathleen or Dad?: The column says something different for each tab. On my test, it’s an easy way for me to see what is most likely a paternal match. On my Dad’s test, it was an easy way for me to filter out the yes answers and delete the no answers after copying the tab. It saved me from re-typing 83 matches.

What about Notes? What about those 23andMe results?

Well, I’d like to tell you all about it but I can’t! The Notes section will take a little bit more space to explain and this entry is already really long. As for 23andMe, GEDMatch and other DNA results, I’m still figuring out how to organize them. This is a work in progress, but you can be sure I’ll keep my family and friends updated!