Report Finds Marriage Mishaps in Your Family Tree

Anytime you do a lot of work on your family tree, it's a smart idea to let Family Tree Analyzer have a look at it. This free software seems to offer me a new way to dissect my GEDCOM file each time I use it. And I've been doing a lot of work on my tree recently.

Last week I finished perfecting the citations in my family tree for these sources:

• 1851 England Census
• 1861 Census of Canada
• 1861 England Census
• 1871 England Census
• 1880 U.S. Federal Census
• 1881 England Census
• 1891 England Census
• 1900 U.S. Federal Census
• 1901 England Census
• 1905 New York State Census
• 1910 U.S. Federal Census
• 1911 England Census
• 1915 New York State Census
• 1920 U.S. Federal Census
• 1925 New York State Census

That adds up to 944 citations shared among family members found on the same census. Before I fixed them, a few sources had more than 700 citations each due to a catastrophic sync failure with my tree on Ancestry.com. I've given up trying to sync, but by next year I'll upload a clean version of my tree using a new tree name. I won't sync with it once it's uploaded.

Time for a Quick Check-Up

After all that editing, I wanted to see what Family Tree Analyzer (FTA) thinks of my latest GEDCOM file.

My GEDCOM Stats in FTAnalyzer had a strange line item telling me my family tree had some errors.

When you open your GEDCOM in FTA, you get a summary screen filled with basic facts about your tree. This time, I spotted something unusual. FTA said I had 4 lone individuals listed as single families. I needed to find them and see what was going on.

I found them by doing something I hadn't tried before. Usually I click FTA's Main Lists tab which opens to the Individuals tab. This lists everyone in your tree. But this time I clicked the Families tab next to the Individuals tab. I scrolled way to the right and found a column called Family Size. I sorted the data in that column from A to Z, putting all the families with a size of 1 at the top of the list. To my surprise, there were 41 families of 1.

5 Types of "Marriage Problems"

I opened my Family Tree Maker file and found each person from the FTA list, one-by-one. These "families of 1" fell into the following categories:

1. An unwed parent whose child's name you know from their birth record. In these cases, there's nothing you need to do. It really is a single-person family with a child.
2. Someone you meant to delete from the file but overlooked. Before you delete them, delete any of their citations or images. And detach them from an Unknown Spouse* if necessary.
3. Someone whose parents you deleted because you don't want to trace their family. (That's my in-law rule in action.) You may need to detach them from unknown parents. Otherwise leave them be.
4. Someone with a marriage date but no spouse. Take the time to search for the source of this incomplete fact and add their spouse. I've found Italian birth records with a marriage date, but no spouse's name!
5. A complete mystery, unattached to anyone, who you may as well delete.

*Unknown Spouse—As I worked through the list of 41 people, I found that many had an Unknown Spouse attached to them. Even babies who died young had these mysterious spouses. To see the unknown spouse in Family Tree Maker, go to a person's detail page. Then click Relationships rather than Facts or Timeline. If there is a partial marriage fact, delete it. Then detach the individual from their unknown spouse. Now the phantom spouse is gone from your file.

How many of these lurkers are hiding in your family tree? Here's how to find and eliminate them.

When I finished dealing with the 41 people with a family size of 1, I exported a new GEDCOM. Then I opened it in Family Tree Analyzer. Now I have 9 people with a family size of 1 because I made the decision to keep each of them. (Almost all are single parents.) The initial message from FTA saying I had 4 lone individuals listed as single families is gone.

This week I'll tackle my 1930, 1940, and 1950 U.S. Federal Census citations. Then I want to jump straight to the passenger lists of people coming through Ellis Island. Most of the immigrants in my family tree arrived in New York, so this is an important source to whip into shape. Then I'll continue working through my sources in alphabetical order.

After that, I have to deal with my countless Italian document citations. That's fine—I've wanted to work on those for a long time.

How Healthy is Your Family Tree?

If you've been working on your family tree for a while, you've no doubt gotten better at it with practice. That means your earliest work isn't as good as it should be. In my case, I know that censuses and ship manifests for my closest relatives are what I added first. And I'm fixing them as I work my way through my citations.

How did you begin your family tree? Were you searching for certain types of documents  first, like me? Did you begin with an inherited tree that someone else created? Take a look at the different reports FTA can offer you, such as:

• One Report, Endless Possibilities for Improving Your Family Tree
• Let Family Tree Analyzer Find Your Duplicates Duplicates
• 4 Problems You Can Fix with Family Tree Analyzer

Take the Time to Improve the Sources in Your Family Tree

Last week I had to swear off synchronizing my Family Tree Maker file with my tree on Ancestry. (See "A Major Family Tree Change to Fix an Ongoing Problem.") Too many failed syncs made it impossible to go on. In fact, those failed syncs did more damage to my desktop tree than I knew. I'm determined to see this as an opportunity to improve my family tree.

Failed syncs of my Family Tree Maker file left me with tons of splintered and unlinked source citations.

During my corporate life, I always hated when a boss would call a pain-in-the-butt project an "opportunity." An opportunity to improve our website. An opportunity to improve our support for the sales team. It wasn't an opportunity for workers like me who had countless hours of grunt work ahead of us. Don't try to sugar-coat that burden.

