DCAT-AP-UK: DCAT Application Profile for the UK
Help Site map

Adopt

Adoption toolkit

Updated 4 sections on this page are new or updated since 1.2.0-rc.1 (2026-11-06). Everything that changed

Everything an organisation needs to adopt DCAT-AP-UK, in any sector: what conformance means, a route for your sector, a checklist, crosswalks from the models you use now, how to be harvested, words for contracts, and how to name organisations outside government.

Conformance levels

The record builder, the checker and the bulk checker show the level of every record. The quality score follows the five dimensions of the EU metadata quality assessment. K

Conformance levels
LevelTestWhat it means
Level 1: CoreNo errors.The record can be harvested and found. Every mandatory property is there and every value is valid.
Level 2: RichNo errors, and every recommended property given.People can judge the data without asking. This is the level to aim for.
Level 3: ExemplaryLevel 2, and a quality score of 351 or more out of 405.Ready for reuse at scale, including by AI tools and other countries' catalogues.

A route for your sectorUpdated

Central government departments and agencies

  1. Find your critical data assets with the DAM playbooks.
  2. Map your catalogue's fields with the crosswalks.
  3. Export records and check them in bulk.
  4. Switch on the critical data asset flag where it applies.
  5. Declare conformance in your catalogue record.

Devolved governments

  1. Use the nation in the jurisdiction property and the right languages.
  2. Record Welsh, Gaelic and Irish titles and descriptions as language-tagged values.
  3. Map your national catalogue (for example the spatial data infrastructure of your nation) with the crosswalks.
  4. Harvest to the National Data Library when it is ready.

Local government

  1. Start with the spreadsheet template; no new software is needed.
  2. Use your GOV.UK organisation address or local authority code for the publisher.
  3. Check records in bulk and fix the errors.
  4. Publish the records as a DCAT catalogue file next to your open data.

NHS, health and care

  1. Apply the health extension.
  2. Describe access through a trusted research environment in the rights statement.
  3. Apply disclosure control to counts of people.
  4. Map existing HDR UK Gateway records with the crosswalk.

Private sector and suppliers

  1. Apply the private and voluntary sector extension for your registered identifier.
  2. Make your product export and import DCAT-AP-UK, and pass the test records.
  3. Use the data space extension if you take part in one.
  4. Say which version you conform to.

Voluntary sector and charities

  1. Use your charity number in the org-id form (for example GB-CHC-0000000, GB-SC-SC000000 or GB-NIC-000000).
  2. Use the spreadsheet template: no technical skills needed.
  3. Say who may use the data, and for what, with a usage policy.
  4. Ask for help with the contact form.

Research, universities and data services

  1. Give a DOI as another identifier.
  2. Apply the AI-ready extension for data used in machine learning.
  3. Export Croissant for machine learning tools.
  4. Describe cross-border access with jurisdiction and transfer safeguard.

Adoption checklist

Tick as you go. Your ticks stay in this browser only.

Prepare
Map
Check
Publish
Sustain

Crosswalks from the models you use nowUpdated

Field names as the ckanext-dcat European profile reads and writes them. Fields marked extras are stored as CKAN extras or scheming fields. K Source: ckanext-dcatV

CKAN with ckanext-dcat
DCAT-AP-UKCKAN dataset and resource fieldsNote
Titletitle
Descriptionnotes
Keywordtags
Identifierextras identifier
Publisherorganization and extras publisher_uri
Contact pointextras contact_name and contact_uriUse a contact form address for contact_uri, not an email address.
Licencelicense_idMap OGL v3.0 to the CKAN licence id your instance uses.
Release dateextras issued
Last updatedextras modified
Landing pageurl
Versionversion
Themeextras theme
Geographic coverageextras spatial_uri
Time period coveredextras temporal_start and temporal_end
Languageextras language
Update frequencyextras frequency
Conforms toextras conforms_to
Access rightsextras access_rights
DistributionresourcesOne CKAN resource per distribution.
Access addressresource access_url
Download addressresource download_url
Media typeresource mimetype
Formatresource format
Size (bytes)resource size
Checksumresource hash and hash_algorithm
Security classification(none)Add a scheming field; harvesters that do not know it will drop it.
Critical data asset(none)Add a scheming field.

Download as CSV

Being harvested

  1. Publish one catalogue file. A dcat:Catalog with every dataset and data service, as Turtle or JSON-LD, at a stable address such as /catalog.ttl. Give it a modified date.
  2. Page large catalogues. Split catalogues of more than a few thousand records into pages, and link the pages, so harvesters do not time out.
  3. Use stable identifiers. Each record's address must not change when the record is edited; harvesters use it to match records and avoid duplicates.
  4. Declare the profile. Give the catalogue dct:conformsTo with the profile version, and each catalogue record the same.
  5. Serve the right media type. text/turtle for Turtle and application/ld+json for JSON-LD, with cross-origin access allowed so browser tools can read it.
  6. Keep CKAN in step. CKAN sites can use ckanext-dcat to publish the catalogue; map the extra UK fields with scheming, as the CKAN crosswalk shows.

Words for contractsUpdated

Clauses a buyer can adapt when buying or replacing a catalogue product. They are a starting point, not legal or commercial advice. For the full set, covering every open standard named here, exit and technical debt, see avoiding lock-in and technical debt.

1. The supplier's catalogue product must import and export records that conform to DCAT-AP-UK version 1.1 or later, as Turtle and JSON-LD.
2. The product must accept every example record and reject every failing test record published with the profile, reporting the rule broken.
3. The product must publish a harvestable catalogue file and must not require a proprietary format to export metadata.
4. The product must support the sector extensions the buyer names, and new minor versions of the profile within six months of release.
5. Contact points must be stored as team names and contact form addresses; the product must not require a named person.
6. The buyer owns the metadata and may export all of it at any time without charge.

Naming organisations outside governmentUpdated

GOV.UK addresses only cover government. For everyone else use a registered identifier in the org-id.guide form; the private and voluntary sector extension checks the form. K

Identifiers for organisations
SchemeExampleFor
GOV.UK organisationhttps://www.gov.uk/government/organisations/ordnance-surveyDepartments, agencies and public bodies on GOV.UK
Companies House (GB-COH)GB-COH-00000000Companies registered in the UK
Charity Commission for England and Wales (GB-CHC)GB-CHC-0000000Charities in England and Wales
Scottish Charity Regulator (GB-SC)GB-SC-SC000000Charities in Scotland
Charity Commission for Northern Ireland (GB-NIC)GB-NIC-000000Charities in Northern Ireland
Mutuals Public Register (GB-MPR)GB-MPR-12345RCo-operatives and community benefit societies
Education providers (GB-UKPRN)GB-UKPRN-10007788Colleges, universities and training providers
Legal Entity Identifier (XI-LEI)XI-LEI-213800ABCDEFGHIJKL01Any legal entity, worldwide, including in financial services

The tools

Search the portal

Keyboard shortcuts

/ or Ctrl K
Search
?
These shortcuts
Esc
Close menus, tooltips and dialogs
Arrow keys
Move between tabs and search results