Tamr Documentation

Reviewing and Labeling Record Pairs

Evaluating and labeling the pairs that Tamr suggests provides feedback to make the matching model more accurate.

Tamr makes match or no match suggestions for pairs of records. In a mastering project, the Tamr column on the Pairs page shows the = (match) or 🚫 (no match) suggestion along with an indication of the level of confidence for the suggestion: H (high), M (medium), or L (low).

Tamr suggestions for record pairsTamr suggestions for record pairs

Tamr suggestions for record pairs

You select the = or 🚫 icon in the Your Response column to label a pair as a match or no match.

For some record pairs, this column might already include a check mark indicator over the icons, as in the following example.

A green check above the match (equals sign) or no match (no symbol) Your Response iconsA green check above the match (equals sign) or no match (no symbol) Your Response icons

A green check above the match (equals sign) or no match (no symbol) Your Response icons

These check marks alert you to labels that one (or more) of your colleagues have already applied to the pair. You can still label these pairs with your own evaluation.

When you label pairs, you use your expertise to indicate whether the two records DO or DO NOT represent the same entity.

As you respond, be sure to look for records where Tamr has high confidence about a prediction that is wrong. The feedback you provide by labeling these pairs is the most valuable for improving the matching model.

Labeling a Record Pair

Options on the Pairs page allow you to label record pairs one at a time or in bulk.

To label record pairs individually:

  1. Navigate to the Pairs page in a mastering project.
  2. In the Your Response column for a pair, select the match or no match icon.
Labeling a pair as No MatchLabeling a pair as No Match

Labeling a pair as No Match

To give multiple pairs the same label:

  1. Navigate to the Pairs page in a mastering project.
  2. Use the checkboxes that appear as you move your cursor over the left end of the rows (as shown above) to select pairs to label. Use Ctrl+click (Windows) or Cmd+click (Mac) to select multiple record pairs.
  3. Select the Match or No Match option above the table.

Viewing a Record Pair Side-By-Side

To make a detailed comparison of two paired records, it can be easier to view the record values in a side-by-side orientation. When you compare record details, all values are shown. Shading is used to bring attention to differences.

To view a record pair in more detail:

  1. Select a pair by clicking anywhere in its row.
  2. Select Compare details. A side-by-side view of the records' values opens in a new dialog box.
The Compare details option opens the two records in a pair side by side.The Compare details option opens the two records in a pair side by side.

The Compare details option opens the two records in a pair side by side.

In this view, Tamr gives values that are identical in both records a shaded background to help you focus on the values that have differences. The Tamr suggestion for the pair appears at top left, and you can use the = and 🚫 icons at top center to label the pair.

Keyboard Shortcuts

Side-by-side view supports the following keyboard shortcuts.

  • M for Match
  • N for No Match
  • S for Skip
  • Left arrow key for Previous
  • Right arrow key for Next

Adding Comments to a Record Pair

To add a comment

  1. Select a pair by clicking anywhere in its row.
  2. Select Open Details to open a panel with information about the record pair.
  3. Open the Comments tab and add your text.

To indicate that a pair has a comment, a dialog icon appears in that row on the Pairs page. When you select Open Details and view the comments for a pair, Tamr displays the most recent comments entered (up to 100).

Updated 25 days ago



Reviewing and Labeling Record Pairs


Evaluating and labeling the pairs that Tamr suggests provides feedback to make the matching model more accurate.

Suggested Edits are limited on API Reference Pages

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