Yet here I am calling this problem an opportunity to improve the source citations in my family tree.

There were 2 things I now know happened to my desktop tree with each failed sync:

1. My tree no longer recognized some addresses. This was plain to see and easy enough to fix. I viewed each bad address in the Places tab of Family Tree Maker and made a few clicks. If you use FTM, see the company's instructions for standardizing locations.
2. My tree split my shared source citations into a bunch of identical citations. That's because an Ancestry tree sees each citation differently than FTM. Many citations weren't linked to anyone at all. These may be leftovers from people I deleted without first deleting their citations. Thousands of duplicate citations were increasing my tree's file size dramatically.

I've had a project on my radar to update citations for documents found on the Italian Antenati portal. The links in my old citations don't work anymore because of a huge change to the Antenati website. Spelling out the town, year, and document number would make each record findable—even if that website changes the links again. But it's a huge task.

Develop a Format and Stick to It

When I saw the mess my U.S., Canada, and U.K. source citations were in, I knew what I had to do. It was time to improve my oldest citations and make them match my current style.

For example, I'm looking at the 1920 U.S. Federal Census document image for my husband's ancestor. These days I like to add a ton of detail to the document image's description. But this early find says only:

lines 48-50; Honolulu City, Honolulu, Oahu, Hawaii, enumeration district 45, sheet 11B; image 22 of 138
https://www.ancestry.com/interactive/6061/4442141_01017/114577201

That's pretty helpful, but my newer format is better. The citation should say this:

lines 48-50; 1920 United States Federal Census; Hawaii Territory > Honolulu > Honolulu > District 0045; Honolulu City, Honolulu, Oahu, Hawaii, enumeration district 45, sheet 11B; image 22 of 138

https://www.ancestry.com/discoveryui-content/view/114577201:6061

Source Citation: Year: 1920; Census Place: Honolulu, Honolulu, Hawaii Territory; Roll: T625_2036; Page: 11B; Enumeration District: 45

Source Information: Ancestry.com. 1920 United States Federal Census [database on-line]. Provo, UT, USA: Ancestry.com Operations, Inc., 2010. Images reproduced by FamilySearch.

Original data: Fourteenth Census of the United States, 1920. (NARA microfilm publication T625, 2076 rolls). Records of the Bureau of the Census, Record Group 29. National Archives, Washington, D.C.

To be clear, I'm putting that extra long citation into the properties of a document image. When I drag the image into FTM, all that info comes along for the ride. Then I use everything from the URL down to populate the source citation for this document's facts. Let me dissect that format so you can follow my logic.

• lines 48-50 — This tells me and anyone who sees my copy of this document on Ancestry where to look on the page. This goes for ship manifests, too.
• 1920 United States Federal Census — This is the name of the record collection that has this document.
• Hawaii Territory > Honolulu > Honolulu > District 0045 — When you look at the document on Ancestry, this is the detail shown at the top of the screen.
• Honolulu City, Honolulu, Oahu, Hawaii, enumeration district 45, sheet 11B — These details can help locate this document on or off Ancestry.
• image 22 of 138 — This tells you exactly which image to go to in the collection on Ancestry.
• https://www.ancestry.com/discoveryui-content/view/114577201:6061 — The URL points to this record (not the document image) on Ancestry. This URL also contains the Source Citation and Source Information I add beneath the URL. I used to link to the image on Ancestry.com. But it's more useful to link to the record page.

This style includes enough detail so anyone can find the image—even without a link or an Ancestry account. And I attach the image to the Media tab of the citation itself. That's something I didn't know was possible until a few years ago.

Once I finish a citation, I copy and paste it to each family member in the census. And I can delete the duplicate copies each failed sync generated.

How to Check All Your Source Citations

I started this process by looking at the Sources tab in Family Tree Maker. There's a long list of all my sources on the left, in alpha-numeric order. Each one contains lots and lots of citations I can improve and share with each family member. In the end I'll have a neat, perfect list of citations with no duplicates.

As long as there's a mess to clean up, why not make the source citations in my family tree live up to my standards?

Each time I delete a ton of duplicate or unlinked citations, my tree's file size gets smaller. Amazingly, my FTM file went from 4 gigabytes on my failing laptop to 360 megabytes on my new computer. I'm still in shock.

I look forward to uploading my improved, streamlined GEDCOM file to Geneanet.org. I'll overwrite the version that's there, rather than synchronize it. I want anyone who sees that tree to find usable links to every bit of evidence I have for a person.

Once I finish my long list of U.S., Canada, and U.K. citations, I'll figure out how to tackle those obsolete Antenati citations.

Even if you haven't suffered damage to your family tree, revisiting your earliest citations is worthwhile. Have a look at them and see how many you're happy with. Bringing them all up to your standard will fortify your family tree.

A Major Family Tree Change to Fix an Ongoing Problem

After 2 gigantic genealogy headaches, I've decided to quit stressing and change course. Genealogy Headache #1 is about this blog.

Trying to Cater to Everyone

