We are pleased to announce record merge functionality in Tamr RealTime, expanded Jobs API support, and a number of Data Product improvements.

Merge golden records with Tamr RealTime

Using the Tamr RealTime API record merge functionality, you can now merge two existing golden records. You select which which record will be the surviving record and which record will be retired. All links associated with the retired record become associated with the surviving record; references to the retired record return the surviving record.

You can:

• Choose whether to update the surviving record values from the merged record.
• Replace all field values all field values in the surviving record by supplying a new value for each field.
• Preview merge results, using the dryRun option.

See record merge for more details.

Jobs API supports non-legacy data products

You can now use the Job API to programmatically mange jobs for B2B Customers, Healthcare Providers, and Contacts data products created with the new configuration experience. See Jobs API for more information.

Data product improvements

We have made a number of improvements to B2B Customers, Healthcare Providers, and Contacts data products created with the new configuration experience.

Golden record table views and sorting improvement

Views feature available

You can now save Views for the golden records table. Configure the table using any combination of the sorting, filtering, and format options, and then save those settings as a View for later use. Views are shared across all data product users, and each data product can have up to six different views. See Utilizing Review Tools for more information.

Table sorting improvement

The golden records table is now sorted by cluster size by default. Larger clusters appear at the top of the table.

Insight improvements

Delta metrics

Insight reports now include delta metrics to help you understand how your data changed after data product refresh. For example, you can see the number of new, moved, and removed source records.

Enrichment Value insights for multiple provididers

For the B2B Customers data product, you can now view Enrichment Value insights for each data provider used to provide firmographic enrichment. If have configured multiple providers for the data product, the Insights dropdown menu includes an Enrichment Value insight for each provider.

Print Insight PDFs

You can easily download a PDF of an insight page using the page’s Print icon.

Quickly identify attributes for which uniformity score is calculated

When configuring a data product, you can select whether to calculate the uniformity score for each attribute. The uniformity score provides insight into how similar the values for this attribute are within the source record cluster.

Now, when you select to calculate the uniformity score for an attribute, a uniformity score icon appears next to the attribute name.

New firmographic match type

We added new firmographic match type, MATCH_REGISTRATION_NUMBER, in the B2B Customers data product. This match type indicates that Tamr matched the company or organization to referential data from external data providers based on its registration number.

For existing B2B Customer data products in which you have mapped a Registration Number attribute, you may notice that some matches are updated to this match type.

See Tamr Enrich ID for more information about match statuses.

Clustering metadata available for source records

The Source Records page and published dataset include new attributes to help you understand how source records were clustered.

• Suggested Cluster ID (clustering_metadata.ml_cluster_id`): The cluster assigned to the record by the model.
• Rule Cluster ID (clustering_metadata.rule_cluster_id`): The cluster to which the record was moved by by clustering rules, which override the model.
• Applied Clustering Rules (clustering_metadata.applied_clustering_rules): The numbers of the rules applied to this record. Rule numbers are available on the Configure Data Product page.
• Verified Cluster ID (clustering_metadata.verified_cluster_id`): The cluster for a record after being manually moved to a new cluster through curation, or verified in its original cluster. Verification overrides both the model and any clustering rules.

See Persistent Identifier Attributes in Data Products for more information.

Bug fixes and other improvements

• Improved job stability through an update to the job management service. This service now enforces a limit of 5 concurrent jobs. See Monitoring Jobs for more information.
• Fixed an issue on the Manage Cluster Details page in which default View were not loading correctly.
• Fixed an issue in which configured Display Settings on the Entities page were not saved.
• General styling and usability improvements.