Generated from
folio-assistant-core/dsa/skills/dsa/dsa-dcat-record.md— do not edit here.
dsa-dcat-record — Write the DCAT 3 record and link versions (P2.4–5)
Skill id:
dsa-dcat-record· Package:dsa· Process:folio-assistant-core/dsa/processes/dsa-document-lifecycle.bpmn(Task_Catalogue, P2.4–5) · Checker:folio-assistant-core/scripts/check-dsa-hash.ts(bun run cat check:dsa-hash)
Whereas filing-dublin-core
covers DCMI Metadata Terms on ingested library sources, a published Data
Sharing Agreement requires a W3C DCAT 3 catalogue record describing the
agreement as a catalogued resource, its immutable legal text distribution and
SHA-256 checksum, its ODRL 2.2 policy link, and its version chain.
Required vocabulary (existing specs only)
Every field in dcat.jsonld must come from W3C DCAT 3 (including its
normative SPDX checksum terms in §6.8.12 and ADMS status terms in §6.4.30),
W3C ODRL 2.2, or DCMI Metadata Terms:
- Resource (
@type: "dcat:Resource"):@id— immutable version IRI (for example,https://example.org/dsa/042/v2).dcterms:title,dcterms:description,dcterms:issued— bibliographic metadata.dcat:version— version string (for example,"1.0","2.0").dcat:previousVersion—{ "@id": "<prior-version-resource-id>" }on every version after the first (DCAT 3 §6.4.25).adms:status— life-cycle status IRI (DCAT 3 §6.4.30; seedsa-catalogue-status).odrl:hasPolicy—{ "@id": "<odrl-agreement-uid>" }when the version carries a computable ODRL 2.2Agreement; that uid is this record’s own@id, the fixed-version URL (seedsa-odrl-source).dcat:distribution— array ofdcat:Distributionnodes.
- Distribution (
@type: "dcat:Distribution"):@idanddcat:downloadURL— immutable URL of the signed legal text file cited by the ODRL Agreement’sdcterms:source(seedsa-odrl-source).dcat:mediaType— media type (for example,"text/markdown"or"application/pdf").spdx:checksum— SHA-256 checksum object (seedsa-checksum).
Versioning rules
- New version, new URL, new hash: amending or renewing an agreement with
changed text creates a new version directory (for example,
v2/) with a new@id, a newdcat:version, a newdcat:downloadURL, and a newly computedspdx:checksumValue. - Explicit version chain: the record of an amended version MUST carry
dcat:previousVersionnaming the fixed-version URL of the version it amends, that is, the prior version’sdcat:Resource@id(v2points tov1). Consent processing walks this chain to carry older Consents across a narrowing amendment, so a missing or wrong link failscheck:dsa-hash. - No custom properties:
check:dsa-hashrejects any property not defined in ODRL 2.2, DCAT 3, or DCMI Terms.
Processes that run this skill
| process | step(s) that name it |
|---|---|
| Data sharing agreement document life cycle | P2.4–5 · Write the DCAT 3 record |