A day or two before last week's article, I changed the blog's design. Why? Because it wasn't working well on mobile devices. The moment I published, I knew I had a big problem. The new design was missing important elements that I needed back.

Immediately after publishing (6 a.m. New York time), I searched for a new design. I made changes on the fly, possibly disrupting my readers. I do apologize for that. Since then I've been working my way through my 543 blog articles to make all the images work well on mobile devices. They're all finished now.

It's all been a nightmare, during which I had to settle into a new computer. And that brings me to Genealogy Headache #2.

Hitting the Limits of Technology

Last March I bought a new laptop because my 5-year-old one was threatening to die. But the new one turned out to be under-powered. It was OK (not great) for most things. But it was the worst for running Family Tree Maker. This month I stopped making excuses for its bad behavior. I demoted it to my "travel laptop" and bought a high-powered tower computer.

It took hours to get situated—transferring files, re-installing some programs, adjusting preferences. Once it was all ready, I ran Family Tree Maker and made a couple of changes. It behaved wonderfully. I closed it and the automatic backup happened in a fifth of the time it used to take. Finally I was ready to try to sync my file with my Ancestry tree.

Each step of the sync process was going amazingly fast! I was holding my breath in anticipation. And then…it failed. Worse, it told me my file was corrupt and not repairable. That meant I'd have to download my tree from Ancestry, fix it in Family Tree Maker, and try again.

This happened to me about 3 years ago (according to my old blog articles). Downloading the tree from Ancestry undid all my carefully crafted source citations. I don't want to do that again! I've put up with all this because only Ancestry lets you change your tree offline and synchronize it online. Plus, Ancestry has the best user interface for displaying a tree. Hands down.

Another Approach to Sharing a Family Tree

The reason I'm so keen to share my constantly-updated family tree is distant cousins. My tree is a treasure for anyone with ancestors from my ancestors' towns in Italy. My tree on Ancestry has 57,096 people. At least 53,000 are from a small area of Italy, and they date back to the late 1600s.

Now I've got a new idea. I'll let my Ancestry tree and DNA tests continue to attract distant cousins. But what if I put my tree on another website and swap out the old GEDCOM for a new one every few months? Forget all that stress from failed syncs!

Problem: How to display my family tree without letting anyone change it AND update the entire file anytime I like.

After weighing the options, I'm going with Geneanet.org. With a free membership, I can upload a GEDCOM, and after I've made a lot of updates, I can re-upload a GEDCOM. I'm not uploading documents, but I've got them all here. If someone contacts me about their branch, I'm more than happy to share every bit of my research.

I chose Geneanet based on these important features:

1. No one else can edit my tree! That's paramount.
2. I don't have to build my tree on their site; I can upload a GEDCOM.
3. I can upload a new GEDCOM later and overwrite the current family tree.
4. I can share my updated tree with whomever I want.

Geneanet happens to be free, but that wasn't a top priority. You can pay a very reasonable price for a premium subscription, but I don't need what it offers.

Now I can go hog-wild editing my Family Tree Maker file without worrying about the next failed sync. I'm sure many of you are happy with your methods. Perhaps:

• your family tree is small enough that an Ancestry sync never fails
• you'd rather die than pay Ancestry a single dollar when FamilySearch is free
• you don't want to share anything online because "that's how they get ya!" (cue the eyeroll)
• you don't mind letting any jamoke with web access rewrite your research.

While I didn't upload my documents to Geneanet, I'm thrilled to see it makes all my sources available as proof.

I'm going to enjoy using Family Tree Maker with my new computer's speed. I'll keep on adding everyone from my ancestral towns who fits. I'll ignore my tree on Ancestry until someone writes to me and wants to know more. And hopefully Google will stop emailing me about my blog's mobile issues.

And speaking of technology gone wrong:

• Prepare Your Family Tree for Your Computer's Demise
• Moving Your Family Tree to a New Computer
• How to Back Up Your Family Tree Files Automatically

Pluck the Stragglers Out of Your Family Tree

I love when someone finds their family in my online tree and contacts me. Last week I heard from a new-found 4th cousin.

Often our connection is distant—cobbled together through the relatives of in-laws. I had this type of connection last week, too. A woman found her grandmother in my tree and wanted to know what else I could tell her.

I told her everything came from the 1920 census and a few New York City death certificates. But I had nothing else to offer.

In fact, as I wrote in my reply, she shouldn't be in my family tree at all. I explained that her grandmother's sister married a man named Celentano. That man's uncle married my grandmother's 1st cousin, Consiglia Sarracino.

I knew from the names Celentano and Sarracino that this was some of my earliest family tree research. When I started, I followed every possible thread for my American cousins.

I used censuses to stretch out the Celentano family as far as I could. And then I built out the families of the people who married into the family. That's how her grandmother wound up in my tree.

Enforcing the In-Law Rule

It wasn't until much later in my genealogy life that I created an in-law rule:

I will not add anything to an in-law's profile beyond their facts and their parents' facts UNLESS my cousin asks me to research that family.^*

^*This rule does not apply to my Italian research where entire towns are inter-related, and I want everyone.

Establish a rule to keep your family tree on the path you want.

