11 October 2019

2 Ways to Find the Loose Ends in Your Family Tree

You know all those things you left unfinished in your tree? No you don't.

With so many branches in your family tree, how can you find all the loose ends? How can you find every spot where you didn't finish searching for facts?

I have countless branches in my family tree. That's what happens when you piece together everyone who ever lived in your ancestral hometowns. Researching one of my grandfather's towns added 15,000 people to my tree. And now I'm working on the other grandfather's town.

Sound crazy? Think of it this way. I'm so familiar with every family name and street name from my grandfather's towns that the worst handwriting doesn't slow me down a bit. Plus, I had to work out every relationship in town to take Grandpa's branch back to the 1690s.

The whole time I was working on his town, I was dreaming of doing the same for all my ancestral towns. But before I add another 15,000 Italians to my family tree, I want to take the time to tie up some loose ends.

Here are 2 great ways to quickly see which birth, marriage, and death facts you're missing. These are loose ends you may be able to tie up.

1. Use Your Family Tree Software

I use Family Tree Maker, so you'll have to see how you can do this in your program. The idea is to sort your index of people by birth date, death date, or marriage date.

If you're reasonably sure of the year, you can search for the exact date.
If you're reasonably sure of the year, you can search for the exact date.

In Family Tree Maker, your index of people is probably showing names and birth dates by default. If so:
  • Click the pull-down menu next to the word "Sort"
  • Choose "Birth Date"
  • Scroll through your index and look for estimated or incomplete birth dates
If you want to look at Marriage Dates or Death Dates instead:
  • Click the icon to the right of "Index" that looks like 3 vertical bars
  • Choose "Marriage Date" or "Death Date"
  • Click the pull-down menu next to the word "Sort"
  • Choose "Marriage Date" or "Death Date"
  • Scroll through your index and look for estimated or incomplete dates
With the list sorted, you'll easily see where you have:
  • an estimated date (such as "Abt 1818"), or
  • an incomplete date (such as "1836" or "May 1817").
On my computer I have vital records from my ancestral Italian hometowns for a certain range of years. If someone from one of my towns has "1863" as their birth date, I should be able to find their birth record. Then I can change the birth year to an exact date. Loose end tied up!

2. Use Family Tree Analyzer

If your family tree software doesn't have an easy sort feature, or your tree exists only online, have no fear. The must-have free program Family Tree Analyzer has got you covered.

Launch Family Tree Analyzer and:
  • Load your latest GEDCOM file
  • Click the Individuals tab
  • Click the top of the "BirthDate" or "DeathDate" column to sort the facts
  • Scroll through the list and look for estimated or incomplete birth or death dates
To examine marriage dates in Family Tree Analyzer:
  • Click the Facts tab
  • Select all "Relationship Types"
  • Select only the "Marriage" fact
  • Click the "Show only the selected Facts for Individuals…" button
  • In the new window that opens, click the top of the "Fact Date" column to sort by marriage date
  • Scroll through the list and look for estimated or incomplete marriage dates
You may find that you have a long list of incomplete dates. Whenever I have a big task to do, I like to whittle it down by going after the easy stuff. Pick that low-hanging fruit and shorten that list as much as you can.

If your family tree software can't handle this project, Family Tree Analyzer can.
If your family tree software can't handle this project, Family Tree Analyzer can.

For this project, I would first work on the dates that are a bit more certain. "1818" is more certain than "Abt 1818". I must have a source for that "1818", but the "Abt 1818" is an educated guess or guestimate.

Tackle the missing months and dates first. Then you can work on the harder-to-find estimated dates.

You won't find them all, so don't beat yourself up about it. But I'm sure you can shorten that list of loose ends. Most of them are loose simply because that wasn't your focus at the time.

For instance, let's say I was entering an exact marriage date for a couple. The marriage documents included birth records for the bride and groom. That gave me a source for each of their parents' birth years. Because I was focused on the marriage facts, I didn't take the time to chase after the parents' birth records. The result is 2 loose ends.

Before you begin your next research project, take some time to see what you've overlooked. Go back and tie up as many loose ends as you can. Those exact dates will help your research in the future.

08 October 2019

Why All Siblings Are Critical to Your Family Tree

Marie's branch was a dead end until I found one ancestor's siblings.

I've been sharing genealogy discoveries with Janet for a long time. Her in-laws are from my grandfather's town in Italy. Her father-in-law saw my photo of my Italian cousins. They were his nieces!

We realized right away that his brother's wife was my great aunt—my grandfather's sister. Janet and I pieced together many generations of her father-in-law's family tree.

But there was more to the story. Her mother-in-law Marie is a solid DNA match to my father and me. I was eager to figure out our connection. But Marie's tree hit a dead end at her great grandparents.

Here were the problems we faced:
  • Her great grandfather and great grandmother had very common names for this town.
  • We weren't positive when they were born. Our only clue was from the birth record of one of their children.
  • They married too late for us to find their marriage documents online.
Yesterday I made up my mind to punch through this brick wall. I needed to find more of this couple's children—more of Marie's grandmother's siblings. Each additional birth record might give me the clues I needed to go further.

Here's what I did.

Marie's great grandparents were Giovanni and Maria. (That's right. "John and Mary"!) They had Marie's grandmother when they were more than 40 years old. It's only GeneaLOGICAL™ that they would have had some children before her. (Also see "Finding the Siblings Your Ancestor Never Mentioned".)

