DQ for Dynamics™/DQ for Workbooks Wiki

User Tools

Site Tools

You are here: Start » admin_functionality » create_session » step_2_set_attribute_groups
admin_functionality:create_session:step_2_set_attribute_groups

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
admin_functionality:create_session:step_2_set_attribute_groups [2021/03/04 20:05]
conor.doyle 		admin_functionality:create_session:step_2_set_attribute_groups [2023/01/23 16:53] (current)
hayden.law [Related Entities]
Line 41: Line 41:
  
 ---- ----
 +
 ==== Match vs Score ==== ==== Match vs Score ====
  
Line 53: Line 54:
 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: 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:
  
-{{ :admin_functionality:create_session:scoring_vs_matching_example.png?800 |}}+{{ :admin_functionality:create_session:scoring_vs_matching_example.png?800 |}} 
  
 ---- ----
-===== Match Key ===== +===== Across Entity Configuration =====
- +
-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. +
- +
-{{ :admin_functionality:settings:kathy.png?nolink&600 |}} +
- +
-==== 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.  +
- +
-{{ :admin_functionality:settings:christopher.png?nolink&600 |}} +
- +
-==== 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. +
- +
- +
----- +
-===== Across Entity  Configuration =====+
  
 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:
  
-{{ :admin_functionality:create_session:1.2.png?600 |}}+{{ :admin_functionality:create_session:xentityv3.png?800 |}}
  
 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:
Line 119: Line 69:
 {{ :admin_functionality:create_session:cross_ent_step_2_2.png?nolink |}} {{ :admin_functionality:create_session:cross_ent_step_2_2.png?nolink |}}
  
-**NOTE:** Attributes map have already been manually mapped on the [[admin_functionality:settings:map_entities|Across Entity Mapping]] page, or Auto mapped on the [[admin_functionality:settings:map_entities_setup|Map Entities Setup]] page.+**NOTE:** Attributes map have already been manually mapped on the [[admin_functionality:settings:map_entities| Across Entity Mapping Page.]]
  
-Next, you must add attributes to a group folder. This can be in custom groups or default groups: +---- 
- +**Page Functions:**
-{{ :admin_functionality:create_session:step_2_5.png?nolink |}} +
- +
-{{ :admin_functionality:create_session:1.4.png?300 |}} +
- +
-**Note:** Any default grouping you have made in the settings menu will be imported. See the **[[admin_functionality:settings:set_attribute_groups| Set Attribute Groups Guide]]** for more detail.+
  
-Alternatively, default groups from other entities can be added using:+{{ :admin_functionality:create_session:functions.png?200 |}}
  
-{{ :admin_functionality:create_session:step_2_6.png?nolink |}}+  * **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 Column ====+==== Priority Column ====
  
-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 'Priority' for each group with the help of drop-down selection. 'Priority' is used to select the weighting for the match group.
- +
----- +
-==== Target Column ==== +
- +
-This column contains the Attribute from the Target Entity +
- +
----- +
-==== 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. The 'Priority' drop-down will have five values:+{{ :admin_functionality:create_session:priority_cross_entity.png?800 |}}
  
 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 157: Line 97:
   * Medium   * Medium
   * Normal   * Normal
-  *  
  
----- +Priority is used to select a weight for the group in the match process.
-===== 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. +
- +
-{{ :admin_functionality:settings:kathy.png?nolink&600 |}} +
- +
-==== 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.  +
- +
-{{ :admin_functionality:settings:christopher.png?nolink&600 |}} +
- +
-==== 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.+
  
 ---- ----
 +==== Match vs Score ====
  
-==== Include For Matching Column ====+This section describes the difference between including groups for scoring vs including groups for scoring.
  
-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.+{{ :admin_functionality:create_session:include_for_matching.png?800 |}}
  
-**Note:** At least one group must be included for matching.+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. 
-===== Miscellaneous Functions =====+
  
-This section allows you to setup the groups that will be used for matching and scoring of duplicates.+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:
  
