-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DANS Archiving, Bag, and OREMap updates #9859
DANS Archiving, Bag, and OREMap updates #9859
Conversation
@qqmyers I'll move this milestone 6.1 issue to "ready for Review", but I'm assigning you first so that you can handle the 6.0 merge and address any EE10 issues. |
Hey @qqmyers - after you updated from dev and took yourself off the ticket, did you intend to leave the PR in draft? (is there anything else you need to do here?) |
Sorry - probably should have left myself on it. The code is reviewable at this point but I need to add docs/release note. There isn't a corresponding issue in this repo (there is one at DANS). |
@sekmiller - release note and some doc updates added - all yours. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine except for a minor typo/formatting issue
What this PR does / why we need it: Adds some additional information to the OAI_ORE map file included in the Archival Bags (and used as the default OAI_ORE metadata export) and defines an official v1.0.0 for the format of this file (after which further changes should require updating the format version). Initial changes in this draft PR:
Adding the OAI_ORE version info to the map file
Adding info about the software/version of Dataverse used to create the Bag/OAI_ORE file
Adding info about the version state (draft, released, deaccessioned, archived) to the OAI_ORE including any deaccession reason and forwarding url provided.
Which issue(s) this PR closes:
Closes #
Special notes for your reviewer:
Suggestions on how to test this:
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
Additional documentation: