Configure Mapping

Once the upload is complete you should see the Configure Mapping screen.

If no data was chosen the Configure Mapping screen will look like the following.

If there is no data to map, either click Continue or set an Automation Submissions with automation set up will run to the requested stage without further interaction. method to proceed.

Follow the steps below to understand mapping data sets.

1Data Gateway will attempt to map each field with values in the source data. If it succeeds you will see:

If there are unmapped classes or attributes you will see a banner similar to one of the examples below:

Orange banners are warnings but do not prevent the user from continuing the submission.
Red banners warn of unmapped data that needs to be mapped before the submission can proceed to the next stage.

1Data Gateway will have attempted to create mappings. If it managed to configure it automatically you will see something like the screen below after clicking Review Mapping.

A fully mapped Schema Mapping, automatically configured by 1Data Gateway.

Schema Mapping takes a Source Class and maps it to a Target Class. These can be changed by clicking their drop down menus.

Source Classes / Source Attributes are derived from the data uploaded by the user. Selecting a Source Class will populate the Source Attributes.
Target Classes / Target Attributes are derived from the schema set in the portal. Choosing a Target Attribute in the right-hand column will map the source attribute to that target attribute.

Clicking the Toggle Classes button will toggle whether classes are mapped from "Source to Target" or "Target to Source".

Schema Mapping with a pair of classes annotated.

Source and Target Attributes can also be edited. Clicking an attribute drop down menu brings up a full list of all available attributes.

A class in Schema Mapping that is opened up and annotated to show all associated attributes which can be edited or deleted.

Target classes and attributes can be "removed" from a mapping by clicking the Bin icon next to their drop down menu.

Note: Only one instance of a Source Attribute can be assigned as a Target Attribute.

Mapping has been applied notification

Mappings can be saved, reset or loaded by clicking the Manage Schema button.

Manage Schema Mappings button

Configure Mapping stage with Manage Schema Mapping button annotated.

There are three sets of mappings:

Natural Mapping: Automatically created mapping based on source and target class/attribute names.
Predefined Mapping: Applied if mapping has already been defined by an Administrator during the set up of the specification.
Saved Mapping: A mapping previously saved by the user. Up to five mappings can be created and saved.

The current mapping configuration is what will be saved when Save Mapping is clicked. It does require a name to be saved.

Manage Schema Mappings popout with a saved example schema.

Even if Schema Mapping is not allowed, the Schema can be exported to a PDF for download.

Schema Mappings with an option to Export the Schema.

Click Export Schema to bring up the Export Schema popout, then use the dropdown to select whether the mapping should be generated as Target to source or Source to target.

Export Schema Mappings popout with a saved example schema.

Once the mappings are all assigned make sure to click Apply for the mapping to be saved.

Note: Unless the project allows unmapped properties, all attributes and classes must be mapped before you can continue with the submission. Continue will remain greyed out while you cannot progress.

Select Continue to proceed to Process Submission. Alternatively, select the ellipsis on the right side of the button to open the automation / notification options.

Note: For more information, visit the Notifications page.