The 17 December 1878 statement of Thomas Tredway indicated that Jemima DeMoss and Elisha Meads were married in Harford County, Maryland, “at her fathers [John DeMoss, Jr.] house in Harford County” on 9 November 1817.
I do not think that’s strong enough evidence to conclude that Jemima’s mother was deceased on the date of Jemima’s marriage. Use of the word “father’s” to describe the real property of a person’s parents in the 19th century was not uncommon. Her father could actually have been deceased at the time of the marriage as well–even though the word “late” or “deceased” was not used in the reference–and her mother could have been living.
I already knew that John DeMoss, Jr. lived in Harford County, Maryland, but the statement would have been helpful had that not been known. I knew that John owned real estate, but the reference to his “farm” would have suggested real estate ownership instead of him being a tenant farmer.
My ahnentafel chart (an ancestor table that lists direct-line ancestors) had blanks in it. I don’t have any gaps until I get to my third-great-grandparents. That’s where the blanks in my pedigree start. I don’t have the names of three of my Irish ancestors in that generation.
And it grows from there.
In my 4th great-grandparent generation, there are eight ancestors of probable Irish origin whose names are not currently known. They may never be. Another 4th great-grandmother, probably from Pennsylvania or Maryland, is also a mystery. The number of blanks only increases as my tree goes into the generation of my 5th great-grandparents and beyond. Unknown ancestors from New York State and various areas of the American South are unknown to me at this time. They may remain that way.
I don’t know what percent of my tree in the generation of my 5th or 6th great-grandparents is incomplete. It’s not because I cannot calculate percentages. I don’t care because it frankly does not matter. I’m not in a competition. Some locations and time periods are more difficult to establish parent-child connections in. Some ancestors, for one reason or another, are more difficult to trace to their parentage.
The goal for me is to document as many ancestors as I can as completely as possible. Sometimes that is easier to do than others. There’s no need to set an arbitrary benchmark to meet.
We have the ancestors we have with the research challenges that come with them. It’s the path of discovery that matters…not the largest accumulation of names and relationships.
The ability to merge sources (particularly census) into a tree at Ancestry.com is really a nice one.
However, one must be careful not to indicate that a source says something it does not. The reasons are pretty obvious–but here’s an example with the names changed.
Thomas Smith was born in Harford County, Maryland, on 2 May 1865 and you have three primary sources to back it up. The 1880, 1900, 1910 and 1920 census all indicate he was born in Maryland. Let’s say that they all point to a year of birth of 1865
Yet if you aren’t careful when you tie the census record to his date and place of birth, you seemingly indicate that the census indicates he was born on 2 May 1865 in Harford County, Maryland. I’ve never seen a census between 1880 and 1920 that provides that specific of a place of birth.
Shouldn’t you create a “new” place/date of birth that is 1865 in Maryland and tie the census source to that?
ThruLines at AncestryDNA is meant to be a tool to help analyze matches that have at least a partial family tree attached to their DNA results. The purported tree connecting you to the DNA match may or may not be correct.
The white boxes (John G, John M, and Theodore Trautvetter) in the illustration are names and relationships that are in the tree I have attached to my test results. The gray boxes (with “evaluate”) in the corner are names and relationships that have been pulled using AncestryDNA’s automated “tree stitching” based on one or more user submitted trees.
The tree of the match may only go back so far as the parent of the match. The names and relations may have been pulled from one or more trees others have submitted to AncestryDNA and those trees may or may not be connected to any DNA results. Each name and relationship in the gray boxes will have to be evaluated manually.
The white boxes are from your tree. The others are not and, like a therapist, you’ll have to evaluate those relationships for viability.
Ancestry.com’s ThruLines is a means to facilitate working with DNA matches that have trees attached to them. ThruLines then extends the tree in an attempt to show you how you connect with the DNA match. People are only in your ThruLines if they are:
a DNA match to you,
have a tree attached to their DNA results,
able to be connected to your genealogical tree using the “big ol’ tree” Ancestry.com uses to make connections.
The connection to you and the match via ThruLines is only as accurate as the genealogical pedigree information in their “big ol’ tree.” Because that “big ol’ tree” is made from compiled trees, the information in it may be inaccurate. Because of that the suggested path of connection may not be entirely correct. There may be extra generations, not enough generations, etc. It is also possible that your genealogical connection to that DNA match is through another family and not the one that ThruLines suggests.
The illustration is a good example of individuals who are connected to me, but whose connection to me is incorrect–because it is based on trees of other individuals that contain incorrect information. To make the craziness of the ThruLines as simple as possible to understand, a man named Alexander Neill (son of John Neill shown in the illustration as my 3rd great-grandfather) is in the big ol’ tree three times–twice as nephews of his actual father and once correctly (but not shown in the illustration). These two incorrect Alexanders have lines of descent down to my known DNA matches.
So all the DNA matches in the illustration actually descend from John Neill (my 3rd great-grandfather). None descend from any siblings of this John. ThruLines suggests that the DNA shows evidence that I descend from an earlier John Neill (born in 1773) and his father Charles McNeill. That’s not correct. All my DNA matches (related to this family) are known to come from John Neill my 3rd great-grandfather. The only way a DNA match would suggest a descent from the earlier John or Charles would be if that DNA match descended from the earlier John or Charles–without descending through my 3rd great-grandfather John Neill.
There’s “tree evidence” of the connection between John Neill and his “father” and “grandfather”–using that phrase very loosely–but no DNA evidence at all. The paper “evidence” of the earlier John (and Charles) is weak, weak enough that I’ve not put that information in my actual tree. And there’s no DNA evidence (yet) connecting the earlier John or Charles to me because no DNA matches to me have John or Charles in their tree without also being a descendant of my 3rd great-grandfather.
ThruLines is a tool. Personally I find it helpful to sort out matches that have a tree. But I have to doublecheck those connections.
DNA matches that have no trees or whose submitters fail to respond can be a challenge to those working through their genealogy DNA matches. Sometimes there’s a clue in that username that may help you to determine who that match likely is.
These approaches are best done after you’ve worked on matches that you can determine. That work usually allows a researcher to have an idea of what general part of your tree a match is from. Two treeless matches with submitters who did not respond were likely determined using their username. Unfortunately those usernames did not appear to be the actual name of the submitter.
In both cases, the shared matches that I had with the match in question allowed me to know which portion of DNA testee’s tree the match was related through. That helped.
This match was known to connect to the test kit submitter through the submitter’s maternal grandmother. The connection to the kit submitter was in the second-third cousin range and not someone who could easily be identified as closer matches were. This match had no tree and did not respond to a couple of contact attempts. A Google search was conducted for their username that was used for their DNA results. It turned out an old MySpace account had the same user name. Looking at the public information on that page (including their actual name) provided enough identifying information that the match’s identity and relationship to the DNA kit I managed could be determined.
Named for my parents
This match was known to connect to my DNA results through one of my paternal great-grandfathers George Trautvetter. The username, which I have changed, was of the form “bobandesmerelda.” There was no attached tree and no response to communication. In reviewing all the descendants of George Trautvetter’s grandfather (also a George Trautvetter), I located a deceased great-granddaughter named Esmerelda who I had not researched any further. Information on her indicated her husband was named Robert. While I’m not certain exactly who the match is, it seems possible that the submitter named the account for their parents–Bob and Esmerelda. The genealogical cousinship I have with Esmerelda is consistent with the predicted relationship range based upon the shared DNA. Not 100% proof, but suggestive enough for me to classify the match as determined.
In both cases, my analysis is in my DNA match notes so that I remember later exactly how these matches were determined and can re-evaluate later if necessary.
Due to a scheduling issue, we’ve moved the FamilySearch webinar to 28 Sept. at 7:30 pm. central time. Recordings will also be available for those who cannot attend live. Details on our announcement page.
The one thing that always concerns me is whether or not the images I get online from FamilySearch as as high of a quality as the high quality scans I made directly from microfilm myself at the Family History Library years ago. In most cases, really high quality scans don’t impact the legibility of the text, but there are times where they do.