Trying to Solve a DNA Mystery with Logic

I'm mapping out a strategy to discover how my parents are distant cousins, as our DNA tells us.

An analysis of my raw DNA on GEDmatch.com shows that my parents are "probably distantly related." Their Ancestry DNA results predict that they are 4th–6th cousins. That should mean they share a set of 5th–7th great grandparents.

I want to find that link between mom and dad's DNA.

But there's another piece to this puzzle. My mom's sister's son (my first cousin Nick) is a DNA match for my dad. Ancestry DNA estimates my cousin and my dad are 5th–8th cousins. Nick's related to both my mom and my dad.

My mission is clear: Find the set of ancestors that my parents share…and see if they're the same ancestors my dad and my cousin share!

Plotting out where my ancestors lived,
they were all pretty close together.

My method is less clear. So let's work through the logic.

My dad's side of the family comes the Benevento province (similar to a U.S. county). My mother's side comes from the same province. What if, at some point, a man from one of dad's towns married a woman from one of mom's towns?

For at least several hundred years, all my ancestors lived no more than 25 or 30 miles apart. Many lived 5 or 10 miles apart, but that's as the crow flies. I've visited these rural, hill towns. They're separated by windy, hard-to-navigate, and sometimes washed-out roads.

My husband and I spent nearly an hour trying to get from one town (Colle Sannita) to the neighboring town (Baselice). We thought we'd never make it.

That experience got me thinking about how hard it was for my ancestors to go from town to town on a mule-drawn cart. That's why it's more logical to look at towns that were closer to one another.

I have 2 main choices. I can concentrate on my 2 grandfathers' towns, the ones that are a nightmare drive apart. Or I can take a hard look at 2 towns that are much closer together.

Colle Sannita (Grandpa Iamarino's town) neighbors the town of Circello. They're very close to one another, and the roads don't have to switch back and forth over mountains. Much easier on a mule cart.

One set of my 3rd great grandparents
had an inter-town marriage.

I've known for years that my cousin Nick's dad's family came from Circello. (Remember, Nick is my cousin on our mothers' sides.) But I found out recently that my 3rd great grandfather was born in Circello.

Francesco Saverio Liguori was born in Circello in 1813. In 1840 he married Anna Donata Cerrone in Colle Sannita, settled there and raised his family.

So my dad has some roots in Circello. When you look at these 2 facts:

• Nick's last name comes from Circello
• my dad's DNA match list has at least 3 people with that name

…it seems as if that last name may connect my cousin to my dad. But will it connect my mom to my dad? That's the big goal.

Is Nick a DNA match to my dad because of his own last name? Or is the connection through his mom, who is the same distant cousin of my dad as her sister—my mom?

Here's the plan I'm going to follow, and hope it leads to identifying that DNA connection.

1. I'll work to build out Nick's Circello branch of the family tree.
   
2. I'll also work to build out his grandmother's family tree. Why? Because she was from my Grandpa Iamarino's town! His grandparents had exactly the type of inter-town marriage I need to explore.
   
3. I'll study my grandparent chart and look for last names that don't seem native to their town. For example, my 4th great grandmother's last name (Tricarico) isn't one I've seen in the town where she lived. Maybe her parents or grandparents came from another town. And maybe, just maybe, her ancestors will tie my mom and dad together.

I've spent so much time living among my ancestors' vital records collections, I can spot an uncommon name in a given town. Liguori, my 3rd great grandfather's last name, was out of place. And that turned out to be entirely true.

It's important to get really familiar with last names in your ancestors' towns. Maybe you can learn the main names in your ancestor's town by looking at land records. Or by paying attention to all the names on the index pages when searching for your ancestor's birth record.

Wish me good luck. I'll report back when I think I've found that missing link!

And speaking of DNA clues:

• Delving Deep into Your Genealogy with DNA
• When DNA Says You're Related, You Determine How
• Collaborating with Your DNA Matches

How to Find Official Sources for Family Facts You Just Know

Imagine your grandchild inherits your family tree. How reliable will the information be for your generation?

I don't need a document to tell me I was born in Mother Cabrini Hospital in New York City. Or that I was baptized in Our Lady of Pity Church in the Bronx. (Both gone now, by the way.)

But years from now, if my grandchild wants to carry on my genealogy work, what proof will they have for facts about me, my siblings and my cousins?

Marriage registers, yearbooks, newspaper
clippings…these are official sources for your
living relatives.

Everyone says to start your tree with yourself and the facts you know. Then you move on. Finding census forms, draft registration cards, death records and so much more. But have you returned to yourself and your generation to find proof for your facts?

Your Own Documents

You should have your own birth certificate in your possession. I even have my baptismal certificate, along with two marriage certificates.

I need to scan those documents and put them in my family tree. (For the worriers: You can mark individual images as private in Family Tree Maker. Hopefully in your software, too.)

Of course, I'm not going to ask my brother and my cousins to let me scan their birth certificates. So what do you do?

Public Records Index

On Ancestry.com you can access volumes 1 and 2 of the U.S. Public Records Index, 1950–1993. The information in these databases comes from a combination of:

• telephone books
• post office change-of-address forms
• other public documents.

In my experience, the birth dates given in these collections are often wrong. For me, an entry might say I was born on the 1st of the month instead of the 24th. But it generally has the right year.

So, when all else fails, a public records source proves the person in your tree existed:

• by their name
• in a specific place
• in a specific range of time.

Newly Released Indexes

It pays to watch social media for genealogy news. That's where you can learn about groups like Reclaim the Records. They're on a mission to get access to the genealogical and archival data we genealogists want so much.

They've scored tremendous wins, particularly for New York and New Jersey documents. But they're also working to release data from many U.S. states.

Thanks to them, I've found documentation for several events, including:

• my parents' marriage license
• my grandfather's 2nd marriage license
• my and my close cousins' births
• my grandmother Lucy's birth

Seeing the index of New York births, I finally found my grandmother's birth certificate number.

Lucy's birth record has eluded me for years. Now I know her New York State birth certificate number is 60968. On the index she has no first name and a badly misspelled last name. No wonder I couldn't find her certificate! It's definitely her because my father has always known she was born on 10 Dec 1908 in Hornell, New York.

Newspapers

I haven't found much historical information on my family in the newspapers. But I'm constantly finding references to my brother in newspapers. His career has always had a big public relations aspect to it. So any search for Iamarino brings up my brother. I found his North Carolina marriage announcement that way.

Proof of a modern-day marriage may be found in the bride's hometown paper.

You may have more luck searching for your family. Think about all the events you could search for when it comes to your contemporary relatives:

• birth, marriage and death announcements
• public relations announcements for various professionals
• graduating class lists

Your facts and your closest, living relatives' facts may not be your top priority. But documenting these things you've known all your life:

• your mom's birth date
• your brother's middle name
• your aunt's home address

…will go a long way toward strengthening your legacy.

Set aside some time to find documents or public sources for your own nuclear family. Some day your grandchild may thank you from the bottom of their heart.

And speaking of proof:

• How Do I Get There From Here?
• How to Avoid Going Down Wrong Path
• Trust But Verify Your Relative's Family Tree

This Genealogy Policy Takes the Guesswork Out of Names

My in-law policy is working so well, I've created a naming policy for my family tree.

In my last article, I wrote about how freeing it can be to set policies for building your family tree. My new policy for handling the in-laws of distant relatives has been incredibly helpful.

This past weekend I found 29 more people who were in my family tree simply because they were an easy get. For instance, a man named Giovanni married one of my distant relatives in New York City long ago. I do want him and his parents in my tree. But I no longer want his 8 siblings—or any of their spouses and children—in my family tree.

So I removed them. And if I ever wanted them back, the census sheets where I found their names are still part of my tree. I'm keeping the documents because they contain Giovanni and his parents.

If your ancestor changed their name,
are you recording both names?

This in-law policy makes me happy because it's always there to guide me. It'll keep me from reaching out too far. It'll put an end to those awkward messages I get from people wondering why their grandfather is in my family tree.

It makes me so happy, I want to consider other genealogy policies.

I didn't have to think too hard about it before I realized—I already have another genealogy policy.

What I'm about to describe is not an established, official genealogy rule. There's a good amount of personal preference.

So think about your own personal preferences as you read on.

Naming Conventions in Your Family Tree

I'm putting my naming convention policy in writing. But it's based on practices I already follow. This is the style I've developed over the years.

Now, with a policy in place, I'll be sure to be consistent.

#1 Birth Names

If your ancestors emigrated to a country with a different language, they probably went by a different name. Giovanni became John. Anton became Anthony. Pablo became Paul.

I record my ancestors using the name on their birth record. If I haven't seen their birth record, I check each census. If they were born in another country, and on some censuses they use an ethnic name, then I believe that's their given name.

In Family Tree Maker, I use their birth name as their Name fact.

Record multiple names for your ancestor if they unofficially changed their name.

#2 Common Names

In their new home in a new country, many of our ancestors tried to fit in. They identified themselves by a non-ethnic name, like Mary instead of Maria Rosa.

We don't want to lose track of those new names. The new name is likely to be what's on their death record.

In Family Tree Maker, I record their common, or assumed name, as a second name fact. The software lets me add multiple names and set one as the preferred fact. Their birth name is that preferred fact.

Last names are important, too! If your ancestor changed their last name in their new country, you need to record that. You can make it their alternate name—their non-preferred name. For example, I have ancestors named Muollo. That's so hard for an American mouth to say, that one Muollo man changed his name legally to Williams.

That may seem like an odd choice. But you pronounce Muollo as mwoe-low. That could sound as if you're mumbling Williams. I need to record the Williams name because that's the legal last name of this man's children.

#3 Nicknames

Everyone in my parents' Bronx neighborhood in the old days had a nickname. In my family there were men called Baldy and Blondie. People in the family never called them anything else. So I need to preserve those colorful nicknames in the family tree, too.

In Family Tree Maker, I record a nickname with the AKA (Also Known As) data fact. Having spelled out this policy, now I'll be sure to fill in what I'm missing.

#4 Reference Words

I've been working on my document tracker a lot lately. This is a spreadsheet where I log each document I've found for the people in my tree. Everyone who has a document image gets a line in the document tracker.

A simple shorthand highlights my
closer ancestors, and their father's name.

Filling it out helps me realize which documents I'm missing for each person. It encourages me to do more. Lots of times I'll enter something in the "Need to find" field, like "1902 immigration record". Then I think, "Why not search for it right now?" And I know I'm doing good work.

Here's where I'm using a naming convention in my spreadsheet.

I have tons of people in my tree with the same name. Don't we all? In the small towns where my ancestors were born, many men had the same name. On the town's birth records, the mayor would sometimes write the new father's name as, for example, "Giovanni, son of Giuseppe".

So I'm doing that in my spreadsheet. After a person's name, I add, in parentheses, (son of Giuseppe), or whatever the father's name is. That helps me when I need to locate the person in my family tree.

I also like to identify certain close relatives in the spreadsheet. I use this shorthand: 2G is a 2nd great grandparent, 2GA is a 2nd great aunt, 2GU is a 2nd great uncle.

What naming conventions are you using? Are you being consistent?

Spend a little time thinking about the names in your tree. What policies can you set to make your family tree make more sense?

And speaking of being consistent in your family tree:

• It's Time to Revisit and Improve Your Earliest Family Tree Research
• How to Handle Foreign Words in Your Family Tree
• These 4 Simple Rules Will Improve Your Genealogy Research

How to Keep from Going Too Far with Your Family Tree

How do you know when to stop gathering documents and facts for the in-laws in your family tree?

For certain types of distant relatives, I'm collecting
the basic documents and stopping right there.

I've been thinking about this ever since I decided to delete the in-laws of distant relatives from my tree.

Here's an example. When I was new at family history research, "easy" families were impossible to resist. So, when I saw my Great Uncle Mike's granddaughter-in-law had a tree with 7 generations of Uncle Mike's wife's family, I "adopted" them all.

I added this big branch to my tree with little or no documentation. I found documents for some of the people, but I didn't care enough about this branch to see it through. They weren't mine.

My new policy is simple. Unless I have a reason to go further, I will stop at the parents of a relative's spouse. I kept Uncle Mike's wife's parents, but the rest of her many ancestors are gone.

The 2 main reasons I would break this policy are:

1. An in-law asked me to research their family.
2. The in-law family is from the same town as mine and may be related.

With this new policy fresh on my mind, I found myself looking at documents for a relative's wife today. I downloaded Emily's naturalization papers from FindMyPast.com 2 weeks ago. They were offering free access for a few days.

The site had indexed Emily by her married name—my family name—which is why I found her. I recognized who she was immediately and downloaded the 2 pages. Then they sat on my desktop for a while.

When I finally examined the naturalization papers, I realized I had Emily's:

• date and place of birth in Italy
• immigration date with the name of the ship

The pages also confirm the birth dates I had for her husband and son, so they're well worth having.

Before I found her naturalization papers, all I had for Emily was:

• Her 1927 marriage certificate—but not a copy of it. I saw and transcribed it at the New York City Municipal Archives years ago. Her parents' names were on that marriage certificate, so I already had them in my tree.
• The 1940 U.S. Federal Census.
• The Social Security Death Index record of her death in 1991.

Knowing that I have no plans to add anyone else from her family, what other documents should I try to find and add to my tree?

Her naturalization papers say she was born on 2 Dec 1907 in Savignano, Italy. So I've got to look for that document. Vital records for Savignano are available online, so I drilled down to the year 1907 and found it.

This document gives me her mother's original name and her father's age and occupation. I don't need any more details about Emily's parents.

In 1907 Emily's town was called Savignano di Puglia. She was born on Via San Giovanni.

Oh, by the way, her name isn't Emily. I always thought it might be Emilia, but now I have her birth record. She was born Ermilinda Franceschina Concettina D'Apice. She signed her marriage certificate as Emily, and her naturalization papers say Emily. But those papers also include the name "Ermelinda".

Now I have Emily's:

• 1907 birth in Italy
• 1927 marriage in New York
• 1940 census in New York
• 1944 naturalization in New York
• 1991 death in New York

What's the most important piece of documentation missing from that list? She was born in Italy and married in New York. How did she come to America, and with whom?

Emily and her sister Giuseppa came to New York in 1919 to join their sister Elvira in the Bronx.

Her naturalization papers include an immigration date of 19 Dec 1919 aboard the S.S. Duca D'Aosta.

When I found her ship manifest, she was single and sailing with her much older, unmarried sister, Giuseppa. They listed their father Angelo, so I knew they were the right family from Savignano. They were joining their other sister, Elvira, at 628 Morris Avenue in the Bronx.

Emily's street in Savignano still exists. It's always nice to get an idea of where the people in your family tree came from.

I had to laugh when I saw that address, because if you were going there, you were bound to meet my relatives.

So now I've learned the names of 2 of Emily's sisters, the age of one of them and the address of the other. But I have a policy now. No unnecessary siblings of the spouse of a distant relative.

That's why Giuseppa and Elvira D'Apice will live in my tree only in Emily's immigration notes. Having a policy makes it much easier to deal with questionable situations like this. What I will add, because her husband and son belong to my family, is her 1930 census. And maybe I'll find her and her sisters in the 1920 census. But no more than that!

If you're a fan of Mel Brooks' movie "The Producers," you may recognize the phrase I will repeat when I'm tempted to add a wildly distant in-law to my family tree. "Be brutal! Be brutal!"

And speaking of trimming your family tree:

• When to Cut a Branch Off Your Family Tree
• How to Decide Who to Cut from Your Family Tree
• It's Time to Revisit & Improve Your Earliest Family Tree Research

4 Tips to Help You Find that Missing Ancestor

Here's how I'm finding the missing connections for my newly discovered ancestor.

Recently I told you how I found a big error in my family tree. It was the result of hard-to-read documents and my not being familiar with a particular town's families. I wound up following Rubina Cenzullo when I should have been looking for Ruffina Zullo.

Some of my ancestors moved to nearby towns to marry.

When her death record showed me the truth—that Ruffina was born in another town—I knew exactly what I had to do.

The most important documents I needed to find in the new town (Apice, Italy) were:

• her birth record (around 1816)
• her marriage to my 3rd great grandfather (around 1843)

But now I have a new family named Zullo, and a whole new branch to discover. Ruffina's parents were Leonardo and Caterina. But I want to learn the names of my 4th and 5th great grandparents in this branch.

Here's what I'm doing to expand my new Zullo branch.

Find Siblings, Marriages, Deaths