How many other far-flung in-law branches are still in my family tree? How can I find them in my enormous file?

I explored Family Tree Analyzer software for a while, but it wasn't a shortcut. Maybe there is no shortcut.

Stragglers in my tree would come from my parents' and grandparents' generations. Those are the people I would have found in my early census searches.

Most of my close cousins are from my maternal grandmother's family. In my earliest days, I would have spent time on the families of Grandma's aunts and uncles, the Saviano family.

This is a manageable group to work with. Grandma had only 3 Saviano aunts or uncles who lived long enough to marry and have children.

Uncle Semplicio

As a little girl, my mom was afraid of her great uncle Semplicio. He was an older man with one eye. He literally lived in a closet next to her apartment for a while.

Long ago I met someone online with a connection to Semplicio's wife Giovina. With his encouragement, I built an enormous tree for Zia Giovina. Once I decided to follow my in-law rule, I cut out every relative but Zia Giovina's parents.

Looking in Family Tree Maker, I see families for 3 of Semplicio and Giovina's children. I can view each family to see if I need to delete anyone. Nope. Everyone was following the in-law rule.

Aunt Filomena

My grandmother's aunt is an example of going out of my way to document an in-law. But I want it this way. One of her grandsons is very interested in our family history, and he helped me with it.

Plus, Filomena's husband came from a town very close to Filomena's Italian hometown. There may be a family tie somewhere in their past!

Uncle Raffaele

Uncle Raffaele died long before I was born, but his wife Lucia was sometimes at family gatherings. My brother and I knew her and Aunt Filomena as "Zee Loo Gee" (Zia Lucia) and "Zee Vulla Men" (Zia Filomena). We never saw Zee Vulla Men without Zee Loo Gee.

I have extended families for Raffaele and Lucia's children in my family tree. Clicking through to view them all, I found only one in-law family I should delete. I do want to preserve the research, but not in my main tree. I'll follow my own advice and export this group of people to a new tree before deleting them from mine. (See "How to Export and Delete Branches from Your Family Tree.")

Exporting the 46-person branch was easy, but it didn't seem to capture the media files. I'll do that myself. My document tracker file will help me see which media files belong to this batch of people.

Deleting the branch was tricky. There wasn't one ancestor whose descendants capture the whole group. Instead, I worked my way through the families, noting all their media files. Then I viewed a family tree chart for each group and deleted them from my family tree.

I made sure all the right media files were no longer in my main tree, and I exported a new GEDCOM from Family Tree Maker. A GEDCOM is a text file that follows a standard format that any family tree software can understand. I opened the GEDCOM with Family Tree Analyzer to see if I missed anyone. Would FTA find unrelated people from this branch still in my family tree?

If your family tree is big, Family Tree Analyzer can narrow it down to certain types of names for you.

Here's how to check:

• Launch Family Tree Analyzer and open your latest GEDCOM.
• Go to the Main Lists tab to see everyone in your tree on the Individuals tab.
• To exclude close family and true cousins from this search:
  • Scroll to the right to find the Relation to Root column.
  • Click the arrow button at the top of the column to open a small window.
  • Unclick Select All, then click to select only the blank field at the top of the list.
  • Click the Filter button to close the small window.
• Scroll all the way left to find the Surname column.
• Click the arrow button at the top of the column and choose Sort A to Z.
• Browse the shorter list for the last names you don't want to find.

Success! I didn't find anyone who wasn't supposed to be there. Now I can backup and save my Family Tree Maker file.

But I'm not really done, of course. I have some cousins through my paternal grandmother, and her mother had a bunch of brothers. I can run through this same process with that branch and a few others.

Should You Do This, Too?

The main reasons for going through this export/delete process are:

• to stop misleading people into thinking you're their blood relative
• to stop spending time on branches that aren't the focus of your family tree
• to conserve computer resources.

Plus, I don't like it when I see a name in my tree index and think, "Who on earth is that?"

How to Tell if a Hint is Any Good

I never cared about Ancestry hints. That why I have them turned off when I'm working on my tree in Family Tree Maker. But last year I helped out another genealogist by adding to a few research trees she had on Ancestry. That's when I saw the value of hints.

They're a real time-saver! Say you're piecing together the life of someone you don't know. If they have a bunch of documents in their hints, that's where I'd want to look first.

But you never want to accept hints blindly and add them to your family tree. Think of them as nothing more than a possible match. They could be wrong, you know. Each one is there for you to check out.

It's your job to examine each hint and figure out if it matches your family.

A Well-Timed Hint

I grew up with about ten 1st and 2nd cousins on my mom's side of the family. One of these cousins recently asked for access to my online Ancestry tree. I warned her that:

• My tree is freakishly big because I'm connecting entire Italian towns. See How Do You Define Your Ultimate Genealogy Goal?
• I had absolutely nothing on her father Larry's family.

Larry died shortly after my 1st child was born in 1989. It came as a shock to me, and a terrible loss. In recent years I've tried to learn about his family, but I never had enough details to get anywhere.

