We're excited to announce several upcoming features, including an API to create and manage source records and a new page to control how Tamr handles possible duplicates.

Coming Soon! Source Records API

With our new Source Records API, you will be able to:

• Create a new source record in a table, linking it to an existing golden record or creating a new golden record.
• List source records associated with a specified golden record ID.
• Get a source record by its source system name and source record ID.
• Update a source record to replace its data with new or changed values.
• Move a source record to link it to a different golden record, or link it to a newly created golden record.

Coming Soon! Fully Control How Tamr Handles Possible Duplicates

Soon, we'll be releasing a new Duplicate Handling page in RealTime data product configuration.

This page will allow you to:

• Choose the default merge behavior for your data product and decide how to handle suggested duplicate records based on match confidence levels: merge them automatically, send them to a curation queue for review, or ignore them.
• Create multiple suggested duplicate queues to apply different duplicate handling rules to different kinds of records.
• Route suggested duplicates to specific curation queues based on attribute values (for example, send high priority accounts or records from a specific region to separate queues).
• Automatically dismiss stale queue items to help curators focus only on relevant items.

Bug Fixes and Other Improvements

• Resolved an issue that prevented sources from loading from S3 connections that restrict bucket access to Tamr VPC endpoints.
• Record merges in the UI are now prevented when the total cluster record count would exceed the record limit.
• Added general usability, styling, and performance improvements.