Demo 11 - BlockingBadIndex

Compared with Demo 10, Demo 11 shows the Identity Capture configuration with misaligned Blocking Index.

The input file contains 1001 records with 15 attributs. The details of input data can be seen in the screenshot below:

Different than Demo 10, Demo 11 only used one index before the rules.

Index X1 is: Blocking all records by same FirstName SOUNDEX match, and LastName exact hashing, and StreetNbr exact hashing matching.

Compared with Demo 10, without Index X2, it only extracts FirstName has SOUNDEX match, LastName Exact match and StreetNbr Exact Match. Then Rule 2 cannot be covered by the rules since some FirstName which are Nickname match can be blocked away from Index X1.

To run OYSTER in command line Enter ‘BlockingBadIndexRunScript.xml’ and press Enter to perform the run as shown in screenshot listed below.

Information about the run will be displayed in the Command Prompt. For this run, there are 1001 references processed and grouped as 863 identities. The running time is 0 seconds. The OYSTER run statistics for this run are shown in screenshots listed below.

After the run finishes, the Output folder will contain several files which are shown in the screenshot below.

The link file output is the same logic as Identity Capture configuration. OYSTER creates the persistent identifiers for identities and stores them in the link file. Being persistent, these IDs are the same as were generated in the previous MergePurge run and the same method as described previously was used to get the matches.

Back to OYSTER Demonstration Run page