Data lineage and catalog

At a glance

Lineage visualizes the journey of your data from its origin to its final use. The catalog inventories your entity types with their metadata (owner, steward, quality score, freshness). These two views help you understand where your data comes from and who is responsible for it.

Before you begin

• You must have the governance.read scope to view lineage and the catalog.
• The governance.write scope is required to modify catalog metadata.
• Entity types with instances must exist in your ontology.

Steps

View the lineage graph

1. Open the Governance module from the sidebar.
2. Select the Lineage tab.
3. The interactive graph is displayed:
   • Each node represents an entity type.
   • Each arrow represents a data flow (input or output).
   • Navigate with zoom and pan.
4. Click on a node to see its upstream and downstream dependencies.

Example: in a supply chain, the lineage shows that Supplier feeds Order, which feeds Delivery, which feeds Invoice. If the supplier data is incorrect, you immediately identify all impacted downstream types.

Manage the catalog

The catalog lists all your entity types with governance metadata:

1. In the Lineage tab, switch to the Catalog view.
2. For each entity type, view:

Field	Description
Owner	The person responsible for this data type.
Steward	The operational contact for questions about this data.
Description	Business explanation of this entity type.
Quality score	Compliance percentage against active checks.
Instance count	The volume of data of this type.
Freshness	Date of last update relative to the SLA.
Tags	Custom labels for organization.

3. Click Edit to update the owner, steward, description, or tags.

Monitor freshness

The Freshness alerts section identifies entity types whose data is overdue relative to the defined SLA:

1. Check the alerts at the top of the catalog view.
2. Each alert indicates:
   • The entity type concerned
   • The delay relative to the SLA (in minutes or hours)
3. Click on the alert to go directly to the concerned entity type.

tip

Define a freshness SLA tailored to each data type. Financial data may require hourly freshness, while reference data may tolerate daily updates.

Expected result

You have a complete map of the origin and journey of your data. The catalog centralizes responsibilities and quality metrics for each entity type. Freshness alerts warn you of stale data.

Limitations and common errors

Situation	Solution
The lineage graph is empty	First create relationships between your entity types in the Ontologie.
The quality score shows "N/A"	No quality check is configured for this type. Create one in the Quality tab.
The freshness alert is incorrect	Verify the SLA configured for this entity type in the catalog.

Need help?

Contact us: Support and contact.