How-To configure a duplicate check

Owned by Marco Mele (Unlicensed)
Last updated: 04. Jun 2024 by Christian Huber (Unlicensed)
3 min read

Introduction

With the duplicate check of the CoreOne Suite, it is possible to check which Core Identities are similar or even exact duplicates of each other. The similarity will be determined by a few parameters that can be set in the database. These parameters can not be set in the GUI for now. The acknowledgement however, can be done in the GUI. At the moment there are no actions that can be performed other than “acknowledge”.

Manual for the Web-GUI

Step 1 - Identity management

Navigate to the the “identity Management” to the tab “Duplicates“. In this tab all the acknowledged duplicates will be displayed and if they are acknowledged or not. It’s also visible when the duplicate occurred. The view of ‘acknowledged’ or ‘not acknowledged’ can be changed in the top-right corner.

Step 2 - Detail page of a duplicate

To get into the detail page of the duplicate, just click on the duplicate you want to open. In the detail-view of a duplicate all the matching attributes will be displayed. Also the Core Identities that matched will be listed. In this view it is also possible to acknowledge the duplicate.

Step 3 - Acknowledge the duplicate

To acknowledge the duplicate you have to click on the acknowledge-button in the top right corner. When the acknowledge-button is clicked, it will display a pop-up where a comment can be made why the duplicate got acknowledged.

Configuration Database

In this table all duplicates will be listed.

SELECT * FROM moving_appcustomer_900000.servicedmcore_core_identity_detected_duplicate;

 

All the Attributes of the duplicates will be listed in this table.

SELECT * FROM moving_appcustomer_900000.servicedmcore_core_identity_detected_duplicate_attribute;

 

In the detection_rule table you can decide how many attributes need to match and of which coreidentity_type.

SELECT * FROM moving_appcustomer_900000.servicedmcore_core_identity_type_duplicate_detection_rule;

 

The entries of the detection_rule table can be specified in this table. The detection_threshold specifies how many percent need to match.

SELECT * FROM moving_appcustomer_900000.servicedmcore_core_identity_type_duplicate_detection_rule_entry;

 

The detection_type determines how the checks are performed.

  • Equals = Needs to match exactly

  • Phonetic = Matches if it sounds alike (e.g. Meier and Meyer)

SELECT * FROM moving_appcustomer_900000.servicedmcore_duplicate_detection_type;

 

The Duplicate-Check has to be activated in the Settings.

  • Module.DM.IdentityManagement.Setting.EnableCoreIdentityDuplicateCheck

  • In the Table setting_setting_value, set the ‘bool_value’ to 1

SELECT * FROM moving_appcustomer_900000.setting_setting;

SELECT * FROM moving_appcustomer_900000.setting_setting_value;

 

 

Levenshtein distance

On the following Page, you can calculate the Levenshtein distance online. This shows the phonetic similarities.

https://awsm-tools.com/text/levenshtein-distance

 

 

© ITSENSE AG. Alle Rechte vorbehalten. ITSENSE und CoreOne sind eingetragene Marken der ITSENSE AG.