Content Negotiation not working correctly for 10.5572/ajae.2015.9.4.280 Returns html instead of json. Preventing ORCID user from adding this work to their ORCID profile.
ORCID reported that their "Add by DOI" feature (allowing ORCID users to add a record to their ORCID profile by inputting a DOI) is not working for the DOI 10.5572/ajae.2015.9.4.280
I confirmed that 10.5572/ajae.2015.9.4.280 is registered and appears in both our APIs.
Paula Demain, Product Manager at ORCID, tells us that the "Add by DOI" feature uses Content Negotiation.
I ran the following curl request to check whether 10.5572/ajae.2015.9.4.280 returns metadata via Content Negotiation
curl -LH "Accept: application/rdf+xml;q=0.5, application/vnd.citationstyles.csl+json;q=1.0" https://doi.org/10.5572/ajae.2015.9.4.280
The results return html. For example, the data beings as follows.
`
High Time-resolution Characterization of PM<sub>2.5</sub> Sulfate Measured in a Japanese Urban Site
-Asian Journal of Atmospheric Environment
| Korea Science</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="shortcut icon" href="/favicon.png" type="image/x-icon">
<link rel="icon" href="/favicon.png" type="image/x-icon">
<!-- Google Fonts
<link rel="stylesheet" type="text/css" href="https://fonts.googleapis.com/css?family=Noto+Sans+KR:300,400,500,700">
-->
<link rel="stylesheet" type="text/css" href="https://fonts.googleapis.com/css?family=Montserrat:400,500,600,700">
<!-- CSS Global Compulsory -->
<link rel="stylesheet" type="text/css" href="/fontawesome/css/all.min.css">
<link rel="stylesheet" type="text/css" href="/css/helper.css">
<!-- Polyfill or Shim -->
<!--[if lt IE 10]>
<script src="/js/shim/es5-shim.min.js"></script>
<script src="/js/shim/es5-sham.min.js"></script>
<script src="/js/shim/json3.min.js"></script>
<![endif]-->
`
However, if you run the equivalent curl request for a typical DOI, the results return JSON. For example
curl -LH "Accept: application/rdf+xml;q=0.5, application/vnd.citationstyles.csl+json;q=1.0" https://doi.org/10.1111/sms.13539
The resulting data begins as follows.
{"indexed":{"date-parts":[[2019,12,17]],"date-time":"2019-12-17T08:10:16Z","timestamp":1576570216272},"reference-count":53,"publisher":"Wiley","issue":"1","license":[{"URL":"http:\/\/onlinelibrary.wiley.com\/termsAndConditions#vor","start":{"date-parts":[[2019,9,18]],"date-time":"2019-09-18T00:00:00Z","timestamp":1568764800000},"delay-in-days":0,"content-version":"vor"},{"URL":"http:\/\/doi.wiley.com\/10.1002\/tdm_license_1.1","start":{"date-parts":[[2019,9,18]],"date-time":"2019-09-18T00:00:00Z","timestamp":1568764800000},
I checked a number of DOIs and all results are in JSON except for 10.5572/ajae.2015.9.4.280
Background
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 - [ ]