"Accept:text/x-bibliography; style=bibtex" in REST API request returns bibtex, but not all characters are transformed correctly
Background
Due to the problem described in issue 1540, a user attempted an alternate way to retrieve bibtex via the REST API
Observed behavior
Instead of doing this
curl -LH "Accept: application/x-bibtex" http://api.crossref.org/works/10.1002%2Fcncr.29046/transform
which results in the bibtex missing the journal title
@article{2014,
doi = {10.1002/cncr.29046},
url = {https://doi.org/10.1002%2Fcncr.29046},
year = 2014,
month = {sep},
publisher = {Wiley},
volume = {121},
number = {3},
pages = {386--394},
author = {Caroline C. Billingsley and David E. Cohn and David G. Mutch and Julie A. Stephens and Adrian A. Suarez and Paul J. Goodfellow},
title = {Polymerase {\varepsilon} ({POLE}) mutations in endometrial cancer: Clinical outcomes and implications for Lynch syndrome testing}
}
they tried this
curl -LH "Accept:text/x-bibliography; style=bibtex" http://api.crossref.org/works/10.1002%2Fcncr.29046/transform
which produced bibtex that includes the journal title and ISSN, but missing certain character transformations that would be expected.
@article{2014, title={Polymerase ɛ (POLE) mutations in endometrial cancer: Clinical outcomes and implications for Lynch syndrome testing}, volume={121}, ISSN={0008-543X}, url={http://dx.doi.org/10.1002/cncr.29046}, DOI={10.1002/cncr.29046}, number={3}, journal={Cancer}, publisher={Wiley}, author={Billingsley, Caroline C. and Cohn, David E. and Mutch, David G. and Stephens, Julie A. and Suarez, Adrian A. and Goodfellow, Paul J.}, year={2014}, month={Sep}, pages={386–394}}
for example, the epsilon "ɛ" in the article title should be replaced with "\varepsilon".
Expected behavior
The user expected there to be some method to produce bibtex which includes a journal title and transforms the characters according to latex guidelines.
How urgent
I don't know if we even support this method of retrieving bibtex, so I redirected the user to Content Negotiation instead.
But, I wanted to document the behavior in case we decide to formalize this method of retrieving bibtex through the REST API.
If we don't support it, it would be nice if that could be clarified via an error message, instead of returning metadata that's almost correct, but not quite.
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 -
AC 1 -
AC 2
-
-
Acceptance testing passed -
Deployed to production