As part of the data product mastering flow, Tamr Cloud groups records that refer to the same entity into a cluster, using a trained model. Cluster size can range from one record to thousands of records.

Tamr Cloud also applies rules that produce a single entity that best represents each cluster. These rules determine the most appropriate value for each mastered entity attribute.

If you have curator (or higher) permissions for a data product, you can review and, if necessary, override the Tamr Cloud-computed clusters and attribute values for that data product.

Note: Your data product enters a read-only state while a flow is running, meaning you cannot edit clusters until the flow finishes running. You can edit attribute values while a flow is running.

Curating Data

Adjusting Clusters

When you override clusters, by merging entities, creating new entities, or by moving source records between entities, these changes are applied after records are clustered the next time the flow is run. These changes then persist on subsequent mastering flow runs. Because overrides are applied after clustering, they do not impact how other source records are clustered. See Modifying Source Record Clusters.

Overriding Attribute Values

When you override an attribute value, the value updates automatically. This value is persistent; it is not overwritten when the mastering flows delivers updated data. If the mastering flow is re-run, this value persists.
See Editing Mastered Entity Attribute Values.

Override Process

This diagram shows how Tamr Cloud applies overrides as part of the mastering process. When you merge entities, move records between entities, or create new entities, your changes are applied the next time the flow is run, as part of the Clustering step. First, source records are clustered using the model, and then the overrides are applied. Because overrides are applied after clustering, they do not impact how other source records are clustered.

For attribute overrides, Tamr Cloud automatically updates the mastered entity data with the override value. The override value is also included in exported data. When the mastering flow is re-run, attribute overrides are re-applied when the flow completes.