This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
admin_functionality:create_session:step_2_set_attribute_groups [2018/07/24 15:26] luke.swanton [Match Key Column] |
admin_functionality:create_session:step_2_set_attribute_groups [2021/03/04 20:15] conor.doyle |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Step 2 - Setting the Attribute | + | ====== Step 2 - Setting the Match Groups ====== |
---- | ---- | ||
===== Single Entity Configuration ===== | ===== Single Entity Configuration ===== | ||
Line 6: | Line 6: | ||
As per the global setting applied, the list groups will appear here. If needed, you can update this section for the current session. | As per the global setting applied, the list groups will appear here. If needed, you can update this section for the current session. | ||
- | {{ : | + | {{ : |
- | ---- | ||
- | ==== Field Groups Column ==== | ||
- | **Note:** Any default grouping you have made in the settings menu will be imported. See the **[[admin_functionality: | + | **Note:** Any default grouping you have made in the settings menu will be imported. See the **[[admin_functionality: |
- | However custom groups can be added by using: | + | ---- |
+ | **Page Functions:** | ||
- | {{ : | + | {{ : |
- | Alternatively, | + | * **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. | **Note:** Groups and attributes can be re-arranged by using the drag and drop function. | ||
Line 26: | Line 26: | ||
==== Priority Column ==== | ==== Priority Column ==== | ||
- | By default, the priorities will appear as per the global settings. You can set/modify the ' | + | By default, the priorities will appear as per the global settings. You can set/modify the ' |
+ | |||
+ | {{ :admin_functionality: | ||
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: | 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: | ||
Line 37: | Line 39: | ||
Priority is used to select a weight for the group in the match process. | 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 ' | ||
+ | |||
+ | {{ : | ||
---- | ---- | ||
Line 90: | Line 107: | ||
---- | ---- | ||
- | ==== Include For Matching Column | + | ===== Across |
- | + | ||
- | Each group has a checkbox, if you disable matching for a group, it will not be used in the search for duplicates but will still be used to assess its overall duplicate score. | + | |
- | + | ||
- | **Note:** At least one group must be included for matching. | + | |
- | + | ||
- | ---- | + | |
- | ===== Cross Entity | + | |
After you have selected your desired Entities from Step 1, you will be presented with a screen similar to this: | 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: | To start the process you must first go through and assign your related fields from the entities: | ||
- | E.g. Lead.Address_1_Name maps to Account.Address_1_Name | + | E.g. Address1_Country --> Address1_Country (as shown in the screenshot below) |
{{ : | {{ : | ||
- | Next, you must add them into a group folder, This can be in custom groups or default groups: | + | **NOTE:** Attributes map have already been manually mapped on the [[admin_functionality: |
- | **Note:** Any default grouping you have made in the settings menu will be imported. See the **[[admin_functionality: | + | ---- |
- | + | **Page Functions:** | |
- | {{ : | + | |
- | Alternatively, | + | {{ :admin_functionality: |
- | {{ : | + | * **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. | **Note:** Groups and attributes can be re-arranged by using the drag and drop function. | ||
---- | ---- | ||
- | ==== Field Groups | + | ==== Priority |
- | This column contains the Attribute from the Source Entity | + | |
- | ---- | + | By default, the priorities will appear as per the global settings. You can set/modify the ' |
- | ==== Target Column ==== | + | |
- | This column contains | + | |
- | ---- | + | {{ :admin_functionality: |
- | ==== Priority Column ==== | + | |
- | + | ||
- | By default, the priorities will appear as per the global settings. You can set/modify the ' | + | |
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: | 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: | ||
Line 141: | Line 147: | ||
* Medium | * Medium | ||
* Normal | * Normal | ||
- | * | + | |
+ | Priority is used to select a weight for the group in the match process. | ||
---- | ---- | ||
- | ==== Match Key Column | + | ===== Match Key ===== |
- | This column allows you to specify your matching engine. | + | 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: |
- | There are six options available: | + | ==== 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 | ||
+ | |||
+ | 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. | ||
+ | |||
+ | {{ :admin_functionality: | ||
+ | |||
+ | ==== 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 ' | ||
+ | |||
+ | ==== Metaphone ==== | ||
+ | |||
+ | Metaphone improves the Soundex algorithm by using information about variations and inconsistencies in English spelling and pronunciation, | ||
+ | |||
+ | 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), | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ==== 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. | ||
+ | |||
+ | **Include for Matching:** With the help of a checkbox feature, you can configure the ‘Include for Matching’ to select the attributes to be used for matching purposes. By default, the group is included for matching. You do have the option to uncheck the group and mark it as excluded. The groups which are not included for matching are still used for percentage scoring. | ||
- | * DQ Fonetix (Recommended) | ||
- | * DQ Metaphone | ||
- | * DQ Soundex | ||
- | * Metaphone | ||
- | * SoundEx | ||
- | * No MatchKey | ||
---- | ---- | ||
+ | |||
==== Include For Matching Column ==== | ==== Include For Matching Column ==== | ||
Each group has a checkbox, if you disable matching for a group, it will not be used in the search for duplicates but will still be used to assess its overall duplicate score. | Each group has a checkbox, if you disable matching for a group, it will not be used in the search for duplicates but will still be used to assess its overall duplicate score. | ||
- | **Note:** At least one group must be included for matching. | + | **Note:** At least one group must be included for matching. |
+ | |||
+ | ---- | ||
===== Miscellaneous Functions ===== | ===== Miscellaneous Functions ===== | ||
Line 169: | Line 216: | ||
**Note:** However this will vary depending on entity and the default groups you have setup. | **Note:** However this will vary depending on entity and the default groups you have setup. | ||
- | |||
- | {{ : | ||
**Matching Language:** When creating these groups you have the option to choose the matching language. The following can be used: | **Matching Language:** When creating these groups you have the option to choose the matching language. The following can be used: | ||
Line 182: | Line 227: | ||
This option is located: | This option is located: | ||
- | {{ : | + | {{ : |
**Display Attributes by:** This is located just below the language drop-down, and allows you to filter the display names between the database ' | **Display Attributes by:** This is located just below the language drop-down, and allows you to filter the display names between the database ' | ||
Line 193: | Line 238: | ||
This is done by using the drop-down menu available on the ' | This is done by using the drop-down menu available on the ' | ||
- | {{ : | + | {{ : |
**Note:** On this same menu under the ' | **Note:** On this same menu under the ' | ||
Line 204: | Line 249: | ||
**Attribute Searching: | **Attribute Searching: | ||
- | {{ : | + | {{ : |
**Note:** You must search by the title of the display mode you are in. | **Note:** You must search by the title of the display mode you are in. |