Trying to Solve a DNA Mystery with Logic

I'm mapping out a strategy to discover how my parents are distant cousins, as our DNA tells us.

An analysis of my raw DNA on GEDmatch.com shows that my parents are "probably distantly related." Their Ancestry DNA results predict that they are 4th–6th cousins. That should mean they share a set of 5th–7th great grandparents.

I want to find that link between mom and dad's DNA.

But there's another piece to this puzzle. My mom's sister's son (my first cousin Nick) is a DNA match for my dad. Ancestry DNA estimates my cousin and my dad are 5th–8th cousins. Nick's related to both my mom and my dad.

My mission is clear: Find the set of ancestors that my parents share…and see if they're the same ancestors my dad and my cousin share!

Plotting out where my ancestors lived,
they were all pretty close together.

My method is less clear. So let's work through the logic.

My dad's side of the family comes the Benevento province (similar to a U.S. county). My mother's side comes from the same province. What if, at some point, a man from one of dad's towns married a woman from one of mom's towns?

For at least several hundred years, all my ancestors lived no more than 25 or 30 miles apart. Many lived 5 or 10 miles apart, but that's as the crow flies. I've visited these rural, hill towns. They're separated by windy, hard-to-navigate, and sometimes washed-out roads.

My husband and I spent nearly an hour trying to get from one town (Colle Sannita) to the neighboring town (Baselice). We thought we'd never make it.

That experience got me thinking about how hard it was for my ancestors to go from town to town on a mule-drawn cart. That's why it's more logical to look at towns that were closer to one another.

I have 2 main choices. I can concentrate on my 2 grandfathers' towns, the ones that are a nightmare drive apart. Or I can take a hard look at 2 towns that are much closer together.

Colle Sannita (Grandpa Iamarino's town) neighbors the town of Circello. They're very close to one another, and the roads don't have to switch back and forth over mountains. Much easier on a mule cart.

One set of my 3rd great grandparents
had an inter-town marriage.

I've known for years that my cousin Nick's dad's family came from Circello. (Remember, Nick is my cousin on our mothers' sides.) But I found out recently that my 3rd great grandfather was born in Circello.

Francesco Saverio Liguori was born in Circello in 1813. In 1840 he married Anna Donata Cerrone in Colle Sannita, settled there and raised his family.

So my dad has some roots in Circello. When you look at these 2 facts:

• Nick's last name comes from Circello
• my dad's DNA match list has at least 3 people with that name

…it seems as if that last name may connect my cousin to my dad. But will it connect my mom to my dad? That's the big goal.

Is Nick a DNA match to my dad because of his own last name? Or is the connection through his mom, who is the same distant cousin of my dad as her sister—my mom?

Here's the plan I'm going to follow, and hope it leads to identifying that DNA connection.

1. I'll work to build out Nick's Circello branch of the family tree.
   
2. I'll also work to build out his grandmother's family tree. Why? Because she was from my Grandpa Iamarino's town! His grandparents had exactly the type of inter-town marriage I need to explore.
   
3. I'll study my grandparent chart and look for last names that don't seem native to their town. For example, my 4th great grandmother's last name (Tricarico) isn't one I've seen in the town where she lived. Maybe her parents or grandparents came from another town. And maybe, just maybe, her ancestors will tie my mom and dad together.

I've spent so much time living among my ancestors' vital records collections, I can spot an uncommon name in a given town. Liguori, my 3rd great grandfather's last name, was out of place. And that turned out to be entirely true.

It's important to get really familiar with last names in your ancestors' towns. Maybe you can learn the main names in your ancestor's town by looking at land records. Or by paying attention to all the names on the index pages when searching for your ancestor's birth record.

Wish me good luck. I'll report back when I think I've found that missing link!

And speaking of DNA clues:

• Delving Deep into Your Genealogy with DNA
• When DNA Says You're Related, You Determine How
• Collaborating with Your DNA Matches

