Content Negotiation returns 500 error response for specific DOI

Metadata Retrieval Interfaces for Machines
1

Hello,

When attempting to retrieve a citation for DOI 10.3847/2041-8213/abeb1c using content negotiation we are consistently getting a 500 Internal Server Error response. This is the only DOI for which content negotiation is failing for us at the moment and using the polite vs. public API does not seem to make any difference.

> GET /10.3847/2041-8213/abeb1c HTTP/1.1
> User-Agent: curl/7.29.0
> Host: doi.org
> Accept: text/x-bibliography; style=chicago-fullnote-bibliography; locale=en-GB
>
< HTTP/1.1 302 Found
< Date: Mon, 17 Jul 2023 15:22:03 GMT
< Content-Type: text/html;charset=utf-8
< Content-Length: 229
< Connection: keep-alive
< location: https://0-api-crossref-org.libus.csd.mu.edu/v1/works/10.3847%2F2041-8213%2Fabeb1c/transform
< vary: Accept

  ...

> GET /v1/works/10.3847%2F2041-8213%2Fabeb1c/transform HTTP/1.1
> User-Agent: curl/7.29.0
> Host: api.crossref.org
> Accept: text/x-bibliography; style=chicago-fullnote-bibliography; locale=en-GB
>
< HTTP/1.1 500 Server Error
< date: Mon, 17 Jul 2023 15:16:41 GMT
< transfer-encoding: chunked
< server: Jetty(9.4.40.v20210413)
< x-ratelimit-limit: 50
< x-ratelimit-interval: 1s
< x-api-pool: public
< x-rate-limit-limit: 50
< x-rate-limit-interval: 1s
< permissions-policy: interest-cohort=()
< connection: close
2 Likes
2

Scratch that, this is not the only DOI that we’re having problems with. These ones below are all also returning 500 errors.

10.3847/1538-4357/abd0fc
10.3847/1538-4357/ac0ce9
10.3847/2041-8213/abeb1c

3

Hello,

This is a bug in the system it would seem.

We have created a ticket for our tech team to investigate this and as soon as we know more we will be able update you on this.

All of the DOIs are available on our APIs but for some reason they are not showing up in content negotiation.

Thank you,
Paul

5

Hello,

Are there any updates on this issue? All the DOIs listed above are still returning 500 errors during content negotiation.

Thanks,
Marcin

6

Bumping this with another DOI that returns a 500 with content negotiation:
10.1103/PhysRevD.108.L031103

Here, too, other DOIs are working with content negotiation and the DOI works fine using the REST API
It looks to me that a common feature seem to be the very long author lists of these articles?

7

Here is another one returning 500 with content negotiation:

10.1051/0004-6361/202245042

8

Another DOI that is returning a 500 error during content negotiation:
10.3847/1538-4357/ac99e0

Are there any updates on a resolution to this problem?

9

Hello,

Many thanks for the messages and sorry for the delay.

Unfortunately there is no further progress on the fix for this I am afraid. Looking at the DOIs we can only see a similarity in that they all have larger than usual contributor lists but there hasn’t been any research or developments on this as of yet.

You can follow along with the ticket here: [CR-684] - Jira

Once we have more it will show on the jira ticket and on here.

Best regards,
Paul

10

Having said that there has not been any progress with this, we believe that another ticket fix has actually resolved the issue with the long citation list issues.

So I tested these DOIs and they do now get 200 codes via content negotiation and so I hope this issue is fixed.

Do let me know if you are getting any further issues.

Thank you,
Paul

11

Hi,

I can confirm that the DOIs we’ve had problems with are now working and returning 200 OK via content negotiation.

10.3847/1538-4357/abd0fc
10.3847/1538-4357/ac0ce9
10.3847/2041-8213/abeb1c
10.3847/1538-4357/ac99e0

Thanks,
Marcin