Drawing Inspiration from the Genealogy Pros

Do high-profile genealogists inspire you to do better family tree research?

If this sounds like I'm writing a grade school assignment, stick with me.

The genealogy professional I find most inspiring is Megan Smolenyak Smolenyak. She's a key researcher behind my favorite genealogy shows, "Who Do You Think You Are?" and "Finding Your Roots". She's an author and the former Chief Family Historian at Ancestry.com.

Megan works to identify the living descendants of deceased military personnel. She helps get the remains of these service members back to their homes.

Ms. Smolenyak also solves the mysteries of unclaimed bodies in the morgue. Finding living descendants is hard! You can watch a well-produced video to get a feel for Megan's work.

Megan's work with fallen military personnel reminded me of a website in my Favorites list. It's a database of Italian soldiers who died in World War I. There's another site for soldiers who died in World War II.

Long ago I searched for any Italian soldier with my maiden name who died in the first world war. I found only one: Alfonso Iamarino, born in my grandfather's hometown of Colle Sannita on 15 Feb 1892.

Alfonso's birth record and military record led to a ton of names, and our relationship.

Finding living people is hard. But I should be able to identify this soldier's ancestors and siblings. My goal was to see where Alfonso fits in my family tree.

The fallen soldiers website tells me Alfonso's birth date and his father's name. The collection of the town's vital records sitting on my computer will make it easy to find his relatives.

But how will I find his relationship to me? Step by step.

Initial Facts

In 1892 when Alfonso was born, his father Pasquale was 30 years old. His mother Orsola Marino's age is not stated.

Since Pasquale was 30, I looked for and found his birth record in 1862. It even says at the bottom that he married Concetta Orsola Marino on 21 Dec 1889. I'll be sure to search for Alfonso's siblings later. But I want to go up his tree first.

Pasquale Iamarino's parents were Nicola Iamarino and Concetta Zeolla. The 1862 birth record said his parents were both 40 years old. But I couldn't find Nicola's birth record.

Don't know when a couple got married? Work your way back to their first baby.

Searching Sideways

Since I couldn't find Nicola's birth record around 1822, I needed more information. If Nicola and Concetta were 40 in 1862, they should have several older children.

I checked the index of births for each year, going backwards from 1861. Nicola and Concetta's ages were so inconsistent! I found these babies:

• Michele Arcangelo Iamarino, born 5 Apr 1859
• Francesco Saverio Iamarino, born 19 Jan 1857
• Giuseppantonio Iamarino, born 19 Feb 1852
• Antonio Iamarino, born 13 Nov 1850
• Angelantonio Iamarino, born 2 Apr 1849

I couldn't find any babies born before Angelantonio. It was time to search for Nicola and Concetta's marriage record.

I found them quickly. They married on 21 Feb 1848. The marriage records should include their birth records and their parents' names.

I found Concetta's 1824 birth record. But Nicola was different. Instead of the usual birth record, there's a 2-and-a-half-page document in hard-to-read handwriting. After staring at it for a while I was able to read it.

It says, in effect, "Oops! We can't find Nicola's birth record in the register. It isn't written there, and we don't know why. But we do know he was born in September 1819."

Family Tree Maker's color coding keeps me from overlooking these important relationships.

Making the Link

The unusual birth record for Nicola tells me who his parents were, as does his marriage record.

And that's where I found a lucky surprise. Nicola's parents were Angelo Iamarino and Anna Elena Pozzuto. Those names were familiar to me because I'd been looking at them about an hour earlier.

It turns out Nicola's sister Liberantonia was married the same day as he was. Their documents are listed one after the other in the 1948 marriage register. An hour before I found Nicola's marriage record, I discovered that Liberantonia's grandparents were my 5th great grandparents.

That makes Libera my 1st cousin 5 times removed. Her brother Nicola is also my 1st cousin 5 times removed.

Suddenly I realized Alfonso Iamarino, the only Iamarino to die in World War I, is my cousin. Alfonso's 2nd great grandparents are my 5th great grandparents. Poor Alfonso is my 3rd cousin 3 times removed.

Hey. I like this. I'm ready to choose another fallen soldier from my ancestral towns and figure out how we're related. For those of you who are of Italian descent, be sure to bookmark these sites:

• Search for fallen soldiers from World War I
  
• Search for fallen soldiers from World War II
  

How do your genealogy heroes inspire you?

And speaking of finding someone's ancestors:

• 3 Ways to Find Your Ancestors in a Huge Pile of Documents
• How to Find More Great Grandfathers for Father's Day
• How I Gained 2 More Generations in 1 Day

Let Family Tree Analyzer Find Your Duplicates Duplicates

The duplicates in your family tree aren't as easy to find as that.

I've written about the free program Family Tree Analyzer many times. It's the work of programmer and genealogy fan Alexander Bissett. See the bottom of this article for links to other articles about this software.

Today I've installed the newest version of FTA, and I'm eager to find something else to explore.

I've looked at the many options on the Errors/Fixes tab before. But this time I'm focusing only on the Duplicate Fact and Possible Duplicate Fact options.

Be sure to try the Possible Duplicate Facts option in Family Tree Analyzer.

Hopefully your list of duplicate facts won't be too long. I have 7 duplicate facts and 65 possible duplicate facts in a tree of 21,001 people. That's a reasonable amount. I can look at each one and fix the error.

As I whittle down my list of duplicate fact errors, I'm finding they fall into these categories:

• Just plain forgetting that you already entered that fact.
• Accidentally choosing the wrong fact type, like Marriage instead of Marriage License.
• Adding the wrong date to a fact. This often happens to me with the 1940 U.S. census. It shows you someone's address on a date in 1940, but it also says if they were in the "same house" or "same place" in 1935. Sometimes I may paste in the 1940 date again instead of typing 1935.
• Attaching a fact to the wrong person. I have a married couple in 1800s Italy with the respectful titles of Don and Donna. I accidentally gave both titles to the husband!

The types of duplicates formed a distinct pattern.

And then there are some results that are not errors. Family Tree Analyzer does call them "Possible Duplicate Facts" after all. Here's where I'm seeing that happen:

• Duplicate marriage banns. In Italy, a couple might post marriage banns in the bride's hometown and the groom's hometown—on the same date. That looks like a mistake, but it isn't.
• The same type of fact with no date. There are cases where I entered 2 addresses for people, but I didn't add a date. I need to go back to the source and pin down a date.

I'm very satisfied with this exercise. These are the types of errors you'd never find on your own. It's great that Family Tree Analyzer can be another set of eyes for you.

Find out what else Family Tree Analyzer can do for you.

Here are some Family Tree Analyzer articles you may have missed:

• How to Find Errors in Your Family Tree
• Use This Tool to Discover Family Tree Insights
• One Report, Endless Possibilities for Improving Your Family Tree
• It's Time to Make Your Family Tree Clear and Consistent

Create a Genealogy Task List to Keep Track of Loose Ends

My 12-year-old task list is a big help to my genealogy research today.

As soon as I realize I can't find a document for a person in my family tree, I make a note. I want to document that fact that I searched for this record, but I couldn't find it.

If I add a note like this to someone in Family Tree Maker, I also add a bookmark to the person. The bookmark in the index of names is a sign that there's something about this person I haven't figured out.

An even better option is to add a task to this person in Family Tree Maker. Your task list is the first thing you see each time you open your family tree file.

Document those unfinished tasks and family mysteries. Some day you may find the answer.

If you don't use Family Tree Maker, look for similar options in your genealogy software. If all else fails, you can keep a text file of all the little family history mysteries you'd like to solve one day. You might want to list them alphabetically by the person's name, and add the date you recorded the note.

Let's look at one of my tasks and what I can do to solve it.

Teofilo Iamarino was my great grandfather's brother. The task I recorded for him 7 years ago is, "Did he stay in the US? Check for 1910, 1920 census." Let's see what I do know about my 2nd great uncle Teofilo:

• I have his Italian birth record from 1876.
• I have his Italian marriage record from 1896.
• I have his February 1909 ship manifest. He arrived in Boston, but headed to New York with my great grandfather and other relatives. My great grandfather came to America a handful of times, worked, and went back to Italy.
• I have Teofilo back in Italy for the October 1912 birth of his son. He has to have been in Italy since at least January 1912.
• I have his 1918 U.S. World War I draft registration card when he lived in Detroit, Michigan. The card says his nearest relative is his wife in Italy. I'm a little surprised that he had to register. He was a non-declarant alien who had no plans of becoming a U.S. citizen.
• I have him in Italy for the July 1923 birth of his daughter. He has to have been in Italy since at least October 1922.

Each document you find may be a clue that leads you to the next.

That timeline of known events tells me:

• He may have been in New York for the 1910 census.
• He may have been in Detroit for the 1920 census.

I'm not sure if I ever looked for Teofilo in Michigan, so I can check the U.S. census and include his Detroit address.

Nothing.

When I take out the Michigan address and hope to find Teofilo anywhere in 1910, I also get no results.

I can do a broad search for any documents I don't already have. I can leave off his last name and search for any Teofilo born in Italy in 1876.

Hurray, I found something new! I found Teofilo and 3 other men from his hometown arriving in New York in September 1913. According to the documents, he was in Italy in 1912. But he returned to New York for more work, leaving his wife to care for their young children.

In 1913 Teofilo returned to his brother Giuseppe's home in the Bronx. That's the same Giuseppe my great grandfather often returned to. It's the same Giuseppe my dad lived with as a toddler.

But wait! There's more. On the ship manifest, when asked if he had been in the U.S. before, Teofilo says yes, he was in New York from 1909–1911. That bit of information goes straight to the question I've been trying to answer: Was Teofilo in the United States for the 1910 census? If this ship manifest is right, then yes, Teofilo should have been in New York for the 1910 census.

I don't know why he's in Detroit, but now I know when he was in New York.

Teofilo's brother Giuseppe has no boarders living with him in the 1910 census. It's only Giuseppe, his wife and daughter. Is Teofilo in another household nearby?

I can return to Giuseppe's 1910 census online because I always note exactly where I found an image. I can go page-by-page looking for Teofilo.

I love paging through a Bronx neighborhood in the census. I recognize most of the last names. They're names from my ancestral hometowns, or they're names of my parents' friends and neighbors.

Unfortunately, Teofilo was not in that 56-page census collection. But I can look at other collections that are in the same general neighborhood. The important thing is, I now have reason to believe Teofilo is there.

Before I look for more documents, I want to check out the other townsmen with Teofilo on that ship in 1913. One of them, Francesco Pozzuto, is a good fit with someone in my family tree. He may be the father of a woman who is a critical DNA match. She and her son are DNA matches to both my father and my mother. I'm adding a note and a bookmark to him right now.

This example shows the value of creating these tasks or bookmarks. Years can go by. Without that note, I wouldn't have realized I needed to do more research on Teofilo Iamarino. There are literally 21,000 other people in my family tree.

But today I felt like looking at my task list in Family Tree Maker. And I wound up discovering a ship manifest for Teofilo with a very important clue.

Genealogy is a long game. Leave detailed notes for future-you whenever you can.

How to Make Your Sources Clear and Accurate

NOTE: There is a way to make your sources indisputable. Please see "Taming a Tangle of Source Citations."

Don't practice smash-and-grab genealogy. Make this method an unbreakable habit.

Seventeen years ago. That's when I graduated from scribbling in a notebook to building a family tree on my computer. I've had Family Tree Maker and an Ancestry.com subscription since 2002.

From the start, I never liked the option of saving a fact or a document to my family tree on Ancestry.com. I hated the ridiculously long source citations it added to my tree. I wanted my sources to be clear and easy to understand.