How to Find Official Sources for Family Facts You Just Know

Imagine your grandchild inherits your family tree. How reliable will the information be for your generation?

I don't need a document to tell me I was born in Mother Cabrini Hospital in New York City. Or that I was baptized in Our Lady of Pity Church in the Bronx. (Both gone now, by the way.)

But years from now, if my grandchild wants to carry on my genealogy work, what proof will they have for facts about me, my siblings and my cousins?

Marriage registers, yearbooks, newspaper
clippings…these are official sources for your
living relatives.

Everyone says to start your tree with yourself and the facts you know. Then you move on. Finding census forms, draft registration cards, death records and so much more. But have you returned to yourself and your generation to find proof for your facts?

Your Own Documents

You should have your own birth certificate in your possession. I even have my baptismal certificate, along with two marriage certificates.

I need to scan those documents and put them in my family tree. (For the worriers: You can mark individual images as private in Family Tree Maker. Hopefully in your software, too.)

Of course, I'm not going to ask my brother and my cousins to let me scan their birth certificates. So what do you do?

Public Records Index

On Ancestry.com you can access volumes 1 and 2 of the U.S. Public Records Index, 1950–1993. The information in these databases comes from a combination of:

• telephone books
• post office change-of-address forms
• other public documents.

In my experience, the birth dates given in these collections are often wrong. For me, an entry might say I was born on the 1st of the month instead of the 24th. But it generally has the right year.

So, when all else fails, a public records source proves the person in your tree existed:

• by their name
• in a specific place
• in a specific range of time.

Newly Released Indexes

It pays to watch social media for genealogy news. That's where you can learn about groups like Reclaim the Records. They're on a mission to get access to the genealogical and archival data we genealogists want so much.

They've scored tremendous wins, particularly for New York and New Jersey documents. But they're also working to release data from many U.S. states.

Thanks to them, I've found documentation for several events, including:

• my parents' marriage license
• my grandfather's 2nd marriage license
• my and my close cousins' births
• my grandmother Lucy's birth

Seeing the index of New York births, I finally found my grandmother's birth certificate number.

Lucy's birth record has eluded me for years. Now I know her New York State birth certificate number is 60968. On the index she has no first name and a badly misspelled last name. No wonder I couldn't find her certificate! It's definitely her because my father has always known she was born on 10 Dec 1908 in Hornell, New York.

Newspapers

I haven't found much historical information on my family in the newspapers. But I'm constantly finding references to my brother in newspapers. His career has always had a big public relations aspect to it. So any search for Iamarino brings up my brother. I found his North Carolina marriage announcement that way.

Proof of a modern-day marriage may be found in the bride's hometown paper.

You may have more luck searching for your family. Think about all the events you could search for when it comes to your contemporary relatives:

• birth, marriage and death announcements
• public relations announcements for various professionals
• graduating class lists

Your facts and your closest, living relatives' facts may not be your top priority. But documenting these things you've known all your life:

• your mom's birth date
• your brother's middle name
• your aunt's home address

…will go a long way toward strengthening your legacy.

Set aside some time to find documents or public sources for your own nuclear family. Some day your grandchild may thank you from the bottom of their heart.

And speaking of proof:

• How Do I Get There From Here?
• How to Avoid Going Down Wrong Path
• Trust But Verify Your Relative's Family Tree

This Genealogy Policy Takes the Guesswork Out of Names

My in-law policy is working so well, I've created a naming policy for my family tree.

In my last article, I wrote about how freeing it can be to set policies for building your family tree. My new policy for handling the in-laws of distant relatives has been incredibly helpful.

This past weekend I found 29 more people who were in my family tree simply because they were an easy get. For instance, a man named Giovanni married one of my distant relatives in New York City long ago. I do want him and his parents in my tree. But I no longer want his 8 siblings—or any of their spouses and children—in my family tree.

