Working with Matching Projects for Consolidation (Staging) Objects

webMethods, OneData, and Terracotta 10.2 | Managing Master Data with webMethods OneData | webMethods OneData Consolidation MDM Guide | Working with Consolidation Projects | Working with Matching Projects for Consolidation (Staging) Objects

Creating a Matching Project

Defining Attribute Mappings for Data Quality Matching Projects

Defining Rules and Rule Mappings for a OneData Matching Project

Mapping a Matching Project to Consolidation (Staging) and Consolidation Gold Objects

After you configure the matching project in the data quality software, create a matching project for the Consolidation (staging) object in OneData. The project contains the mapping of data quality server matching attributes.

Note: Consolidation objects do not require both cleansing and matcher projects. Based on your requirement, you can create only a cleansing project or a matcher project.

Inbound attributes are used by the data quality server to match input. The inbound and outbound attribute names in the OneData matching project should match those configured in the matching project or service of the corresponding data quality server. OneData adds nine outbound attributes for a data quality project.

Ensure that you map the attributes of the data quality project to the corresponding columns of the Consolidation and Gold objects.

There are two steps to creating the matching project in OneData:

1. Map the matching attributes between the data quality server and OneData. For information about creating matching attributes, see Defining Attribute Mappings for Data Quality Matching Projects and Defining Rules and Rule Mappings for a OneData Matching Project.

2. Create a matching project in OneData and connect it to the data quality server (Trillium, Integration Server, or inbuilt OneData Matching. For information about how to create a matching project in OneData, see Creating a Matching Project.