◇ OpenCyber Academy
Postgraduate · Chapter 6 · English

Chapter 6 — Metadata, lineage and catalogue

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Chapter 6 — Metadata, lineage and catalogue

Lesson map

Lesson 06 published. Map, example, EX026.

flowchart TD
  N0["Learning outcomes"]
  N1["6.1 Definitions"]
  N2["6.2 Lineage"]
  N3["6.3 A lightweight catalogue"]
  N4["6.4 Communicating the change"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX026"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["6.1 Definitions"]
  N2["6.2 Lineage"]
  N3["6.3 A lightweight catalogue"]
  N4["6.4 Communicating the change"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX026"]
[Learning outcomes]
    |
    v
[6.1 Definitions]
    |
    v
[6.2 Lineage]
    |
    v
[6.3 A lightweight catalogue]
    |
    v
[6.4 Communicating the change]
    |
    v
[Worked example] --> [Exercise EX026]

Learning outcomes

You will (1) document definitions behind key measures; (2) trace lineage of a board measure; (3) build a lightweight catalogue.

6.1 Definitions

The board's on-time delivery measure counts shipments delivered by the end of the promised day. Customer contracts define on time as within the promised delivery window, often two hours. The board sees ninety-plus percent on time while customers complain. Lucía documents both definitions in a glossary and proposes that the board measure follow contract windows, with the old measure renamed same-day delivery. The governance group agrees, accepting that the reported figure will fall. Lucía writes both definitions into the glossary with their sources.

6.2 Lineage

Lucía traces the on-time measure from the board report back through the reporting database, the shipment system and tracking events from Corran devices and carriers. She finds that shipments without a delivery event are excluded from the measure entirely, rather than counted as late or unknown. This inflates the figure. She records the lineage in the catalogue and recommends that missing delivery events be counted as unknown and reported separately. The operations director approves this change, and the board report adds a separate line for unknown delivery status.

6.3 A lightweight catalogue

Corran has no catalogue tool. Lucía creates entries in the company's existing wiki for the twelve most used data sets and measures, each with description, owner, steward, source, refresh time, definition links and known issues. She asks stewards to update entries when changes occur. Within a few weeks, planners begin linking to entries in emails. She notes that a modest catalogue that people use is better than an ambitious one awaiting a budget. Stewards update the entries during their weekly quality meeting.

6.4 Communicating the change

When the board measure changes, the reported figure drops sharply. Lucía prepares a short note explaining the new definition, why it matches contracts and how the old figure overstated performance. She includes both figures for three months so the board can see the bridge. Dr. Achebe notes that changing definitions without explanation damages trust, while explaining openly builds confidence that the new figure is more honest. The board accepts the new measure, and the chair asks that future definition changes always be explained in the same way, with both figures shown side by side.

Worked example

Lucía documents conflicting on-time definitions and aligns the board measure with contract windows, finds excluded shipments without delivery events, builds wiki catalogue entries and explains the falling figure to the board.

Synthetic case. Measures are synthetic.

Errors and limits

Excluding records with missing events inflates performance figures.

Exercises

Continue studying — lesson 06 (chapter 06 of 12)

← Chapter 05 · Course chapter index · Chapter 07 →

Continue to the next authored lesson.