Defining the Merging campaign - 6.5

Talend Data Stewardship Examples

Talend Documentation Team
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
Administration and Monitoring > Managing users
Data Governance > Assigning tasks
Data Governance > Managing campaigns
Data Governance > Managing data models
Data Quality and Preparation > Handling tasks
Talend Data Stewardship

In this scenario, you define the CRM Data Deduplication campaign to allow data stewards to address potential duplicates in the contact records in the CRM system of an enterprise.

Start by defining the campaign metadata.


  2. Enter a name and a description for the new campaign.
  3. Select Merging as the campaign type.
  4. Leave the DEFINE SOURCES option inactivated as duplicate data in this example comes from one source.
    When you define source names in the campaign, make sure that they do not contain dots and that they do not start with a dollar signs.
  5. Click the switch next to ENABLE TASK RESOLUTION DELAY and set the delay to be used to calculate the due dates.

    The due date is calculated by adding the delay you set to the date and time of loading the tasks in the campaign. If you leave this option disabled, the DUE DATE column in the task list stays empty and tasks do not have resolution delay.

    The due date in a Merging campaign is only on master records.

  6. Click in the CAMPAIGN OWNERS field and select from the list one or more users to grant them access on the current campaign.
    This list shows all the users defined in Talend Administration Center and assigned the role of campaign owners.