URL in bibtex output via Content Negotiation and REST API unnecessarily encodes slash between DOI prefix and suffix as %2F
Background
This came in through the Community Forum https://community.crossref.org/t/content-negotiation-bibtex-url-field/2252
And originally posted as an issue in the habanero github from one of their users https://github.com/sckott/habanero/issues/99
Observed behavior
both curl -L -H "Accept: application/x-bibtex" "https://doi.org/10.1021/acs.jpcc.0c05161"
and
https://api.crossref.org/works/10.1021/acs.jpcc.0c05161/transform/application/x-bibtex
return the URL with the slash between the DOI prefix and suffix as "%2F" rather than "/"
url = {https://doi.org/10.1021%2Facs.jpcc.0c05161},
This behavior can be replicated across DOIs, e.g. https://api.crossref.org/works/10.7748/ns2005.04.19.31.41.c3841/transform/application/x-bibtex
url = {https://doi.org/10.7748%2Fns2005.04.19.31.41.c3841},
https://api.crossref.org/works/10.1016/0022-247X(92)90144-3/transform/application/x-bibtex
url = {https://doi.org/10.1016%2F0022-247x%2892%2990144-3},
And the same behavior is observed when using the Actions > Cite feature in CRMDS
Expected behavior
URL should not have that slash encoded
url = {https://doi.org/10.1021/acs.jpcc.0c05161},
How urgent
Definition of ready
-
Product owner: @ppolischuk1 -
Tech lead: @dtkaczyk -
Service:: label applied -
Definition of done updated -
Acceptance testing plan: staging -
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 -
URL field in bibtex response does not include unnecessarily encoded slashes
-
-
Acceptance testing passed -
Deployed to production