Before creating a Golden Record from multiple data sources, Helix must first determine which records from the various data sources refer to the same person. The matching rules define the criteria used to decide when two records belong to the same person. Power users can customize the rules; other users may only view them. The matching process runs nightly.
Note: These matching rules are only for the Golden Record. They are not used for deduplication in KORE Ticketing.
How rules work
Select the Matching Rules tab to open the interface. On the left side, you'll see the fields and groupings you can use to create rules. On the right side, you'll see any existing rules. Each rule consists of one or more criteria. Those criteria specify which fields to compare and how to compare them.
When Helix runs the matching process, it takes two records and compares them using the first rule. It uses the field mappings to determine which fields from the source data to compare. If all of the rule's criteria are satisfied, then the rule is met and the two records will be used to combined into that individual's Golden Record. Otherwise, Helix proceeds to the next rule, and so forth. If none of the rules are met, Helix concludes that the records are for different individuals.
When using a group in the match criteria, only one field from each record needs to match.
Caution: A field is null if it contains no data whatsoever. Null fields never match other null fields. However, if the field contains any data indicating it’s blank (such as spaces, dashes, “n/a”, or even the word “null”), it is not null and can potentially match.
Create or edit a rule
Click + New Rule to add an additional rule to the list. Enter a name for the rule. Next, choose at least one field or grouping to use in your criteria. Find it in the left column, then click and drag it into the new rule.
To change an existing rule, you can drag new criteria into the rule and remove existing criteria with the x button. To remove a rule entirely, use the trash can icon.
When finished, click the Save button.
Criteria match types
For each field or grouping you add, open the drop-down list next to it within your rule and choose the type of match you wish to use. Most criteria use "exact" or "fuzzy" matches:
- Exact: The two fields must contain the exact same value, except for capitalization and leading or trailing spaces. For example:
- "MacArthur" will match "Macarthur" or "MacArthur ", but not "McArthur" or "Mac Arthur".
- “Muhammad” will match "MUHAMMAD", but not “Mohammad”.
- "404-555-0199" will not match "(404) 555-0199".
- Fuzzy: Helix will apply KORE's logic to determine when two different values are likely to represent the same thing. For example:
- "Mac Arthur" and "Mac-Arthur" will match "MacArthur" since all whitespace and formatting are removed before comparing.
- “Muhammad” will match “Mohammad” since it's a very common variation of the spelling.
- "Bob" will match "Robert" since it's a very common shortening of the name.
- "404-555-0199" will match "(404) 555-0199" since all formatting is removed before comparing.
- "404-555-0199 x101" will match "404-555-0199 ext 101" since alpha characters are considered part of the formatting and are dropped before comparing.
- "404-555-0199" will not match "404-555-0199 x101" since the extra digits for the extension are not dropped before comparing.
The Email field can use "exact" matches or two other types:
- Domain: Helix ignores the username portion of the email address. For example:
- "email@example.com" will match "firstname.lastname@example.org".
- Without Domain: Helix only compares the username portion of the email address. For example:
- "email@example.com" will match "firstname.lastname@example.org".