Some data flow processes are not harvestable using the bridges. If these processed are not modeled in Talend Data Catalog, it will leave gaps in the lineage and impact analysis answers and provide an incomplete picture of the physical architecture of your systems.
Data mapping specifications are high-level logical definitions of the way data “flows” from some number of source models into elements of a target model.
These mappings are specified using a simple web based drag and drop type mapping specification editor. They are defined using descriptive text. You may also define pseudo operations using an operation editor.
The data mapping specifications form a content within Talend Data Catalog which defines logical mappings between source and target data stores. The data stores themselves are modeled separately as model contents within Talend Data Catalog but external to the data mapping specifications.
Each data store model content is referenced as either a source, a target, or can be both a source and target. One may then drag and drop objects (e.g., schemas, tables or columns) in a data source onto objects in a data target, thus creating maps. These maps may then be documented in descriptions or with more explicit operations.