Data Catalogue & Lineage

A searchable catalogue of datasets and columns, lineage from source system to dashboard, a documentation standard with coverage routines, and certified data people can find and trust.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Data Catalogue & Lineage, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

207

Starter tasks

📊 Data & Analytics

Data Catalogue & Lineage

Documenting datasets, columns and their upstream sources in a searchable catalogue so people can find and trust the right data.

  1. Catalogue scope and pilot domain choice
  2. Audit of existing data documentation
  3. Catalogue tool shortlist and selection
  4. Automated metadata ingestion from the warehouse
  5. Minimum documentation standard per dataset
  6. Catalogue editor roles and curation rights
  7. Most-used tables documented first
  8. Hand-traced lineage for one critical report
  9. Domain, tier and tag taxonomy for the catalogue
  10. Pilot release to the first user group
  11. New table registration check
  12. Monthly documentation coverage report
  13. Quarterly description freshness review
  14. Catalogue questions channel and answer rota
  15. Metadata ingestion health check
  16. Deprecation notices and sunset banners
  17. Catalogue search and usage review
  18. Quarterly lineage accuracy spot check
  19. Certified dataset badge and renewal
  20. Monthly catalogue changelog for data users
  21. Table, column and job-level lineage explained
  22. OpenLineage events and integrations
  23. How query-log lineage parsing works and fails
  24. Writing table and column descriptions people use
  25. Technical, business and operational metadata
  26. Catalogue API for scripted metadata updates
  27. Impact analysis before a schema change
  28. Column-level lineage for tier-one pipelines
  29. Business glossary terms linked to catalogue columns
  30. Lineage extended to BI dashboards
  31. Descriptions kept in version control and synced
  32. Sensitivity classification tags in the catalogue
  33. Quality and freshness signals on catalogue pages
  34. Retiring the legacy data dictionary spreadsheet
  35. Search ranking, synonyms and popular results
  36. Downstream impact report in pull requests
  37. Company-wide catalogue launch week
  38. Documentation sprint for one domain
  39. Lineage evidence pack for a regulated report
  40. Catalogue and lineage through a platform migration
  41. Catalogue tool contract renewal review
  42. Bringing an acquired company's data into the catalogue
  43. Lightweight catalogue for a small data team
  44. Federated catalogue across business units
  45. New engineer's first week through the catalogue
  46. Answering where-does-this-number-come-from questions
  47. Inheriting an undocumented warehouse
  48. Cross-platform lineage stitching
  49. Catalogue metadata to ground an AI data assistant
  50. Lineage completeness scoring by domain

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Catalogue scope and pilot domain choice

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Catalogues fail most often by trying to document everything at once and finishing nothing.

First tasks

  • List every system that holds data people search for today
  • Write down which systems the first release will and will not cover
  • Choose the pilot domain and note why it won
  • Name the pilot users and invite them to a kick-off

Audit of existing data documentation

Most organisations already have documentation, just spread across wiki pages, a data dictionary spreadsheet, transformation YAML files, BI tool descriptions and the heads of two long-serving analysts. Finding and sorting it before buying or building anything shows what can be imported, what is out of date and what was never written.

First tasks

  • Search the wiki for pages that describe tables or columns
  • Collect any data dictionary spreadsheets and note when each was last edited
  • Rate each documentation source as import, rewrite or discard
  • Search team chat for repeated questions about where data lives and log the tables named
  • Ask the agent to summarise the gaps into a one-page findings note

Catalogue tool shortlist and selection

The options run from the catalogue built into your warehouse or cloud platform, through open-source tools you host yourself, to commercial catalogues with automated lineage. Scoring three candidates against the connectors you actually need, lineage depth, search quality, hosting effort and price stops the decision being made on a polished demo alone.

First tasks

  • List the connectors the tool must have for every in-scope system
  • Shortlist three catalogue options including one built-in or open-source
  • Run a two-week proof of concept on the pilot domain with the leading option
  • Score each option and estimate three-year cost including hosting staff time
  • Record the decision and the reasons the other options lost

Make it yours.

Install Data Catalogue & Lineage, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.