Dear crossref team,
On this doi : 10.1038/s41467-024-46528-w .
Nature Communications article.
I get “resource not found”
doiRa status is ok.
regards,
Renaud
Dear crossref team,
On this doi : 10.1038/s41467-024-46528-w .
Nature Communications article.
I get “resource not found”
doiRa status is ok.
regards,
Renaud
Hi Renaud,
The DOI 10.1038/s41467-024-46528-w appears to be resolving correctly now.
Let me know if you are finding an instance of this not working. The metadata was initially deposited with us back on 2024-03-13.
Warm regards,
Poppy in Technical Support
Hi Poppy,
The doi resolves but not the api : https_api_crossref_org_works_10.1038_s41467-024-46528-w
Hi @Ren ,
Thanks for clarifying. Yes, I can see that DOI 10.1038/s41467-024-46528-w has not yet been indexed by our REST API. The DOIs is active and registered, as you can see if you resolve it: https://0-doi-org.libus.csd.mu.edu/10.1038/s41467-024-46528-w and the DOI and its metadata are present in our XML API: https://0-doi-crossref-org.libus.csd.mu.edu/search/doi?pid=support@crossref.org&format=unixsd&doi=10.1038%2Fs41467-024-46528-w
So, clearly the issue is one of indexing with the REST API. We’ve had a bug in that indexing that we fixed last week and are working to re-push all records that were missed in the past. I’ve manually re-pushed this DOI back through the indexing process. The DOI should be in the REST API by this time tomorrow.
My best,
Isaac