Videos serve multiple purposes from marketing and business meetings to personalized visual representations. Digitization has made the use of videos more prevalent than ever. It is possible that some will become erroneously attached to new FSID Ref# facts.The relevance of merging video is huge in the recent market. N.B.: the script assumes there are no sources, media, or any other element attached to the existing Ref# facts and makes no attempt to preserve those linkages nor to delete the records in the corresponding tables. Requires the REGEXP extension which is not included in all SQLite managers SQLiteSpy does support it. This feature is of uncertain value.Ī temporary table xRefnBak is created by the script and is deleted when the SQLite manager closes the database. The script also preserves and pushes to the front existing FSID Ref# facts for a person not currently matched in the database to Family Search, i.e., the FSID has been somehow lost or the fact was manually added. This script shuffles existing Ref# facts to follow the FSID Ref# facts it creates by copying the former out to a temp fable xRefnBak, deleting the originals from the EventTable and then appending them after the FSID Ref# facts are created. This enables the Duplicate Search Merge (DSM) option “Find people with the same reference numbers (and ignore everything else)” to pair up people with the same FSID Ref#.
Sample of database after script has run to copy the FamilySearch ID into the first Ref# fact for each person for those persons having been matched to FamilySearch.Ĭreates a Ref# fact containing the FamilySearch ID for each person in the database matched to a person on FamilySearch Family Tree in the format “fsid: XXXX-XXX”. Thus it requires this FSID Ref# fact to be the lowest record number of all the Ref# facts for a person in the EventTable.Įnter a SQLite script that addresses these issues enabling DSM to pair up matching FSID Ref# facts. Duplicate Search Merge compares only the first Ref# fact for a person to the first Ref# fact for each other person. Moreover, it is complicated if the people have pre-existing Ref# facts for other purposes that must be preserved. Getting the FSID into a Ref# fact is a laborious task if there are more than a few people to do. This should also be useful when people matched to FamilySearch get duplicated in a database through other avenues such as overlapping downloads from FamilySearch into the same database. “Find people with the same FamilySearch ID (ignore all other information)”Ībsent that third option, the user figured that if she could get the FSID into a Reference Number (Ref#) fact for each person, the databases could be combined and DSM with option 2 would reliably pair up the duplicate people.Wouldn’t it be nice if there was another option: