Demo 5 - RefToRefAssertion

The Identity Capture configuration is the first of two methods that can be used to generate an initial knowledge base. The second method that allows an initial knowledge base to be created is the Reference to Reference Assertion. This is the process of forcing references to match even when no defined match rules would be able to bring them together. The forced matches are based off of previous user knowledge of the references.

This run will use the input test data file named "RefToRefAssertion.txt". This data consists of four references composed by six attributes. The first attribute is the RefID, this is a unique identifier associated to each record. The last attribute is the @AssertRefToRef attribute; this is defined by the user and is based on previous knowledge of the source references. This last field is what OYSTER uses to force matches by matching records who share the same Assert value. The other attributes consist of FirstName, LastName, DOB, and SchCode. When these attributes are combined as they are in the source file they are used to define a set of sample student references.

Input text file screenshot

RefToRef AssertionAttributes runs cause OYSTER to build (or update) an identity output file and in this run it was stored in the RefToRefAssertionOutputIdentities.idty file. This file is the Identity Knowledge Base that can be updated and maintained in future runs. You will again notice that since Trace is turned on, attributes were attached to each reference so that they can later be traced back to their origin.

Attribute script screenshot

First open command line and read the class path of oyster jar file, Enter ‘RefToRefAssertionRunScript.xml’ and press Enter to perform the run.

Run Demo Command Line screenshot

output from command line screenshot

After the run finishes, the Output folder will contain the RefToRefAssertionLinks.link, RefToRefAssertionLog_0.txt, RefToRefAssertionOutputIdentities.idty, Identity Change Report.txt, RefToRefAssertionOutputIdentities.emap, and RefToRefAssertionOutputIdentities.indx files

output folder screenshot

OYSTER creates the persistent identifiers for identities and stores them in the RefToRefAssertionLinks.link file, You can note that the rule used to perform matches is “@AssertRefToRef” identifying that the assertions were correctly run.

output link file screenshot

Back to OYSTER Demonstration Run page