Last year I started a stand-alone tree for my RootsTech Relatives. This year I decided that I wanted to repeat the process, however, I decided I would update what I had started last year.
My prior post “Creating a Tree for RootsTech Relatives” explains how I created the tree.
For my matches, in the FSID custom fact which stands for FamilySearch ID, I had typed Match. So, the first thing I did was use the Edit – Find and Replace function to find all the occurrences of “Match” and replace it with Match – 2022.
I had a smart filter that included all FSID contains Match, I modified it to contains 2022 and renamed the filter to 2022 Matches. I had 559 inputted matches from last year.
Then I created a new smart filter that included all FSID contains 2023 and named that filter 2023 Matches.
So, if I apply the new smart filter, the index will limit the view to only show those individuals who are my 2023 Matches. I use this view to verify that I have entered all the matches that FamilySearch has reported have joined.
I have noticed that last year, it didn’t always show the last deceased person’s info for my relatives. This year it is giving me that information, and I am able to update my previous matches.
If this year’s match was previously entered from last year, I modify the FSID field that contains Match – 2022 to Match – 2022, 2023.
If this year’s match is a newly entered match, then I enter Match – 2023
I have found some matches who have changed their username as in Shannonhill54 is now known as Shannon. Therefore, in the birth description, I entered 2022 = Shannonhill54. I think their former username might be their legal name and thus I don’t want to lose that name.
Thus, when I click “View Relatives”, I start at the top of my list and I type in their username into my FTM Index, if I find them, I modify their entry and verify that it’s the same. I also add those deceased people that last year wasn’t being displayed to me. If they are a new match, I start at the common ancestor and follow the path down to them, entering those individuals who are not already in my tree. Many in the lines of my matches are already in my tree and thus the process goes pretty fast.
Currently, I have very few matches, thus, keeping up with this project this year has been relatively easy (knock on wood).
Also, it seemed that my matches are pretty low, so I made sure to look at how I am connected to my relatives on the shared tree in FamilySearch. I wanted to make sure my known ancestors were showing connected to me. I did find that my 3rd Great Grandfather wasn’t attached to his wife, so I added him.
The purpose of this Relatives tree is for giving me another hint. Perhaps, I have a DNA Match that I don’t recognize the name in my main tree, I could see if they are in this Relatives tree and then research to see if the lineage is accurate. Also, it has extended many of my branches, I can see if that new ancestor is really the parent of my proven ancestor. I might be able to extend my tree back a generation or two or more.
Have fun at RootsTech this year, whether you attend in person or virtually.
