Data mapping: Difference between revisions

Revision as of 10:23, 18 April 2006

Revision as of 15:29, 27 April 2006

Line 1:

'''Data mapping''' is the process of creating [[data element]] [[mapping]]s between two distinct [[data model]]s. Data mapping is the first step in creating a [[data transformation]] between a data source and a destination.

For example, a company that would like to transmit and receive purchases and invoices with other companies might use data mapping to create data maps from a company's data to standardized [[ANSI ASC X12]] messages for items such as purchase orders and invoices.

'''X12 standards''' are generic [[Electronic Data Interchange]] (EDI) standards designed to allow a [[company (law)|company]] to exchange [[data]] with any other company, regardless of industry. The standards are maintained by the Accredited Standards Committee X12 (ASC X12), with the [[American National Standards Institute]] (ANSI) accredited to set standards for EDI. The X12 standards are often called '''[[ANSI ASC X12]] standards'''.

Line 8:

==Hand-coded, graphical manual ==

Data mappings can be done in a variety of ways using procedural code, creating [[XSLT]] transforms or by using graphcialgraphical mapping tools that automatically generate executable tranformation programs. These are graphical tools that allow a user to "draw" lines from fields in one set of data to fields in another. Transformation programs are automatically created in XSLT, [[Java programming language]] or [[C++]].

==Using auto-connect features==

Line 14:

==Semantic mapping==

[[Semantic mapping]] is similar to the auto-connect feature of data mappers with the exception that a [[metadata registry]] can be consulted to look up data element synonyms. For example, ofif the source system lists FirstName but the destination lists PersonGivenName, the mappings will still be made if these data elements are listed as [[synonyms]] in the metadata registry.

==Examples of commercial data mapping tools==