Looking Ahead

 

While I'm working on extricating myself from the current tree-building mess I'm in, I thought I'd take a moment, despite being early, to introduce next month's research project. After all, tree-building, while a lot of work, only rarely provides the kind of fascinating discoveries worth writing about.

As the Twelve Most Wanted project has done for the past several years, come July, I shift my focus away from the three selected ancestors from my mother-in-law's line and move on to my father-in-law's tree. With a step like that, we leap from colonial America to land in the turmoil of mid-1800s Ireland, a very different part of the dominion of the United Kingdom.

In the next three months, we'll focus on three Irish ancestors from my father-in-law's family. The process will begin with the selection for July: John Kelly.

Regardless of who he was in my father-in-law's family tree—we'll get to that next Monday—we first need to consider how convoluted a search like that can be. 

Just by considering his name—John Kelly—we already realize what a challenge we face in the coming month. A given name like John, bestowed upon an Irish-born son of the mid-1800s, would put him in ample good company. While I don't have statistics for popular names in the exact year of his birth, just taking a glance at name popularity statistics for a time period just after his death, we can see that the name John was a popular choice for Irish parents. One source indicated that, by 1911, John was the most common man's name in Ireland.

Add to that predicament the fact that the surname Kelly won't make the situation any easier. Based on data available in the mid-1800s, the surname Kelly wasn't exactly the number one surname on the island but it came in close—the second most common surname in all of Ireland, after Murphy.

And there you have it: the task lying ahead of us for next month's selection for my Twelve Most Wanted. Truth be told, I've needed to jump into this messy research project for years but being aware of the challenge just seemed to help point my attention in other directions. Now that I'm running out of low hanging fruit in my hunt for ancestral history, it's finally time to face up to the challenge when July gets here next week.   

Each Step Makes the Next One Easier

 

As I work through the finishing touches of last month's research project, adding DNA matches to my mother-in-law's Jackson ancestors, I realized one encouraging detail. For every DNA match whose place I secured in her family tree, it made the next step easier to complete.

There are requisite tools to have at hand in order to make such a statement. I'm working now on those Jackson DNA matches by way of Ancestry.com's ThruLines tool, along with their ProTools capability of listing shared matches. Each identified match fills a known place in the family tree, thus becoming a beacon of relationship for all the others in this line, no matter how small the match may be.

The last time I checked, that Jackson progenitor, Lyman, had seventy three matches listed in his ThruLines results. But for each of those seventy three, there are multiple others who show up if I click on the Shared Matches tab under ProTools. Many of those share very little genetic material with my husband, the proxy test taker for this project. Yet, bit by bit, identifying each one's place in the Jackson family presents a second helpful clue by showing me how even more mystery matches fit into the tree.

It's amazing to see how many DNA matches turn out to have siblings, parents or children, or close cousins who have also tested. Identifying one's place in the tree brings the others into the picture more clearly, multiplying my effort. All I need to do is keep at it, adding more and more matches until I run out of options. Then, usually after a short waiting period, even more DNA matches show up—perhaps thanks to a Father's Day sale or other promotion—and the relationship clues help zero in on where the newer ones belong, as well.

I'm still quite a long way from completing those seventy three ThruLines matches—plus those other affiliated cousins—but it has helped find some otherwise invisible Jackson descendants. Of course, only six of the original thirteen children of Lyman Jackson have appeared in those DNA results, represented by their descendants, but I'm hoping this process will coax some of the other Jackson lines out of their hiding places and onto my mother-in-law's family tree. 

Dime a Dip

 

Yesterday's summer cleaning adventures—both of the real-life and genealogical kind—brought to mind some unexpected memories. On the real life front, cleaning projects unearthed an unused gift certificate for one hundred dollars—an impressive gift when it was received years ago, though just enough to purchase a decent restaurant dinner for two nowadays.

A day's worth of such discoveries, going through old files in the summer heat, was enough to prompt our family to head to our favorite ice cream shop after dinner. That, in turn, put me in mind of the dime-a-dip ice cream parlors of bygone years. Perhaps it was owing to the many projects unfolding during the day in our family—our daughter was helping a friend explore potential real estate projects, comparing prices today with original purchase prices on eighty year old homes—that put me in mind of an entire world of dime a dip life.

Meanwhile, on the genealogical front, I was delving into my mother-in-law's Jackson roots, a reach so far removed from today's generation that I barely can find matches who reach a mere ten centiMorgans of shared genetic material. As rarified as that "dime" of genetic material may seem in today's inflated economy, just like the dime-a-dip of the ice cream world, it can yield some useful results. 

This was my day to chase those "shared matches" of Jackson descendants to help build out that family tree. Simply by using the ThruLines results for Lyman Jackson, my mother-in-law's fourth great-grandfather, I used as a next step the "Shared matches" option from Ancestry's ProTools to find close relatives to each Jackson DNA match.

