Include resource URL in JSON response
Background
This is a feature enhancement we'd like to have in place before putting out the 2022 public data file.
Sample files:
JSON output:
"resource": {
"primary": {
"URL": "http://multi-science.atypon.com/doi/10.1260/1475473021502739"
},
"secondary": [
{
"URL": "http://triggered.edina.clockss.org/ServeContent?url=http%3A%2F%2Fmulti-science.atypon.com%2Fdoi%2Fpdf%2F10.1260%2F1475473021502739"
},
{
"URL": "http://triggered.stanford.clockss.org/ServeContent?url=http%3A%2F%2Fmulti-science.atypon.com%2Fdoi%2Fpdf%2F10.1260%2F1475473021502739"
}
]
}
Item Tree model: https://drive.google.com/file/d/1iOLOKAWjZs03gnrfs0ByuuQ8byaxv1na/view
Definition of ready
-
Product owner: @ppolischuk1 -
Tech lead: @dtkaczyk -
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 -
Item Tree model extended to contain primary and secondary URLs, consistently with the linked diagram -
new top-level JSON element called resource
containing primary and secondary URLs from deposited XML
-
-
Acceptance testing passed -
Deployed to production
Notes
This will require adding new field(s) to the mapping, indexing and retrieving code, and then re-indexing.
Edited by Patrick Polischuk