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

Your role

Your role

Routes through the profile for the people who record, check, build, buy and use metadata. These are proto-personas: written from the backlog and policy, and not yet tested with users.

New to metadata?

Easy Read

  • Government holds a lot of data.
  • People need to know what data there is, and how to get it.
  • Metadata is the label on the data. It says what the data is, who looks after it and who can have it.
  • This profile is a set of rules for writing those labels the same way everywhere.
  • When everyone writes labels the same way, people can find data more easily.
  • It is a proposal. People who look after government data will decide whether to use it.

A good record answers five questions for the person who finds it: what is this, who looks after it, can I have it, what may I do with it, and who do I ask? The title and description answer the first; publisher the second; access rights the third; the licence the fourth; and the contact point the last.

Roles

Catalogue manager

Runs a department's data catalogue and its exports to central services.

Needs: I need to know exactly which fields to export and in what form, so that central services can harvest our records without rework.

Worries: Changing our catalogue's fields costs money and time. I need to know what changed from the xGov MEM.

Your route

  1. The xGov MEM crosswalk
  2. The profile, class by class
  3. Check an export
  4. Declare conformance in the catalogue record

Data owner or steward of a critical data asset

Accountable for a data asset shared with other public bodies, and for its entry in the Data Asset Management return.

Needs: I need to record our critical data assets once, in a form the return can be built from, without retyping.

Worries: I am not technical. I don't want to learn RDF.

Your route

  1. Build a record with critical data asset switched on
  2. What critical data assets add
  3. Name roles, not people

Chief data officer or Data Asset Management policy coordinator

Leads the department's response to the Data Asset Management Policy.

Needs: I need to know whether adopting this profile meets the policy, and what it costs my teams.

Worries: Another standard, another change. Is it endorsed?

Your route

  1. How it fits the policy and the strategy
  2. Every backlog item and how it was dealt with
  3. Status and what endorsement needs

Engineer building a harvester or discovery service

Builds the service that collects records from many catalogues, as in the metadata-based discovery pattern.

Needs: I need machine-readable shapes and stable identifiers, so I can validate what I harvest and map it to one canonical record.

Worries: Identifiers that don't resolve, and shapes that disagree with the documentation.

Your route

  1. SHACL, JSON Schema, JSON-LD context, LinkML
  2. How the three validators are kept in step
  3. The namespace status

Data lead in a devolved or local government body

Works for a body in Scotland, Wales or Northern Ireland, or a council, where the policy may not apply.

Needs: I need to know what applies to us, how to record our languages and places, and whether our national catalogues fit.

Worries: England-only rules presented as UK-wide.

Your route

  1. The four nations view
  2. Languages, including Welsh and Gaelic
  3. Places, with GSS codes

Supplier of catalogue software

Sells or maintains a data catalogue product used by public bodies.

Needs: I need a precise specification and test records so I can say my product conforms, and prove it.

Worries: Vague obligations that every buyer interprets differently.

Your route

  1. Test records that must pass and must fail
  2. Obligations and cardinalities
  3. Buying tools without lock-in, in the Data Quality Commons

Researcher, analyst or member of the public

Looks for public sector data in the National Data Library or a department's catalogue.

Needs: I need records that tell me what the data is, whether I can have it, and who to ask, in words I understand.

Worries: Records full of jargon, with broken links and no one to ask.

Your route

  1. What a good record tells you
  2. Can I have it?
  3. Who do I ask?

Inclusion and accessibility

Accessible

Built to WCAG 2.2 AA: keyboard, screen reader and zoom friendly, checked with axe-core on every build, light and dark contrast tested. A manual audit is still to do.

Languages

The profile records every language a resource is in, including Welsh, Scottish Gaelic, Irish, Scots and Cornish. The portal itself is in English only for now (open register O-07).

Plain English

Every definition is written for people who are not specialists, with Easy Read and a glossary. Technical forms are offered alongside, never instead.

Equality

Personal and special category data are flagged in records, so gaps and risks affecting particular groups are visible early. Records name roles, never people.

Your display

Change the theme, text size and spacing from Display options. Nothing is sent anywhere.

Help

If you cannot use something here, use the contact form or ask a colleague to raise it for you.

Display options

Text size, line spacing, colours, contrast, motion and link style are in Display options at the top of every page.

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