Lab 1: Import a Partially Configured Match Processor

Transcription

1 Lab 1: Import a Partially Configured Match Processor You will start these labs by importing a process that includes a partially configured match processor set up to work against very similar customer data to that used in the EDQ Matching 101 training module, the Introduction to Matching self-paced training course and the Match and Parse Oracle University training course. The following configuration is already done for you: Inputs Identifiers Clusters Basic Comparisons If you require a refresher about any of the items above, please consult the EDQ Matching 101 module or the Introduction to Matching self-paced course. In the labs that follow this one, you will configure: Compound Comparisons Scoring Match Rules Relationship Outputs Import a Package 1. Open the Director user interface and log in as the dnadmin user (in the EDQ Trn virtual machine, the dnadmin user s password is also dnadmin). 2. Follow the menu path File >> Open Package File 1. Navigate to the file a1-total Matching With EDQ-Start-Point.dxi which you will find in C:\share\edq_training_assets_12.2.1\Data Files\matching. Select the file and click Open. A folder named a1-total Matching With EDQ-Start-Point.dxi will appear at the bottom of the Project Browser. 2. Drag the Projects node from beneath the a1-total Matching With EDQ-Start- Point.dxi folder and drop it on top of the Projects node directly below localhost (where localhost is your server name). Page 4 of 30

2 3. An a1-total Matching Browser. With EDQ-Start-Point project should appear in the Project Page 5 of 30

3 Lab 2: Examine the Configuration 1. In the Project Browser, expand the a1-total Matching With EDQ-Start-Point project, then expand the Processes node, and double-click the Total Matching process to open it on the Canvas. You should see three connected processors: a reader, a processor called Very Simple Data Prep, and the Advanced Match processor. 2. Double-click the Advanced Match processor to open it, and then double-click the Input sub-processor to open it. Note that the attributes being input are very similar to those used in the EDQ Matching 101, the Introduction to Matching self-paced course and the Match and Merge Oracle University course. Only one attribute is Page 6 of 30

4 different: this data formerly present. 3. Close the Input sub-processor set includes a NationalID attribute that was not 4. Next, double-click the Identify sub-processor to open it, and simply note that each input attribute has been mapped to an identifier with a similar name. 5. Close the Identify sub-processor 6. Next, double-click the Cluster sub-processor to open it, and note that three clusters have been configured. These are based on the State, Phone Number and First Name attributes respectively (the exact same configuration as in the EDQ Matching 101 module and the Introduction to Matching course). Although this configuration is not optimal it will suffice for training purposes. Page 7 of 30

5 7. Close the Cluster sub-processor. 8. Next, double-click the Match sub-processor. It should open on the Comparison tab. You can see that one or more basic comparisons have been configured for most of the attributes. In many cases these are Character Edit Distance (CED) comparisons. Character Edit Distance comparisons assess the similarity of strings by measuring how many differences there are between them (for example, there would be a character edit distance of 1 between Jon and Joe). There are also some exact comparisons and the Date of Birth has a Date Edit Distance (DED) comparison. Page 8 of 30

6 9. For the time being, close the Match sub-processor. Page 9 of 30