Ruffina was born in 1816 when her father was about 27 years old. There could be siblings born before Ruffina, for sure. To find them, I used the GetLinks program to download all the Apice birth records. (Read about how GetLinks works with FamilySearch and the Antenati website. You'll find the download link there, too.)

I downloaded her town's 1809–1815 birth records and looked for Ruffina's siblings. I found:

• Saverio Antonio Nicola Zullo, born in 1811
• Saverio Zullo born in 1813

When two children of the same parents have the same name, it's a safe bet that the 1st child died before the 2nd was born. The 1st Saverio, in this case, should have died before the 2nd Saverio was born in 1813.

To prove that, I downloaded the town's 1811 death records. I found that the 1st Saverio died in October 1811.

But I found a surprise, too. A month earlier, in September 1811, another Ruffina Zullo died. She was the daughter of the same parents as the other children, and she was 2 years old. It's only because this Ruffina died that my Ruffina got her name.

The correct name led me to a new family unit.

This opens up another avenue for me to explore. I checked the 1809 Apice birth records. Ruffina was not born in Apice in 1809 (not in 1810 or 1811, either).

But I noticed something important. There are lots of people named Zullo in Apice to this day. But there was no one there with the same last name as Ruffina's mother: Trancuccio.

While thinking about this, I formed a theory.

Did Leonardo and Caterina, the parents of the Zullo siblings, marry in another town? Was it Caterina's hometown? That would explain why no other people in Apice have Caterina's last name. If this theory is right, 1809 Ruffina could have been born in Caterina's hometown.

This isn't far-fetched at all. Many times in 1800s Italy a couple would marry in the wife's town but live in the husband's town. My Ruffina's daughter Vittoria has a similar story, but with more complications.

Vittoria married Antonio (these are my 2nd great grandparents). Antonio was from Pastene; Vittoria from Santa Paolina. They married in Santa Paolina and had 1 child. Then they moved to the neighboring town of Tufo and had 2 more children. Then they moved to Antonio's town of Pastene to have the rest of their children. (And that's why my great grandparents met and married in Pastene.)

I used a website to see where Caterina's last name exists in Italy. I find it mostly in 2 nearby towns. Another tip: Enter the last name into a genealogy site search for immigration records. See where those people came from.

I downloaded the 1809 and 1810 birth records from these 2 likely towns. So far, I haven't found my 4th great aunt Ruffina Zullo. But I have found people with the last name Trancuccio.

I still like my theory, but I may have to check more towns.

I won't be visiting this ancestral hometown—at least not the old part 
of town. It was destroyed and abandoned after a 1962 earthquake.

There was another surprise waiting for me when I located my 3rd great grandmother Ruffina's siblings. On her brother Saverio's 1811 birth record, the father of the baby is "Leonardo Zullo di Saverio". That means "Leonardo Zullo, son of Saverio".

That's exactly what you hope to find! Saverio is baby Saverio's grandfather, and my 5th great grandfather. This Saverio Zullo was born in about 1764, possibly in the same town where Ruffina was born in 1816.

What can I do with 1764 Saverio's name to help build my tree some more?

Well, while looking for Ruffina's siblings, I saw several other Zullo babies born to different fathers. I also found some Zullo men and women who married in that town between 1809 and 1815. I can download all those records easily.

I can put together Zullo babies, brides and grooms. I'll match siblings by comparing their parents' names. With luck, I'll find a sibling for my 4th great grandfather, Leonardo Zullo. And maybe one of that sibling's records will tell me my 5th great grandmother's name. (I'll bet it's Ruffina!)

No matter who you're looking for, or which branch you're trying to grow, these basic tasks can help you succeed:

1. Found an ancestor's birth record? Search the surrounding years for the births of their siblings. Comb each record for more information, like ages, occupations and other relatives.
2. Based on the oldest sibling's birth, try to find marriage records for their parents.
3. Starting in the year of the youngest sibling's birth, try to find death records for their parents.
4. Pay attention to names. If your ancestor is from a big city, this isn't as helpful. But if you're looking at records from a really small town, you should see a lot of last names repeated. These are the long-standing families in that town. If your ancestor's last name is unique, maybe they're from another town.

Finding out Ruffina was born in Apice when I knew she married and had babies in Santa Paolina was a big surprise. Keep your mind and your eyes open. Let the facts you have suggest a theory about the facts you don't have. Then try to prove that theory. Don't give up the search!

And speaking of climbing to the next generation:

• Step-by-Step Discovery of My 5th Great Grandparents
• 5 Steps to Grow Your Italian Family Tree
• Today I Demolished My Family Tree's Only Brick Wall

One Report, Endless Possibilities for Improving Your Family Tree

Update: Family Tree Analyzer is now available for Mac.

Family Tree Analyzer

It's always fun to create an up-to-date GEDCOM from my family tree and get the latest insights from Family Tree Analyzer.

I've written about this free PC-based program several times now (see links at the bottom of this article). Today let's look at how you can use its Main Lists tab to produce an all-in-one report.

First, your family tree software should have an export option. You can use the export option to create a GEDCOM. If you keep your family tree online only, and not in desktop software, you've given up some control of your family tree. Ancestry.com lets you export a GEDCOM from your online tree, but other sites, like FamilySearch.org, do not.

