Family Search Data Definitions – Part 2 – Forums

#1 · 2026-07-02, 6:34 pm

I decided to create a 2nd post so this does not get buried. After working some more with the data, I gave the FamilySearchTable to AI and asked it to analyze the data. Here is what it came up with:

Status 5 = the original bulk import batch — every one of these rows was written in the same ~24‑hour window on 2022‑09‑10/11, and no rmID in this group exceeds 1648. This is clearly your initial FamilySearch link-up.
Status 0 = everything that's been touched since — it spans the entire timeline from the original import date all the way to your most recent activity (June 2026), and includes the newest rmIDs (up to 2596). This looks like your "current/active" or "ongoing" link status, picking up both older links that got re-touched and brand-new links.
Status 4 = a small, tightly clustered batch of 21 records, all modified between Jan–Sep 2025 and all with rmID in a narrow high range (2363–2535). This looks like a distinct one-off batch operation (a specific import or cleanup pass) rather than routine ongoing work.

Anyone else willing to analyze their data to see if they come up with the same. We could update the data definitions:

Status 0: Manual match of FSID with RMID

Status 4: AutoMatch in FSC performed after initial run

Status 5: Initial AutoMatch performed in FSC

Charles

#2 · 2026-07-03, 8:52 pm

My test results with RM v11.4.0.0 show:

Automatch vs manual match has no impact on FamilySearchTable.Status value (Status=0 in both cases.)
FamilySearchTable.Status=4 indicates an Import from FS

I also confirmed in my old RMv7 db that LinkTable.Status=0 for all records. (This makes sense because I never used the import feature in RM7.) It's possible that LDS Church members could see additional values.

The timeline of the changes noted in your post aligns with RM v8.2. (8.2.5 was released on Sept 6, 2022 and several FamilySearch related fixes occurred in the 8.2.x releases.) It's possible that V8 temporarily introduced Status values=1,5 versus 0,4 and that this change was later abandoned. That would also explain why the values of "0,1,4" were reported by users during the RM9 data dictionary update.

Finally, additional testing showed that the FamilySearchTable.Modified value is used to populate the "Person changed on FamilySearch" predefined filter group option in the FamilySearch Person Tools window. Specifically, when FamilySearchTable.Modified=1, the Person displays in the "Person changed on FamilySearch" predefined filter group. This filter group can also be accessed via the "View" button in the "What's New" section of the FamilySearch Central window.

I've added comments to the RM11 Data Dictionary Project Spreadsheet.

kevync has reacted to this post.

#3 · 2026-07-06, 2:07 pm

Quote from Charles Banks on 2026-07-06, 2:07 pm
Kevin,

Thanks for responding, I was afraid that I provided too much information for anyone to respond to. Originally, I was using Family Tree Maker for years and first started with using RM 8. The interesting thing is that I brought my data over from FTM using GEDCOM and then created a new tree on ANC with RM. The only thing I used Family Search for was hints and did not know/understand Family Search Central. I do not recall ever selecting 'AutoMatch' yet I started getting hints. I've had this discussion with someone that I had to have used AutoMatch to make the connection. After several years of working with RM I started exploring FS and FSC. I had a lot of mis-matched users on FS and a number of people not connected to FS. It was probably version 9 that I finally used AutoMatch which only connected a small number. With version 10 I started making an effort to connect people as I came across them.

Currently, I have everyone in RM connected to FS connected but am still doing cleanup. What AI told me makes sense in that a large number of people were connected (somehow) initially. Later, I know that I used AutoMatch for a small number and everyone else has been added manually. So, that does align with the numbers, but still begs the question:

Why is it called status, and what is it used for?

The modified=1 I understand and can verify with the API calls and last modified date. Every time you open FamilySearch Central, API goes through every record (matched) in RM and looks for changes. If it finds a change, the modify flag goes from 0 to 1 and it will show up in FSC. Once you click on a person in FSC the flag goes from 1 to 0.

What I don't understand is: if you make a change in RM, nothing happens — why doesn't that trigger the modified flag the same way a change on FS does?

By going into FSC every day and looking at every record, I keep my list manageable and it has been a useful tool. Just trying to understand things more.

Charles

Kevin,

Thanks for responding, I was afraid that I provided too much information for anyone to respond to. Originally, I was using Family Tree Maker for years and first started with using RM 8. The interesting thing is that I brought my data over from FTM using GEDCOM and then created a new tree on ANC with RM. The only thing I used Family Search for was hints and did not know/understand Family Search Central. I do not recall ever selecting 'AutoMatch' yet I started getting hints. I've had this discussion with someone that I had to have used AutoMatch to make the connection. After several years of working with RM I started exploring FS and FSC. I had a lot of mis-matched users on FS and a number of people not connected to FS. It was probably version 9 that I finally used AutoMatch which only connected a small number. With version 10 I started making an effort to connect people as I came across them.

Currently, I have everyone in RM connected to FS connected but am still doing cleanup. What AI told me makes sense in that a large number of people were connected (somehow) initially. Later, I know that I used AutoMatch for a small number and everyone else has been added manually. So, that does align with the numbers, but still begs the question:

Why is it called status, and what is it used for?

The modified=1 I understand and can verify with the API calls and last modified date. Every time you open FamilySearch Central, API goes through every record (matched) in RM and looks for changes. If it finds a change, the modify flag goes from 0 to 1 and it will show up in FSC. Once you click on a person in FSC the flag goes from 1 to 0.

What I don't understand is: if you make a change in RM, nothing happens — why doesn't that trigger the modified flag the same way a change on FS does?

By going into FSC every day and looking at every record, I keep my list manageable and it has been a useful tool. Just trying to understand things more.

Charles

Family Search Data Definitions - Part 2