Setting a data model in the Arbitration Campaign - 6.5

Talend Data Stewardship Examples

author
Talend Documentation Team
EnrichVersion
6.5
EnrichProdName
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
task
Administration and Monitoring > Managing users
Data Governance > Assigning tasks
Data Governance > Managing campaigns
Data Governance > Managing data models
Data Quality and Preparation > Handling tasks
EnrichPlatform
Talend Data Stewardship

The data model used in a campaign decides the structure of the data to be managed.

In a campaign, you need to select what data model to use for the syntactic and semantic validation of data and decide the read/write access permission per role to each of the attributes in the selected data model.

Procedure

  1. In the home page, click Data Model and select from the model list the data structure you want to use in the Beta Candidates campaign.

    The Data Model list gives access to all the data models that have been defined on the Talend Data Stewardship server.

  2. Select the buttons next to each of the attributes in the data structure to set permission per attribute and per data steward and define who can view/edit which attributes.
    Option Description
    gives a read/write access to the attribute in the data model.
    gives only a read access to the attribute in the data model.

    This type of access is useful if the data steward needs to access the information to make a relevant decision but must not change the value, for instance unique identifiers of other elements linked to the entity the steward is viewing, or data that you know is reliable and must not be changed.

    gives no access to the attribute.

    Hiding an attribute is useful if the information is sensitive and should not be visible by the data steward, financial information for instance. Another example of attributes to be hidden is if the information is just noise for the steward, technical identifier for instance, but need to be propagated as part of the task.

    In this example you have only the NOMINATOR role. You want to make the technical identifier invisible to the stewards who are assigned the role and grant them a read/write access to all other attributes.