Input Parameters:
- Configuration file – the file path of the configuration file to be used when this procedure is run.
- Main datasource ID – specifies the data source to be used within the configuration file, which contains the table and column mapping specifications. This datasource will be considered the Main dataSource.
- Overlap datasource ID – specifies the data source to be used within the configuration file, which contains the table and column mapping specifications. This datasource will be considered the Overlap datasource.
- Level – Matching Level at which to group the records (Individual, Family, Household, Business, Custom).
After running msp_FindOverlap, this will group all matching record pairs into sets of matching records. If you have previously run FindExactOverlap, then we recommend that you copy the matching pairs data from your exact_matches table into you matches table prior to running this grouping step, unless Merge Exact Matches is enabled.
|
Setting |
Description |
|
generalSettings->preventBridgedMatches |
When enabled mSQL will attempt to stop match groups containing bridged records such as: J Smith John Smith Julian Smith In the scenario above, both John Smith and Julian Smith match with J Smith, but not with each other. |
|
generalSettings->masterRecordIdentification |
When this setting is active, mSQL will use the MasterPriority matrix to determine which record in a matching group should be marked as the master record (i.e. the best record). When this setting is off, the record with the lowest unique_reference will be chosen as the master record. |
|
dataSources->ConnectionString |
Connection string used to connect to the database during processing. |
|
outputSettings->groupedMatchesTable |
Name of the group matches output table that will be produced during the processing of this procedure. Note that if the overlap attribute is empty, then the name in the name attribute will be used. |
|
outputSettings->matchesTable |
Name of the matches table containing the matching pairs that will be used as the input source for this procedure. Note that if the overlap attribute is empty, then the name in the name attribute will be used. |
Overlap matches_grouped table structure
During processing the stored procedure will output the results to the matches_grouped table (this name can be configured – see above). The structure of the output table is as follows:
|
Column |
Description |
|
ID |
Record ID for each matching group. |
|
Record1 |
Reference ID of the first record in the matching pair (from the Main database) |
|
Record2 |
Reference ID of the record that is deemed to match Record1 From the Overlap datasource. |
|
Score |
The Score column is copied from the relevant level’s total score (grouping can only take place on one matching level; to group using multiple levels requires multiple runs of GroupMatches/GroupOverlap). |
|
MatchRef |
Indicates the unique reference of the master record in the group. In the case of an overlap, the MatchRef column indicates the unique reference of the record from the overlap table; in effect, it’s a simple copy of the Record2 column. |
|
BaseScore |
Indicates the lowest score of all the matches in the group, normally not relevant to an overlap. |