Mapping Input Fields to a Unified Schema

You map fields in your source records to the fields in the industry-standard schema for your selected data product template.

When you create a data product, Tamr Cloud automatically creates predefined output fields for the unified schema. After adding input datasets to a flow, map the input fields from these datasets to the unified output fields.

  • You must map at least one input field to each output field. If any output fields do not have mappings, the flow will not run.
  • You can add new output fields if your input dataset includes a field not represented by the predefined output fields.
  • A single input field can be mapped to multiple output fields.
  • Do not map multiple fields from the same dataset to the same output field.
  • Multiple input fields from different datasets can be mapped to the same output field.
  • If your input datasets contain fields that you do not want to include in the unified schema, you do not need to map those fields to an output field.

important Important: Do not delete or rename the predefined output fields in the right pane.

Updating Schema Mapping

  1. From the Menu menu icon select Designer.
    If you need to select the data product, on the Home page locate the data product and then select More ⁝ > Designer.

  2. Select the Align to Customer Data Model (Schema Mapping) step.

  3. Change the input datasets for the step by selecting Settings gear icon to open the Edit Step dialog.

  4. In the Edit Step dialog, add your input datasets:

    • In the Input section, select Add.
    • From the Dataset dropdown, select your input dataset.
    • Repeat to add each of input datasets you added to your flow.
    • Select Update.
  5. On the Align source fields page, map input fields to output fields as follows:

    • To map a field, drag the field from the input fields panel (left) to the appropriate field in the output fields panel (right).

    • Automatically map field(s) by selecting source dataset fields then selecting Actions > AutoMap. See AutoMap Fields below for more detail.

    • To remove a field mapping, select the input field in the input fields panel (left) and then choose Actions > Unmap.

    • To add a new output field, drag and drop a field from the input fields panel (left) to the Add New section at the top of the output fields panel (right).
      You can also add a new output field by selecting Actions > Create in the output panel (right) and entering a name for the field. Then, drag and drop a field from the input fields panel (left) to the new field in the output fields panel.
      Note: Field names can contain ONLY alphanumeric characters and underscores.

    • To remove an output field, select the field in the output fields panel (right) and then select Actions > Remove. The output field and its related mappings are removed.

      Tip: You can sort input and output fields in ascending or descending order to more easily find specific fields. To sort, select the up or down arrow next at the top of the field column.

  6. When you have finished the schema mapping updates, navigate back to the flow by selecting the back arrow next to the step description.

AutoMapping Fields

The AutoMap feature can help you quickly map source fields to appropriate fields in the unified schema, by:

  • Identifying source fields that match previously mapped source fields. AutoMap applies the same mapping for the matching fields.
  • Identifying source fields that match unified schema fields. AutoMap maps these fields to their matching unified schema fields.

AutoMap considered fields to be a match when they contain the same words, not including delimiter characters, plural words, and partial matches. Delimiters recognized include camel case, but not lower case characters. AutoMap does not map two fields from a single source to the same output field. Additionally, unlike the Map option, AutoMap does not create an output field if no match is found for the selected field.

Two names are considered a match if the names are an exact match when split on:

  • The following characters: - \ _ ( ) / \
  • The boundary between lowercase and uppercase letters.
  • The boundary between letters and numbers.
  • Whitespace characters.
ExampleResulting Action
Match casesMatch: addressLine1, address_line_1, and Address Line (1)
These 3 fields would be mapped to the unified schema field address_line_1.
Delimiters acceptedMatch: company_id and company id
These 2 fields would be mapped to the unified schema field company_id.
Delimiters not acceptedNo match: addressline1 and addressLine1
No mapping.
PluralsNo match: region and regions
No mapping.
PartialsNo match: Primary Street Address and Street Address
No mapping.