search

UKGovLD / registry-core

Linked data registry - core application and example UI
https://github.com/UKGovLD/registry-core/wiki
Apache License 2.0
23 stars 9 forks source link

Superseded items must know what they are superseded by #38

Closed dr-shorthair closed 9 years ago

dr-shorthair commented 10 years ago

When an item status is changed to 'superseded', the UI dialogue must walk through a step to record what it is superseded by.

Using the API, an request to change status to 'superseded' should fail unless a value for dct:isReplacedBy is provided.

dr-shorthair commented 10 years ago

I see that the property reg:predecessor is provided - https://github.com/UKGovLD/ukl-registry-poc/wiki/Principles-and-concepts#status-and-life-cycle so the information can be recorded, but is not currently enforced by a workflow.

dr-shorthair commented 9 years ago

Further discussions with potential adopters have reinforced this requirement.

  1. a successor property is required - reg:successor owl:inverseOf reg:predecessor .
  2. the API should not allow status to be changed to 'superseded' without a reg:successor value being provided.
der commented 9 years ago

Done. Added reg:predecessor. Added second argument to the status update API to state the successor, required in the case of setting status to superseded. Normal update also checks that successor is present in metadata before accepting change of status to superseded. Extended UI to provide form field to specify successor and to display successor as part of core metadata.

dr-shorthair commented 9 years ago

Onya Dave. Will test soon!