07 June 2022

Finding Fallen Soldiers in Your Family Tree

With more than 43,000 people in my family tree, I'm bound to have lots of loose ends. A lack of vital records is usually to blame.

Today I decided to find my Italian relatives who died in World War I. If you have Italians in your family tree, you can search for their name or hometown. Start at https://www.cadutigrandeguerra.it/CercaNome.aspx.

Before you click away, this article covers more than Italy!

I began with my grandfather's hometown of Colle Sannita since I've been doing a ton of research there. The town lost 96 of their men in World War I. The second man on the list is a perfect example of a loose end.

I knew that a man named Agostino Basile had married Orsola Marino in 1908 because her birth record says so. But I didn't know anything about him. This website led me to a page showing the details of Agostino's military service. It included his birth date, so my first step was to find that record and see who his parents were. His birth record also mentions his 1908 marriage to Orsola Marino.

The website tells me Agostino was in the 47th infantry. He died of his wounds in combat in an area called Carso. When I looked into that, I found it's a region on the border of Italy and today's Slovenia. Italy lost thousands of men in this general area during the war.

When vital records don't tell you the end of the story, military records may have the answer.
When vital records don't tell you the end of the story, military records may have the answer.

Agostino is no longer a loose end. Now I know he died 8 years after marrying Orsola, who is my 3rd cousin 3 times removed. Her birth record also says she married another man in 1923—seven years after her 1st husband died. I wonder if it was a long time before Orsola knew Agostino was dead.

There's also a website to help you find Italian soldiers who died in World War II. Scroll way down the page at https://dimenticatidistato.com/elenco-nazionale-caduti-per-comune-di-nascita to find a list of provinces. Click yours to open a PDF that's divided by town.

To find casualty lists from other parts of the world, go to the FamilySearch wiki and type "world war i casualty" into the search box. The search results include:

  • The United States
  • Hungary
  • Bavaria
  • Germany
  • Czechia
  • Poland
  • East Prussia
  • and a ton more, including individual counties in the U.S.

Follow the links on each page to see what types of documents and information are available.

One resource gives you access to tons of international military records.
One resource gives you access to tons of international military records.

Whichever resources are the best fit for your family tree, bookmark them right away. I have another 94 men to look into from the Colle Sannita casualty list alone. And I've got a bunch of ancestral hometowns I want to explore next.

31 May 2022

3 Ways to Best Use Family Tree Hints

I've always done my family tree building in desktop software (Family Tree Maker). Then I synchronize it with my Ancestry family tree. I don't have "hints" turned on in my desktop software.

I didn't see much value to hints. They were usually wrong for my family. I never looked at them again.

Recently, I've been collaborating on several family trees, working directly on Ancestry. As a time-saver, I tested out the hints for these trees. I have no doubt that the technology behind Ancestry's hints has improved.

If you keep a few things firmly in mind, these hints can be a terrific benefit to your research. Very basically:

  • Don't accept every hint you see.
  • Don't believe someone else's unsourced family tree without investigation.
  • Think of hints as a little voice in your head saying, "Maybe this is the answer."

That little voice can save you time and steer you in the right direction. But you still have to proceed with caution.

Before I continue with the best ways to use family tree hints, a quick word about unsourced family trees. My own 42,800-person family tree serves up tons of hints to people of Southern Italian descent. But much of my work is missing sources. What's my excuse? I'm working to connect everyone who lived in my ancestral hometowns. If I added the images and sources as I went, I might not live long enough to complete my project! I'm building this tree as a database, and eventually I will add more and more images and sources.

The family trees you see as hints may have facts without sources, too. Don't dismiss them right away! Those trees may represent a family's oral history. Or the builder may be doing what I'm doing—gathering facts from published vital records. Take these hints as what they are: HINTS.

Now let's look at the 3 ways to best use family tree hints.

1. Locate Many Documents at Once

Hints in themselves are a powerful search tool. Instead of sifting through all the search results for a person, you can see the best results in one step.

I finally see the value in Ancestry hints. Here's how to use them without getting into trouble.
I finally see the value in Ancestry hints. Here's how to use them without getting into trouble.

