Family Search Data Definitions - Part 2
Quote from Charles Banks on 2026-07-02, 6:34 pmI 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
rmIDin 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
rmIDin 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
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
rmIDin 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
rmIDin 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