Article titles missing from API

We’re coming across many DOIs that are missing titles of the articles. Do you have a suggestion for handling this?

Here are some examples:

10.1023/a:1016128715865
10.1002/job.v45.2
10.1023/a:1008061017938
10.1023/a:1005245323115
10.1117/12.2522248.6035319717001
10.1007/s10050-002-8747-8
10.1023/a:1005545214937
10.1021/jf981000
10.1023/a:1009201426184
10.1002/ijc.v144.9
10.1002/ddr.v85.2
10.1186/1472-6750-6-39
10.1002/adfm.v19:2
10.1023/a:1005400507802
10.1002/adfm.v19:1
10.1002/adfm.v19:19
10.1023/a:1011078627247
10.1023/a:1010364221169
10.1002/mawe.v39:10
10.1023/a:1020219915922
10.1049/hve2.v6.3
10.1186/1476-072x-5-41
10.1023/a:1025909109843
10.1023/a:1006826331115
10.1023/a:1018536509950
10.1111/jace.v107.4
10.1186/1741-7007-2-15
10.1111/acfi.v63.5
10.1186/gb-2006-7-6-r45
10.1023/a:1020687518999
10.1023/a:1006951407168
10.1023/a:1006094117427
10.1002/ima.v32.4
10.11646/zootaxa.4878.3
10.1023/a:1016079012214
10.1186/1477-7827-2-4
10.1186/1471-2148-5-12
10.1186/gb-2005-6-2-207
10.1023/a:1011240818338
10.1023/a:1008728103512
10.1023/a:1020745026766
10.1021/bp040011m
10.6002/ect.2015.0336
10.1093/ref:odnb/29386
10.1023/a:1018902229399
10.1023/a:1018974818012
10.1023/a:1014466114854
10.1023/a:1005348614843
10.1021/bi060694
10.25100/cm.v49i1
10.1023/a:1022446730452
10.1023/a:1022459100409
10.1023/a:1026103601075
10.1023/a:1022103222857
10.1186/cc1740
10.11646/zootaxa.3946.2
10.11646/zootaxa.4885.1
10.11646/zootaxa.4706.1
10.11646/zootaxa.4122.1
10.11646/zootaxa.4555.2
10.1023/a:1010256109582
10.1186/1742-2094-4-3
10.1002/ijc.v154.8
10.1111/bjet.v55.1
10.1111/bjet.v55.2
10.1002/slct.v8.23
10.1002/slct.v8.45
10.1023/a:1005485400448
10.1023/a:1005870329601
10.1023/a:1015678312153
10.1023/a:1021927526790
10.1023/a:1005886011722
10.1023/a:1006302330879
10.1023/a:1023007717757
10.1023/a:1009608630145
10.1023/a:1016571825025
10.1111/ter.v35.5
10.1111/ter.v36.1
10.1111/ter.v35.6
10.1002/grl.v51.5
10.1002/cbin.v48.3
10.1111/jpn.v107.3
10.1111/jpn.v107.4
10.1111/jpn.v107.5
10.1111/jpn.v107.6
10.1111/jpn.v108.1
10.1023/a:1017487815091
10.1023/a:1005938624418
10.1002/app.v139.32
10.1023/a:1015210604906
10.1186/1742-2094-1-16
10.1023/a:1020893515049
10.1023/a:1013635427949
10.1023/a:1006056000957
10.1023/a:1026388522182
10.1186/1477-7827-2-33
10.1002/eost.v69.44
10.1023/a:1019886409596
10.1002/mawe.v55.2
10.1002/mawe.v55.1

Hello @bms ,

Thanks for your message, and welcome to the community forum.

We do have a bug in the REST API indexing that is impacting a small percentage of registrations each day. It looks like the DOIs on your list are some of those DOIs. To be clear, the DOIs were successfully registered, but did not get indexed by our REST API. They are already in our XML API: https://0-doi-crossref-org.lib.rivier.edu/search/doi?pid=support@crossref.org&format=unixsd&doi=10.1002/ddr.v85.2

I have added your example to the ticket our technical team is using to monitor the bug with indexing. Our technical team is actively working on a fix for this issue. It’s the highest priority ticket with our developer Carlos.

More as I have it,
Isaac

Hi Issac, I don’t seem to find the title of the journal articles in the xml data either. I’ve tried many of the dois in the list above (as well as the link you sent above).

Hi @bms ,

DOI 10.1002/ddr.v85.2 is a journal-issue-level DOI, so it wasn’t registered for a journal article:

Here are some other journal-issue-level DOIs:
https://0-doi-crossref-org.lib.rivier.edu/search/doi?pid=support@crossref.org&format=unixsd&doi=10.1002/eost.v69.44 - journal-issue-level DOI
https://0-doi-crossref-org.lib.rivier.edu/search/doi?pid=support@crossref.org&format=unixsd&doi=10.1111/jpn.v107.4 - journal-issue-level DOI

Comparatively, this DOI is a journal-article-level DOI: 10.1023/A:1020893515049

https://0-doi-crossref-org.lib.rivier.edu/search/doi?pid=support@crossref.org&format=unixsd&doi=10.1023/a:1020893515049

So, is this one: https://0-doi-crossref-org.lib.rivier.edu/search/doi?pid=support@crossref.org&format=unixsd&doi=10.1186/1742-2094-4-3

My best,
Isaac

Thanks.
I believe that all of the DOIs in my original post are journal-article-level DOIs. Using the one in your example above (DOI: 10.1023/A:1020893515049 ; I don;t seem to have permissions to post links to the API)
The title of the article can be found on the journal website: “Uranium sorption on amorphous titanium and zirconium phosphates modified by Al3+ or Fe3+ ions”. As I mentioned in the original post, that information is not returned by either of the APIs.

Hi @bms . I’ve provided you with privileges to post links. We have a number of spam-prevention measures in place on the community forum, but we still get a few requests each day to post spam from new users, so we restrict new users ability to post links for a short period of time. Apologies for that extra hoop. It shouldn’t be an issue for you now.

-Isaac

Hello again @bms ,

I believe that all of the DOIs in my original post are journal-article-level DOIs.

They’re not (at least they’re not registered with us as journal articles). DOIs 10.1111/jpn.v107.4 and 10.1002/eost.v69.44 and 10.1111/acfi.v63.5 are registered as issue-level DOIs. I haven’t checked all of the DOIs on your original list, but the ones on prefixes 10.1002 and 10.1111 have all been registered as journal-issue-level DOIs thus far.

On DOI: 10.1023/A:1020893515049
No journal-article title was registered with us for DOI 10.1023/A:1020893515049. That’s why it is not appearing in the XML API metadata record. Springer Science and Business Media LLC did not include journal-article titles for this DOI in their registration.

My best,
Isaac

I was just looking back at a few more examples from your original post and I see that these DOIs with the colon in their suffix are indeed in our REST API. You just need to encode that character to get the results: https://0-api-crossref-org.lib.rivier.edu/works/10.1023/A%3A1020893515049
https://0-api-crossref-org.lib.rivier.edu/works/10.1023/a%3A1005245323115

-Isaac

Hi @bms . Looks like Carlos on our technical team has pushed a number of these that were not appearing earlier today; and, now they are present in the REST API:

https://0-api-crossref-org.lib.rivier.edu/works/10.1111/acfi.v63.5
https://0-api-crossref-org.lib.rivier.edu/works/10.1111/jpn.v107.4
https://0-api-crossref-org.lib.rivier.edu/works/10.1002/eost.v69.44