Because I run a tight ship, I have 275 sources in my Family Tree Maker file. And I have 20,963 people at the moment.

Here's how I keep my sources neat but thorough and retraceable.

Once I found the citation detail and citation text on Ancestry.com, it became too easy. I had to do it.

One Name to Rule Them All

When I started building my family tree, most of my sources were census pages and ship manifests. I didn't know what other people were doing. I only knew I wanted clarity. So my census source titles are as simple as can be:

• 1900 U.S. Federal Census
• 1910 U.S. Federal Census
• 1920 U.S. Federal Census
• 1930 U.S. Federal Census
• 1940 U.S. Federal Census

If my tree has that the source of a person's address as the "1930 U.S. Federal Census," there's no mistaking where it came from. It doesn't need to say, "United States of America, Bureau of the Census. Fifteenth Census of the United States, 1930. Washington, D.C.: National Archives and Records Administration, 1930. T626, 2,667 rolls."

But a simple source title does not give us everything we need in our family tree. Behind the scenes, we need all the information. We need an absolute way to get back to the source. We need a link to the proof of each fact in our tree.

Fill in these details for the main source, not for each fact or document.

More Details Under the Hood

Family Tree Maker has a Sources tab where you can see and control all your sources. I've gone down the list of source titles looking for a few things:

• Are people attached to this source? If not, I can delete the source. Maybe it belonged to people I've removed from my family tree.
• Are there duplicate or very similar titles? If I decide to merge a couple of sources, I have to update each person with a fact linked to the source I want to merge.
• Does each source have a clear title, citation details, a web address, and a repository?

If a source needs more detail, I go look it up. For example, I'll look up the 1915 New York State Census on whichever website I prefer. It can be Ancestry.com, FamilySearch.org, or any of the other official sites you may use. (Yes, it may be in a book, too.)

Instead of going to a particular document or record, go to the top-level page for that collection. On Ancestry.com, that page has the source citation detail and text, the exact name of the collection, and its URL.

These extra details make your family tree research more reliable.

Add enough details to each image to allow anyone to find it for themselves.

Specific Micro-Details Where They Count

I want each document image in my tree to show exactly where it came from. It should tell anyone who's looking at it how they can find the original.

On the image of a 1920 ship manifest, for example, I added a breadcrumb trail to the description.

If you view this immigration fact in my tree, you'll see only the source title: "New York, Passenger Lists, 1820-1957". But the image itself has a description. And that gives you everything you need to know to find the original image file:

• Line number(s). For a ship manifest or census form, I note which line number(s) to look at.
• Source title. This is the exact name of the collection as seen on Ancestry, FamilySearch, or wherever. This will match my source title mentioned above.
• Location of the film. Most of our genealogy documents exist on a roll of film somewhere. If I were trying to find that roll of film in a drawer at an archive, where would I look? This is always shown beneath the source title on Ancestry. For example, Roll > T715, 1897-1957 > 2001-3000 > Roll 2853. Or Wisconsin > Milwaukee City > 14 > Draft Card S.
• Image number. If I asked you to go to John Stefaniak on a roll of Milwaukee, Wisconsin draft registration cards, it'd still take you a while to find him. So I include the image number. For example, image 664 of 973.
• Web address. Sure, a URL may be different today than it was 5 years ago. But maybe it won't change for decades. And if it does, the film location and image number are even more important.

If you haven't been capturing these details for your documents, you may feel overwhelmed. Don't feel that way. Make it a habit going forward. Add a chunk of this annotation work to your annual genealogy goals. I finished all 630 of my census documents, but I have to go back and fix many of my 365 ship manifests.

The name of the game when it comes to your family tree's sources is usefulness. Each source should be useful in these 3 ways:

• Understandable. Anyone can see where your information came from in general.
• Retraceable. Anyone can follow your breadcrumbs to get to the original document collection.
• Specific. At the document image level, anyone should be able to see exactly where this one unique image came from.

Make this a mandatory part of your fact gathering from now on. Don't just get the image and put it in your family tree. Don't just add the facts and let the image serve as your source. Gather all the facts about your source and record them where they belong. Right away.