When I viewed my tree online to see what my cousin was about to see, I found something new. There were a couple of green Potential Father and Potential Mother hints for Larry. In fact, there were 9 hints for him. The first was the 1950 census I'd been unable to find on my own.

Sometimes I laugh at potential parent suggestions. But this time, the hints were pure gold.

Now that I had confirmation for a handful of Larry's facts, I started looking into his father. I soon found an unsourced family tree that had several generations of Larry's family. But was this information right?

Is This Hint Any Good?

Larry's grandparents came from Italy. That meant I could verify those unsourced names and dates. I used the online Italian vital records website, Antenati, and searched the right town.

I confirmed and added to the family's names and dates. I got the correct spelling for the family name. (See Look Past the Misspellings to Find Your Ancestors.) Plus I found many more names and dates specific to Larry's paternal line. I wouldn't have trusted any of these names or facts from a hint or a tree without seeing the documents for myself.

How to Harvest a Hint

After many years of ignoring hints, I'm now open to exploring them. When you have a lack of information, as I did for Larry's family, the right hints can push you onto the right path. But you must confirm that it's the right path by doing the research for yourself.

When you look at a hint:

1. Make sure it doesn't contradict something you know for sure. Is the person born in a state or country that's impossible for your person? Are they the wrong age by a long-shot?
2. Examine all the documents and see if any don't fit with the others. The one hint that referred to Larry as a lawyer was absolutely not my cousin. I know what he did for a living. Take a look at 3 Ways to Tell If That Hint is No Good.
3. See which documents your favorite website offers you for this person. This gives you more data points to compare. Some documents may not fit in, especially when compared to those that do.

Documents are critical. ("Pics or it didn't happen!") You need to see and verify the facts for yourself. That's why you must fully research hints that come from unsourced family trees.

It's up to you to confirm whether a hint is putting you on the right path. And if it is, the race is on!

My cousin was hoping to tie a particular last name to her family. When I found her grandparents' NYC marriage certificate, I had the answer. The bride's mother had the last name we were looking for.

That's a perfect example of a fact I wouldn't believe or accept without seeing the document for myself.

I hope you find hints that set you on the right research path. Just remember, they may be way off base.

Your Genealogy Mission for 2023

Which genealogy projects do you expect to work on in 2023? I was hoping to complete a big project in 2022, and I thought I had it all wrapped up. Then I found I had a bit more to do. (As of this writing, I have finished!)

I'm eager to get this piece done so I can dive into the next big thing. It's a continuation of my main theme—connecting everyone from my ancestral hometowns. In 2022 I published an inventory of every available vital record for Colle Sannita. That's my paternal grandfather's town. (See "How to Create Your Ancestral Hometown Database.") These documents are available on Italy's Antenati website, but they aren't all searchable.

Set yourself up for the most enjoyable year of genealogy!

Anyone searching the web for "colle sannita searchable vital records" will find my file. It shows the name of every person captured in the town's available vital records. The file has links to Antenati web pages where you can see the documents for yourself. (See "How to Use the Online Italian Genealogy Archives.")

Besides that very helpful inventory of documents, I did a crazy thing last year. I connected everyone from those 38,000+ documents in my Ancestry family tree. Blood or marriage connects the whole town, with very few exceptions.

I see this as my legacy—my contribution to Italian genealogy.

On New Year's Eve, I was finishing up my inventory of vital records for my other grandfather's hometown, Baselice.

I thought I was about to finish, but I found some work still to do on 1932–42 deaths and marriages. Once I finish and publish the inventory, I'll work everyone from Baselice into my family tree, too. (Most of them are already there because of one of my first big genealogy projects. See "Why I Recorded More Than 30,000 Documents.")

This ongoing project motivates me every single day. It's my full-time job. A job I love. As I work through one town, all I can do is think about which town I want to do next!

Make Progress on More than One Track

When you have more than one big project to do, shake off any boredom by having another task to jump to. Fitting everyone from Baselice into my family tree will take a long time. I may feel bogged down at times.

I can keep up my energy by shifting to another town once in a while. Three of my other towns' vital records are almost ready to go into their own inventory spreadsheet. Two other towns of mine need me to finish renaming the files.

All my towns' vital records are on my computer, but mass-downloads are not possible anymore. I have them stored in separate folders by town, by year, and by type (birth, death, marriage). My file name format for the vital records is the full name of the person who was born or died, followed by their father's first name. For example, the first document image in the "1809 births" folder for the town of Circello is:

1 Angelo Antonio Maria Ianesso di Nicola.jpg

This is the 1809 birth record for Angelo, the son of Nicola. The word "di" means "of" in Italian. It's used to show someone's father's name. Naming conventions in many cultures lead to having a bunch of people in town at the same time with the same name. It saves confusion if you add a father's name to distinguish one Antonio Bianco from another.

The #1 in the file name is the document number in a book. That'll be very helpful if a descendant of Angelo finds his name in my published inventory some day. They'll be able to find the right document easily.

For marriage records, my file names don't include fathers' names—only the full name of the groom and bride. It would be too confusing to see a marriage document with a name like:

1 Vito Aufolisi di Giovanni & Elisabetta Cerrone di Giuseppe.jpg

