As described in DataGalaxy's meta-model, objects from different modules can be linked to each other. This is used to:
- Highlight how objects are actually used.
- Feed the analysis module (exploration & lineage).
In the tables below:
- Physical links (shown in gray in the original diagrams) are the ones that appear in both lineage and exploratory analysis. Only 5 link types are physical:
- Implements / Is implemented by
- Uses / Is used by
- Calls / Is called by
- Is an input(output) for / Has as input(output)
- Is a source(destination) usage for / Has as source(destination) usage
- Logical links (shown in blue in the original diagrams) only appear in exploratory analysis.
Parent-child links within a single module (e.g. Glossary object hierarchy, Dictionary object hierarchy) and links between the catalog and the Products, Governance, and Strategy modules are documented separately and aren't part of this migration batch yet.
Diagram: physical links (gray) vs. logical links (blue). (Re-add this image here — the original Freshdesk link expires after a few days.)
Diagram: links between modules, in DataGalaxy's meta-model. (Re-add this image here — the original Freshdesk link expires after a few days.)
Diagram: links within the catalog (Glossary ↔ Dictionary). (Re-add this image here — the original Freshdesk link expires after a few days.)
Diagram: links specific to Universe/Domain objects within the Glossary. (Re-add this image here — the original Freshdesk link expires after a few days.)
Several Glossary and Usages object types share an identical relation pattern. Rather than repeat the same row for each one, the tables below group them together in the "Object type" column — e.g. "Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Process, Usage" share one row where the source article listed them as separate, near-duplicate blocks.
Which links start from the Glossary?
Logical links
| Object type | Relation A → B | Relation B → A | Related object type |
|---|---|---|---|
| Universe | has domain | is a domain for | Domain |
| Universe | is the universe for | has universe | Dimension, Dimension group |
| Concept, Business term, Indicator, Indicator group, Nomenclature, Nomenclature value, Domain, Dimension, Dimension group | has domain | is a domain for | Domain |
| Concept | is a synonym of | is a synonym of | Concept |
| Concept, Business term, Indicator, Dimension | generalizes | specializes | (same type) |
| Concept | depends on | is required by | Concept |
| Concept | is part of the dimension | groups | Dimension |
| Business term, Indicator | is calculated by | contributes to the calculation of | Business term, Indicator |
| Business term | has nomenclature | lists the values for | Nomenclature |
| Indicator | varies by dimension | breaks down | Dimension |
| Nomenclature value | transcodes | transcodes | Nomenclature value |
| Dimension | has universe | is a universe for | Universe |
| Dimension | groups | is part of the dimension | Concept, Business term |
| Dimension group | has universe | is a universe for | Universe |
| Domain group | No relation possible for this object type. | ||
| All Glossary object types above | is linked to | is linked to | Any DataGalaxy object |
Physical links
| Object type | Relation A → B | Relation B → A | Related object type |
|---|---|---|---|
| Concept, Business term, Indicator, Indicator group, Nomenclature, Dimension, Dimension group | is used by | uses | Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Usage, Process, Usage field, Component |
| Concept, Business term, Indicator, Indicator group, Nomenclature, Dimension, Dimension group | is implemented by | implements | Database, FileStore, NoSQL source, TagBase source, Model, Directory, Equipment, Table, View, File, Document, Tag, Column, Field |
Which links start from the Dictionary?
Logical links
| Object type | Relation A → B | Relation B → A | Related object type |
|---|---|---|---|
| Sources (Database, FileStore, NoSQL source, TagBase source), Containers (Model, Directory, Equipment), Structures (Table, View, File, Document, Tag), Fields (Column, Field) | has domain | is a domain for | Domain |
| Sources, Containers, Structures, Fields | has universe | is a universe for | Universe |
| Sources, Containers | is a data source for | has as data source | Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Usage, Process |
| Sources, Containers | is a system of record for | has as system of record | Concept, Business term, Indicator, Indicator group |
| Sources, Containers, Structures, Fields | is linked to | is linked to | Any DataGalaxy object |
Physical links
| Object type | Relation A → B | Relation B → A | Related object type |
|---|---|---|---|
| Sources, Containers | is an input for | has as input | Data flow, Data processing |
| Sources, Containers | is an output for | has as output | Data flow, Data processing |
| Sources, Containers, Structures, Fields | is used by | uses | Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Usage, Process, Usage field, Component |
| Sources, Containers, Structures, Fields | implements | is implemented by | Concept, Business term, Indicator, Indicator group, Nomenclature, Dimension, Dimension group |
| Structures, Fields | is an input for | has as input | Data flow, Data processing |
| Structures, Fields | is an output for | has as output | Data flow, Data processing |
Which links start from Processing?
Logical links
| Object type | Relation A → B | Relation B → A | Related object type |
|---|---|---|---|
| Data flow, Data processing | depends on | is required by | (same type) |
| Data flow, Data processing | precedes | follows | (same type) |
| Data flow, Data processing | has universe | is a universe for | Universe |
| Data flow, Data processing | has domain | is a domain for | Domain |
| Data flow, Data processing | is linked to | is linked to | Any DataGalaxy object |
Physical links
| Object type | Relation A → B | Relation B → A | Related object type |
|---|---|---|---|
| Data flow, Data processing | has as input | is an input for | Database, FileStore, NoSQL source, TagBase source, Model, Directory, Equipment, Table, View, File, Document, Tag, Column, Field |
| Data flow, Data processing | has as output | is an output for | (same targets as above) |
| Data flow, Data processing | has as source usage | is a source usage for | Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Usage, Process |
| Data flow, Data processing | has as destination usage | is a destination usage for | (same targets as above) |
Which links start from Usages?
Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Process, and Usage all share the same relation pattern below. Usage field and Component share a reduced version of it (no source-data or cross-Usage relations).
Logical links
| Object type | Relation A → B | Relation B → A | Related object type |
|---|---|---|---|
| Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Process, Usage, Usage field, Component | has domain | is a domain for | Domain |
| Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Process, Usage | has universe | is a universe for | Universe |
| Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Process, Usage | has as data source | is a data source for | Database, FileStore, NoSQL source, TagBase source, Model, Directory, Equipment |
| Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Process, Usage, Usage field, Component | is linked to | is linked to | Any DataGalaxy object |
Physical links
| Object type | Relation A → B | Relation B → A | Related object type |
|---|---|---|---|
| Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Process, Usage, Usage field, Component | uses | is used by | Concept, Business term, Indicator, Indicator group, Nomenclature, Dimension, Dimension group |
| Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Process, Usage, Usage field, Component | uses | is implemented by | Database, FileStore, NoSQL source, TagBase source, Model, Directory, Equipment, Table, View, File, Document, Tag, Column, Field |
| Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Process, Usage | calls | is called by | Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Process, Usage, Usage field, Component |
| Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Process, Usage | is a source usage for | has as source usage | Data flow, Data processing |
| Application, Dashboard, Screen, Algorithm, Dataset, Open Dataset, Report, Feature, Process, Usage | is a destination usage for | has as destination usage | Data flow, Data processing |