As an example, let's look at my step-grandmother, Sadie. When I view her profile in my Ancestry family tree, I see 3 hints (you may see many more):

  • Sadie in 3 other family trees
  • Sadie's naturalization papers, complete with her photo
  • Sadie's Social Security Death Index listing

Since I do the work myself, I already have Sadie's naturalization and SSDI. These 2 results are a quick way to add solid facts to your tree without the effort.

Don't accept the Ancestry member trees hint without giving it a lot of consideration. More on that next.

2. Find People From the Same Family

When you do look at the Ancestry member trees hint, there are a few things to consider:

  • If they have different information than you, what is their source? Do they have something right that you have wrong?
  • Why is your person in their family tree? Are they a relative?
    • In my 1st of 3 tree results, I've stumbled upon the great grand-nephew of my step-grandmother. I don't have much info on Sadie's nephew, so this is a way to see who his descendants are.
    • In my 2nd tree result, someone has pulled most of my family into his tree. When I went to send him a message asking why, I found that we'd already had a conversation about this long ago. We do have an extremely distant connection.
    • My 3rd tree result belongs to my friend and collaborator. Her husband is the nephew of my great aunt.
A family tree can be a valid hint, but don't accept it. Think of it as your homework assignment.
A family tree can be a valid hint, but don't accept it. Think of it as your homework assignment.

It's not uncommon for me to find family trees that have pulled facts and documents from my tree. I can look at these trees to find my connection to their family, and maybe discover a new branch. But these are not hints to simply accept and add to your tree.

Instead, explore each hinted tree to see what they've done. Then do the research yourself. For example, I will not pull in my step-grandmother's nephew's family. But I will use that tree as a suggestion to search for more documents on Sadie's nephew and his family.

3. See Who Other Researchers Believe to Be Ancestors

Some time ago, Ancestry added Potential Father/Potential Mother hints. These show up in your tree as bright green icons. Click a potential parent, then click Review Details to see the source of the hint. I found these hints for my uncle's grandmother. I had her last name, but not her first name.

Rarely do I believe a potential father/mother hint. But this family tree showed extensive genealogy research.
Rarely do I believe a potential father/mother hint. But this family tree showed extensive genealogy research.

The hint for her potential father had a completely different last name. The hint for her potential mother showed the same family, but it had a document image as a source. This is worth reviewing. There isn't a direct way to get to the source tree, but if you click "Where is this information from?" you can see the name of the source tree and the owner. You can then do a Member Search for the owner and find the tree to review.

When I went to that tree, it was clear this person had done extensive research on my uncle's family. The last name I have for my uncle's grandmother may be wrong. I'm horrified to say that I have know idea of my source for that name.

This potential father/potential mother hint seems valid. But I won't simply accept the hints. Instead, I'll explore this person's tree and try to recreate her work.

The vital records for my uncle's hometown are available online now, but they weren't there a year ago when I last looked. This person seems to have found church records. I'll contact her and hopefully we'll collaborate. If she's right, I've opened up an enormous new branch for my uncle's family. This was a great hint.

One of the worst things you can do when building your family tree is click to accept every hint. They're called hints for a reason. They are suggestions of where to look.

Use hints as search shortcuts. Use hints to find distant relatives. Use hints to expand your tree. But do these things carefully to keep from going in the wrong direction.

In response to the comment below, Blogger is being idiotic and will not let me reply. So, I updated the 2 articles explaining how to use Antenati. Getting a high-res image is way easier than it was before. See https://family-tree-advice.blogspot.com/2017/05/how-to-use-online-italian-genealogy.html and https://family-tree-advice.blogspot.com/2022/01/antenati-tips.html

24 May 2022

Look Past the Misspellings to Find Your Ancestors

My second grade teacher taught us to read by making us "sound it out." I remember my class sounding out a sentence in one voice. "We went to the park" sounded like: wuh ee, we; wuh en t, went; tuh oo, to; thuh uh, the; puh arr k, park." It sounded weird, but it worked.

That lesson from too many decades ago helped me break down a family tree brick wall last week.

There's an Italian-American woman who wants to visit her ancestral hometowns. She wants to identify her ancestors so she might connect with people in the towns. One branch of her tree was giving me problems. I couldn't be sure where this particular husband and wife came from, and my searches were coming up empty.