Doing it right, from the start, makes the whole process much easier.

And speaking of sources:

• Do These 3 Things Before You Add Another Name to Your Family Tree
• 3 Housekeeping Tasks for a Professional-Quality Family Tree
• 6 Easy Steps to Valuable Source Citations

4 Quick Family Tree Clean-up Tasks

Keep these in mind each time you work on your family tree and do it right.

Here are 4 things you can do to make your family tree better and more professional. Think of this list as a mental break. These tasks don't take a ton of thought, and you can tackle them when you're:

• frustrated by a brick wall in your family research
• bored because there's nothing good on TV
• trying to avoid doing your chores
• unable to decide which of your dozens of branches you want to work on.

(c) Can Stock Photo / rawf8

1. Add Missing Birth Dates

Does your family tree software let you sort everyone in your tree by birth year? If so, you can easily see who's missing a birth date. If not, scan your entire list of people, looking for gaps in the birth column.

It's much easier to make smart choices—and avoid errors—if you have a rough birth year for everyone. For example, you'll never attach a child to a set of parents if you see their birth years are 80 years apart. And what if you have several people with the same name? You'll never mistake the one born in about 1750 for the one born in about 1900.

Follow one of these 3 rules to give people an estimated birth year:

• If you know their spouse was born in 1860, give this person the same approximate birth year: Abt. 1860.
• If you know when their child was born, you can assume the parent may be 25 years older than their first child. Carolina was born in 1790. I don't know when her parents Angelo and Libera were born, but I can estimate it was 25 years before Carolina. I'll give them the birth date of Abt. 1765.
• If you know when someone's parents were born, you can assume the child is 25 years younger than the mother. Giuseppe was born in 1915, and his wife Serafina was born in 1921. I don't know when their son Joseph was born. I can estimate it was when Serafina was 25. I'll give Joseph a birth date of Abt. 1946.

These estimates may be off by 20 years or more. For example, what if Joseph is the 5th child of Giuseppe and Serafina? He would have been born well after 1946.

But the estimates are going to be useful to you.

Note: I do NOT add a source to an estimated birth year fact. There is no true source. This also signals to me that I used my own rules to estimate this fact.

These simple rules make it easy to add estimated birth and death dates and places.

2. Give Everyone a Real Name

Sort all the people in your family tree alphabetically by last name. Are all the same-named people listed together? Or have you given people fake names that make sense only to you? Anna "Jason's-Wife", Antonio "Greco the Father", Antonio "Greco the Son".

Let your family tree display speak for itself. When we see father and son Antonio Greco in your tree, it's obvious which is the father and which is the son. (It'll be even more obvious when you replace blanks with estimated birth years.)

You can always add your hints to a person's notes.

When I know someone's first name but not their last name (or the opposite), I used to use the word Unknown. It was a placeholder for their missing name. Then I saw a comment by chief Ancestry.com genealogist Crista Cowan. She draws a blank (5 underscores) for the unknown name. "Aida Unknown" becomes "Aida _____". "Unknown Davis" becomes "_____ Davis".

I do think this looks neater and its meaning is unmistakable. But when viewing my list of all individuals in my family tree on Ancestry, the blank last names don't show up in the list. I can search for an individual, like Aida _____, but I can't see all the unknowns at once.

If this matters to you, you might prefer to use Unknown (or another word) instead of _____.

Having real names and a standard placeholder name makes your family tree more professional.

3. Use Approximate Death Dates

I have a TON of people in my family tree with no death date. Here are 3 reasons to enter an estimated death date or a date range.

• Findability. Let's say someone was born about 100 years ago. You don't have a death date for them. That person will be private on Ancestry.com and assumed to be living. If you'd like to help your distant cousins find you through your tree, make those dead people dead.
• Note to Self. I haven't found the death record for my 3rd great grandfather, Teofilo Zeolla. But I do know he was dead when his grandchild was born in 1868. So I can estimate his death date as before the baby's birth date: Bef. 14 Aug 1868.
  
  Better yet, I know he was alive when his youngest child was born in 1859. I can narrow down my search for his death record by recording his death as between his last child's birth and his grandchild's birth: Bet. 20 May 1859–14 Aug 1868.
