GUI of Talend Data Mapper - 6.3

Talend Data Mapper User Guide

EnrichVersion
6.3
EnrichProdName
Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
task
Design and Development
EnrichPlatform
Talend Studio

The Talend Data Mapper allows you to define and execute transformations (called maps) between data records or documents. For the purposes of this product, a document is the same thing as a data record.

The Talend Data Mapper has three main parts:

  • Repository navigator - The Repository navigator is a tree view in the left pane consisting of structures, maps, and namespace containers. To view one of these workspace objects, select it in the browser and open it.

    In the Talend Studio, the Repository navigator is located under the Hierarchical Mapper node, which can be found in the Data Mapper tab in the Mapping perspective; and in the Repository tab in the Integration and Mediation perspectives, under the Metadata node. When Talend Data Mapper is running in Eclipse without the Talend Studio, it is located in the Project Explorer.

  • Functions - The Functions tab in the left pane has all of the functions that can be used to create expressions.

  • Editor Area - The editor area contains an editor for each structure, map, or namespace container that is open. You can close an editor by clicking the [X] icon on the editor's tab.

To create a mapping, you drag and drop data from the input document to the output document. For more sophisticated mappings, you can create an expression that specifies the value of the output element. The expression is built from functions that operate on input (or output) values.

At any time, you can view all or a portion of your mapping using a sample document. You can also view all or a portion of the sample document. In addition, a powerful search capability is included that allows you to look for any text in your transformation maps, expressions, or document definitions.

You can import document definitions, also called structures, from specification files (like XML Schema, Guideline XML, or examples), or you can enter them manually. Structures can refer to other structures, allowing any part of a document definition to be reused. Furthermore, to handle cases where a structure is derived from another structure (like a specific implementation guideline of an EDI or XML specification), a structure can inherit from another structure.

Structures can have example document instances associated with them, which you can edit directly. Example document instances are also used when testing maps associated with the structure.

You can use various runtime projects (provided separately) in the environment where you can execute maps independently of the studio.