Demo 10 - BlockingGoodIndex

Compared with Demo 9, Demo 10 shows the Identity Capture configuration with correctly aligned 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 9, the attribute script lists two Boolean matching rules. In addition, there are two indices created before the rules.

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

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

The Rules and Index in this Demo are in alignment. Index X1 contains hash functions which extract FirstName has SOUNDEX match, LastName Exact match and StreetNbr Exact Match. This index is the same as Rule 1 which is aligned. Index X2 contains hash functions which extract LastName has SOUNDEX match and StreetNbr has Exact match. This index can conver Rule 2 because Rule 2 has same LastName and StreetNbr match, and include one more Nickname match on FirstName.

To run OYSTER in command line Enter ‘BlockingGoodIndexRunScript.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 833 identities. The running time is 1 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