How to Avoid Going Down the Wrong Path

It's a good thing the Family Tree Maker^®/Ancestry.com^® TreeSync^® feature isn't working right now because that saved me from committing a genealogical sin.

I nearly posted bad information about someone. Publicly.

This wake-up call reminds me that it is so easy to be led astray when researching a family you know nothing about. It all started when a woman contacted me on ancestry.com about her great grandfather Rudolph, who is in my tree.

He is in my tree with very few facts because he was the father of a woman who married a cousin of mine. Since the cousin himself is so distant to me, I did not go into great detail about his wife's ancestors—just the names of her parents.

But after hearing from Rudolph's descendant and collaborating with her to find his marriage record, I spent a little time searching for more facts about him.

Many cultures embrace the practice of naming children after their grandparents, which is a potential pitfall for genealogists. I fell right into that trap yesterday, following the wrong Rudolph, son of the wrong August.

I found what seemed like Rudolph's family, but missing Rudolph, only to be told that while the husband and wife's names matched, the birthplace, immigration year, and occupation did not match what his descendant knew to be true and had thoroughly documented.

Multiple, agreeing sources let you know you've got things right.

There's a reason why everyone tells you start your family tree with yourself and work your way up. Once you get beyond the relatives you knew personally—such as your grandparents and their siblings—nothing is certain until you have an abundance of corroborating facts.

For example, if you're investigating a distant branch, such as the in-laws of your great great uncle, you probably won't have any first-hand knowledge of that family. To help ensure you're putting the right facts in your tree you'll need a few things:

• Your great great uncle's marriage record can give you his wife's name (let's call her June for this example), birth year, and her parents' names.
  
• Now you can look for June in census records, making sure to match the names you know and June's birth year.
  
• Once you find them you can search for the same family, possibly at the same address, in different census years, making sure the facts line up. There should not be too much discrepancy among the censuses when it comes to recorded immigration years, age, place of birth, and occupation. Since you know when June was married, you would not expect to find her with her family instead of her husband after that time.
  
• Before going too far with June's family, search for any military records for the man you've identified as her father. Check to see if the censuses closest to the military record match for residence, wife's name or number of children.

As I browse through my tree of 19,295 people, I can find a number of dubious facts that I know need further investigation. But you know what it's like. So many relatives, so little time.

Be careful with your genealogy facts out there.

Family Tree Maker is a registered trademark of The Software MacKiev Company. Ancestry.com and TreeSync are registered trademarks of Ancestry.com Operations, Inc.

POW: My Grandfather's World War I Experience

My grandfather Adamo Leone
(standing center) in World War I.

As a child I had a language barrier with my maternal grandfather. Adamo was a smiling, sweet man who didn't speak much and rarely in English.

He'd tell me in Italian to slow down or be quiet—with a smile on his face—but I don't remember him telling me stories.

I loved him unconditionally, but I knew nothing about him.

Perhaps the only tidbit of a story I had was that Adamo had been a prisoner of war during World War I, fighting for Italy, and that he was forced to eats rats to stay alive. That's all I ever heard.

With the 100th anniversary of World War I upon us, I've been thinking about my grandfather a lot, wondering where he fought, where he was imprisoned, and what horrible conditions he faced.

Some research into Italy's experience in World War I led me to the 1917 Battle of Caporetto in northern Italy. The battle was so devastating that 11,000 Italian soldiers died, 29,000 were wounded, and more than a quarter of a million were taken prisoner.

Adamo may have been among these prisoners.

The Austro-Hungarians who captured the Italians were unprepared to care for this many men. At least 100,000 Italian soldiers died in captivity. The men were kept in a large number of camps in places like Mauthausen (future site of a WWII concentration camp) and Milowitz, and they were dying from tuberculosis and starvation.

Adamo and family in America.

It's easy to imagine eating rats to stay alive.

The prisoners were doing hard labor in coal mines and stone quarries on a food supply of less than 1,000 calories a day.

Those who survived the camps until the end of the war were kept in quarantine camps by the Italian government so they could be interrogated and either cleared or prosecuted as traitors.

Adamo had come to America in 1914 to join a few of his cousins. He returned to Italy in August 1915, shortly after Italy entered the war. He did not leave for America again until February 1920, 15 months after the war ended.

I once heard that Adamo stayed with his parents in Italy for about two years, recovering from his captivity.

Imagine then making the decision to leave them forever to return to a better life in New York City.

It's easy to understand his sweeping this story under the rug. I'm just so glad he came back.

Why You Should Be Using the Free "Family Tree Analyzer"

In 2012 I had an idea for a genealogy program. I created a simple program called Census Taker to analyze your tree and produce a list of every person likely to be found in the newly released 1940 census.

It worked great for me, but it was limited. I studied Java programming, hoping to make the program better. I began rewriting my program, but time after time I ran into problems.

Then, suddenly, I found something in a Google search. A free program called Family Tree Analyzer that does everything I wanted my program to do—and a million times more. Goodbye, my fledgling programming career!

Programmer and genealogist Alexander Bisset makes it easy to analyze your family tree.

Family Tree Analyzer analyzed my 18,946-person tree without blinking. It provides a detailed table of each individual's facts in a flawless format that looks eerily like what I was struggling to do with my program.

The "Individuals" table helps you see what you're missing and plan your genealogy research accordingly.

It found every possible data error in my file. It found potential duplicate people. It let me export everything to a spreadsheet so I can fix the problems.

One small piece of what it does is like my Census Taker, but way better.

The Treetops button shows you the eldest person (or people) in your tree with a given surname. I entered my maiden name of "Iamarino". The Iamarinos at the top of 2 branches were born in 1640 and 1710. Awesome.

The Locations, Occupations and Sources tabs show how many people are associated with a particular source, place or job. I'll use it to find typos or places where I want to make the wording more consistent.

I've barely scratched the surface, but I strongly recommend you try this program. Family Tree Analyzer can provide you with all kinds of analysis to help you fortify your family tree.

Find out what else you can do with this free software:

• Use This Tool to Discover Family Tree Insights
• Run This Genealogy Report To Help Clean Up Your Dates
• How to Find Errors in Your Family Tree
• How to Handle the Unrelated People in Your Family Tree