That looks like it could be an image with 2 birth records or 2 death records.

Stay Open to Sudden Breakthroughs

Of course, there will always be other smaller projects to distract you from your more lofty goals. That's OK. Go with the flow! This past weekend I finally had a breakthrough on my 2nd cousin's father's family. When my cousin asked me if she could access my family tree, I was sorry to tell her that her dad's family isn't in there at all.

Then I saw an Ancestry hint that finally opened his family up to me. I'm hoping to find his grandfather's Italian birth record to give to my cousin.

Get ready for your best year of genealogy yet!

This is Much More than a Hobby

Two weeks ago I suggested you look back at your family tree work in 2022 and see where it leads you in 2023. (See "It's Time to Wrap Up Your Genealogy Year.") You may not have a grand scheme in mind. But I'll bet you learned what works, what doesn't work, what makes you happy, and what's a total bore. Whichever projects work well and make you happy should get top priority.

Here are a few examples of smaller projects I've suggested in the past. Which ones look enjoyable to you?

1. Trim the waste out of certain document images. See "How to Improve Your Digital Genealogy Documents."
2. Share your tree with those who are interested. See "5+ Ways to Share Your Tree with Family."
3. Research fallen soldiers from your town. See "Fallen Soldier Memorials Inspire a Research Project."
4. Scan and safeguard your precious family photos. See "It's Time to Organize All Your Family Photos."
5. Make a trivia game of your family tree. See "Share Your Family History in a Fun New Way."
6. Fill in your Ahnentafel chart. See "3 Things to Do with Ahnentafel Numbers."
7. Document a cemetery that means something to you. See "The Genealogy Project You Bring Home from Vacation."

I know I'll be happy, productive, and entertained by my genealogy work in 2023. Don't you agree that being productive at something you love is a big key to happiness? I used to feel that way about my job. Now that I'm retired, I'm sticking to my same schedule and working on my true passion. And I never get interrupted by stupid conference calls!

I'd love to hear from you. Where do you think 2023 will lead you in your family tree work?

Top Ten Genealogy Articles of 2022

When I publish a new genealogy article each Tuesday, I try to find topics to make everyone happy. For my final article of 2022, let's take a look at the 10 most popular articles from this year.

Here are the most-read articles of 2022 in reverse order.

Number 10: Your Family Tree Checkup/Tune-up List

When I find a new document for my family tree, I follow all the steps to make sure nothing slips through the cracks.

Number 9: How to Make Your Own Genealogy Correspondence Database

Make all your past genealogy correspondence easy to find. Create a categorized database of all your messages.

Have you missed any of the top 10 articles from Fortify Your Family Tree?

Number 8: Genealogists Can Find Shocking Family Stories

My cousin never knew his grandmother's story. He only knew there were 2 boys who looked like twins. When I pulled the whole story together, it was a complete shock to him and me.

Number 7: Using Color to Understand Your Family's Last Names

Color coding lets you see right away if someone in your family tree is your direct ancestor. And you can tell which of your grandparents descends from them.

Number 6: How to Find the True Cousins in Your Family Tree

You can use the free Family Tree Analyzer tool to identify all the blood relatives in your tree. Find out how many 3rd, 4th, 5th and more distant cousins you've added.

Number 5: Why DNA Matches Appear Closer Than They Are

If your people came from small or remote towns, you may have more than one relationship to a DNA match. Multiple relationships can make them appear to be a closer cousin than they are.

Number 4: Simple Tips for Understanding Italian Marriage Records

This series of articles will help you understand Italian vital records. And you don't need to speak Italian.

Number 3: How DNA Can Help Find Your Ancestral Hometown

If your DNA matches know their ancestral hometowns or match the population there today, it's clear. Your people must have come from the same area.

Number 2: How to Make the Best of the New Antenati Website

Learn how to adapt to the latest design of the Italian Antenati website and make the very best of it. It's a treasure trove for those with Italian ancestry. Not speaking Italian shouldn't scare you away!

Number 1: 7 Days to a Better Family Tree

The next 7 days you decide to work on your family tree, pick one of these goals and work on only that one thing. No distractions allowed.

The purpose of this blog is to help you create a more professional family tree. That's why many articles are about finding errors, and improving citations and images. DNA is a popular topic. With my knowledge of Italian genealogy, Italian document articles widely read, too.

In 2023, I'll try to find new ways to engage you with tips, lists, and helpful spreadsheets. I'm open to suggestions. Just leave a comment or drop me a line. Thanks so much for reading!

It's Time to Wrap Up Your Genealogy Year

I haven't created a list of next year's genealogy goals since 2020. I stopped because my techniques and my true mission kept evolving.

The best example of this is what happened after I finished this 2019 genealogy goal:

• Log 5 years' worth of birth records from each of my ancestral hometowns into spreadsheet.

I completed that goal, but my next project made my 2019 effort useless. The purpose of logging those 5 years of documents was to make it easier to search for any one person.

But I found an infinitely better method. And it was much easier to completely finish than adding to the spreadsheet. I renamed thousands of Italian vital record image files to include the name of the person and their father.

What's the next logical step to take in your genealogy journey?

