Controlling Auto-matching

Auto-matching for databases defined by Custodian is switched by default on unless the user decides to turn it off, please be aware custodian likes to keep auto-matching on and therefore if any changes are made to the model (like a match rule change, table change) then the system will turn it back on. This is to prevent data loading/being added by the user and not matched causing integrity issues in the matching and tasks.

However a user with schema rights is able to switch off automatching, this affects the following situations:

  • And records created by the user
  • Data loaded by the feeds
  • Data created via the API
  • Data Inserted directly into monsterDB
  • Rematch requests will be ignored.

To turn auto-matching off for a domain “node”, from the monsterDB command line:

db.nodes.setAutoMatch(false)

Conversely, to turn it on:

db.nodes.setAutoMatch(true)