An End-of-Year Tune Up for Your Family Tree

The end of the year is a perfect time to give your family tree a thorough check for errors. How many times during the past year did you:

• Add a person without checking if their birth date fits in with their parents and siblings?
• Change the way you record a particular fact, like someone's nickname?
• Accidentally attach a marriage date to the first spouse instead of the second?
• Update a person's birth year without changing their parents' estimated birth years?
• Attach a census fact to the youngest child in the family who wasn't born yet?

All kinds of human errors can happen while you're caught up in the genealogy zone. I generated two reports to find errors in my more than 33,000-person family tree:

• In Family Tree Maker, I ran the Data Errors Report.
• In Family Tree Analyzer, I opened a brand new GEDCOM file to look for the usual types of errors. If you don't use Family Tree Maker, create or download a GEDCOM file of your family tree. Then open it in Family Tree Analyzer and check out the error list.

Human error will always creep into your genealogy research. Here are 2 reports that will find the mistakes in your family tree.

I saved the Family Tree Maker report as a very long PDF file. It's long because it lists "The marriage date is missing" each time I don't know a couple's marriage date. That isn't an error. These early documents aren't available, so I'm ignoring that message.

The report also thinks it's an error when a husband and wife have the same last name. It isn't. I use only maiden names for the women in my family tree, but sometimes a Marino marries a Marino. What're you gonna do?

Here are the errors from the Family Tree Maker Data Errors Report that I'm fixing in my family tree:

• The birth date occurred before his/her father/mother was 13. This happens when new information changes my estimated birth date for a person. Let's say I add a person to my family tree with a birth year of 1800. If I know their parents' names, I give them an estimated birth year. My rule is to say the parents are 25 years older than their oldest child—until I find hard facts. So I'll give the 1800 baby's parents an estimated birth year of "Abt. 1775." But what if I discover that baby was born in 1782? If I don't redo the math for the parents' estimated birth year, I'll have a "parent too young" error.
• The birth date occurred after his/her mother was 60. I have two very large families where the children's births spanned way too many years. In one case, the oldest child was so much older than the rest that their birth year had to be wrong. I had to look at their children, too, to make sure I used a valid date estimate.
• The birth date occurred more than one year after his/her father died. This happened with people born in the 1700s. All I could do was adjust the child's birth year to the year their father died.
• The birth date occurred more than one year after his/her mother died. Same problem as above.
• Baptism date occurred before individual's birth date. This was my typo, and I' glad the report pointed it out.
• The individual was married before the age of 13. Unfortunately I have a couple of cases where that's true.
• The marriage occurred after the death date. A man's wife died before him, and I marked his death date as After her date. Then he remarried, and I forgot to delete that death estimate.

These reports will find conflicting facts in your family tree.

• The marriage occurred after the spouse's death. I must have given a marriage date to the first spouse instead of the second. It's too easy to make that mistake.
• Event immigration (or divorce or marriage) contains no data. I can't explain how some of these happened, so I appreciate this safety net.
• This individual's children sort order may be incorrect. I thought that was automatic. I may have clicked the wrong button on this family.
• Person does not have a preferred spouse set. Somehow I added marriage date without adding a spouse's name.
• The birth date is missing. These are living people I added recently. I don't know how old they are, so I'll have to add estimates based on their parents' ages.
• The name may include a nickname. I had a man's nickname in parentheses with his name. Now I've changed the nickname to an alternate Name fact.
• Residence date occurred before individual's birth date. The 1940 census says where the family lived in 1935. It may be the same house or the same place/town. Twice I gave the 1935 address to kids born after 1935. Now I've deleted those residence facts.
• The age at death is greater than 120. This is usually not an error. If I don't have a document to tell me when someone died, but I know they were dead when their child died, I'll say they died "Bef. [the child's death date]." This error report isn't taking the "Before" into account.
• The burial date occurred before his/her death. This was my typo, but yikes! What a thought.

Find those troublesome families in your family tree with one of these genealogy error reports.

When you're working in Family Tree Maker, the software will make an alert sound if:

• You add a baby to a parent who's too young, too old, or too dead.
• A bride or groom is under the age of 13.
• A husband and wife have the same last name.

I appreciate those warnings—except for the last one. But if you update someone's birth date later, you may not get the warning. That's what these reports are good for.

Give your family tree an error cleanse before the new year. Start off 2022 with a cleaned-up, fine-tuned, fortified family tree.

What You're Losing With Your Private Family Tree

My family tree software almost gave me a heart attack. I routinely make a backup of my Family Tree Maker file after working on it for a while. It's not uncommon for me to make 3 or 4 backups in a long day of research. Then I close and compact my file before I synchronize any changes with Ancestry.com.

Still, there's a feeling of dread when my file takes to long to respond. Last week the FTM program stopped dead. I'd opened my family tree file to make one change and output an updated family tree chart. I began clicking my way up the generations, trying to get to the eldest Ohama in my husband's family tree.

But I couldn't click anything! Nothing was responding. I decided to leave it alone and do something else for a while. But the program was still stuck. After an hour, I held my breath and killed it.

When I relaunched Family Tree Maker, I saw the expected error message. I clicked Continue. I was confident I'd made only one edit that day, so I restored my tree from the full backup I made the day before.

Everything was fine! I repeated the change I made earlier and output that family tree chart I wanted.

Why do I stick with Family Tree Maker when it can cause me so much worry? Because I can share my up-to-date, uneditable family tree with every member of Ancestry.com. I want people to find my research, but I don't want them to change it. The shared trees of Family Search, Geni, and elsewhere are horrifying to a control freak like me. Plus, Ancestry has the best interface for viewing a family tree.

Share your family tree on a big stage for your own benefit.

I've been building two other family trees lately that I'm not sharing online. One is for my son's girlfriend and one is for my college roommate. These trees don't belong online because I wasn't asked to share this information.

But my enormous family tree is another story. When the Italian government started posting vital records online in 2017, my genealogy goal changed.

I'm not satisfied with documenting my direct ancestors and cousins. I want to connect everyone from my ancestral hometowns. I don't care if someone is the mother-in-law of the 2nd husband of my 1st cousin 5 times removed. She's from one of my towns and has a connection to me. She belongs in my tree.

Strangers often thank me for the people, facts, and documents I've put together for their family. Sometimes they turn out to be a DNA match to my parents or me.

When all goes well, I can build onto my new contact's branch of the family. I can follow their ancestors to America, picking up what might otherwise have been a dead end. Sharing your family tree is the surest way to open up those dead ends.

The latest person to write and thank me for his ancestors turns out to be my 5th cousin once removed. Just knowing who my mom's 5th cousin is blows my mind. Thank you, internet.

This week I'm gathering vital records for his ancestors, adding them to my family tree, and sharing them with him on Ancestry. To me, this is the ideal collaboration. Don't touch my work. But let's work together. We can benefit one another.

You can talk to me all day long about your preferred family tree software. But nothing compares to the combination of Family Tree Maker on my desktop and Ancestry.com.

How to Find the Stragglers in Your Family Tree

I'm living in my 16th home, so I know a thing or two about moving. To lighten the load before you pack, you sort your stuff into three categories: keep, sell, or throw away.

We can use a similar rule on our family trees. I generated a list of unrelated people in my family tree. I fit each person into one of three categories: research, keep, or delete.

This started when a Family Tree Maker user asked how to find the loose (unrelated) people in her family tree. One person answered "Family Tree Analyzer" without an explanation. I launched my copy of the program and answered with these instructions:

Family Tree Analyzer is a free program that can analyze your tree in many ways. Export a GEDCOM from your tree and open it with Family Tree Analyzer. Once it's open, click the Main Lists tab and view the Individuals tab (the first tab). Scroll to the right to find the Relation column and click to sort by it. The "Unknowns" are your loose people.

I did this and exported my full list of people to a spreadsheet. Then I sorted and deleted everyone who did have a relationship to me.

Take a fresh look at the unrelated people in your family tree.

Now I had a spreadsheet of all the unrelated people in my family tree. I set out to categorize them as research, keep, or delete. I added a new column to my spreadsheet with the heading "Reason." As I worked my way down the list of alphabetized names, I added the reason they're in my tree.

For example, I had dozens of disconnected people with the last name Asahina. They're in my tree because of an undocumented connection to my husband's Ohama family. In the "Reason" column, I gave each of these people "Asahina" as the reason they're in my tree.