The first sibling I found was Marie's grandmother's older brother, Francesco. He was born 8 years earlier than her in 1874. In 1874, the birth records in this town were not a fill-in-the-blanks form. This left room for more details.

What I found on his birth record were both of his grandfather's names. That's a fantastic find!

If I didn't look for all their children, I'd never have broken through this brick wall.
If I didn't look for all their children, I'd never have broken through this brick wall.

Now I knew that Giovanni's father was Giuseppe, and Maria's father was Donato. Plus, this record was 8 years earlier than Marie's grandmother's birth record. So it had more reliable ages for Giovanni and Maria.

That's an important concept when you're researching people from a century or more ago. People didn't always know their correct age. You and I have to give out our full birth date every time we see a doctor. But back in the day, someone might not know their age. So, the older the genealogy record, and the younger the person, the more likely they are to remember their age. If you don't have their birth record, their marriage record probably has the right age.

I searched all the birth records in a span of years. I found the only Giovanni with the right last name and a father named Giuseppe. And I found the only Maria with the right last name and a father named Donato.

Probably their first-born child, Francesco's birth record had the extra clues I needed.
Probably their first-born child, Francesco's birth record had the extra clues I needed.

As luck would have it, their parents were already in my family tree. The key to the whole thing was that one sibling's birth record that had both grandfathers' names on it.

I kept piecing together several of Marie's ancestors, with the help of a few sibling records. At last, I found our true relationship. Marie went from being the wife of my 1st great aunt's brother-in-law, to my 5th cousin twice removed. She and Grandpa are 5th cousins.

I've gone all-out researching each of my grandfather's hometowns. In their small towns, everyone is related in some way. I have some families with 8 to 12 children. Each of the children is critical! You never know when their record will have the facts you need to break through your brick wall.

04 October 2019

When to Use Estimates in Your Family Tree

Estimates in your tree can help you avoid mistakes. See where they belong.

Family Tree Analyzer is a wildly useful, free program for genealogists. Each time I run it, I find something else I want to do with it.

Here's what I'm going to do with Family Tree Analyzer today.

This free tool offers countless ways to find the errors or missing info in your family tree.
This free tool offers countless ways to find the errors or missing info in your family tree.

A while ago, I created a policy to follow with my family tree. Every individual in my tree needs to have an estimated birth year and at least a country of birth. If I don't know when someone was born, I can:
  • give them about the same birth year as their spouse
  • subtract 25 from the year their oldest known child was born
  • add 25 to their younger parent's age
Enter an estimated age in your family tree as "about" whatever year. Family Tree Maker, the genealogy software program I use, automatically abbreviates about as "Abt". Your software may handle this automatically, too.

Note: Whenever I enter an estimated date, I do not add a source. That way I know my own policy is the only source.

With an estimated age in your tree, you won't set someone born "Abt 1800" as the parent of someone born in 1920. It can also help you decide which of the 13 men named "Giovanni Pozzuto" in your tree is the one you're looking for. (And that's not counting all my Giovannantonio Pozzutos!)

Adding each person's likely country of birth and death is helpful, too. It can prevent a mix-up between a family that came to America and one that never left their mother country.

Family Tree Analyzer (FTA) makes it easy to see who in your family tree is missing a birth year and country. First, go to ftanalyzer.com to download the latest PC or Mac version. Launch the program and open your newest GEDCOM file. (I just realized you can drag and drop your GEDCOM into the FTA window!)

Once FTA loads your file, click the Main Lists tab. You may see a lot of empty fields in the BirthLocation and DeathLocation columns. In the BirthDate column, look for the word UNKNOWN.

Family Tree Analyzer helps you find everyone in your tree with no birth date—not even an estimate.
Family Tree Analyzer helps you find everyone in your tree with no birth date—not even an estimate.

I've been on a roll lately, adding dozens and dozens of babies from my grandfather's hometown to my tree. So I have more than 22,000 people in my family tree. To make this task easier with such a big tree, I can click any column name in FTA to sort the results.

If I click the BirthDate column, all my UNKNOWNs group together. I'm happy to see I have only 11 of them. Those are usually people I added in a hurry, or while the dog was begging me for peanut butter. I can check all 11 people in my family tree and calculate their estimated birth year. It didn't take long for me to apply my rules and give each of the 11 people an estimated birth year and country.

Next, if I click the BirthLocation column in FTA, all the blank fields group together. Oh no. I've got tons and tons of blank birth locations.

When it comes to adding an estimated country of birth or death, there may be times when you want to keep it blank. Was the oldest child in a family born before or after the parents migrated? If you're not sure, you should leave it blank. Otherwise you might think you shouldn't look for that child on a ship manifest.

That's why I made another policy for the estimated birth or death country. If it's before 1850, I feel safe in assuming my relatives were born and died in Italy. There wasn't a lot of trans-Atlantic migration going on at that time. And my hometowns are so remote, and were so poor, that taking a ship somewhere wasn't an option then. I can assume my Angela Bianco—born in 1772 and died in 1836—was only ever in Italy. I may not be positive which town she was born in, but I feel sure it was in Italy.

Adding these unsourced estimates can help you avoid errors. And it tells FTA not to look in the Canada, Ireland, US, or UK Census for someone who was born and died in another country.

My own list of empty places of birth is overwhelming. It's something I've been more careful about recently. And I fix it each time I find someone with a blank location. Family Tree Analyzer is a good motivator for me to do a better job with so many aspects of my family tree. What can it show you today?