Skip to content

/doi-metadata-search

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Irregular behavior for DOIs with special characters #137

Closed
adam3smith opened this Issue Apr 10, 2019 · 4 comments

Comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@adam3smith @mfenner @gbilder
@adam3smith
Copy link

adam3smith commented Apr 10, 2019

Looking at this DOI: 10.1175/1520-0477(1996)077<0935:WOTWSM>2.0.CO;2 (similar behavior observed with other "weird" DOIs)
We observer the following behavior:

  1. https://doi.org/10.1175/1520-0477(1996)077<0935:WOTWSM>2.0.CO;2
    resolves without issues
  2. the CrossRef API returns metadata for both the regular and the URI encoded version of the DOI, i.e. https://api.crossref.org/works/10.1175/1520-0477(1996)077<0935:WOTWSM>2.0.CO;2
    works, as does https://api.crossref.org/works/10.1175%2F1520-0477%281996%29077%3C0935%3AWOTWSM%3E2.0.CO%3B2
  3. Content negotiation works when requesting bibtex: curl -LH "Accept:application/x-bibtex" https://doi.org/10.1175%2F1520-0477%281996%29077%3C0935%3AWOTWSM%3E2.0.CO%3B2
    So far so good! BUT
  4. Content negotiation requesting CrossRef Unixref silently fails: curl -LH "Accept:application/vnd.crossref.unixref+xml" https://doi.org/10.1175%2F1520-0477%281996%29077%3C0935%3AWOTWSM%3E2.0.CO%3B2 returns empty.
  5. As an additional clue, search.crossref.org also comes up empty: https://search.crossref.org/?q=10.1175%2F1520-0477%281996%29077%3C0935%3AWOTWSM%3E2.0.CO%3B2

I know these are old and relatively rare DOIs, but we've already gotten the first complaint 5 days after switching Zotero's DOI import to content negotiation, so would love to get this working.

CC @zuphilip
@mfenner

This comment has been minimized.

Sign in to view
Copy link
Member

mfenner commented Apr 10, 2019

These things are called SICIs (https://en.wikipedia.org/wiki/Serial_Item_and_Contribution_Identifier) and predate DOIs. They are a pain to work with as they are not URL-friendly. I will ping our Crossref colleagues, as this is about their content negotiation and this might not be the best repo for this discussion. I mention @gbilder here just in case.
@gbilder

This comment has been minimized.

Sign in to view
Copy link

gbilder commented Apr 10, 2019

Hi. Thanks. Looks like the SICI problem has been reported for search:

CrossRef/cr-search#22

And I have opened new ticket for API/CN:

CrossRef/rest-api-doc#454
@adam3smith

This comment has been minimized.

Sign in to view
Copy link
Author

adam3smith commented Apr 10, 2019

Thanks! I subscribed to the API/CN ticket. @mfenner if you think it´s more appropriate there (as it seems), happy for you to close this one.
@mfenner

This comment has been minimized.

Sign in to view
Copy link
Member

mfenner commented Apr 10, 2019

Ok, closing this ticket.

@mfenner mfenner closed this Apr 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.