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.

Manage and improve · Metadata Weaver

Describe your data once. Publish it everywhere.

Paste one metadata record. The Weaver reads DCAT, schema.org, CKAN or an ODCS data contract, writes it out in all four, and shows exactly what each catalogue is missing, including the 13 critical data asset properties. It runs in your browser. Nothing is uploaded.

In short: a plain English summary
  • This page tidies up the description of a dataset.
  • Paste the description in. It shows what is missing.
  • It writes the description in several standard formats.

1. Your record

Try an example:
For example a data.gov.uk CKAN package, a DCAT JSON-LD record, a schema.org Dataset from a web page, an ODCS contract, CSV on the Web (CSVW) metadata or a Frictionless datapackage.json.

Don't paste personal data. Contact points should name a team or role, not a person.

Contract change check

Before you publish a new version of an ODCS data contract, check it, and compare it with the last version. The check lists changes that would break the people who use your data, and the version number to use.

Run it yourself

The Weaver is part of the open toolkit (MIT licence). Use it in your own catalogue, pipeline or AI agent, with no dependency on this site.

Command line

python -m dqkit weave record.json --report
python -m dqkit weave record.json --to dcat
python -m dqkit contract-check new.yaml --against old.yaml

Python

from dqkit import weaver, contracts
w = weaver.weave(record)
w["outputs"]["dcat"], w["cda"]["coverage"]
contracts.diff_odcs(old, new)

AI agents (MCP)

The toolkit's MCP server offers weave_metadata and check_contract, read-only. See the tutorial.

In GitHub Actions

Fail a pull request when a contract change breaks consumers without a major version bump: contract-check exits with 1.

Why a weaver, not just a crosswalk

Our assessment

A crosswalk tells you that dct:title and name mean the same thing. Teams still have to retype records for each catalogue, and gaps only show up after publishing. A weaver does the translation, keeps one source of truth, and shows gaps before anything goes live.

  • Worth building: the same dataset is often described in data.gov.uk (CKAN), a department catalogue (DCAT), web pages (schema.org) and a data contract (ODCS). Each copy drifts.
  • Safe to share: it's deterministic, open and runs offline, so any organisation can replicate it, including Crown Dependencies, Overseas Territories and partners abroad.
  • Honest: nothing is invented. Missing fields stay missing and are reported. Fields a standard can't carry are listed as "not carried".
  • Since version 2.1: CSVW and Frictionless inputs, GeoDCAT-AP and StatDCAT-AP outputs, and profile checks for DCAT-AP, GeoDCAT-AP, StatDCAT-AP and the UK critical data asset properties. Since version 2.12: a concept-by-concept mapping of the Weaver to the UK cross-government Metadata Exchange Model, DCAT and DQV, ready for review: download the mapping (CSV). It becomes the Weaver's UK profile once the Data Standards Authority's peer review route has checked it.