So I removed them. And if I ever wanted them back, the census sheets where I found their names are still part of my tree. I'm keeping the documents because they contain Giovanni and his parents.

If your ancestor changed their name,
are you recording both names?

This in-law policy makes me happy because it's always there to guide me. It'll keep me from reaching out too far. It'll put an end to those awkward messages I get from people wondering why their grandfather is in my family tree.

It makes me so happy, I want to consider other genealogy policies.

I didn't have to think too hard about it before I realized—I already have another genealogy policy.

What I'm about to describe is not an established, official genealogy rule. There's a good amount of personal preference.

So think about your own personal preferences as you read on.

Naming Conventions in Your Family Tree

I'm putting my naming convention policy in writing. But it's based on practices I already follow. This is the style I've developed over the years.

Now, with a policy in place, I'll be sure to be consistent.

#1 Birth Names

If your ancestors emigrated to a country with a different language, they probably went by a different name. Giovanni became John. Anton became Anthony. Pablo became Paul.

I record my ancestors using the name on their birth record. If I haven't seen their birth record, I check each census. If they were born in another country, and on some censuses they use an ethnic name, then I believe that's their given name.

In Family Tree Maker, I use their birth name as their Name fact.

Record multiple names for your ancestor if they unofficially changed their name.

#2 Common Names

In their new home in a new country, many of our ancestors tried to fit in. They identified themselves by a non-ethnic name, like Mary instead of Maria Rosa.

We don't want to lose track of those new names. The new name is likely to be what's on their death record.

In Family Tree Maker, I record their common, or assumed name, as a second name fact. The software lets me add multiple names and set one as the preferred fact. Their birth name is that preferred fact.

Last names are important, too! If your ancestor changed their last name in their new country, you need to record that. You can make it their alternate name—their non-preferred name. For example, I have ancestors named Muollo. That's so hard for an American mouth to say, that one Muollo man changed his name legally to Williams.

That may seem like an odd choice. But you pronounce Muollo as mwoe-low. That could sound as if you're mumbling Williams. I need to record the Williams name because that's the legal last name of this man's children.

#3 Nicknames

Everyone in my parents' Bronx neighborhood in the old days had a nickname. In my family there were men called Baldy and Blondie. People in the family never called them anything else. So I need to preserve those colorful nicknames in the family tree, too.

In Family Tree Maker, I record a nickname with the AKA (Also Known As) data fact. Having spelled out this policy, now I'll be sure to fill in what I'm missing.

#4 Reference Words

I've been working on my document tracker a lot lately. This is a spreadsheet where I log each document I've found for the people in my tree. Everyone who has a document image gets a line in the document tracker.

A simple shorthand highlights my
closer ancestors, and their father's name.

Filling it out helps me realize which documents I'm missing for each person. It encourages me to do more. Lots of times I'll enter something in the "Need to find" field, like "1902 immigration record". Then I think, "Why not search for it right now?" And I know I'm doing good work.

Here's where I'm using a naming convention in my spreadsheet.

I have tons of people in my tree with the same name. Don't we all? In the small towns where my ancestors were born, many men had the same name. On the town's birth records, the mayor would sometimes write the new father's name as, for example, "Giovanni, son of Giuseppe".

So I'm doing that in my spreadsheet. After a person's name, I add, in parentheses, (son of Giuseppe), or whatever the father's name is. That helps me when I need to locate the person in my family tree.

I also like to identify certain close relatives in the spreadsheet. I use this shorthand: 2G is a 2nd great grandparent, 2GA is a 2nd great aunt, 2GU is a 2nd great uncle.

What naming conventions are you using? Are you being consistent?

Spend a little time thinking about the names in your tree. What policies can you set to make your family tree make more sense?

And speaking of being consistent in your family tree:

• It's Time to Revisit and Improve Your Earliest Family Tree Research
• How to Handle Foreign Words in Your Family Tree
• These 4 Simple Rules Will Improve Your Genealogy Research