Second, there are other ways to do what I'm about to describe besides using Family Tree Analyzer. But to me, this program is the best way to do it. (Do a Google search for "convert GEDCOM to spreadsheet".)

Now let me show you what you can do with an all-in-one report from Family Tree Analyzer.

After loading your GEDCOM in Family Tree Analyzer, click Main Lists.

Launch Family Tree Analyzer and open your most recent GEDCOM file. The software will analyze your GEDCOM for several facts.

When it's finished, click the Main Lists tab. With the Individuals tab clicked, you'll see a table containing every person and fact in your tree!

Click the Export menu at the top of the program window to generate a "csv" file. This is a file you can open with any spreadsheet software, like Excel.

Excel gives you tools to sift, sort and manipulate the data any way you like. But I don't want to turn this into a long Excel tutorial. If you don't know how to filter and sort your contents, here's a good, short YouTube video. Jump ahead to 1:44 and watch until 2:24. Short and sweet.

In your spreadsheet, choose a Fact Type (column E) to filter by, such as Occupation. Now click Excel's Sort button and sort by Fact Comment (column H).

Now you have:

• a simple view of all the occupations in your family tree
• an alphabetical list of what you typed in for the description.

I'd like to do 2 things with the occupation descriptions:

1. Fix Errors. I can scroll down the list and scan for typos. In the image below, you can see there's an address instead of an occupation. I can fix that. In my family tree software, I'll go to the person named in columns B and C. It turns out I'd entered an address for the place of work, but left out the word "dentist" for these 2 men.

A filtered, sorted spreadsheet of your family tree facts simplifies a lot of tasks.

2. Complete My Job Translations. Most of my genealogy research work is in Italian documents. I thought it was cool to enter a person's occupation in Italian, so I made a separate translation list for my own use. But one day I realized there's a Find and Replace function in Family Tree Maker. So now I'm including the English translation in parentheses, like this: "calzolaio (shoemaker)".

Family Tree Maker is smart enough to make suggestions as I type in a field. So if I type "calz", it suggests "calzolaio (shoemaker)".

But I'll bet I overlooked a lot of jobs when I did my find and replace. This spreadsheet helps me find those untranslated Italian words, like agrimensore, benestante, eremite, and so on. Now I can finish this translation task and make my family tree more valuable for myself and others.

Let's pick another Fact Type.

1. Click the Filter button at the top of column E.
2. Click Select All to make every fact type available again.
3. Click it again to uncheck the whole list.
4. Now click to select the Birth fact type and click OK.
5. Click the Sort button and sort by Fact Location, column G.

Scroll down through the alphabetical list of all the birth locations. Do you see a lot of blank locations toward the bottom? In a recent article (see "5 Clean-up Tasks to Improve Your Family Tree"), I explained the value of having approximate birth dates and places in your tree. It can give you better hints and search results.

For example, I have a man named Salvatore Martuccio who was born in about 1873. I don't want to see a hint for finding him in the 1880 census in America when he and his family were always in Italy. So I need to add Italy as his place of birth. I think I know which town he was born in, but I have no documentation. So I'll keep it loose and say he was born in Italy.

This spreadsheet makes it easier to find facts—and missing facts—so I can finish my clean-up tasks.

Here's another idea. I'll filter the Fact Type column by Immigration and sort by Fact Comment. When I first started recording immigration facts in my family tree, I used this format:

Arrived aboard the [ship name] with [wife, children, brother, etc.] to join [person's name and relationship] at [address].

Then I realized I could use the Emigration fact type to say:

"Left on the [ship name] to go to [destination city]."

With the ship name in the emigration or departure field, I could shorten my immigration or arrival description to:

"Arrived with [wife, children, brother, etc.] to join [person's name and relationship] at [address]."

I can use this filtered and sorted spreadsheet to find all the descriptions I want to edit in Family Tree Maker. Hurray! More work to do!

I'd like you to think of this method as a way of seeing everything that's hidden from plain sight in your family tree. Work on what's important to you. No matter how much you decide to correct, improve or simplify, you'll wind up with a better, stronger, more reliable family tree.

So filter, sort, and see how much you can accomplish!

And speaking of Family Tree Analyzer:

• Why You Should Be Using the Free Family Tree Analyzer
• Run This Genealogy Report To Help Clean Up Your Dates
• Use This Tool to Discover Family Tree Insights
• This Genealogy Report Shows You What's Missing