Generated from
folio-assistant-core/dsa/skills/dsa/dsa-catalogue-status.md— do not edit here.
dsa-catalogue-status — Set the catalogue status when an agreement changes or ends (P14.5)
Skill id:
dsa-catalogue-status· Package:dsa· Process:folio-assistant-core/dsa/processes/dsa-document-lifecycle.bpmn(Task_SetStatus, P14.5) · Checker:folio-assistant-core/scripts/check-dsa-hash.ts(bun run cat check:dsa-hash)
When a Data Sharing Agreement is amended, renewed, terminated or expires (P14
in dsa-document-lifecycle.bpmn), its W3C DCAT 3 catalogue record must reflect
its life-cycle status without deleting or overwriting any previously published
version.
Using W3C DCAT 3 §6.4.30 (adms:status)
W3C DCAT 3 §6.4.30 specifies adms:status (http://www.w3.org/ns/adms#status)
on dcat:Resource with the ADMS status vocabulary (http://purl.org/adms/status/):
- In force / published release:
"adms:status": { "@id": "http://purl.org/adms/status/Completed" } - Draft under negotiation or review:
"adms:status": { "@id": "http://purl.org/adms/status/UnderDevelopment" } - Superseded by an amended version (
dcat:previousVersionpoints here):"adms:status": { "@id": "http://purl.org/adms/status/Deprecated" } - Terminated or expired agreement (P14.5
Task_SetStatus):"adms:status": { "@id": "http://purl.org/adms/status/Withdrawn" }
Preservation of immutable versions
- Never delete or alter the signed legal text of an ended version: historical grants and audit logs continue to verify the SHA-256 digest of the version that was in force when a data access occurred.
- Update only the catalogue life-cycle status (
adms:status) (or publish the superseding version linked viadcat:previousVersion) and re-runbun run cat check:dsa-hashto confirm that every version’s legal text digest anddcterms:sourcecitation remain intact.
Processes that run this skill
| process | step(s) that name it |
|---|---|
| Data sharing agreement document life cycle | P14.5 · Set the status to ended |