User Tools

Site Tools


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 [2018/07/19 13:40]
conor.doyle
admin_functionality:create_session:step_2_set_attribute_groups [2021/03/04 20:17]
conor.doyle
Line 1: Line 1:
-====== Step 2 - Setting the Attribute Groups ======+====== Step 2 - Setting the Match Groups ======
 ---- ----
-===== Field Group Configuration =====+===== Single Entity Configuration =====
 ---- ----
-==== Field Groups Column ==== 
  
-The Default Groups set in the settings menu will automatically be importedbut custom groups can be added by using:+As per the global setting appliedthe list groups will appear here. If needed, you can update this section for the current session.
  
-{{ :admin_functionality:create_session:step_2_5.png?nolink |}}+{{ :admin_functionality:create_session:step2v3.png?800 |}}
  
-Or Alternatively Default groups from other Entities can be added using: 
  
-{{ :admin_functionality:create_session:step_2_6.png?nolink |}}+**Note:** Any default grouping you have made in the settings menu will be imported. See the **[[admin_functionality:settings:set_attribute_groupsMatch Groups Guide]]** for more detail.
  
-**Note:** Groups and Attributes can be re-arranges by using the drag and drop function.+---- 
 +**Page Functions:** 
 + 
 +{{ :admin_functionality:create_session:functions.png?200 |}} 
 + 
 +  * **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 ==== ==== 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:+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. 
 + 
 +{{ :admin_functionality:create_session:priority_column.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:
 +
   * Exact   * Exact
   * Very High   * Very High
Line 30: Line 41:
  
 ---- ----
-==== Match Key Column ====+==== Match vs Score ====
  
-This column allows you to specify your matching engine.+This section describes the difference between including groups for scoring vs including groups for scoring.
  
-There are six options available:+{{ :admin_functionality:create_session:include_for_matching.png?800 |}}
  
-  * DQ Fonetix (Recommended) +Include for matching - This will include a match group, along with its attributes, in the matching process.  
-  * DQ Metaphone + 
-  * DQ Soundex +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.  
-  * Metaphone  + 
-  * SoundEx +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: 
-  * No MatchKey+ 
 +{{ :admin_functionality:create_session:scoring_vs_matching_example.png?800 |}} 
  
 ---- ----
-==== Include For Matching Column ====+===== Across Entity  Configuration =====
  
-Each group has a checkboxif 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.+After you have selected your desired Entities from Step 1, you will be presented with a screen similar to this:
  
-**Note:** at least one group must be included for matching+{{ :admin_functionality:create_session:xentityv3.png?800 |}} 
 + 
 +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) 
 + 
 +{{ :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.]]
  
 ---- ----
-===== Miscellaneous Features=====+**Page Functions:**
  
-This section is where you setup the groups that will be used for matching and scoring of duplicates.+{{ :admin_functionality:create_session:functions.png?200 |}}
  
-You will see screen similar to this: +  * **1. Expand All -** Expand all match groups 
 +  * **2. Add Match Group -** Add existing match group or create new group 
 +  * **3. Delete -** Tag and then remove match groups 
 +  * **4. Refresh -** Refresh to pre saved settings
  
-**Note:** However this will vary depending on entity and what default groups you have setup.+**Note:** Groups and attributes can be re-arranged by using the drag and drop function.
  
-{{ :admin_functionality:create_session:step_2_1.png?nolink&600 |}}+---- 
 +==== Priority Column ====
  
-**Matching Language:** When creating these groups you have the option to choose the matching languageThe following can be used:+By default, the priorities will appear as per the global settingsYou 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.
  
-  * English +{{ :admin_functionality:create_session:priority_cross_entity.png?800 |}}
-  * French +
-  * German +
-  * Italian +
-  * Spanish+
  
-This option is located:+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:
  
-{{ :admin_functionality:create_session:step_2_2.png?nolink |}}+  * Exact 
 +  * Very High 
 +  * High 
 +  * Medium 
 +  * Normal
  
-**Display Attributes by:** This is located just below the language drop-downand allows you to filter the display names between the Database Schema Name and user friendly Display Name.+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. 
 + 
 +{{ :admin_functionality:create_session:include_for_matching.png?800 |}} 
 + 
 +Include for matching - This will include a match groupalong 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 score group 'Name' including the attributes 'First Name' & 'Last Name', the records will not score as duplicates upon scoring of these valuesThis setup would look like this: 
 + 
 +{{ :admin_functionality:create_session:scoring_vs_matching_example.png?800 |}} 
 + 
 +---- 
 +===== Match Key =====
  
-**Display Attributes Sorting:** The displayed Attributes can also be sorted in:+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:
  
-  * Ascending A-Z +==== Soundex ====
-  * Descending Z-A+
  
-This is done by using the drop-down menu available on the 'Entity Attributes' title.+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.
  
-{{ :admin_functionality:create_session:step_2_3.png?nolink |}}+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.
  
-**Note:** On this same menu under the 'Columns' option, you can also turn on or off the Attribute Icons and Title's.+{{ :admin_functionality:settings:kathy.png?nolink&600 |}}
  
-**Hover Actions:**+==== DQSoundex ====
  
-  * Hovering over an attribute in 'Display Name' mode will give a tool-tip containing that Attributes 'Schema Name' and vice versa when in 'Schema Namemode. +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 'Cathyand 'Kathy', as well as ‘Ph’ as in Phonetix to ‘F’ in Fonetix.
-  * 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: +==== Metaphone ====
-{{ :admin_functionality:create_session:step_2_4.png?nolink |}}+
  
-**Note:** You must search by title in the display mode you are in+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.  
 + 
  
-**Expand/Collapse all:** This button will let you expand all folders or collapse all folders+==== DQMetaphone ====
  
-{{ :admin_functionality:create_session:step_2_7.png?nolink |}}+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.
  
-**Delete Selected Item:** Pressing this button will delete the current selected item+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:create_session:step_2_8.png?nolink |}}+{{ :admin_functionality:settings:christopher.png?nolink&600 |}}
  
-**Refresh:** This will erase any changes you make a revert it make to the default.+==== DQFonetix™ ====
  
-{{ :admin_functionality:create_session:step_2_9.png?nolink |}}+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:
  
-**Back:** This will direct you back to step 1+  Five spoken languages – English, Spanish, French, Italian and German 
 +  Avoids false matches 
 +  Overcomes character variances  
 +  Deals with diacritics
  
-{{ :admin_functionality:create_session:step_4_2.png?nolink |}}+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.
  
-**Skip to Start:** This is only applicable to Cloned sessions+==== No Match Key ====
  
-{{ :admin_functionality:create_session:step_4_3.png?nolink |}}+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.
  
-**Next:** This will direct you to step 3 
  
-{{ :admin_functionality:create_session:step_4_4.png?nolink |}} 
admin_functionality/create_session/step_2_set_attribute_groups.txt · Last modified: 2021/03/04 20:17 by conor.doyle