Showing posts with label naming customs. Show all posts
Showing posts with label naming customs. Show all posts

Tuesday, September 25, 2018

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.

If your ancestor changed their name, are you recording both names?
If your ancestor changed their name,
are you recording both names?
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.

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.
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.
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?

Please take this 3-question survey to help me make this content better for you. Thank you!

Tuesday, June 19, 2018

Using First Names as Evidence of Family Relationships

If you don't have at least 10 people in your family tree with the exact same name, you may be new to genealogy.

Many cultures follow specific baby-naming conventions—but not always. For example:
  • name your first-born son after his paternal grandfather
  • name your first-born daughter after her paternal grandmother
  • name your second-born son after his maternal grandfather
  • name your second-born daughter after her maternal grandmother
My paternal grandparents followed this convention. They named my father and his sister after their paternal grandparents. My mother's family did not follow the rules. If they had, my grandmother and I would both be named Mary Louise.

For help with your ancestors' child-naming customs, follow these links:
If I've left out your ethnicity, try a Google search including the ethnicity and "naming customs" or "naming conventions".

Here's an example of an Italian couple who followed the rules, but put a slight twist on them.

Giorgio and Maria followed the naming rules closely, but not perfectly.
Giorgio and Maria followed the naming rules closely, but not perfectly.
Giorgio and Maria named their first son and daughter after Giorgio's parents, Onofrio and Lucia. They named their second daughter after Maria's mother, Concetta.

But their 2nd through 5th sons were not named after Maria's father, Francescantonio. Instead, 3 of those sons had the Antonio part of Francescantonio in their name:
  • Giovannantonio
  • Giuseppantonio
  • Antonio
You can use your ethnicity's naming customs to help you place a person in a particular family.

Let's say you have a man named Pietro Iamarino. (I have 11 of them in my family tree.) You don't have his birth or death record yet, so you can't confirm his parents' names. But 1 or 2 of his children's birth records call him Pietro, son of Giuseppe.

Now you know he belongs to a father named Giuseppe. But I have 10 Giuseppe Iamarino's in my family tree! Of course I need a Giuseppe who's about the right age to be Pietro's father, but what if I have a few of those? (I do.)

When I examined the facts about my right-aged Giuseppe Iamarinos, one man stood out.

This family makes sense, but I had to track down birth records to prove it.
This family makes sense, but I had to track down birth records to prove it.
Giuseppantonio Iamarino was born in 1819 and married in 1840. That fit with Pietro who was born around 1848. Plus, Pietro named his first son Giuseppantonio—not Giuseppe.

But that is not proof. It's an educated guess at this point. So I attached Pietro to Giuseppantonio, but I added a bookmark and a note to Pietro to remind myself that I needed to prove this relationship. The proof came later when I found Pietro's 1848 birth record.

Use caution when you're piecing together ancestors' families from hundreds of years ago. Naming conventions can offer strong clues—clues that lead to a theory. But the names themselves are not the proof you need.

Use these naming customs to form your theory. Then prove it.

Keep searching for that proof and avoid making a mess of same-named, misplaced people in your family tree.

Stay connected! Follow me on Twitter or Facebook and know the moment a new article comes out.