Hi - I am seeing a few cases where I do an API works query that returns no results for a DOI that does resolve to a URL.
I tried to post the actual URLs but it is not allowing any links in the post.
DOIs pattern are: 10.1353/sub.0.0003, 10.1353/ajh.2006.0019
This is an extremely rare occurrence (50 out of 100,000+) but I want to make sure I am not doing something wrong. Is there something going on here that I am not accounting for?
DOI 10.1353/ajh.2006.0019
XML API: https://doi.crossref.org/search/doi?pid=support@crossref.org&format=unixsd&doi=10.1353/ajh.2006.0019
REST API: This DOI has been aliased to another DOI. Because of that, we have hidden it from being retrieved. We’re working on a better way of communicating this via the REST API response for aliased DOIs, but that’s the reason you’re receiving a ‘resource not found’ message for this DOI in the REST API.
The result in the XML API confirms that the DOI has indeed been aliased to its primary DOI:
10.22059/jcamech.2022.348203.754 is a different situation. That DOI was registered with a different registration agency, mEDRA.
There are several DOI registration agencies. The majority of DOIs for scholarly publications are registered with Crossref, but definitely not all.
Only Crossref DOIs are indexed in our APIs and searchable on our Metadata Search interface. So, that’s why you can’t find a record for 10.22059/jcamech.2022.348203.754
You can check the registration agency for a DOI using the following API route: https://api.crossref.org/works/{doi}/agency
And, mEDRA, DataCite, and Crossref collaborate in supporting the Content Negotiation service which will give you basic bibliographic metadata for DOIs from all three agencies. That’s documented here https://citation.crosscite.org/docs.html
I hope that helps clarify things.
And, sorry about the restriction on putting links in your posts. It’s necessary to help avoid spam on the forum.