Then she shared a family history that her ancestor wrote about this brick wall branch. The document had exact birth dates for the couple. It listed 2 or 3 hometowns for both the husband and wife. That was curious. Then again, it could mean that they were born in one town and their parents were born somewhere else.

I focused on the husband first. I checked a website that lists the names of every town in Italy. Of the 3 hometowns in the family history document, only one existed. I did not find him there.

The other 2 towns did not exist, and the spelling didn't look like proper Italian. I figured this was how the town sounded to the family history author when her ancestor said it. This was a phonetic spelling of the town.

Say It, Don't Spell It

With that in mind, I kept saying the 2 misspelled town names aloud, over and over again. I scanned the list of Italian towns as I repeated the sounds again and again. I didn't find them.

You may not know how to spell the name of your ancestor's town. What to do? Sound it out.
You may not know how to spell the name of your ancestor's town. What to do? Sound it out.

One of the best methods for finding a hometown is to find your ancestor on a ship manifest. I knew I wouldn't find the hometown on his ship manifest because he came to America too early. My ancestors were kind enough not to arrive before 1898, giving me a good look at the names of their hometowns.

The family history document had one more good clue about this couple. They got married in Manhattan in about 1888. I went straight to the search page for the New York City Municipal Archives. I knew I should find the marriage document there. I hoped it would have the bride and groom's parents' names. I did not expect it to list a hometown.

My searches failed. I couldn't find this couple, even when I included all the city's boroughs and expanded the years. Then I searched for a variation of the bride's last name. Experience tells me that an Italian last name ending in i usually ended in o at an earlier time. So I searched for her name ending in an o. This produced a long list of possibilities. I looked at the search results, hoping to find one with both her name and his.

That's when I found them. I never thought a clerk would misspell his very common last name. I swear, the NYC clerks in the late 1800s were illiterate. Who spells Italy Ytali? Someone who hears an Italian pronounce Italy and can't spell, that's who.

See How It Sounds

Now I had my couple's parents' names, even though the clerk mangled each one. (Saverio is a first name. Saviero is not.) Since the groom's mother's name was not common, I did an Ancestry search for her. The one search result made me gasp. (I guess I'm a gasper.) It was someone else's family tree that included my groom's entire family—but not him.

Everything about this unsourced tree made perfect sense to me. The parents matched the NYC marriage record. The family history mentioned the groom's sister and brothers, and here they were. I never accept someone's family tree as fact, but I was able to verify what they were showing.

The one thing that made me certain this was the right family was their hometown. Remember those misspelled town names? The ones I kept saying aloud to hear their sound? This tree had one of the town names. When I said it aloud, I knew for a fact it was the misspelled town from the document.

Keep sounding out that foreign town name as you search for something that matches the sound.
Keep sounding out that foreign town name as you search for something that matches the sound.

Now it was time to prove this person's tree right or wrong. I searched the properly spelled town for my groom's birth record. I found him in the year before the date from the family history. (Always assume early ancestors may not know their own birthday.) There he was with the same parents I'd found misspelled on his NYC marriage record.

Knowing the right town, I used vital records to take the groom's family back 4 generations!

Most people would see that other family tree and think, "That's not the town great grandpa used to talk about." But I saw the town name and said it aloud as an Italian would. I heard it as a match for the botched spelling in the family history document.

When you pronounce an R in Italian, it sounds like a D. My grandfather used to call my grandmother Mary something that sounded like Moddy. That wasn't a D sound. It was a rolled R. That's why the family history had the town name so wrong.

What Else Makes That Sound?

My second grade teacher's "sound it out" method is still working for me. Have you heard your ancestor's hometown spoken with a foreign accent but never saw it written? You may not know how to spell it at all.

I used this method in my own family tree once before. (See Case Study on "What If There's No There There?") My great grandmother used to talk about where she came from. Her granddaughter passed that along to me as a phonetic spelling: Pisqualamazza. That's not a town. So I searched passenger lists for anyone around her age with her last name. I looked at each search result to see the hometown. When I saw Pescolamazza, I knew that was it. And that's where I found her birth record. Now I can name her 3rd great grandparents.

If you can't locate your ancestral hometown, keep your mind and ears open. Sound it out as you try to mimic the right accent. If you heard your grandfather say it when you were a kid, try to remember exactly how it sounded. Then see what sounds the same.