API returns no works for a DOI that does resolve

[ajt_muse]

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?

Thank you,

Abba

[ifarley]

Hi @ajt_muse ,

Thanks for flagging these for us.

I see both of those example DOIs in our APIs:

DOI 10.1353/sub.0.0003
REST API: https://0-api-crossref-org.libus.csd.mu.edu/works/10.1353/sub.0.0003?mailto=support@crossref.org
XML API: https://0-doi-crossref-org.libus.csd.mu.edu/search/doi?pid=support@crossref.org&format=unixsd&doi=10.1353/sub.0.0003

DOI 10.1353/ajh.2006.0019
XML API: https://0-doi-crossref-org.libus.csd.mu.edu/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:

Please let me know if you have any additional questions,
Isaac

[ajt_muse]

Thanks Isaac.

I was assuming it was because of an Alias situation.

I am going to switch my process to use the XML query instead of the REST API.

Thanks,

Abba

[ifarley]

Hi Abba,

I agree with that switch. Also, I updated your account in the forum so you can post links going forward.

-Isaac