Product: MergeOmatic
Description: This solution describes how to configure MergeOmatic
Environment: All
Version: All


Click the Configure button on the Find Tab to define rules for determining duplicates, determining which constituent record should default as the survivor, what data is displayed when reviewing possible duplicates, and which data are merged.


Define which data to use when evaluating duplicates

MergeOmatic uses the preferred address when searching for duplicates and calculating similarity scores. To include alternate addresses in the searching and scoring, select the appropriate address types

Survivor Scoring

When records are merged, the record with the highest "Survivor Score" is kept while duplicate records are merged in to it.

Note: If a record is linked to BBNC that record will always be designated as the survivor

Configure how the survivor score is calculated by selecting whether to choose the record that was added first, added last, or modified last and assigning points to reflect the relative importance of each record type.

You may also assign points to records found by queries – this allows you to assign points based on constituency codes, education, or other factors.

Merge Data

Indicate the data to be merged

Archive Merged Data
MergeOmatic records biographical and other information about each merged record as a notepad on the survivor record. Select the appropriate notepad type.

If you wish to record the merged record’s constituent id as an alias on the survivor record, select the alias type. Select None to not record the source record’s constituent id as an alias on the survivor record.

If the survivor and the possible duplicate have the same constituent attribute, constituent code, and/or constituent appeal, select whether to merge those fields or not.


Indicate which columns you wish to view while reviewing possible duplicates

To add a column, highlight it in the Available Columns pane and click the right arrow to move it to the Selected Columns pane.

To remove a column, highlight it in the Selected Columns pane and click the left arrow to move it back to the Available Columns pane.

To change the sequence of columns, highlight it in the Selected Columns pane and click the up or down arrow to move it within the list.


Duplicate Search
Clear records to be scanned
This will remove all records from the processing queue. This also clears the date last processed information.

Note: Clearing the search queue will NOT delete any constituents and it will NOT undo any merges. It will not remove previously processed records from the search results. It merely clears the list of records queued up for processing and clears the last processed dates from those records. 

Clear possible duplicates
This will clear the results list; the next time you perform a search the list will be populated anew.

Note: Clearing the search results list will NOT delete any constituents and it will NOT undo any merges. It merely clears the list of possible duplicates

Merge Queue
Clear duplicates to be merged
This will return all records in the merge queue to the search results list

Offline Processing
Export queue
If you have found, marked, and added records to the merge queue using an off-line copy of your database, you may create an offline processing file and import it into a fresh copy of your database in order to perform merges.

You will be prompted for the name of your file and then prompted for whether to clear all records from the merge queue.

Import merge queue from file
This will import the offline processing file back into MOM. Records not already in the merge queue will be added; it will not remove any records that are currently in the queue and it will not duplicates records that are currently in the queue.

Define duplicate scoring rules and test the resulting score

MergeOmatic uses sophisticated algorithms to evaluate whether records are possible duplicates and to represent the relative confidence on a 100-point scale.

Note: The following settings have a significant impact on successfully finding duplicate records in your system. Only users with advanced knowledge of how these settings work should attempt to make changes.

Scoring Deductions
The Similarity Score represents the confidence that records are duplicates. A score of 100 represents the highest confidence.

Enter the amounts to deduct from the similarity score when there are differences between the duplicate records.

Scoring Weight
The relative impact that various matching and non-matching fields have when determining if records are duplicates are based on assigned weights for those fields. For example, matching email addresses has a much larger impact on whether records are considered duplicates than matching ZIP codes would, so email is given a larger weight than ZIP code.

Change the weights by entering new values.

Restore Defaults
Restores the default deduction and weight values

For additional information, please refer to the MergeOmatic User Guide.