Semantic Mapping

Semantic mapping and linking involves creating links between objects. In general, such semantic links describe a relationship between something that is:

• more general to something more specific, e.g., from a term “Quarterly Profit” to a field on a report named “Regional Quarterly Profit”
• from design to implementation, e.g., from an entity in a logical model to a table in a database that implements that logical model
• from a term in the glossary to a field in the data lake.

In this way, you may trace linage both

• Semantic Usage : From the more general or design to the more specific or implemented (down)
• Semantic Definition : From an implementation or specific object to its design or defining term (up).

In particular, semantic mappings are very flexible and allow for a user managed when necessary:

• Semantic mappings may be defined between any two contents (glossary and/or model/PDM)
• You must explicitly create and manage a mapping content for each set of two models/glossaries you wish to define mappings between. Note, once created you may populate it (map) individual data elements as much as you want within the scope of those two models
• As there is content in the repository:
• It may be managed using the semantic mapper
• It may be exported and re-import using the CSV format
• It can be "embedded" so as to be migrated from semantic mapping to term classification if from a glossary.

This section deals with semantic mapping based links.