Configuring Matching Parameters

The Decision Maker is configured in master.xml and defines how to handle certain decision points in the matching process, such as weight thresholds, how to handle multiple records above the match threshold, and whether records originating from the same system can be automatically matched.

You can customize the Decision Maker by performing any of the following actions:

• Specifying the Master Index Decision Maker Class

• Defining How to Handle Multiple Assumed Matches (OneExactMatch)

• Specifying Whether Same System Matches are Allowed (SameSystemMatch)

• Specifying the Master Index Duplicate Threshold

• Specifying the Master Index Match Threshold

• Adding and Deleting Master Index Decision Maker Parameters

Specifying the Master Index Decision Maker Class

If you create your own Decision Maker class, you can specify the new class to be used by changing the value of the decision-maker-class element.

To Specify the Decision Maker Class

1. In the Projects window, expand the Configuration node in the project you want to modify, and then double-click master.xml.
2. Scroll to the DecisionMakerConfig element.
3. Change the value of the decision-maker-class element to the path and name of the new Decision Maker class.

   For example:

   <decision-maker-class>com.sun.mdm.index.decision.impl.MyDecisionMaker
   </decision-maker-class>

4. Save and close the file.

Defining How to Handle Multiple Assumed Matches (OneExactMatch)

The OneExactMatch parameter determines how records above the match threshold are processed. This parameter can only be modified directly in the XML file. For more information, see Manager Service Configuration in Oracle Java CAPS Master Index Configuration Reference and Chapter 2, Understanding Operational Processes, in Oracle Java CAPS Master Index Processing Reference.

To Create Potential Duplicates When Multiple Records Match

1. In the Projects window, expand the Configuration node in the project you want to modify, and then double-click master.xml.
2. Scroll to the OneExactMatch element in the DecisionMakerConfig element.
3. Change the value of the parameter-value element to true.

   For example:

   <parameter>
      <parameter-name>OneExactMatch</parameter-name>
    <parameter-type>java.lang.Boolean</parameter-type>
    <parameter-value>true</parameter-value>
   </parameter>

4. Save and close the file.

To Match the Highest Weighted Records When Multiple Records Match

1. In the Projects window, expand the Configuration node in the project you want to modify, and then double-click master.xml.
2. Scroll to the OneExactMatch element in the DecisionMakerConfig element.
3. Change value of the parameter-value element to false.

   For example:

   <parameter>
    <parameter-name>OneExactMatch</parameter-name>
    <parameter-type>java.lang.Boolean</parameter-type>
    <parameter-value>false</parameter-value>
   </parameter>

4. Save and close the file.

Specifying Whether Same System Matches are Allowed (SameSystemMatch)

The SameSystemMatch parameter determines whether two records with local IDs from the same system can be merged automatically. If your local systems contain reliable data, and rarely duplicate their own records, set this parameter to true. This parameter can only be modified directly through the XML file.

To Allow Same System Records to be Automatically Merged

1. In the Projects window, expand the Configuration node in the project you want to modify, and then double-click master.xml.
2. Scroll to the SameSystemMatch element in the DecisionMakerConfig element.
3. Change the value of the parameter-value element to false.

   For example:

   <parameter>
    <parameter-name>SameSystemMatch</parameter-name>
    <parameter-type>java.lang.Boolean</parameter-type>
    <parameter-value>false</parameter-value>
   </parameter>

4. Save and close the file.

To Prevent Same System Records From Being Automatically Merged

1. In the Projects window, expand the Configuration node in the project you want to modify, and then double-click master.xml.
2. Scroll to the SameSystemMatch element in the DecisionMakerConfig element.
3. Change the value of the parameter-value element to true.

   For example:

   <parameter>
    <parameter-name>SameSystemMatch</parameter-name>
    <parameter-type>java.lang.Boolean</parameter-type>
    <parameter-value>true</parameter-value>
   </parameter>

4. Save and close the file.

Specifying the Master Index Duplicate Threshold

The duplicate threshold is the lowest matching probability weight at which two records are considered potential duplicates of one another. Any records with lower probability weights are not considered to be possible matches. Any records between the duplicate and match thresholds are flagged as potential duplicates, and must be resolved manually. You can configure the duplicate threshold by using the Configuration Editor or by modifying the XML file directly.

To Specify the Duplicate Threshold (Configuration Editor)

1. In the Projects window, right-click the Configuration node in the project you want to modify, and then click Edit.

   The Configuration Editor appears.

