Tamr Documentation

Solving Data Quality Challenges with Tamr

You use Tamr projects to address data quality issues that result when siloed data from internal and external sources is integrated.

Tamr software automates core data preparation activities: combine, consolidate, and categorize. In an iterative process, it uses expert input to capture domain knowledge and assure accuracy, and then applies models to make the technology scalable.

To help you achieve different goals for your data, Tamr offers the following types of projects.

  • Schema mapping projects align disparate data sources to a unified schema, guided by recommended mappings.
  • Mastering projects match and de-duplicate records into clusters for mastered views of any entity. To complete the process of mastering data records, golden records projects use attributes in clustered data records to reliably create unique, complete, up-to-date records for entities.
  • Categorization projects create a normalized view of data by applying a meaningful hierarchy to records.
  • Enrichment Projects (if enabled) use Tamr enrichment services to validate, standardize, and supplement your data.

You can then use the clean, unified data that results from one or more Tamr projects to power the analytics, data visualization, business intelligence, and other tools in use by your organization.

User Roles and the Tamr Documentation

Each Tamr project type involves contributors who have different areas of expertise.

  • Admin: The project leaders who manage deliverables and assign roles to team members, and the project engineers who work with data preparation and transformation, are generally given the admin user role. As Tamr admins, these team members can complete all tasks, for all project types, in Tamr. They are the only users who can work with datasets, projects, jobs, and user accounts.
  • Curator: The validation leaders and decision makers who compose business rules, provide initial data expertise to train Tamr models, and assign tasks to subject matter experts are generally given the curator user role. Curators take the lead role in setting up mastering and categorization projects, and then assign work to reviewers and validate their contributions. Only team members who have the curator (or admin) role can do work in schema mapping projects or golden records projects.
  • Reviewer: The team members who have deep knowledge of the data and can act as subject matter experts are generally given the reviewer user role. For mastering and categorization projects, reviewers contribute recommendations and expert commentary on Tamr suggestions. Before the feedback provided by reviewers can affect Tamr's output, it must be validated by curators. Reviewers may have read access to schema mapping or golden records projects, but do not take an active role.

This Tamr Documentation set provides an overview of each project type, followed by user guides that focus on tasks that can be completed by each user role: admin, curator, and reviewer. An additional guide for system administrators provides information for team members responsible for system security, installation, configuration, and so on.

For information about how users with the admin role assign roles, see Managing User Accounts and Access.

Updated 23 days ago

Solving Data Quality Challenges with Tamr

You use Tamr projects to address data quality issues that result when siloed data from internal and external sources is integrated.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.