NIST policy regarding updates to data publications changed recently, and this PR adapts to the new policy. In particular, when an author replaces a previously published file, the policy mandates that it receive a new EDI-ID and a new DOI. This PR now supports this use case while retaining the original PDR identifier and tracking the version according to the PDR versioning convention. To help track the evolution of a publication, several new kinds of dates are now embedded into the NERDm metadata. Further, the policy allows under rare circumstances for old versions of publications to be "deactivated"--that is, it files being no longer downloadable. This PR also adds support for doing this automatically, triggered by MIDAS via a "status": "deactivated" property in the submitted POD file.
This PR relies strongly on a corresponding update in MIDAS; thus, testing on datapubtest with the updated MIDAS is necessary.
NIST policy regarding updates to data publications changed recently, and this PR adapts to the new policy. In particular, when an author replaces a previously published file, the policy mandates that it receive a new EDI-ID and a new DOI. This PR now supports this use case while retaining the original PDR identifier and tracking the version according to the PDR versioning convention. To help track the evolution of a publication, several new kinds of dates are now embedded into the NERDm metadata. Further, the policy allows under rare circumstances for old versions of publications to be "deactivated"--that is, it files being no longer downloadable. This PR also adds support for doing this automatically, triggered by MIDAS via a
"status": "deactivated"property in the submitted POD file.This PR relies strongly on a corresponding update in MIDAS; thus, testing on datapubtest with the updated MIDAS is necessary.