2. Click the Matching tab.
3. In the Duplicate Threshold field, enter the lowest weight at which two records should be considered a potential match.

   ---

   Note - This value can be any float value lower than the match threshold but higher than the lowest possible matching probability weight.

   ---

4. On the Configuration Editor toolbar, click Save.

To Specify the Duplicate Threshold (XML Editor)

1. In the Projects window, expand the Configuration node in the project you want to modify, and then double-click master.xml.
2. Scroll to the DuplicateThreshold element in the DecisionMakerConfig element.
3. Change the value of the parameter-value element. For example:

   <parameter>
      <parameter-name>DuplicateThreshold</parameter-name>
      <parameter-type>java.lang.Float</parameter-type>
      <parameter-value>7.9</parameter-value>
   </parameter>

   ---

   Note - This value can be any float value lower than the match threshold but higher than the lowest possible matching probability weight.

   ---

4. Save and close the file.

Specifying the Master Index Match Threshold

The match threshold specifies the matching probability weight at which two records will be automatically merged, depending on the value of the OneExactMatch parameter and the number of records at or above the match threshold. You can configure the match threshold by using the Configuration Editor or by modifying the XML file directly.

To Specify the Match Threshold (Configuration Editor)

1. In the Projects window, right-click the Configuration node in the project you want to modify, and then click Edit.

   The Configuration Editor appears.

2. Click the Matching tab.
3. In the Match Threshold field, enter the lowest weight at which two records should be considered a match.

   ---

   Note - This value can be any float value higher than the duplicate threshold but lower than the highest possible matching probability weight.

   ---

4. On the Configuration Editor toolbar, click Save.

To Specify the Match Threshold (XML Editor)

1. In the Projects window, expand the Configuration node in the project you want to modify, and then double-click master.xml.
2. Scroll to the MatchThreshold element in the DecisionMakerConfig element.
3. Change the value of the parameter-value element.

   For example:

   <parameter>
      <parameter-name>MatchThreshold</parameter-name>
      <parameter-type>java.lang.Float</parameter-type>
      <parameter-value>28.5</parameter-value>
   </parameter>

   ---

   Note - This value can be any float value higher than the duplicate threshold but lower than the highest possible matching probability weight.

   ---

4. Save and close the file.

Adding and Deleting Master Index Decision Maker Parameters

New parameters cannot be used with the default Decision Maker class and existing parameters should not be deleted. If you create a custom Decision Maker class, you might need to add new parameters or delete existing ones for the new class. You can only perform these tasks by modifying the XML file directly.

To Add a New Decision Maker Parameter

1. In the Projects window, expand the Configuration node in the project you want to modify, and then double-click master.xml.
2. Scroll to the DecisionMakerConfig element.
3. Create a parameter element inside the parameters element, but outside any existing parameter elements. Define the following elements:

   • parameter-name – The name of the parameter.

   • parameter-type – The type of parameter. Valid values are java.lang.Long, java.lang.Short, java.lang.Byte, java.lang.String, java.lang.Integer, java.lang.Boolean, java.lang.Double, or java.lang.Float.

   • parameter-value – The value of the parameter.

     For example:

     <parameters>
        <parameter>
           <parameter-name>OneExactMatch</parameter-name>
           <parameter-type>java.lang.Boolean</parameter-type>
           <parameter-value>false</parameter-value>
        </parameter>
        <parameter>
           <parameter-name>MaxDuplicates</parameter-name>
           <parameter-type>java.lang.Boolean</parameter-type>
           <parameter-value>5</parameter-value>
        </parameter>
     </parameters>

4. Save and close the file.

To Delete a Decision Maker Parameter

1. In the Projects window, expand the Configuration node in the project you want to modify, and then double-click master.xml.
2. Scroll to the DecisionMakerConfig element.
3. To delete one parameter, remove all text between and including the parameter element.

   For example, to delete the ExtensiveSearch parameter in the following sample, you would delete the boldface text.

   <parameters>
      <parameter>
         <parameter-name>OneExactMatch</parameter-name>
         <parameter-type>java.lang.Boolean</parameter-type>
         <parameter-value>false</parameter-value>
      </parameter>
      <parameter>
         <parameter-name>ExtensiveSearch</parameter-name>
         <parameter-type>java.lang.Boolean</parameter-type>
         <parameter-value>true</parameter-value>
      </parameter>
   </parameters>

4. To remove all parameters, remove all text between and including the starting and ending parameters element.
5. Save and close the file.