Other people are in my tree because my family says they are cousins, but the documents don't exist. I gave them a last name as a "Reason." They are either Saviano (my great grandmother's maiden name) or Sarracino (my great grandfather's name).

Now that everyone in the list had a particular reason to be there, I sorted the spreadsheet by the reasons.

• Some people were from my grandfather's hometown. I worked with vital records to figure out their connection. I had lots of success and deleted them from the spreadsheet.
• A couple of families were in the published 1742 census for my grandfather's town. I did some research, but I couldn't find a bridge between the civil records and 1742. I decided to keep these 12 people anyway.
• There were a few families of three: two parents and a baby. I searched for more of their children. Unfortunately, all the children died young. Without a marriage to build on, I could not connect this small family to anyone else. I deleted them from my family tree and the spreadsheet.
• When it came to the Asahina family, my own notes for two different people gave me the connection I was seeking. The story is, an Ohama family gave one of their babies to a childless cousin. As shocking as that sounds, it's a Japanese tradition. My own father-in-law was nearly given away! In the Ohama family, I'd entered a baby named _____ Asahina with a note saying, "this is the baby they gave away." In the Asahina family, I had attached a note to a woman named Masa Asahina. "A distant cousin says Masa is the Ohama baby given to the Asahina family." Hurray! I merged _____ Asahina with Masa Asahina, connecting the entire family. I removed them from my spreadsheet of unrelated people.
• I tried again to connect a Saviano clan to myself. The family says they are cousins, and I have no doubt of that. But their hometown didn't keep civil records before 1861. Their church records are lacking, too. I added some new documents and facts, but they are still loose in my tree. I will keep them there.

My family tree still has 161 unrelated people I've chosen to keep. Twelve are from the 1742 census of Grandpa's town. The rest are from the town without documentation. I'm OK with that. They all have a now-documented reason for being in my family tree. I'll be on the lookout to see if any distant cousins know more about them than I do. So far, they don't.

In the end, I researched everyone in the list to some extent, deleted a bunch, and kept 161 people. And that's how you sort out and lighten the load before you move on to more research.

If you use Family Tree Maker, use these settings to find the unrelated people in your family tree.

Someone else had a different answer to the "how to find loose people" question. They recommended Family Tree Maker's Kinship Report. With 29,000+ people in my tree, the report takes about 30 minutes to run, and it's 979 pages long. I can export to a spreadsheet by clicking Share, Export to CSV. Then, in Excel, I can filter the results to show only the "Unrelated" Relationship.

I recommend you go with Family Tree Analyzer for quick, useful, effective results. Then get moving and sort out your people.

How to Plug the Holes in Your Family Tree

Bringing a photo of my great grandmother Maria Rosa to life motivated me to do a ton of genealogy work.

I have all the available vital records from her Italian hometown on my computer. I worked hard to rename each file with the name of the subject. Looking at my Family Tree Maker file, I searched the records for all my great aunts and uncles on Maria Rosa's line. (I use a free program called Everything to locate any name in my collection of renamed vital records. It's the best tool you've never heard of.)

For each new great aunt and uncle who married, I added:

• their spouse's name, birth date, and parents.
• their marriage date and place.
• all the couple's children.

I sped up the process by adding all the facts to my family tree without the document images and their citations. I can go back and add those as needed, thanks to my process and the Everything program.

I added several hundred people from Maria Rosa's hometown to my tree in no time! I see this monumental task as the ultimate "Cousin Bait". I must be adding connections to other genealogy fans' and DNA matches' family trees.

Fixing a Hole

Working this fast can lead to gaps. I may go far up a bride's family tree and forget to go back to the groom. I thought I'd better do a spot check and look for the research holes I'd left behind.

Enter Family Tree Analyzer (FTA)—the best software for finding and fixing errors in your tree. And it's free.

Here's how to use FTA to find those information holes:

• Export a GEDCOM from Family Tree Maker (or wherever you build your family tree) and open it in FTA.
• Go to the Main Lists tab of FTA and see the first tab, Individuals. This shows all the facts in your tree.
• Click the BirthDate column to sort all your people by this date. Instead of blanks, you'll see the word UNKNOWN.
• Go to any person with the UNKNOWN birth date in your family tree. You should see that you are, in fact, missing their birth date.

If you still can't find their birth date, you must give each person an estimated birth year.

Everyone in your family tree needs at least an estimated birth year. You're bound to have lots of people with the same name. An estimated birth year will prevent you from adding a 17th century father to a 19th century child.

I have a few rules for choosing an estimated birth year:

• If you know when their first spouse was born, mark them as being born about the same year. (Abbreviate "about" as Abt in your tree.)
• If this makes a woman much too old to have given birth to her children, adjust her estimated age down. You shouldn't make her more than 45 years old or so when she had her last child.
• If you know when their first child was born, estimate them to be 25 years older than the child.
• If you know when their parents were born, estimate them to be 25 years younger than their younger parent.

Finding More Holes

After fixing your unknown birth dates, go back to Family Tree Analyzer. Sort the Individuals list by DeathDate. Of course, lots of people in your family tree are still alive. You may have tons of UNKNOWN listings, many of which you are correct to leave blank.

I found it helpful to sort by the LifeSpan column. At the bottom of the list I have lots of people with a lifespan of 110 years or more. That means I haven't searched for and found their death records.

Thanks to the online Italian vital records, I can find a death record for most relatives born in the late 1700s. I'll choose a few from the list in FTA and search with Everything to fill in some holes.

But Wait! There's More

If you've been a careful genealogist and don't have a ton of missing dates, here's something else to try.

Sometimes a name is missing only because you haven't done the right search yet.

Sort your FTA Individuals list by Forenames. How many first names are you missing? (Note: I record missing names as an underline: _____, so that's what I see in FTA.)

I have a 1st cousin twice removed named Maria Pilla who was born and married in Italy. She and her family came to America, and I found several U.S. records for them. But I never found her husband's first name. After a quick search for Maria Pilla, I realized I had their 1941 marriage record sitting on my computer. Now I know his first name and birth date, his parents' names, and that his mother was my 4th cousin 3 times removed.

Then, of course, there are the UNKNOWN Surnames. These may be all the women whose maiden names you haven't found. Let this list encourage you to give them another search.

Family Tree Analyzer is a great safety net.

If you're a busy genealogist, schedule a weekly checkup day with Family Tree Analyzer. It's available for PC and Mac at ftanalyzer.com. I'm inspired each time I launch it. You will be, too.

Family Tree Fun for Computer Geeks

I started a project in 2019 and said I would share it with you soon. It was harder than I thought, so I put it aside until now. The results are interesting to see.

The geeky background is this:

• In Family Tree Maker, I exported my latest GEDCOM file
• In Family Tree Analyzer (free), I imported the GEDCOM and exported a spreadsheet of all facts
• In Power BI Desktop (free), I imported the spreadsheet and built different views of my data

A few minutes into reviving this project, I noticed a friend's blog post on a similar topic. He showed all the pie charts he generated from his family tree on MyHeritage. I have only the most basic tree on that website, so I got back to work in Power BI Desktop.

In Power BI Desktop, I created graphs showing:

1. Last name occurrences in my family tree from most to least. Most of the last names in my tree (currently with 27,900 people) come from one town. That's no surprise. Years ago I pieced together my Grandpa Leone's town using 1809–1860 vital records. I added 15,000 people to my family tree.

I also see big numbers for last names from Grandpa Iamarino's town. The name Pozzuto is in the #1 position by far. That's because I made an effort to fit every last Pozzuto from the vital records into my tree. My maiden name is in 10th place because I've spent time pushing to find my closest Iamarino relatives.

Do you know what are the most common names in your family tree? This tool can tell you.

2. First name occurrences in my family tree from most to least. My family is 100% from southern Italy, from the region called Campania. I'll bet the most common first names in my family tree are almost the same as other Campania family trees.

The most common first names in my family tree are:

• Giuseppe
• Angelamaria
• Giovanni
• Antonio
• Francesco
• Domenico
• Pasquale
• Maria

3. Birth locations plotted on a world map. The Power BI software plotted every birth location from my family tree on a map. I love zooming into southern Italy to see how centralized my Italian ancestors were. Draw a straight line from the Bay of Naples to the spur of the Italian boot, and that's where my DNA comes from.

Almost any type of family tree data can be plotted to give you the big picture.

4. Ahnentafel numbers from 1 to 2,691. I created a chart using a custom field in my GEDCOM called Ahnentafel. (Each of my direct ancestors has their Ahnentafel number in this field in Family Tree Maker.) I put the numbers on both the X and Y axis of a scatter plot for an interesting visualization of the gaps.

I know almost all my direct ancestors up to Ahnentafel number 748. Then there's a sprinkling from 999 to 1,392. Finally, I have a gigantic gap with two stragglers at 2,136 and 2,691. It's exciting to see my progress this way.

5. Number of children per marriage. I made a pie chart for the number of children in every marriage in my family tree. More than a third of my marriages have only one child. I'll bet I'm missing a ton of kids. That sounds like something to work on. About a quarter of the marriages in my tree have between 4 and 14 kids!

What do you think is the average number of children per family in your family tree?

6. Drill-through by type of data. I'm familiar with this type of chart, but I never thought of using it for genealogy. I started with every individual in my family tree. Then I broke them down by last name. Then I broke each last name down by first name. I followed that with birth location, birth date, marriage date, and death date.

It may not be the most useful tool, but it is cool. I can choose any last name in my tree, then a first name and a birth place. I can click each one to see which facts I have in my tree.

This drill-through chart lets you follow anyone in your family tree through a series of events.

For instance, I can click my name of Iamarino, and then the most common first name of Antonio. Now I see all the locations where an Antonio Iamarino was born. Next I'll click the town name (Colle Sannita) where I have 7 Antonio Iamarinos. Next comes the birth dates of the 7 men. I clicked each one until I found an Antonio for whom I have all the basic facts: birth, marriage, and death dates.

If you'd like to see statistics for your family tree, you can:

• Get adventurous with the free Power BI Desktop program from Microsoft (reach out to me if you're really interested)
• Check out the tools on MyHeritage (see my friend's blog)
• Keep exploring the free program Family Tree Analyzer

A Safety Net for Reckless Family Tree Building

How ironic. Last time, I encouraged you to slow down and be more thorough in your family tree building. I'm having terrific results practicing what I preached. I've been checking every person in my tree with my maiden name. I'm gathering their missing documents. I'm fixing their sources. I'm updating my document tracker. It's awesome.

Then I thought I'd better have a quick look for new DNA matches. Next thing you know, I get swept into a marathon session of finding their ancestors, and working them into my tree.

By the time I came up for air, I'd added basic facts for about 30 people to my tree. Without any sources! Most of the people will be easy to fix. I entered their birth or marriage dates, so I can get their documents cropped and placed in my tree. The documents will help me make strong source citations.

Some of the names and facts rely on my DNA match's tree. I have no documentary proof yet. For them, I'll make a note in my tree and point to my DNA match's family tree online.

I finally stopped this feverish family building when I realized I had no idea how many people I'd added to my tree. How would I retrace my steps when I'd been jumping around among a few DNA matches?

Luckily, I recently learned something new about Family Tree Maker. Maybe this feature has always been there—hiding in plain sight. When you open your tree file in FTM and you're on the Plan tab, there's a place to create a task list. What I never noticed is that there's another tab next to Tasks called Change Log.

Does your genealogy program have this safety net?

The Change Log lists up to 1,000 of the most recent changes you made to your tree, and it timestamps each action. Right now I can see each action for the past 4 busy days. That's fine—I only need to see what I did today.

I printed the change log to a PDF. Now I can accurately and fully retrace my steps. I'll give each person their birth, marriage, and death records. I'll add a detailed note for facts that came from my DNA match's tree.

Almost a year ago, I made it a habit to save the "Sync Change Log" each time I synchronize my FTM tree to Ancestry.com. Much like the Change Log, this PDF details everything I did since my last sync.

Those files will save the day if something goes wrong with your synchronization or your file. The Sync Change Log is an option you'll see shortly after you begin the sync process. See "Log" below.

Make family tree safety a top priority. Start with an external hard drive.

Speaking of family tree safety, I make a full backup of my family tree file during and after each session. The backup files are very big because my tree is so large. I move them to an external hard drive each week during my Sunday computer backup routine. The sync log files are very small.

My safety routine is this:

• Backup: Make a full backup of the family tree, media files included.
• Compact: Close the family tree file, but not the software program. Compact the file (see the Tools menu), being sure to check "Perform extended analysis". Repeat, if needed, until the compact process reduces the file size by 0%.
• Sync: Open the family tree again and click Sync Now.
• Log: The Sync Change Log window shows you how many people, media, and citations you've changed. Click the View / Print Details button. This opens a file showing your changes since the last sync. Choose to Export As PDF, close the window, and continue the sync.
• Close: Give your tree a few moments after the sync is complete to process any media files. Then close the file before exiting the program.
• Backup: Make it a routine to back up all your family tree files to a safe location, like an external hard drive or two.

That's about as safe as you can be. After an unexplained sync crash last November, I made sure to be as careful with my family tree as I possibly can. Are you safeguarding your hard work?

One Man's Big Impact on My Family Tree

Revisiting a clean-up project instantly added dozens of relatives to my family tree.

In July I recommended using Family Tree Analyzer to find the unsourced facts in your family tree. For the steps, see Catch and Fix Your Missing Source Citations.

My report seemed to have a lot of false positives. Many facts in the list actually had proper sources in my family tree. Discouraged, I tried another method. I ran the Undocumented Facts report in Family Tree Maker. I exported the report as a massive Excel file. It's huge because I have 25,000 people in my family tree, and I don't add a source for a person's sex. So everyone made it into the report!

I spent time deleting lots of lines from that spreadsheet. Then I decided to revisit the report in Family Tree Analyzer. This time I excluded another fact type (Parental Info) before exporting it to Excel.

With a bit more fine-tuning, the report turned out great.

I realized I could cut out all the dates that I left unsourced on purpose. When I don't know someone's birth date, I give them an estimate. In your family tree software, you can type "About" or "Abt" when you're entering an approximate date.

If they are a parent, I make them 25 years older than their oldest child. If I know their spouse's birth year, I estimate they were born about the same year.

Since there can't be a source for my "About" dates, I don't need them in this report. I sorted the report by the Date of Birth column and removed every line where the date begins with "ABT" (for about). Now I'm down to about 114 lines in the spreadsheet. The Undocumented Facts report in Family Tree Maker produced a 45,000-line spreadsheet!

Diving into the New Unsourced Facts Report

The first few lines are for my young cousin-in-law. I have no sources for him, but later I'll see what I can find online.

I'd prefer to work on my 19th century Italian relatives first. The first one in the list is Lorenzo Capozza. In my family tree I see he was born in 1828 in my great grandmother's town of Pescolamazza. He married my 3rd great aunt, Nicolina Caruso, on 19 Apr 1856 in that town.

I must have been rushing along when I found this marriage fact. I didn't save the marriage record to my tree. I didn't chase down Lorenzo's birth date or parents. And I didn't add my sources. Bad genealogist!

Lorenzo was 28 years old when he married my aunt in 1856, so he should have been born in 1828. The marriage record says he was born in the same town, but something's wrong. I have all the town's available vital records on my computer. He isn't in the birth records for 1826 through 1829. I can keep searching each year's birth index, or I can go to the detailed records in the 1856 marriage documents.

Before I do that, the marriage record says Lorenzo's parents are Pietro Capozza and Maria Emanuele Pennuccia. I looked for them in my family tree.

One Man Makes His Mark

They're in there, along with their son Antonio, 5 grandchildren, 5 great grandchildren, and at least 12 2nd great grandchildren! I'd already pieced together a huge family for them from the vital records collection. But I never found Lorenzo.

Feel free to borrow this image.

But that's only part of the story. All the people related to Pietro Capozza and Maria Emanuele Pennuccia in my tree are UNRELATED to me. I've given them all my "No Relationship Established" graphic as a profile picture. (See How to Handle the Unrelated People in Your Family Tree.)

The moment I make Lorenzo the son of Pietro and Maria, all those people will be my relatives. The relationship is through Lorenzo's wife, my 3rd great aunt.

Why did I put this enormous unrelated family in my tree, you ask? It was an out-of-control case of mistaken identity! When my great grandparents married in 1906, a couple from her hometown were the witnesses. The male witness was Nicola Capozza—same last name as our Lorenzo. But he was from a different branch of the family.

I realized too late that all those descendants of Pietro and Maria were an unrelated family.

Until now.

With Lorenzo attached to his parents, all those people are now relatives. I have to remove the "No Relationship Established" graphic from each one. How tedious.

But I have a method I'd like to share with you.

This trick simplifies an error-prone task.

Here's how I handle a big change like that. I have that graphic attached to a large number of people, so finding all the right people in a list wouldn't be easy. What I do is:

• Click everyone in the family who needs the graphic removed, one at a time.
• Change their last name to begin with a 1. Capozza becomes 1Capozza. That makes it easy to find the right people in the list of who's attached to that graphic.
• Go to one person with that graphic and click to detach it.
• This brings up a list of each person attached to the graphic. I can select everyone whose name begins with 1.
• Once I remove the image, I rename everyone in my family tree whose name begins with a 1.

That may not seem like a big deal to you, but it's very helpful. I used to struggle with removing that graphic from the right person. A lot of the townspeople have identical names! I use a 1 so it's at the top of my index of all people—easy to find.

Now comes a much bigger challenge. All those new relatives need their vital records and sources!

Get into a Groove to Fortify Your Family Tree

We each have the ability to be thorough, organized genealogists. But we don't always have the time.

I'm going to show you my multi-step process (accent on the multi). I follow this routine for each document image I add to my family tree.

First, let me explain what prompted me to write about how I get my genealogy groove on.

I found 4 notes in my genealogy task list that I wrote a long time ago. These notes list details about birth records I need to add to my family tree. The notes include the person's name, birth date and place, and the URL of the document image.

When I compared the notes to my tree, I realized I had added the facts to each person, but not the birth record images. I must have been in a hurry that day.

Now that I'm looking at those notes again, it's time to complete each task and delete those notes from my task list. Here's what I need to do for each one (deep breath):

1. Go to the birth record stored on my computer. I have tons of Italian vital records downloaded from the Antenati website. I file them in nesting folders by province, town, and year/type of record.
   
   

   

   When you add to your task list, be specific so you can complete the task.
   

2. Crop the image and boost its contrast in Photoshop if needed. Export the cropped image to my "working" folder. This makes my in-progress images easy to find.
   
   
3. Edit the properties of the image file to include a title and comments. The title might be "1835 birth record for [Full Name]". The comments might be: "From the Benevento State Archives: [full URL of original image]". These facts stay with the image and get pulled into my family tree program.
   
   

   

   Adding information to the image itself helps in your tree and when you share the file.
   

4. Attach the image to the right person in Family Tree Maker and make it their profile image. (I don't have photos of my ancestors beyond most of my great grandparents.)
   
   
5. Edit its properties to include the date on the document. Note: I don't put the date in the file's properties because it doesn't carry over into my software.
   
   

   

   Not only do the image's facts get pulled into your tree, you can use them to create a source citation.

6. Select a document category. (I save birth, marriage, and death records as "Vital Records".) This may be a Family Tree Maker thing only.
   
   
7. Add each fact provided by the document to the person. That may include their full name, birth date, baptism date, place of birth, etc.
   
   
8. Add a source citation to each of these facts. The URL I attached to the image is critical to the source citation.
   
   
9. Add mention of this document to my Document tracker. I add a line to my spreadsheet for this person, if they aren't already in there. If I have an 1835 birth record image, I'll add this to the Birth column: "1835 (cert.)". The "(cert.)" tells me I have an image of the certificate. It isn't a fact pulled from somewhere else. It's the actual birth certificate.
   
   
10. Move the image from my "working" folder to my "certificates" folder. It sits there until I do my weekly computer backup. After the Sunday morning backup, I move it to the right sub-folder of "certificates". I have so many certificates that I break them up into alphabetical groups.

OK, now I see why I didn't have time to do this when I found the records.

Despite all the steps, I'm happy to do each one. I know that when I'm done, I'm completely done, with no loose ends dangling. It's all a matter of getting into a groove, making each step a part of your routine, and enjoying the results.

Pressed for time? You can either:

• Leave yourself a detailed note in your task list, or
• Get that document as far as your "working" folder (step 2 or 3) and come back to it later.

Think of yourself as a genealogy manufacturing production line. You are cranking out a piece of perfection.

A Startling Family Tree Discovery

I was working on a distant branch of my family tree, and I wondered what was my exact relation to this person. I used the Relationship Calculator in Family Tree Maker for a visualization.

The tool creates a stepping-stone trail from you (or whomever you choose) to any person in your tree. I thought it'd be fun to see the Relationship Calculator for my grandparents, Pietro Iamarino and Lucy Iamarino. They didn't both have the unusual last name of Iamarino for no reason.

I learned a few years ago that my grandparents were 3rd cousins. The Relationship Calculator in Family Tree Maker lists 3 relationships for my grandparents:

• Pietro is Lucy's husband
• Pietro is Lucy's 3rd cousin (they share 2nd great grandparents)
• Pietro is the nephew of the husband of the 1st cousins twice removed of Lucy

Of course I needed a visual aid to figure out that last relationship. Lucy Iamarino's grandfather had a 1st cousin named Libera Nigro. She married a relative in the Iamarino family. I recognized his name right away. He was the Uncle Joe my dad remembers from his early childhood.

Uncle Joe, or Giuseppantonio Iamarino, was the go-to relative in the Bronx, New York. When my grandfather's father came to America, he stayed with his brother Joe. When my grandmother's father came to America, he also stayed with Joe—his 2nd cousin!

I have a bit of unfinished research business with Uncle Joe. Years ago in the New York City Municipal Archives, I learned Uncle Joe had remarried in November 1928. I'd never found the death record for his 1st wife, Libera Nigro.

Now that indexed New York City vital records are online, I thought I'd search for Libera's death. Instead I found a death record for her daughter.

I have their daughter Giovannangela Iamarino's 1895 birth record from the Antenati website. And I have her 1903 ship manifest. It shows her coming to America with her mother (Libera Nigro) and brother to join her father (my Uncle Joe). Giovannangela, also called Jennie, is with her parents in the 1905, 1910 and 1915 censuses. I had no idea what became of her.

The shocking discovery of cousin Jennie's horrific death is tempered by the discovery of her husband: another cousin.

Until now. When I clicked that death record entry, I learned one key fact right away: Jennie had married a man named Piteo.

The index of her death record has several critical facts:

• It confirms her birth date, so I'm certain she's the right person.
• She was only 27 years old when she died on 18 February 1923.
• She's buried in St. Raymond's Cemetery in the Bronx along with the vast majority of my family.

It was the cause of death that threw me for a loop. The transcription is pretty bad (can't you at least spell kitchen?), but understandable. It says, "Difun Burns of Body (Accidental) Cloths Caughs Fin This And from Kithcen for Range."

Poor Jennie's clothes caught fire while she was cooking ("Cloths Caughs Fin," argh!). She died from burns to her body. Instantly, I pictured this scene in my mind. Was she lighting the stove with a match? Did the flames get too high? Did she use a mapina (dish towel) to beat the flames, but wind up spreading it to her own clothing? She must have been screaming. The entire apartment house must have heard her. Did anyone try to save her? Did she have a small child or children there with her?

But this story seemed familiar. I don't have contact with anyone who would have remembered Jennie. Did I really hear this before?

It was her son's U.S. Social Security Applications and Claims Index that led me further. It lists Jennie Iamarino as mother, Vincent Piteo as father. Their child, Serafino Vincent Piteo, lived to the age of 84 (I'm so glad!). He was born in January 1920 and died in 2004. He probably missed the 1920 census, but I found him with his dad in the 1930 census.

A random, unexpected path led me to a tragic discovery in my family tree.

Now that I had the name of Jennie's husband, I wondered where he came from. I found his World War I draft registration card on Ancestry. As I scanned the card for his place of birth, I nearly cried again. He's from the same town as Jennie and every Iamarino: Colle Sannita.

I realized I had his 1892 birth record in my possession. (See Collect the Whole Set.) Vincent's (Vincenzo's) mother is my 3rd cousin 3 times removed.

While I'm haunted by what happened to poor Jennie, I'm eager to fit her son into my family tree. I can't wait to see how many different relationships he and I have.

How I got to this point, working the Piteo men into my family tree, was very roundabout. And I never found a death record for Jennie's mother. It just goes to show you. You never know what amazing stories you'll find while playing around with genealogy.

How to Work Out Errors in Your Family Tree

The Ellis Island website was my gateway to genealogy. In my early days, I found ship manifests for my 2 grandfathers and other relatives. Then came my Ancestry.com membership, and my next gateway: census records.

What busted my family tree wide open was microfilm. I learned I could go to a Family History Center to view vital records from my Grandpa Leone's hometown. I began a 5-year process of viewing microfilm and typing every fact into a laptop. I have a text file with 29,864 lines of facts from his town's vital records, 1809–1860. I entered those facts into Family Tree Maker software to see how all the families fit together. (If you have an ancestor from Baselice, contact me!)

I'm related to 95% of the town. That research added 15,000 people to my family tree.

But I'm sure I made some errors. I couldn't look at each document again to correct any mistakes. Until 3 years ago. That's when a free website called Antenati published all those vital records and more. Now I have easy access to all the information I transcribed from microfilm in the dark.

Yesterday I ran Family Tree Analyzer to find some of those mistakes. It seems I have a family unit whose birth years don't line up. The 11 children (eleven!) have birth years from the 1760s to the 1780s. The problem is their mother, Antonia Cormano, was too young to have had the first 2 of her children.

And if her birth year is wrong, so are my estimated birth years for her parents and grandparents.

A routine error check lead me to several generations of one family with age issues.

The whole mess hinges on the unknown birth year of her first child, Antonio Colucci. Antonio died before 1809 when civil records began. So I can't find his death record easily. I estimated his birth year as 1746—25 years before his eldest child was born. I need to re-examine the marriage records of his descendants to sort things out.

Side note: Italian marriage documents are awesome. They include the bride and groom's birth records. And if any of their parents are dead, you get their death records. If their fathers and grandfathers are dead, you get the grandfathers' death records!

I wanted to learn the true birth year of Antonia's first-born child, Antonio. To find such an early record, I needed to find a male descendant of his who married after he died. Antonio's grandson Michele Antonio Colucci married in 1854. His marriage records did indeed have a death record for his grandfather Antonio. It shows his birth year as 1759, very different from my estimated birth year of 1746. That would help solve my problem with the birth years of Antonia and her ancestors.

But, of course, there's a complication. If Antonio was born in 1759, then he's too young to have had his 2 children born in 1771 and 1775!

The ripple effect of one bad date is enormous! (Are any "Indiana Jones" fans thinking of Harrison Ford's "Bad dates" line right now?)

Maybe Antonio's death record had his age wrong. These mistakes happen all the time. There were no other well-timed marriages that would include the death record I want. But let's say the birth year of 1759 is about right. Biologically, he could have had a child in 1775. So maybe his daughter Angela's birth year of 1771 is wrong. With a child born in 1797, Angela could have been born a bit later.

Her 1832 death record says she was 61 years old, born in 1771. Early birth records from the town rarely include the parents' ages. My only hope of seeing Angela's age apart from on her death record is her daughter's 1811 birth record. Sadly, that record confirms Angela's husband's age, but doesn't mention her age at all.

It's hard to imagine his age could be off by much when he's only 27 years old.

Well, that was frustrating. All I can do with what I have is fudge Antonio's birth year a bit and work backwards from there.

The following changes are going to need asterisks:

• I'll push Antonio's birth year back a bit and record it not as 1759, but as 1753. That'd make him an 18-year-old father. That's not common in this town, but it sometimes happened.
• I'll leave his father with his documented birth year of 1735. That'd make him an 18-year-old father, too. Like father, like son.
• Despite what her death record says, I'll change Antonia Cormano's birth year from 1742 to 1735. That'd make her an 18-year-old mother. It's like "Romeo and Juliet" if they'd lived.
• Then I'll follow my usual protocol. For Antonia's parents and grandparents, I'll subtract 25 from the year their child was born. If I change Antonia's birth year to 1735, then her parents were born "Abt 1710", and their parents were born "Abt 1685".

I'm not happy with fudging 2 documented dates, but the pieces didn't fit. I plan to work through this entire extended family, adding documents and sources to Family Tree Maker. If I'm lucky, some overlooked document will turn up with a better clue.

Genealogy, like life, can be messy. Slap on that bandage and keep searching.

Are Your Dead Ends Hiding DNA Matches?

Some dead ends are more important than others when a DNA connection is missing.

Despite some juicy leads, I still don't know why my parents share some DNA. They have a distant cousin relationship that I can't nail down. So let's try something else.

Recently I wrote about How to Diagram a Mystery DNA Match. It was a new technique that worked incredibly well on my first try. So why not try it on my parents?

I chose one parent's DNA test and found the other parent in the match list. I clicked to see all the possible relationships for 2 people who share 37 centimorgans. In my relationship calculator spreadsheet, I highlighted these possible relationships.

I know the names of all my father's 3rd great grandparents. I'm missing 8 of my mother's 3rd great grandparents due to a lack of records from their hometown. With so many ancestors known, I was able to rule out all the most likely relationships.

Mom's maternal side still has a lot of missing ancestors, some of which I may yet find.

But my parents may have a half-cousin relationship. What if one of his 3rd or 4th great grandparents married one of her 3rd or 4th great grandparents? I know my Italian ancestors didn't stay widowed for long. They would remarry for help raising the children or for companionship.

I went through my parents' ancestors looking for those I knew had more than one marriage. I kept noticing all the missing ancestors and wondering about them.

I have to keep working on my under-explored towns:

• Apice and Santa Paolina on Mom's side
• Pesco Sannita and Circello on Dad's side

Each one of their towns is pretty close to the others.

Can I fill in more holes in my family tree? Will any new paths lead to my other parent's ancestral hometowns?

I thought it might help to check the Relationship Calculator in Family Tree Maker. It might tell me where to start searching.

I clicked on Dad and checked his relationship to Mom. Besides "husband", I found these relationships:

1. Dad is the nephew of the wife of the 2nd cousin once removed of the wife of the 2nd cousin of Mom
2. Dad is the nephew of the wife of the 4th cousin once removed of the brother-in-law of Mom
3. Dad is the half 1st cousin 3 times removed of the wife of the 2nd cousin once removed of the brother-in-law of Mom
4. Dad is the grand nephew of the wife of the half grand nephew of the wife of the nephew of the husband of the 2nd great aunt of Mom
5. Dad is the nephew of the wife of the 1st great grand nephew of the wife of the 1st cousins of the husband of the half 1st great aunt of Mom

Well, that's clear, isn't it? I checked Family Tree Maker's relationship chart for each of the 5 relationships to make sense of it.

The Relationship Calculator in Family Tree Maker shows you hidden relationships.

Here's what jumps out at me:

• Relationship 1 hinges on a marriage between Mom's paternal hometown (Baselice) and Dad's paternal hometown (Colle Sannita). But that marriage happened only a few years before my parents were born.
• Relationships 2 and 3 above end with the brother-in-law of Mom. That's my Uncle Kenny—my aunt's husband. Other DNA relationships point to a blood relationship between Uncle Kenny and me. I haven't figured it out, but here it is again.
• Relationships 4 and 5 above also include marriages between the 2 towns. These marriages happened in the 1830s and 1850s.

I'm always on the lookout for marriages between my 2 grandfathers' towns. The marriage in relationship #4 includes the last name Pozzuto. All my roads seem to lead to Pozzuto. I found this out when I did some DNA mapping using the Leeds Method. My parents share DNA matches with a high percentage of Pozzuto, and a heapin' helpin' of Zeolla.

So, what does all that analysis tell me to do? Keep working on dead ends in specific areas of my family tree. I'll start by exploring those 2 inter-town marriages. I'll also work on some other towns, searching for Mom's missing ancestors.

I know that any new relationships I add along the way may connect me to more DNA matches.

Do you have DNA mysteries you can't solve? Spend time researching the common branches. Or concentrate on particular last names. Fill in as many blanks as possible.

It's a never-ending journey. But when you love genealogy, the journey is what makes it fun.