For example, here's how I renamed the 2nd birth record of 1809 in one of my towns:

2 Pasquale Maria Cernese di Giovanni.jpg

The baby is Pasquale Maria Cernese (Maria is a common middle name for Italian baby boys), the son of Giovanni Cernese. With all the files renamed this way, I can easily search for all the children of Giovanni Cernese at once. I can run the Windows program called Everything and type in:

"Cernese di Giovanni

That'll show me a list of every possible child of Giovanni Cernese. My work is now a database that I share with other descendants of my towns.

I've explained this, my secret weapon, many times before. This time, it's a prime example of why I stopped setting annual genealogy goals. Instead, I'm constantly working on my tree and imagining how I can make the most of all that data.

So instead of making a 2023 Genealogy Goals List, let's look back for a moment. Let's take stock of our 2022 genealogy accomplishments. Then we can wrap up our genealogy year and dream up what comes next. I'll start. In 2022:

• I finished examining the 38,000 available vital records from Grandpa Iamarino's hometown of Colle Sannita. (See How to Use Your Personal Genealogy Database.)
• I made the names of all those files available to anyone who may search the internet for "Colle Sannita." (See How to Create and Share Your Ancestral Town Database.)
• I followed different types of genealogy leads to unexpected places. (See A Random Search Led to a Detailed Life Story.)
• I returned to my Genealogy To-Do List again and again to keep things interesting. (See Start Your Rainy-Day Genealogy List.)
• I used Family Tree Analyzer, the relationship calculator spreadsheet, and color-coding to see my family tree's facts and connections in different ways. (See How to See Your Cousin Connections More Clearly.)
• I spent November tying up a long list of loose ends in my family tree. (See Make November Genealogy Loose Ends Month.)
• I somehow managed to publish this blog every Tuesday!

As 2022 ends, I'll finish renaming the vital records from my other grandfather's hometown—Baselice. Then I'll be ready to piece together every Baselice family in my tree. And I'll publish my database for other descendants of the town to use.

One big goal is nearly finished, clearly paving the way for my next big genealogy project.

Unless a new idea strikes me, I'll move on to another one of my ancestral hometowns. For me, that's what genealogy is all about. I'm claiming every last drop of my heritage.

What were your genealogy accomplishments in 2022? Where will that work lead you in 2023?

Don't Get Over-Ambitious with Your Family Tree

Recently I wrote about how I ripped 25,000 obsolete source citations out of my family tree. I did it in one place: the Sources tab of Family Tree Maker. And despite being such an enormous change, I had no problems.

It cut my tree's file size in half. I needed that! And I synchronized my tree with the one on Ancestry.com successfully. No problems at all.

That success made me a bit too bold. Recovering from my next decision took 4 days. And I still have a lot of collateral damage to fix, but nothing devastating.

NOTE: Before you tell me how much better your family tree software is, it can't do what FTM can do. Only this software lets me work on my tree on my computer and regularly synchronize my work with my public tree on Ancestry.com. My family tree needs to be shared!

Pushing that Button

I was happily updating source citations for vital records from 1809. I have a few hundred of them in my family tree. I need to update them because the Italian vital record website (Antenati) changed the URLs of every document. I began to notice along the way that attached to each Italian "repository" in my tree was an old URL. And each old URL does not work. That's no good.

Then I went and did a crazy thing. I did a search and replace for the bad part of the URL. As I clicked Replace, I quickly saw how massive a change this was. This one little edit affected thousands of media, citations, and people.

But I'd had good luck before, so maybe it'd all be fine.

As I clicked Replace in Family Tree Maker, I quickly saw how massive a change this was. Undo! Undo! Alas, it was too late.

It wasn't. I started the sync process at 2:30 in the afternoon. Occasional status reports said my edit affected about 7,000 people, 5,000 media files, and 10,000 source citations. Then the progress reports ended. It was simply "analyzing changes" for hours. I set my computer not to go to sleep, and I went to bed.

When I checked my still-running computer in the morning, there were 2 messages:

• Family Tree Maker lost its internet connection, causing the sync to fail.
• FTM had identified 55 people with discrepancies, and it asked me how to handle them. I clicked "overwrite with information from FTM," but with the interrupted internet connection, it was too late.

I had to compact my file again, which takes about 90 minutes. Then I tried to sync again. It still failed. But it went a long way before calling it quits. It appeared to update all the citations, media, and people, but I guess it didn't finish.

I had to go to Plan B. I opened my backup file from just before the doomed search and replace. I began the sync process again. That meant that even this older file was vastly different than my online tree. Much like the last time, the process took 12 hours, and despite promising status reports, it failed.

I closed my file and compacted it, deciding to chat with FTM support in the morning. Brandon at FTM found that one (only one!) of my 57,114 people had gotten corrupted. He advised me to make note of her facts and delete her from my Ancestry tree. Then he said to close and compact my file again before attempting to sync.

This time it worked. I did the ill-fated search and replace on Friday afternoon. I was finally synchronized and ready to go late Sunday morning.

The Aftermath

The back-and-forth between FTM and Ancestry during the failed syncs broke several things. Now that my family tree is synchronized with Ancestry again, here's what I need to fix in my file:

