Creating or updating campaign(s) and data model(s) automatically in Talend Data Stewardship - Cloud - 8.0

Talend Studio User Guide

Version
Cloud
8.0
Language
English
Product
Talend Big Data
Talend Big Data Platform
Talend Cloud
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Module
Talend Studio
Content
Design and Development
Last publication date
2024-02-29
Available in...

Data Fabric

MDM Platform

Talend MDM can be configured with the integration of Talend Data Stewardship to perform the integrated matching tasks. In this case, when you deploy a newly created data model or an updated data model to an MDM server, as long as the data model has a match rule attached to it, the changes of the MDM data model will be propagated to Talend Data Stewardship automatically. To learn more information about Talend Data Stewardship concepts and working principles, see the Talend Data Stewardship Documentation.

When you create a new data model and deploy it to an MDM server, for each entity that has a match rule attached to it, the following changes are made in Talend Data Stewardship:

  • A new Data Stewardship data model is created with attributes that correspond to each simple type element in the MDM entity, and its name is in the format of <MDM_data_model_name> - <MDM_entity_name> - TMDM (for example, PRODUCT - STORE - TMDM).

    Meanwhile, MDM data types are mapped into Talend Data Stewardship data types, and MDM element constraints (if any) are translated into Talend Data Stewardship attribute constraints. For more information, see the documentation about the mapping tables between Talend MDM and Talend Data Stewardship in Master Data Management Examples.

  • A new merging campaign is created using the new Data Stewardship data model, and its name is in the format of <MDM_data_model_name> - <MDM_entity_name> - TMDM (for example, PRODUCT - STORE - TMDM).

    Meanwhile, the Talend Data Stewardship campaign will declare a role for each role access right configured on the MDM entity, and also any role access right configured for an element in the MDM entity will be mapped into the role access right for the corresponding Talend Data Stewardship attribute.

    Besides, the campaign will have only NEW and RESOLVED steps in its workflow, without a VALIDATION step.

    If no role access rights are defined for the MDM entity, the corresponding Talend Data Stewardship campaign has one built-in role created named "Steward", all Talend Data Stewardship attributes are ready-only for this role and the "Steward" role is linked to the NEW step.

When you update a data model and re-deploy it to an MDM server, for each entity that has a matching key contained in this data model, the following changes are made in Talend Data Stewardship depending on your updates in the MDM data model:

  • If you add a new entity with one or more match rules attached to it, a new Data Stewardship data model and a new merging campaign will be created accordingly.

  • If you attach a match rule to an existing entity with no match rule attached to it before, a new Data Stewardship data model and a new merging campaign will be created accordingly.

  • If the Data Stewardship data model already exists, it will be updated accordingly.

  • If the merging campaign already exists, it will be updated accordingly.

  • However, if you remove an entity or remove the attaching of all match rules to an entity, the corresponding Data Stewardship data model and merging campaign which already exist will not be removed. If needed, you can remove them manually.