We are pleased to announce record verification improvements, improved record history for customers using the Tamr RealTime System of Record, new beta features to copy data product and publish configurations as JSON, and other improvements.

Record Verification Improvements

It’s now easier to understand which records are verified in a cluster and to have more control over verifying records when moving records between clusters.

Previously, when curators performed clustering overrides, source records that moved to new clusters were verified in the new cluster, and a verified badge appeared for these records. Other records in that cluster were implicitly verified in the cluster; there was no UI indication that these records were verified, but these implicit verifications ensured that the records in the cluster did not re-cluster with the removed records on subsequent runs.

Through a one-time update in most regions, Tamr added verification badges to all records that were previously implicitly verified.

New UI options let you decide whether to verify all records in the original and destination cluster when moving records. To ensure that all records in both the original and destination cluster remain in their respective clusters on subsequent flow runs, Tamr recommends leaving the verification options enabled, as shown below.

Note: This update is currently scheduled for tenants in the EU on Saturday June 14. See https://status.tamr.cloud/ for the latest details.

Improved Record History

Customers publishing to a RealTime System of Record (SOR) will notice improvements in the tracking of record merges and updates in the 360 pages Record History. Each golden record in the SOR has links to source records from the last batch data product run, which allows the tracking of record merges and updates from clustering changes or curator activity.

Beta Feature: Copy Data Product and Publish Configurations

You can now copy data product configurations and publish configurations as JSON. You can then paste the JSON into a text file, web browser, and so on to view and save the configuration. This can be useful for tracking changes over time and for comparing different data product configurations or publish configurations. See Copying Data Product Configuration and Copying Publish Configuration.

Copy data product configuration from the More menu on the data product tile:

Copy publish configurations from the data product Publish page:

Bug Fixes and Other Improvements

• Resolved an issue in which the Jobs page continually drifted to the right.
• Improved page load times in data product curation pages.
• Resolved an issue in which sources loaded slowly on the Sources page.
• General performance, styling, and usability improvements.