• Lots of unrecognized addresses. I need to delete several of them because the people who lived there are no longer in my tree. But the rest belong in my tree. I can fix these for one person and choose to correct the error everywhere the address is found. I'll fix them as I spot them.
• 7,500 uncategorized media. Luckily I can select bunches at a time and categorize them at once. I fixed them in a few minutes. Media categories don't carry over to Ancestry.com, so these changes were not involved in my next sync.
• A small number of missing media. I have to retrieve them from my computer. Not a problem.
• Some marriage citations split in two: one citation for him and another for her. But they all have the correct updated URL that started this whole mess!
• Some people have duplicated facts—name, sex, birth, etc. I'll fix them as I find them.

A recent success with a big change to my family tree made me a bit cocky. Now I'm paying the price.

That's what broke because of my sync woes. I've started to revisit the hundreds of 1809 source citations I updated at the end of November. But I won't fix them all in one session.

Lessons Learned

I've learned these lessons before! But I got cocky and need a reminder.

• Don't make huge changes all at once, no matter how lucky you feel. Handle big changes in smaller chunks.
• Save and compact your file after you finish one type of change, or a moderately sized batch of changes. Then,
• Sync your file before moving on to another type of big change.

My problem is that I work on my family tree full time. I make a ton of changes every day. I suppose as long as those changes don't affect 7,000 people, 5,000 media files, and 10,000 source citations, I might be alright. Onward!

Which Side the Cousin Falls On is Key

It's always great when someone who writes to you about your family tree turns out to be a distant cousin. They'll usually say, "My great grandfather is in your family tree. How are we related?"

It always takes a little work before I can answer that question. First I find their ancestor in my family tree and see their relationship to me. Then I add my new cousin to my tree—without knowing the names of their parents or grandparents—to see our relationship.

That ends now. A few years ago I shared a spreadsheet I called a relationship calculator. (Download your free copy.) Its main use is to help you name your exact relationship to a descendant of one of your ancestors.

For instance, when I go to Italy I visit my Dad's first cousins. Their grandparents were my great grandparents. If I want to know my relationship to my cousin's grandchild, I can use the relationship calculator. I am the great granddaughter of Francesco Iamarino, and my cousin's grandchild is his 2nd great grandchild. That makes the youngster my 2nd cousin once removed (2C1R). The spreadsheet makes that clear.

What if we look at the same spreadsheet in a different way? This time I want to find my relationship to the great grandchild of a particular cousin in my family tree.

Once you find which cell matches a particular cousin, you'll see your relationship to all their descendants.

I'm randomly choosing Antonio Pilla from my family tree. Born in 1878, Antonio is my 2nd cousin 3 times removed (2C3R). Let's pretend his great granddaughter wrote to me asking how we're related.

Step 1 of 2. Find the Right Cell

"2nd cousin 3 times removed" is in 2 different cells of the relationship calculator:

• once in relation to my 1st great grandparent (column E row 11), and
• once in relation to my 4th great grandparent (column H row 8).

That means I need to understand how I'm related to Antonio Pilla. Our relationship chart on Ancestry.com shows a connection through my Francesco Iamarino. He's my great grandfather. That means Antonio Pilla is my 2C3R found in column E row 11 of the relationship calculator.

Step 2 of 2. Count the Generations

The rest is a snap. Antonio is my 2C3R from column E row 11, and I want to see my relationship to his great granddaughter. All I have to do is move down column E three rows:

1. move down one row for Antonio's child
2. move down a second row for Antonio's grandchild
3. move down a third row for Antonio's great grandchild.

Now I'm at column E row 14 which reads "2nd cousin 6 times removed" (2C6R).

"No kidding, Einstein," you say. "Your 2C3R plus 3 generations equals your 2C6R."

That's right…except when it isn't. And now I finally see why that simple math works only some of the time. It depends on which side of the yellow line your relationship falls on.

The updated relationship calculator (see the link above) has a diagonal string of cells highlighted in yellow. Each yellow cell is a full-cousin relationship: 1st cousin, 2nd cousin, 3rd cousin, etc.

Same type of cousin. One to the left and one to the right of the yellow line. Which side the cousin falls on is everything!

Antonio Pilla fell into cell E11, and that's to the left of the yellow line. But what if my relationship to him was the 2C3R found in cell H8—to the right of the yellow line? You can see that the great granddaughter of a man in cell H8 would be my 5th cousin! The progression would be:

• Antonio 2C3R
• his child 3C2R
• his grandchild 4C1R
• his great grandchild 5C

That's what's been driving me nuts. I couldn't understand why simple math didn't always work. The key is that yellow line.

Maybe you're able to figure out relationships in your head. But as you've seen, you've got to get past one big wrinkle: the yellow line.

Now I can stop putting temporary, unnamed people in my family tree just to figure out a relationship. The answer was right there all along in the relationship calculator!

Find more ways to use the relationship calculator:

• How to Find Your Exact Relationship to Any Cousin
• This Chart Finds Hidden Relationships in Your Family Tree
• Can't Connect to Your DNA Match? Keep Trying