DOIs in staging REST API should be case-insensitive
In production, DOIs are case-insensitive. For example, all these requests return DOI 10.1016/j.apm.2020.03.018:
https://api.crossref.org/works/10.1016/j.apm.2020.03.018 (DOI returned)
https://api.crossref.org/works/10.1016/j.APM.2020.03.018 (DOI returned)
https://api.crossref.org/works?filter=doi:10.1016/j.apm.2020.03.018 (DOI returned)
https://api.crossref.org/works?filter=doi:10.1016/J.aPm.2020.03.018 (DOI returned)
In staging, only lowercase versions return this DOI, and the others return empty result or "Resource not found":
https://api.staging.crossref.org/works/10.1016/j.apm.2020.03.018 (DOI returned)
https://api.staging.crossref.org/works/10.1016/j.APM.2020.03.018 (resource not found)
https://api.staging.crossref.org/works?filter=doi:10.1016/j.apm.2020.03.018 (DOI returned)
https://api.staging.crossref.org/works?filter=doi:10.1016/J.aPm.2020.03.018 (empty result list)
Definition of done
-
Available via a staging URL -
Code reviewed -
Unit tests identified, implemented, and passing -
Public documentation reviewed and updated -
Knowledge base reviewed and updated -
Acceptance criteria met -
elasticsearch version of REST API treats DOIs case insensitively in requests
-