Automatically Unmatch FamilySearch

RootsMagic
1

Give us the ability to automatically unmatch everyone in RootsMagic 10 to the FamilySearch person.

2

It had never occurred to me that such unmatching could be a need, but obviously it could be a very useful feature. I support your request.

I could be wrong, but I don’t that the feature presently exists. RM’s support for Ancestry includes a Disconnect feature, but but I cannot find a comparable feature for FamilySearch.

3

I think a full unmatch from FamilySearch would be a trivial development effort. At the database level it would be the simple query to delete all rows in the FamilySearchTable. I’ve not tried it so that is an untested hypothesis.

4

I am not aware of a way to do that within the RM UI – its a fairly simple SQLITE though not supported or recommended by RM

5

I was wondering if removing the RMID would work vs deleting rows

6

I have not tested, but one possible workaround might be to export the database to a Gedcom file, use a word processor to mass delete whatever ged tag is associated with FS IDs, then import the redacted Gedcom back to RM.

7

I can confirm that a short SQLite query accomplishes what you would like on a RM10 database and that I encountered no complaint from RM 10.0.7 on reopening the unmatched file and launching AutoMatch. This is the query:

DELETE FROM FamilySearchTable;

It should be easy for the RM developers to provide a control in the RM user interface to launch it. @rzamor1

A caution/warning should be included that a subsequent FS automatch takes a long time proportional to the size of the database. A small database of 1600 people took nearly 30 minutes to match 628 of them - processing around 50-some people per minute, Thursday midday. Monitoring the Windows Task Manager, it seemed that RM’s AutoMatch interacts with FamilySearch for a period of less than a minute with data rates around 0.1 Mbps and then pauses that interaction for a similar period.

It might be desirable if the range of both this batch UnMatch and AutoMatch itself could be restricted to a selected group. That would be a little more complex for development but not a big deal.

8

Confirming request for an UnMatch All option for FamilySearch has been reported to development.

1 Like
9

Update: This method of mass deleting all FS ID match info works, per my testing.

  1. Export RM 10 database to gedcom file.
  2. Open gedcom with a word processor
  3. Global search and replace tag _FSFTID with tag FSFTID.
  4. Save revised gedcom
  5. Create new empty database file in RM
  6. Import the revised gedcom.

All FS matches are gone!

10

Along with other things one might not want to lose…

11

TomH: Thanks for that info regarding losses when exporting and reimporting via Gedcom transfer.

The RM10 Compare Files tool is misleading (to a novice user like myself) – I was under the mistaken impression that the tool finds all differences between two RM10 databases. Now I know better.