Differences

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

--- admin_functionality:create_session:step_2_set_attribute_groups [2018/07/23 12:37]
conor.doyle
+++ admin_functionality:create_session:step_2_set_attribute_groups [2021/03/04 20:16]
conor.doyle
@@ Line 1: / Line 1: @@
-====== Step 2 - Setting the Attribute Groups ======
+====== Step 2 - Setting the Match Groups ======
 ----
 ===== 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.
-{{ :admin_functionality:create_session:102.png?nolink&600 |}}
+{{ :admin_functionality:create_session:step2v3.png?800 |}}
-----
-==== Field Groups Column ====
-**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.
+**Note:** Any default grouping you have made in the settings menu will be imported. See the **[[admin_functionality:settings:set_attribute_groups| Match Groups Guide]]** for more detail.
-However custom groups can be added by using:
+----
+**Page Functions:**
-{{ :admin_functionality:create_session:step_2_5.png?nolink |}}
-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.
@@ Line 26: / Line 26: @@
 ==== 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:
@@ Line 39: / 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
-  * Metaphone
-  * SoundEx
-  * No MatchKey
-----
+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.
-==== 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.
+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:
-**Note:** At least one group must be included for matching.
+{{ :admin_functionality:create_session:scoring_vs_matching_example.png?800 |}}
 ----
-===== Cross Entity  Configuration=====
+===== Match Key =====
-After you have selected your desired Entities from Step 1, you will be presented with a screen similar to this:
+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:
-{{ :admin_functionality:create_session:cross_ent_step_2_1.png?nolink |}}
+==== Soundex ====
-To start the process you must first go through and assign your related fields from the entities:
+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.
-E.g. Lead.Address_1_Name maps to Account.Address_1_Name
+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:create_session:cross_ent_step_2_2.png?nolink |}}
+{{ :admin_functionality:settings:kathy.png?nolink&600 |}}
-Next, you must add them into a group folder, This can be in custom groups or default groups:
+==== DQSoundex ====
-**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.
+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.
-{{ :admin_functionality:create_session:step_2_5.png?nolink |}}
+==== Metaphone ====
-Alternatively, default groups from other entities can be added using:
+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.
-{{ :admin_functionality:create_session:step_2_6.png?nolink |}}
+==== DQMetaphone ====
-**Note:** Groups and attributes can be re-arranged by using the drag and drop function.
+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.
-==== Field Groups Column ====
-This column contains the Attribute from the Source Entity
-----
+{{ :admin_functionality:settings:christopher.png?nolink&600 |}}
-==== Target Column ====
-This column contains the Attribute from the Target Entity
-----
+==== DQFonetix™ ====
-==== 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:
+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:
-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:
+  * Five spoken languages – English, Spanish, French, Italian and German
+  * Avoids false matches
+  * Overcomes character variances
+  * Deals with diacritics
-  * Exact
+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.
-  * Very High
-  * High
-  * Medium
-  * Normal
-  *
-----
+==== No Match Key ====
-==== Match Key Column ====
+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.
-This column allows you to specify your matching engine.
+**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.
-There are six options available:
-  * DQ Fonetix (Recommended)
-  * DQ Metaphone
-  * DQ Soundex
-  * Metaphone
-  * SoundEx
-  * No MatchKey
 ----
-==== Include For Matching Column ====
+===== Across Entity  Configuration =====
-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.
+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 |}}
-===== Miscellaneous Functions =====
-This section allows you to setup the groups that will be used for matching and scoring of duplicates.
+To start the process you must first go through and assign your related fields from the entities:
-You will see a screen similar to this:
+E.g. Address1_Country --> Address1_Country (as shown in the screenshot below)
-**Note:** However this will vary depending on entity and the default groups you have setup.
+{{ :admin_functionality:create_session:cross_ent_step_2_2.png?nolink |}}
-{{ :admin_functionality:create_session:step_2_1.png?nolink&600 |}}
+**NOTE:** Attributes map have already been manually mapped on the [[admin_functionality:settings:map_entities| Across Entity Mapping Page.]]
-**Matching Language:** When creating these groups you have the option to choose the matching language. The following can be used:
+----
+**Page Functions:**
-  * English
+{{ :admin_functionality:create_session:functions.png?200 |}}
-  * French
-  * German
-  * Italian
-  * Spanish
-This option is located:
+  * **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
-{{ :admin_functionality:create_session:step_2_2.png?nolink |}}
+**Note:** Groups and attributes can be re-arranged by using the drag and drop function.
-**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'.
+----
+==== Priority Column ====
-**Display Attributes Sorting:** The displayed attributes can also be sorted in:
+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.
-  * Ascending A-Z
+{{ :admin_functionality:create_session:priority_cross_entity.png?800 |}}
-  * Descending Z-A
-This is done by using the drop-down menu available on the 'Entity Attributes' title.
+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_3.png?nolink |}}
+  * Exact
+  * Very High
+  * High
+  * Medium
+  * Normal
-**Note:** On this same menu under the 'Columns' option, you can also turn on or off the 'Attribute Icons' and title's.
+Priority is used to select a weight for the group in the match process.
-**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:step_2_4.png?nolink |}}
-**Note:** You must search by the title of the display mode you are in.
 ----
+==== Match vs Score ====
-**Expand/Collapse all:** This button will let you expand all folders or collapse all folders.
+This section describes the difference between including groups for scoring vs including groups for scoring.
-{{ :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.
-{{ :admin_functionality:create_session:step_2_9.png?nolink |}}
-**Back:** This will direct you back to step 1.
-{{ :admin_functionality:create_session:step_4_2.png?nolink |}}
+{{ :admin_functionality:create_session:include_for_matching.png?800 |}}
-**Skip to Start:** This is only applicable to Cloned sessions.
+Include for matching - This will include a match group, along with its attributes, in the matching process.
-{{ :admin_functionality:create_session:step_4_3.png?nolink |}}
+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.
-**Next:** This will direct you to step 3.
+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:step_4_4.png?nolink |}}
+{{ :admin_functionality:create_session:scoring_vs_matching_example.png?800 |}}

DQ for Dynamics™/DQ for Workbooks Wiki

User Tools

Site Tools

Differences

Page Tools