One after another, those mystery matches who shared such dime-sized genetic results helped guide me to build out that Jackson branch on my in-laws' tree. Yes, of course I used documentation to verify connections; it's just that without that chain of discoveries, I would otherwise not have known to even look in those directions.

Such small DNA matches are often lost in the myriad results at the bottom of the pile. They otherwise would have totally stumped me—if I even bothered to try connecting them to the family tree. But with the right tools, and a huge helping of patience added to the mix, it is possible to let each match find a place in the family tree, no matter how small. 

A DNA Housecleaning

 

Face it: when confronted with twenty thousand DNA matches, it's hard to place those distant relatives in their place on the family tree. Far easier to concentrate on the other, smaller category—fourth cousins or closer—for whom we have much better chances of confirming connections.

But—and there always is a caveat—since I've decided to pursue DNA cousins who share descent from my mother-in-law's fourth great-grandparents Lyman and Deidama Jackson, her proxy test volunteer (her son, my husband) must find connections with matches who are at least sixth cousins. That's where we start dipping into that larger pool of twenty thousand contestants. Facing a number like that, it's time for a DNA housecleaning.

That larger pool of possible cousins is further restricted by genetic limitations. After about the level of third cousin,  some distant relatives will share no identifying genetic material at all with a percentage of their cousins. That is not to say, of course, that there is no DNA shared at all. There is a high percentage of genetic material that all human beings have in common—it's just that the selected SNPs that genealogy companies use to identify closer family connections may not include the array of items passed down from specific distant ancestors.

However, combining use of both a paper trail of documented family connections and data about distant DNA matches may still confirm a distant cousin's place in the family tree, despite sharing only a small number of centiMorgans. In such cases, what I've done is build out the lines of descent from the distant ancestor—the Jackson line in this case—then move from already-confirmed known cousins to "shared matches" identified by tools such as Ancestry's ProTools.

Of Lyman Jackson's thirteen children, there are six whose descendants are itemized in the ThruLines listing at Ancestry.com. Of course, the bulk of those matches come from John Jackson's own line, which is the line of descent leading to my mother-in-law. However, through this process I've managed to connect the majority of other ThruLines Jackson cousins to her family tree.

From that point, my next step is to take each one of those verified Jackson cousin matches and open the "Shared Matches" tab on their own entry. I then look to see how many of those connected cousins I can trace through the family tree. Sometimes, that task presents problems, but in many cases, that two-step sweep leads to discovering other Jackson descendants among those twenty thousand distant matches. And each match confirmed makes the next ones easier to place, as we place more pieces of the puzzle where they belong in the tree.

From there, it's basically "rinse and repeat" as far as I can go with that same process. Bit by bit, it opens up possibilities for where DNA matches fit in the bigger picture of a much-extended family tree. 

More Month Than Projected

 

I remember a phrase from my starving student years, something about always having more month than money. I've always hated running out, no matter what supply was dwindling too fast for comfort. Thankfully, I'm far from those student years, but I still struggle with any sense of not having enough.

How strange it is, then, to find myself with more month than research project. With each month's Twelve Most Wanted candidate, I usually run out of material to secure my research goal before I get to the close of each month. What a shift it has been to find myself ten days away from the start of a new month, yet finished with the goal for that time period.

What to do next? Granted, I could just jump ahead and move on to July's project. With the shift in this upcoming quarter from my mother-in-law's family to that of my father-in-law, that might work, but it would take a leap from colonial American research to the brick wall woes of tracing Irish immigrants back to their beloved homeland. That may become a project never completed, no matter how many months are allotted to the effort.

However, there are so many odds and ends scattered in my wake as I plow through those family history questions each month. What comes to mind most are the DNA connections hinted at, but never quite confirmed, from the collection of literally thousands of matches. 

I'm thinking mostly of the thirteen children of Lyman and Deidama Jackson, whose lives spanned the era in which a nation was birthed. When we last left that endeavor to document the Jackson family, all thirteen children had been identified—barely. There is so much more yet to do.

There are now seventy three DNA cousins among my husband's Jackson matches, according to Ancestry's ThruLines tool, cousins who descend from that couple we had followed for April's version of this year's Twelve Most Wanted. It's time to wrap up those dangling strands and tie them into this family tapestry. Sounds like a "summer cleaning" project to me.

Tipping Towards Summer

 

Perhaps there's something about passing the longest day of the year that begs me to crest other tipping points. We've waved the flag for Flag Day and bid everyone a happy Juneteenth while celebrating dads and the last of the grads. It's time to get on with summer. For some reason, I'm already chomping at the bit to move on with my next project before July ever gets here.

First, though, comes some spring cleaning. Yes, I know we are officially into summer already, but there is no such picturesque way to classify summer cleaning. Dusty, sweaty, and chores are words that come to mind for such a designation, but what I've been working on in the past two weeks has edged into something far less distasteful than that.

Having decided that I'm as good as done with this month's research project—finding the roots of Elizabeth Plummer Ijams, my "Twelve Most Wanted" for June—I decided to do some cleaning up of old projects which didn't have the luxury of acquiring the satisfying label of "done."

First on the list was to return to May's research project, my quest to discover the parents of my mother-in-law's brick wall ancestor, Lydia Miller. I continued building out the lines of descent for three DNA matches sharing ancestors by the name of Anspach, a surname strangely linked to the circle of people connected with Lydia in her earliest years. There's still a lot of work yet to do, but I'm edging closer. Maybe next year, I'll finally cross that finish line.

Next came a general housecleaning of all the open tabs on my computer. When I am building out a line of descent, I keep a tab open specifically for that family. Locking that tab in place allows me to return to the place where I last left off with that family, making it easy for me to pick up the trail at a moment's notice. I went through each of those tabs—after a year or so, that collection can grow cumbersome—and deleted those which are not on my research radar at this point.

That process left me with some Polish lines remaining from my father's ancestry, plus some other more recent lines I'm still wrestling with. All that considered, I actually gleaned eighteen more names for my father's side of the family tree, so that count edges up to 41,957 documented people.

The main focus for this month—actually, the culmination of three months' work—has been my mother-in-law's family. Granted, I didn't add many people this month as I wandered through reports of colonial family in 1600s Maryland, mostly because seventh through tenth great-grandparents won't add much meaningful data for my quest to place DNA cousins in that tree. But in returning to Lydia's project—a much closer reach for my mother-in-law's second great-grandmother—I had plenty to add to that tree.

All told, the past two weeks advanced the count by less than usual—166 new relatives—due to the different nature of the work on those Maryland ancestors. My in-laws' tree now contains 43,629 documented individuals, a number that will remain at about that level as we close out this month's research project.

For the last few days of this month, I'll revisit a few of those older projects and provide updates. After that point, we'll jump into summer both feet first as we move from my mother-in-law's family to my father-in-law's Irish roots. Hopefully, new resources there will allow for some encouraging progress in our research for that side of the family. 

. . . But Then, There's Charlemagne

 

Notwithstanding my reasons given yesterday about not needing to pursue my mother-in-law's colonial Maryland ancestors any longer, there is yet one nagging thought. What about Charlemagne? After all, I have a book that says as much: that my mother-in-law is a descendant of an emperor.

So what? Some sources speculate that, based solely on statistics, anyone of Western European descent could have a chance of being Charlemagne's descendant. After all, Charlemagne was said to have had five wives and several other partners. Those, in turn, gave him at least twenty children. Then, just do the math to see how those generations could multiply over the centuries since Charlemagne's death in the year 814.

Granted, tracing one's lineage back to a date smack dab in the middle of the Middle Ages can be a challenge. Just think of how much I struggled to get back to colonial Maryland.

There is, however, one catch: if we can manage to latch on to European royalty—or at least nobility—someone in our distant past has been diligent to keep proper records of such details. From those records, one organization has, over the decades, compiled three volumes of such lines of descent. Not surprisingly, that organization is known as the Order of the Crown of Charlemagne, whose Genealogist General has been tasked with overseeing such verification.

Published by the Order in three volumes over nearly forty years, Pedigrees of Some of the Emperor Charlemagne's Descendants happens to include a chapter concerning the family line of none other than my mother-in-law's ancestor, Elizabeth Plummer. Thankfully, I was able to access that second volume through a subscription to Ancestry.com, where I easily followed the trail from Elizabeth to her mother, grandmother, and great-grandmother, just as I had noted here in the past few days from other records.

Winding my way back through the genealogy laid out in that chapter was an eye-opening excursion. Sure, there were earls and lords, but there were also ancestors who "died" at the Tower of London, or were beheaded, or hanged for whatever political infraction they might have committed.

The litany brought me back from Elizabeth Plummer's point to the lead entry in the chapter for Isabel de Vermandois. From Isabel's vantage point—she died in 1147—there would still be a long way to go before reaching Charlemagne's era. The book refers the reader to three previous chapters to continue the genealogical saga.

But the story actually does reach back to Charlemagne, himself. Who would have thought? Especially since my mother-in-law, during my initial interview with her before launching into her family history, was so certain that the generation preceding her grandparents had "just gotten off the boat." How wrong she was.

As for my pursuit this month of Elizabeth Plummer's life story and that of the ancestors preceding her, it's sufficient—not to mention, fun—to see someone's research pointing the way to Charlemagne. Do I wish to replicate that search myself? Hardly. There are too many other questions yet to resolve—research adventures for which no keepers of the royal line of descent would care to concern themselves.