Reltio Connect

 View Only
  • 1.  Identifying Duplicates

    Founding Member
    Posted 05-03-2021 08:10
    How can you identify that two organizations, originating from the same ,or different, sources, are matching (are duplicates)? Additionally, can this process be used for identifying if two addresses are the same?

    ------------------------------
    Georgy CHERNYAVSKIY
    Customer Data Process Owner, Data & Performance, Governance
    Schneider Electric
    ------------------------------


  • 2.  RE: Identifying Duplicates

    Reltio Employee
    Posted 05-03-2021 12:16

    Hi Georgy,

    We use match rules to identify duplicates in Reltio, these can be configured in the console match rule editor. 

    A common rule for organization matching might involve a rule looking for exact matches of the organization name and address. An alternative would be to consider the organization tax id to find a duplicate.  While looking for exact matches is always a great place to start, you can use more complex fuzzy rules to find matches exact rules might miss. 

    In Reltio, there are two ways addresses are often modeled. If you addresses are modeled as their own entityType called "Location" than you can use match rules to find duplicates. However, if you addresses are modeled as nested attributes within an entityType like organization, duplicates are combined using matchFieldURIs. Essentially you list the fields within Addresses you would like to use for deduplicating and Reltio takes care of the rest. 



    ------------------------------
    Joel Snipes
    ------------------------------



  • 3.  RE: Identifying Duplicates

    Reltio Employee
    Posted 05-03-2021 12:56
    Hello Georgy

    There are several ways to determine if two organizations are matching.  Remember that an organization is a simple entity and two organizations are two simple entities.

    1.  The following API will return a match explanation based on rules in entity type configuration for entities provided inside the request body as JSONs or specified as an existing entity URI.

    POST {TenantURL}/entities/_verifyMatches

    Request Body:

    {
    "first": {
    "uri""entities/entities1"
    },
    "second":{
    "uri""entities/entities2"
    },
    }

    For more information, please refer to our external documentation here.

    2.  The following API will return all matches for a specific entity group by match groups.

    GET {TenantURL}/entities/10/_matches

    3.  The following API will return matches for a specific rule in an entity-type configuration.

    POST {TenantURL}/_matches
    Request Body:

    [{
    			"type": "configuration/entityTypes/HCP",
    			"attributes": {
    				"FirstName": [{
    					"value": "William"
    				}],
    				"MiddleName": [{
    					"value": "James"
    				}],
    				"LastName": [{
    					"value": "Harley"
    				}],
    				"SuffixName": [{
    					"value": "Mr."
    				}],
    				"Degrees": [{
    					"value": {
    						"Degree": [{
    							"value": "Lord"
    						}]
    					}
    				}],
    				"Address": [{
    						"value": {
    							"AddressLine1": [{
    									"value": "USA, VI, Milwakee, Liberty
    									plate 1234 " }
    								], "ZipPostalCode": [{
    									"value": "123456"
    								}]
    							}
    						}]
    				}
    			}]
    For more information, please reference this link here.

    Support has a number of Knowledge-based articles to help here.

    1.  How can I troubleshoot possible issues with match vs. potential match?
    2. How to troubleshoot if the records not merged based on the Match rule?

    Regards
    Gloria Faley





    ------------------------------
    Gloria Faley
    ------------------------------