Defining Rules and Rule Mappings for a OneData Matching Project
Use the following procedure to create new rules and rule mappings for OneData Matching using the Manage DQ Rules option.
By default, every project in
OneData has a default
OneData Matcher project with a set of rules defined. You can use this default project for matching or add create a new project, add rules and configure it in accordance with your data quality model. For details on the default rules, see
The Default
OneData Matcher Rules and Attributes.
1. On the Menu toolbar, click Define > Data Quality > Consolidation > Project Mapping.
2. In Filter by Project, select the OneData matching project.
3. Click Manage DQ Rules.
If you had selected Inherit Rules from Default Project when creating the OneData project, the rules from the default OneData Matcher project are automatically associated with the project. The Rules Management screen displays rules (associated with the project) separated into BOTH and MASTER pattern grids. The associated rules are displayed first by order of priority, followed by the rules without any associations.
4. In the Rules Management screen, select the exit criteria to process the project rules:
Evaluate all rules. To evaluate all rules in BOTH and MASTER patterns, so that
OneData returns the best match score.
The order of precedence for evaluation is first, BOTH pattern, and then MASTER pattern.
Note:Software AG recommends Evaluate all rules, as it evaluates all rules. However, it might affect performance as all rules are executed.
Exit on first good match. To evaluate rules in the priority set.
If a rule gives a score higher than the good match score, OneData stops rule evaluation without evaluating rules with lower priority. It then returns the score achieved and rule hint.
5. In the relevant pattern grid (BOTH or MASTER) to which you want to add the new rule, click Add Rule.
If the rules are added within the context of a project, OneData automatically associates the rules to the project.
6. Enter the following definition details for the new generic OneData matching rule:
a. In Name, provide a suitable name for the rule.
b. In Hint, enter a suitable description of how the score and pattern are configured.
c. Select Ignore Empty Fields to exclude fields without data for creation of the match score. If this field is not selected, then the empty fields are also considered for match score creation, according to the weightage specified.
d. In Definition, enter a suitable description for the rule.
e. Specify the following rule mapping details:
Field | Value |
Attribute | Enter a name for the attribute: |
Weightage | Enter a weightage value (in percentage) to be given to the attribute with respect to the actual match score. For example, consider that the Name, Street, and City attributes are given weightages of 5, 3, and 1, respectively. When the similarity score is calculated, Name is weighted 5 times, Street, 3 times, and City, 1 time in the final similarity score. |
Is Required | Select the check box only if the attribute meets one of these conditions: Is an inbound attribute. Must have a Project-Object Mapping created. Note:
If you select Is Required, you must define the Project-Object Mapping. In case there is no Project-Object Mapping for the attribute, validation errors occur during rule execution. |
Algorithm | Select a suitable matching algorithm from the available list of token-based, character-based, and hybrid algorithms. Cosine Coefficient Damerau-Levenshtein Dice Coefficient Jaro Jaro-Winkler Levenshtein Monge-Elkan Needleman-Wunsch OneData Similarity (recommended, and the default algorithm) Overlap Coefficient Sift3 Smith-Waterman Smith-Waterman-Gotoh JaccardCoefficient Rivulatus |
f. If you require more than 10 attributes (provided by default) for the rule, click Add New Mapping and add the attribute details as described in previous step.
g. Click Save when you have added all the necessary rule definition and mapping details.
7. Select the Rule Selection check box to associate the rule to the project.
If you do not select Rule Selection, the rule is not associated with the project.
8. If you selected Exit on first good match as the exit criterion, in Priority, select the evaluation priority for the rule.
Note:
The Priority must be unique for each rule. For example, do not set priority 3 for more than one rule.
9. Click Save Rule Assoication.