User Tools

Site Tools


admin_functionality:create_session:step_2_set_attribute_groups

Step 2 - Setting the Match Groups


Single Entity Configuration


As per the global setting applied, the list groups will appear here. If needed, you can update this section for the current session.

Note: Any default grouping you have made in the settings menu will be imported. See the Match Groups Guide for more detail.


Page Functions:

  • 1. Expand All - Expand all match groups
  • 2. Add Match Group - Add existing match group or create a new group
  • 3. Delete - Tag and then remove match groups
  • 4. Refresh - Refresh to pre saved settings

Note: Groups and attributes can be re-arranged by using the drag and drop function.


Priority Column

By default, the priorities will appear as per the global settings. You can set/modify the 'Priority' for each group with the help of drop-down selection. 'Priority' is used to select the weighting for the match group.

By default the priorities will be the same as when set in the default creation, however these can be overridden using the drop-down. The available options are:

  • Exact
  • Very High
  • High
  • Medium
  • Normal

Priority is used to select a weight for the group in the match process.


Match vs Score

This section describes the difference between including groups for scoring vs including groups for scoring.

Include for matching - This will include a match group, along with its attributes, in the matching process.

Do not include for matching - This will not feed the match group to the match engine, however once duplicate records are grouped, this data will be used for scoring records.

E.g Email could be used for matching where sales@dqglobal.com returns multiple duplicate records. However when the data is scored with a score group 'Name' including the attributes 'First Name' & 'Last Name', the records will not score as duplicates upon scoring of these values. This setup would look like this:


Across Entity Configuration

After you have selected your desired Entities from Step 1, you will be presented with a screen similar to this:

To start the process you must first go through and assign your related fields from the entities:

E.g. Address1_Country –> Address1_Country (as shown in the screenshot below)

NOTE: Attributes map have already been manually mapped on the Across Entity Mapping Page.


Page Functions:

  • 1. Expand All - Expand all match groups
  • 2. Add Match Group - Add existing match group or create a new group
  • 3. Delete - Tag and then remove match groups
  • 4. Refresh - Refresh to pre saved settings

Note: Groups and attributes can be re-arranged by using the drag and drop function.


Priority Column

By default, the priorities will appear as per the global settings. You can set/modify the 'Priority' for each group with the help of drop-down selection. 'Priority' is used to select the weighting for the match group.

By default the priorities will be the same as when set in the default creation, however these can be overridden using the drop-down. The available options are:

  • Exact
  • Very High
  • High
  • Medium
  • Normal

Priority is used to select a weight for the group in the match process.


Match vs Score

This section describes the difference between including groups for scoring vs including groups for scoring.

Include for matching - This will include a match group, along with its attributes, in the matching process.

Do not include for matching - This will not feed the match group to the match engine, however once duplicate records are grouped, this data will be used for scoring records.

E.g Email could be used for matching where sales@dqglobal.com returns multiple duplicate records. However when the data is scored with a score group 'Name' including the attributes 'First Name' & 'Last Name', the records will not score as duplicates upon scoring of these values. This setup would look like this:


Match Key

You can set the ‘Match Key’ for each group with the help of drop-down selection. The 'Match Key' is used to select an algorithm for phonetic match token generation. The 'Match Key' drop-down will have six choices:

Soundex

Soundex retains the first letter of the input string to formulate its match token. Soundex removes vowels (a, e, i, o, u) and h and w from the input string. The remaining letters are assigned numbers using a lookup table to produce a token of 4 characters.

This means ‘Cathy’ and ‘Kathy’ will not match as their match tokens begin with a ‘C’ from Cathy and a ‘K’ from Kathy. As such, Soundex does not match well where the start of a word sounds the same but is not the same. Also, due to the numeric substitution it is possible to be shown non-matches (false positive) matches.

DQSoundex

DQSoundex overloads Soundex with the advanced capabilities of DQFonetix™. This improves the start of word logic and modifies the first letter(s) of an input string. DQSoundex will de-pluralise and pre-process the start of words to manage variances like ‘C’ to ‘K’ as in 'Cathy' and 'Kathy', as well as ‘Ph’ as in Phonetix to ‘F’ in Fonetix.

Metaphone

Metaphone improves the Soundex algorithm by using information about variations and inconsistencies in English spelling and pronunciation, to produce a more accurate encoding.

This allows you to find more precise matches than the simple Soundex algorithm. Metaphone considers a larger set of character transformations than Soundex and therefore analyses a string phonetically with far more accuracy.

DQMetaphone

DQMetaphone like DQSoundex is an enhanced Metaphone technology with the advanced capabilities of DQFonetix™. This improves the start of word logic and modifies the first letter(s) of an input string. DQSoundex will de-pluralise and pre-process the start of words to manage variances and improve matching.

In the case shown below (Christopher), Metaphone would have generated three of five names matches. However, after running DQ’s advanced algorithms and advanced logic, DQMetaphone allows ‘Kh’ from 'Khristopher' to match with the ‘Ch’ from 'Christopher'. Thus generating the same match key token.

DQFonetix™

DQFonetix™ contains our advanced phonetic algorithms developed over the last 25 years by DQ Global. The algorithm is property DQ Global and hence we do not share the specification of the process. However, DQPhonetix™ has four key features:

  • Five spoken languages – English, Spanish, French, Italian and German
  • Avoids false matches
  • Overcomes character variances
  • Deals with diacritics

DQPhonetix™ provides your CRM system with the most varied matching window to highlight duplicate matches that may not be picked up – or falsely matches - in Soundex and Metaphone.

No Match Key

Selecting no match key will not generate a phonetic token, hence no match token will be generated. However, this allows you to match identical strings.

admin_functionality/create_session/step_2_set_attribute_groups.txt · Last modified: 2021/03/04 20:17 by conor.doyle