Tamr Documentation

Transformations

Use transformations to alter the records in a unified dataset.

Transformations allow you to change the final output of a unified dataset in Tamr without having to transform each of the individual input datasets before loading them into Tamr. Examples of Tamr transformations include concatenating addresses or names that are stored by multiple input attributes together into a unified attribute, cleaning values by removing whitespace or delimiters, applying consistent formatting to dates, and so on.

Transformations modify the unified dataset of a project. Transformations do not alter input datasets directly.

For detailed information about Tamr transformations, see the Transformations Guide.

You can define transformations in schema mapping, mastering, and categorization projects. To work with transformations, choose the Unified Dataset page.

Note: To add transformations to a mastering or categorization project you must indicate that you want the project to include this feature.

In this example for a new mastering project, check **Enable Transformations** to include this feature.

In this example for a new mastering project, check Enable Transformations to include this feature.

If you decide to include transformations in a mastering or categorization project after an admin has created it, locate the project on the Tamr dashboard and move your cursor over the top right corner to access Edit (pencil icon). The same dialog opens so that you can check Enable Transformations.

To change an existing project, select **Edit**.

To change an existing project, select Edit.

Updated 5 months ago



Transformations


Use transformations to alter the records in a unified dataset.

Suggested Edits are limited on API Reference Pages

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