Understand which relationships between objects appear in a data lineage.
To learn more about all the links available between objects in DataGalaxy, read Relationships between catalog objects.
What are implementation links?
You can create implementation links between objects in the glossary and objects in the dictionary. Implementation links let you identify where your concepts, business terms, etc. are stored in the data sources.
Relevant links:
- Implements / Is implemented by
Example: the "Monthly sales revenue" indicator is implemented by the MONTHLY_SALES_REVENUE column.
What are usage links?
You can create usage links between:
- Uses objects and glossary objects
- Uses objects and dictionary objects
Usage links let you find the meaning, the calculation rule, etc. of an indicator present in a dashboard, for example, and identify in which data source the data used to calculate this indicator is found.
Relevant links:
- Uses / Is used by
Example: the "Monthly sales aggregate" dataset uses the "Monthly sales revenue" indicator and the MONTHLY SALES_REVENUE column.
In the lineage below, the "DataGalaxy Platform" application uses several glossary concepts.
What are input and output links?
You can create input and output links between processing objects and dictionary objects. Input and output links are data-mapping links between different objects present in the sources. They let you define how the data transits through the system, what transformations it may undergo, etc.
Relevant links:
- Has as input source / Is an input source for
- Has as output source / Is an output source for
- Has as input / Is an input for
- Has as output / Is an output for
Example: the data processing T_SRC_REVENUE has a data processing unit that has the MONTHLY_SALES_REVENUE column of the ODS source as input, and the MONTHLY_SALES_REVENUE column of the DWH source as output.
What are call links?
You can create call links between objects in the Usages module. Call links let you identify, within the usages, the applications, dashboards, etc. that call each other, and make them visible in the lineage.
Relevant links:
- Calls to / Is called by
Example: the "Monthly sales report" report calls the "Monthly sales aggregate" dataset.
In the lineage below, the "Power BI" application is called by the "Power BI [en cours]" application.
What is a direct link?
When 2 objects are directly linked (via one of the 4 previous link types), the link is represented by a solid line.
Example: the "Pendo" application is directly linked to the "Nb extension active user" and "Nb extension activation" indicators.
What is a virtual link?
Two objects are virtually linked if their descendants (or the objects themselves) have a direct link. The link is then represented by a dotted line.
Example: between /api/v2/companies/get and "companies" there is a virtual link, because there is a direct link between /api/v2/companies/get and "get" (a descendant of "companies").
In the lineage below, the analytics_dwh schema is virtually linked to the Find_client_id data processing (dotted line), because some of its tables or columns are inputs of that processing.
