Research XML submission processing of archive location metadata
Background
We are expanding the list of archive locations we support in our metadata, and need to confirm if expanding the list will have an impact deposit processing (do we index or validate this metadata?). We will probably need to do this periodically as we expand our membership and encourage them to send us this detail.This is the first time the initial list has been updated - I suspect we don't do anything upon deposit but want to confirm.
Example archive metadata (from https://api.crossref.org/works/10.32013/12345678/transform/application/vnd.crossref.unixsd+xml):
<archive_locations> </archive_locations>
How urgent
We have a number of new archive orgs waiting to be added - not super urgent but delays prevent members from adding this metadata.
Definition of ready
-
Product owner: @SaraBowman @pfeeney -
Tech lead: @jonmstark -
Service:: label applied -
Definition of done updated -
Acceptance testing plan: -
Weight applied
Definition of done
-
Unit tests identified, implemented, and passing -
Code reviewed -
Available for acceptance testing via a staging URL, or otherwise -
Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed -
Knowledge base reviewed and updated -
Public documentation reviewed and updated -
Acceptance criteria met -
Research and Document how our system processes archive location -
Answer question, do we index or validate archive location? -
Review CS code and confirm whether or not code changes are needed for this update
-
-
Acceptance testing passed -
Deployed to production
Notes
Edited by Patrick Polischuk