Error, cannot retrieve metadata

Report ID 1097135021

My Zotero just updated today, and since that all files uploaded can't generate any information, I already tried retrieving metadata several times to all different files and it
didn't work. I just bought additional storage because initially I thought that's the problem, but turns out it isn't. I already tried uninstall and reinstall. Didn't work either. I'm in the middle of deadline and really upset with this.
  • dstillman Zotero Team
    edited March 16, 2025
    [JavaScript Error: "HTTP GET https://doi.org/10.[…] failed with status code 500:

    {"status":"error","message-type":"exception","message-version":"1.0.0","message":{"name":"class org.elasticsearch.client.ResponseException" […] \"reason\":\"No shard available for [get [work][work][10.[…]]
    The doi.org metadata resolver is currently returning errors for some DOIs. This would be affecting the entire academic ecosystem and isn't a problem in Zotero itself.
  • But I just installed Mendeley and it works??
  • So the problem isn't from the metadata. I really disappointed because I just paid for new storage and now it didn't work.
  • dstillman Zotero Team
    edited March 16, 2025
    You're going to have to trust that we know what we're talking about.

    This is an error coming straight from Crossref — specifically, as you can see above, their search cluster is partially down. Getting data from Crossref is the standard way for academic tools to retrieve canonical, up-to-date DOI metadata.

    Mendeley has historically filled in metadata using its own internal crowd-sourced database (which has often resulted in a lot of garbage metadata) and may not use Crossref directly.

    This is a DOI that returns data:

    https://api.crossref.org/v1/works/10.1145/1111320.1111059

    This is a DOI that returns an error:

    https://api.crossref.org/v1/works/10.3982/ECTA11380

    This is a very serious, extremely unusual server error, and I'm sure they'll fix it soon.
  • dstillman Zotero Team
    edited March 16, 2025
    Crossref certainly should be getting their own alerts about this, but since their status page isn't showing it, we've reported it to them for good measure.
  • It seems to be working now
  • Yes, looks like it's been resolved.
Sign In or Register to comment.