• Exclusion. You can avoid unnecessary searches by noting a date by which someone died. Let's say you have a couple named John and Mary. You learn that Mary died sometime before her young child Ann died. Make note of that, and you'll know better than to search for more children born to John and Mary after that date.

4. Enter Assumed Birth and Death Countries

I started doing this so I wouldn't get so many impossible hints. No, Ancestry, my 3rd great grandfather was not in the 1830 United States Federal Census. He was born and died in Italy too early to have come to America for a while.

This also keeps Family Tree Analyzer from telling me I need a census for someone who only ever lived in Italy. (See "This Genealogy Report Shows You What's Missing".)

But I'm conservative with this idea. I don't assume an ancestor born in the 1750s was born in the same town as his descendants. I do assume he was born in the same country. All my ancestors born before 1899 were born in Italy. They didn't move around much. A man might marry a woman from the next town, but not the next country.

I always have this task in mind when I add an estimated birth or death date. Put the country in, too. It's a much safer assumption when the ancestor lived hundreds of years ago.

So don't get frustrated and take a break from genealogy. Make your tree better in these 4 important ways.

And speaking of clean-up tasks:

• How to Handle Foreign Words in Your Family Tree
• Your All-in-One Family Tree Clean-up List
• It's Time to Revisit and Improve Your Earliest Family Tree Research

3 Ways to Keeps Strangers Out of Your Family Tree

Name 3 reasons why you're positive this man belongs in your family tree.

I started this blog out of some frustration. Someone stole my grandfather and added him to their family. They didn't care that he was from the wrong part of Italy and had a well-documented family. They put him and my grandmother in their tree.

But it happens. When you step out a little further onto a distant branch of the family tree, the names are less familiar. It gets easier to make a mistake.

So what are the best ways to avoid adding the wrong person—and everyone attached to them—to your family tree?

Here are 3 smart ways to make sure you're adding the right people to your family tree.
©Can Stock Photo / leonidtit

1. Compare All the Facts

Let's say you find a man in a census document. His name matches the missing son you're trying to find. You don't know who he married. You only know he isn't with his parents anymore.

How do you know he's the right man?

Take the time to compare all his facts to the person you want him to be.

• Do his age and place of birth fit your family?
• Does he have a job that would be impossible based on what you know about him?
• How many years has he been married, and does that make sense based on what you know?

Consider all the facts on the document you found. Are you sure you've got the right person?

2. Follow the Person Through Time

Imagine you're trying to find the death date for a man in your family tree. You find 2 men with almost the same name. One man served in the Army and is buried in a military cemetery. The other man has almost the same birth date. But his Social Security Death Index has a different death date than the veteran.

How do you know which one is your guy?

The answer is to research both men. Follow them through time. Find them in the census. Find their military record. If you can find their burial site online, who is buried next to them?

Research both men with the goal of ruling one man out of your family, as much as ruling one man into your family.

Check and compare all available facts. Are they the same person?

3. Check Other Family Trees

I wouldn't rely on someone else's family tree any more than I would rely on their hand-drawn map of the world.

But you can check other people's trees for corroborating evidence. Let's say you're wondering if this person with limited documentation belongs to you. You find 5 family trees that have him, and they all firmly place him in a family you don't know. That's a lot of evidence that he's not yours.

You can use other people's research to decide to pass on this particular person.

You probably have some unrelated people in your tree by accident. You didn't do it because you don't care about getting the facts right. You did it because this person is way out there on a distant branch. You're not invested in him. You grabbed him on the way to find someone else.

And speaking of unrelated people:

• 2 Reasons to Add Unrelated People to Your Family Tree
• How to Handle the Unrelated People in Your Family Tree