Skip to main content

Search the Commons

Type at least 2 letters. Use the arrow keys to move through results, Enter to open, Escape to close.

Ask a question instead: answers drawn from across the Commons, with links to the source. Or browse the site map.

Pipeline status

In short: a plain English summary
  • This page shows the latest automatic check.
  • It runs every week.
  • It lists problems and who should fix them.
Example portfolio. This run measures the National Data Library pilot assets. Your organisation can run the same pipeline on its own portfolio: see the operating model and tutorial T3, or check a single file now.

How far each asset can be trusted

Suggested trust levels on the IOPC data trust scale. They decide how data may be shared; the data owner confirms them.

Assets

AssetTrust levelRules meeting targetTrendOpen issuesNext dueFiles

Trend: share of rules meeting target at each measurement. One dot means one measurement so far.

Open issues, most urgent first

Scored with the GOV.UK data quality issues framework. An issue is overdue once it stays open longer than its priority allows: Critical and High 1 cycle, Medium 3, Low 6.

PriorityAssetRuleWhat failedPerformanceTargetCycles openFix within

What changed since the last run

Escalations

Catalogue records

CheckSourcePassingTargetPriority

Explore every page and check on the NDL assurance page ›

Downloads from this run

How the pipeline runs

A GitHub Actions workflow runs every Monday at 06:17 UTC, or when someone presses "Run workflow". The asset list lives in one portfolio file, portfolio.ndl.yaml; add a line to measure another asset.

1Test the kitStop if anything is broken, so wrong results are never published.
2MeasureRun each asset's rules when it is due; keep the history.
3ScoreIssues framework priority, trust level, route, ageing.
4SaveCommit results only when something really changed.
5EscalateOpen, update or close one GitHub issue per overdue problem.
6PublishRebuild this portal and publish it on GitHub Pages.

Status: the workflow runs on GitHub every Monday morning, and anyone with access can start it from the Data quality pipeline page in GitHub Actions (Run workflow). Escalations appear as GitHub issues labelled dq-escalation. The same pipeline runs locally with python -m dqkit run portfolio.ndl.yaml. The runbook is docs/OPERATIONS.md.