# Talend Data Stewardship examples

The use cases described in this document show several means of organizing the interactions on data whenever human intervention is required.

From the guided tour embedded in the app, you can import a sample content which corresponds to the below scenarios so that you can start quickly using the application. You can access the guided tour at any time and at any level by clicking your user name on the top bar and selecting Guided tour.

Consider the below scenarios:

* Testing a Beta product: your enterprise has a beta testing project. Beta testing begins with the selection of test candidates. An Arbitration campaign enables you to select appropriate participants for the project.

  For further information, see [Adding an Arbitration campaign for Beta testing](https://help.qlik.com/talend/en-US/data-stewardship-examples/8.0/adding-arbitration-campaign-for-beta-testing "An Arbitration campaign defines a list of possible arbitration choices on tasks. The outcome of an arbitration task is the arbitration choice made by data stewards.") and [Handling arbitration tasks to select Beta testers](https://help.qlik.com/talend/en-US/data-stewardship-examples/8.0/handling-arbitration-tasks-to-select-beta-testers "Arbitration tasks consist in choosing among a list of arbitration choices one choice for each data record. Once you validate your choice, you transition the task to the second state defined in the workflow. The workflow defined at the campaign creation determines which states are available to what data stewards.").

* Approving data in a product catalog: management of product information includes referencing product and making sure it holds the most complete and accurate information. Suppose that you have a catalog with product records where some values need to be fixed or provided. A Resolution campaign enables you to cure such records.

  For further information, see [Adding a Resolution campaign to curate product records](https://help.qlik.com/talend/en-US/data-stewardship-examples/8.0/adding-resolution-campaign-to-curate-product-records "A Resolution campaign enables you to cure any anomalies in data records such as invalid or missing values.") and [Handling resolution tasks to curate product records](https://help.qlik.com/talend/en-US/data-stewardship-examples/8.0/handling-resolution-tasks-to-curate-product-records "Resolution tasks aim to curate the records they contain. Data curation can consist in fixing one or several fields of the records. The outcome of a resolution task is the clean record produced by the data steward.").

* Managing contacts: the sales team has found a number of duplicates in the Contacts objects in the enterprise Customer Relationship Management system (CRM) and this hurts their productivity. A Merging campaign enables you to solve the duplicates by surviving only the appropriate data.

  For further information, see [Adding a Merging campaign to deduplicate records](https://help.qlik.com/talend/en-US/data-stewardship-examples/8.0/adding-merging-campaign-to-deduplicate-records "A Merging campaign enables data stewards to merge several potential duplicate data records into one single master record. Source records can come from the same source (data deduplication) or different sources (data reconciliation).") and [Handling merging tasks to deduplicate records](https://help.qlik.com/talend/en-US/data-stewardship-examples/8.0/handling-merging-tasks-to-deduplicate-records "Merging tasks aim to merge several potential duplicates into one single record: master record. Potential duplicates can come from the same source (data deduplication) or from different sources (data reconciliation).").

* Matching pairs of records: suppose that you have a million of pairs of suspect records for which you need to identify if the second element in each pair is a duplicate. Such process can be a pain point if you do not have the right tool to do this. A Grouping campaign brings you the answer here.

  For further information, see [Adding a Grouping campaign to identify duplicate pairs](https://help.qlik.com/talend/en-US/data-stewardship-examples/8.0/adding-grouping-campaign-to-identify-duplicate-pairs "A Grouping campaign defines a list of possible arbitration choices for pairs or groups of records. The outcome of a grouping task is the choice made by data stewards on the group of records.") and [Handling grouping tasks to decide on relationship among pairs of records](https://help.qlik.com/talend/en-US/data-stewardship-examples/8.0/handling-grouping-tasks-to-decide-on-relationship-among-pairs-of-records "Grouping tasks consist in deciding on a relationship between several records in a group. Once you validate your choice, you transition the task to the second state defined in the workflow.").