DRAFT: Assign updates to existing published frozen archives to integrate errata and related work #116
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
requested feature of letting users assign a sort of updates to their already finalized/frozen published archives. The fundamental issue is that the original MUST remain in place due to any DOI and code-of-conduct policies. So any updates e.g. to replace or supplement existing archives must leave the original intact and only e.g. add informational pointers between involved archives. In that way people finding the original e.g. through a DOI get informed about later errata and people landing at the errata archive can trace the history.
jonasbardino
added
enhancement
jonasbardino
added this to the Python3 support for general research data sites milestone
|
This work is related to ERDA support ticket 33213 so I have included both developers and supporters on reviewers. Some of that work involves actual testing and feedback once deployed on dev/test envs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initial rough outline of the components and parts needed to support the requested feature of letting users assign a sort of updates to their already finalized/frozen published archives.
The fundamental issue is that the original MUST remain in place due to any DOI and code-of-conduct policies. So any updates e.g. to replace or supplement existing archives must leave the original intact and only e.g. add informational pointers between the involved archives. In that way people finding the original e.g. through a DOI will get informed about later errata and people landing at the errata archive can trace the history.
Another important note is that the original archive may already be backed up to long-term storage like tape and cannot easily be modified. So changes to the published archive should be minimal and to the extent possible also self-healing in case of disaster recovery from long-term storage.
In practice users will get a new
Assign Updatebutton on the show archive page for finalized archives similar to the existingRegister DOIbutton there. When using that update button they should be presented with a dialog to mark the current archive as a replacement for another existing (selected) archive of theirs.The registration of that relation involves writing the information to disk and specifically generate a
published-updates.jsonfile inside the published archive folders that the landing pages will then AJAX-query and use to display Archive replacement information and links. That is, both involved archives should get that information into theirpublished-updates.jsonin the process in order to make the linking bilateral.The same method can potentially be extended to cover similar functionality for users to assign a published archive to supplement another existing published frozen one.