-You will see a screen similar to this:  +{{ :admin_functionality:create_session:scoring_vs_matching_example.png?800 |}}
- +
-**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: +
- +
-  * English +
-  * French +
-  * German +
-  * Italian +
-  * Spanish +
- +
-This option is located: +
- +
-{{ :admin_functionality:create_session:sprint26_step2_lang.png?nolink |}} +
- +
-**Display Attributes by:** This is located just below the language drop-down, and allows you to filter the display names between the database 'Schema Name' and a user friendly 'Display Name'. +
- +
-**Display Attributes Sorting:** The displayed attributes can also be sorted in: +
- +
-  * Ascending A-Z +
-  * Descending Z-A +
- +
-This is done by using the drop-down menu available on the 'Entity Attributes' title. +
- +
-{{ :admin_functionality:create_session:1016.png?nolink&600 |}} +
- +
-**Note:** On this same menu under the 'Columns' option, you can also turn on or off the 'Attribute Icons' and title's. +
- +
-**Hover Actions:** +
- +
-  * Hovering over an attribute in 'Display Name' mode will give a tool-tip containing that attributes 'Schema Name' and vice versa when in 'Schema Name' mode. +
-  * Hovering over an attribute's icon will give a tool-tip containing the type of that attribute. +
- +
-**Attribute Searching:** You can filter down the list of attributes by using the search icon: +
- +
-{{ :admin_functionality:create_session:1017.png?nolink&600 |}} +
- +
-**Note:** You must search by the title of the display mode you are in.+
  
 ---- ----
  
-**Expand/Collapse all:** This button will let you expand all folders or collapse all folders. +=====Related Entities=====
- +
-{{ :admin_functionality:create_session:step_2_7.png?nolink |}} +
- +
-**Delete Selected Item:** Clicking this button will delete the current selected item. +
- +
-{{ :admin_functionality:create_session:step_2_8.png?nolink |}}+
  
-**Refresh:** This will erase any changes you make a revert it make to the default.+This section explains how to enable the functionality of using related entity attributes for matching.
  
-{{ :admin_functionality:create_session:step_2_9.png?nolink |}}+In this example, we will run through adding **Opportunity** attributes for matching on the **Account** entity.
  
-**Back:** This will direct you back to step 1.+Go to **Settings** and then head to **Advanced Settings**.
  
-{{ :admin_functionality:create_session:step_4_2.png?nolink |}}+{{ :admin_functionality:settings:resteps1.png?800 |}}
  
-**Skip to Start:** This is only applicable to Cloned sessions.+Within Advanced Settings, select **Related Entities** and then select the appropriate entity. In this example, we will select the Account entity. This will open the [[admin_functionality:settings:custom_settings#related_entities|Related Entities]] configuration.
  
-{{ :admin_functionality:create_session:step_4_3.png?nolink |}}+{{ :admin_functionality:settings:resteps2.png?800 |}}
  
-**Next:** This will direct you to step 3.+Select the related entities that you would like to use for related entity matching under the **Include for Match** header. In this example, we have checked the Include for Match box within the Opportunity row, which will enable Opportunity attributes for matching. After checking the appropriate box, select **Save**.
  
-{{ :admin_functionality:create_session:step_4_4.png?nolink |}}+{{ :admin_functionality:settings:resteps3.png?800 |}}
  
 +Now return to 'Create Session' and on [[admin_functionality:create_session:step_2_set_attribute_groups|Step 2 - Setting the Match Groups]] you will notice Opportunity is now present within the Entity Attributes section on the left.
  
 +{{ :admin_functionality:settings:resteps4.png?200 |}}
  
 +Similar to standard configuration, you can drag and drop any fields within the Opportunity entity and use this for matching.
  
 +{{ :admin_functionality:settings:resteps5.png?800 |}}
admin_functionality/create_session/step_2_set_attribute_groups.1614888336.txt.gz · Last modified: 2021/03/04 20:05 by conor.doyle

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki