Service offering

Data catalogue and lineage

A catalogue that tells people what data exists, what it means, who owns it and where it flows.

Man in a kandura and ghutra working at two monitors by a large window

We put in place a data catalogue that people actually use: harvested metadata, business glossary terms, named owners and policy tags on sensitive fields. Lineage from source to report lets teams see the impact of a change before they make it.

Classification in the catalogue can follow national schemes, such as data classification under the Dubai Data Law and the data management and personal data protection standards of SDAIA's National Data Management Office in Saudi Arabia, so tags mean the same thing to auditors.

What the work involves

  • Catalogue and glossary

    Automated metadata harvesting plus business definitions agreed with data owners.

  • Policy tags

    Sensitive fields classified and tagged, so access rules follow the data across tools.

  • Lineage and impact

    Source-to-report lineage that shows which dashboards and models a change will affect.

  • Data protection by design

    Personal and sensitive data classified and access-controlled from the first pipeline.

  • Ownership and quality

    Named data owners and quality checks, so issues are fixed at source rather than in reports.

When a data catalogue becomes necessary

It becomes necessary when people spend more time finding and checking data than using it.

  • Analysts ask colleagues where data lives and what a field means.
  • Nobody can tell which reports a schema change will break.
  • Sensitive fields are not labelled, so access rules are applied inconsistently.

Talk to us about data catalogue and lineage

Tell us what you need to achieve and by when. We will propose a scope, a team and an itemised quotation.

Talk to our team