4 ms·

Looks nice, but it doesn't retrieve results for many of the DOIs I tried, e.g. 10.1155/2014/863625 and 10.4103/0970-2113.129901, and gave an incorrect result fo

by quasque 12y ago

Looks nice, but it doesn't retrieve results for many of the DOIs I tried, e.g. 10.1155/2014/863625 and 10.4103/0970-2113.129901, and gave an incorrect result for this one: 10.1073/pnas.1324197111 Feature suggestions: would be nice if it accepted PubMed ids, and supported other popular citation styles like Hardvard and Vancouver (or alternatively, permitted some customisation of the citation format).

michaelq 12y ago
Thanks for your feedback! Posting on HN seems to have caused speedcite to exceed Google Scholar's rate limit, so I'll be switching to crossref.org for DOIs. Using the new logic (which I'm about to push), I was able to get the first two DOIs you mentioned, but I couldn't get 10.1073/pnas.1324197111 working on crossref.org or on Google Scholar. Where did you find this DOI? I'd like to figure out a way to support it and its kind.
- quasque 12y ago
  It's from http://www.pnas.org/content/early/2014/04/24/1324197111 http://www.pnas.org/content/early/2014/04/24/1324197111, which I found via PubMed (search for "immunology", page 2). The only two services I've found that accept it are http://hdl.handle.net/ http://hdl.handle.net/ and http://dx.doi.org/ http://dx.doi.org/, and I think they're querying the same database.
  - afandian 12y ago
    Yes. More info here: http://www.doi.org/factsheets/DOIHandle.html http://www.doi.org/factsheets/DOIHandle.html That DOI is newly deposited, as I said in other comments, it may take a while to propagate.
- afandian 12y ago
  Do you know about the new CrossRef API? It might be of use. e.g. http://api.crossref.org/works/10.5555/12345678 http://api.crossref.org/works/10.5555/12345678 You can check the Registration Agency with CrossRef to see who's responsible for it: http://doi.crossref.org/ra/10.1073/pnas.1324197111 http://doi.crossref.org/ra/10.1073/pnas.1324197111 In this case, it is CrossRef. So this should work: http://api.crossref.org/works/10.1073/pnas.1324197111 http://api.crossref.org/works/10.1073/pnas.1324197111 It doesn't. I'll see if I can find out what's wrong. If you have any questions you can email labs@crossref.org EDIT: Looking at the Guest Query, http://www.crossref.org/guestquery/ http://www.crossref.org/guestquery/ it looks like this was deposited recently. There may be a delay in propagation through our systems.
  - michaelq 12y ago
    Cool, I didn't realize CrossRef had an API. That will be helpful in troubleshooting DOIs that fail to resolve for me. Thanks for your offer. I'll definitely reach out once I've accumulated some more questions for you.
  - quasque 12y ago
    How does CrossRef relate to the DOI Foundation? In particular I am curious as to how the DOI data is shared - for example what caused that DOI to be resolvable on dx.doi.org but not doi.crossref.org?
    - afandian 12y ago
      The DOI foundation is responsible for "making sure DOIs work" (I'm sure there's a better definition than that!). Like DNS, there are a number of Registration Agencies (RAs) who are responsible for registering DOIs. An organisation such as CrossRef (or DataCite) RA will say "we want to become an RA". They join, and can then register their own DOIs. DOIs are persistent identifiers, and the main reason you want those is so you can have a persistent link from one thing to another. A normal hyperlink is subject to link-rot, which is an especially bad problem when you've got printed journals or online 'printed journals'. A DOI is a link that goes via the DOI to redirect to wherever the link is meant to point at this point in history. RAs are responsible for registering DOIs and updating the link redirect data whenever the thing being pointed to moves. RAs exist for different purposes. CrossRef exists to enable linking between scholarly publications, so we register DOIs for scholarly publications (journal articles, books, etc). DataCite exists to enable linking to objects like datasets. CrossRef isn't just an DOI RA, but DOIs are a big part of what we do. In addition to this we store metadata from publishers and then let anyone use our APIs to get that data. The DOI foundation maintains a load of DOI resolution servers. They all do the same job: you click on a link, you're load-balanced to one of the machines, and it replies with the relevant redirect. Normally when you click on a DOI in a browser, you are redirected to the appropriate URL. We introduced 'Content Negotiation' for DOIs, which means you can supply an 'Accepts' header and get more bibliographic information about a DOI. This works with a redirect. Here's an example: curl -L -iH "Accept: text/turtle" http://dx.doi.org/10.5555/515151 http://dx.doi.org/10.5555/515151 That query is answered by one of the DOI servers. It doesn't matter which. You see you're redirected to Location: http://data.crossref.org/10.5555%2F515151 http://data.crossref.org/10.5555%2F515151 This is a CrossRef server and it knows all the publication metadata. This then serves all the bibliographic data. So TL;DR: 1 - The DOI foundation runs the DOI system 2 - CrossRef is an RA for DOIs 3 - Every RA runs its own resolution servers to spread the load 4 - Every resolution server can answer any DOI registered by any RA 5 - If you ask for bibliographic content negotiation on a CrossRef DOI, you'll be redirected to the data.crossref.org server which will give you what you asked for And that DOI that worked on dx.doi.org but not data.CrossRef.org might be because it can take a day for the data to propagate to various systems. Any questions, labs@crossref.org
michaelq 12y ago
OK, I've pushed fixes for the DOIs, and the first two DOIs you listed here are working now.

by quasque 12y ago

michaelq 12y ago

Thanks for your feedback! Posting on HN seems to have caused speedcite to exceed Google Scholar's rate limit, so I'll be switching to crossref.org for DOIs. Using the new logic (which I'm about to push), I was able to get the first two DOIs you mentioned, but I couldn't get 10.1073/pnas.1324197111 working on crossref.org or on Google Scholar. Where did you find this DOI? I'd like to figure out a way to support it and its kind.

quasque 12y ago
It's from http://www.pnas.org/content/early/2014/04/24/1324197111 http://www.pnas.org/content/early/2014/04/24/1324197111, which I found via PubMed (search for "immunology", page 2). The only two services I've found that accept it are http://hdl.handle.net/ http://hdl.handle.net/ and http://dx.doi.org/ http://dx.doi.org/, and I think they're querying the same database.
- afandian 12y ago
  Yes. More info here: http://www.doi.org/factsheets/DOIHandle.html http://www.doi.org/factsheets/DOIHandle.html That DOI is newly deposited, as I said in other comments, it may take a while to propagate.
afandian 12y ago
Do you know about the new CrossRef API? It might be of use. e.g. http://api.crossref.org/works/10.5555/12345678 http://api.crossref.org/works/10.5555/12345678 You can check the Registration Agency with CrossRef to see who's responsible for it: http://doi.crossref.org/ra/10.1073/pnas.1324197111 http://doi.crossref.org/ra/10.1073/pnas.1324197111 In this case, it is CrossRef. So this should work: http://api.crossref.org/works/10.1073/pnas.1324197111 http://api.crossref.org/works/10.1073/pnas.1324197111 It doesn't. I'll see if I can find out what's wrong. If you have any questions you can email labs@crossref.org EDIT: Looking at the Guest Query, http://www.crossref.org/guestquery/ http://www.crossref.org/guestquery/ it looks like this was deposited recently. There may be a delay in propagation through our systems.
- michaelq 12y ago
  Cool, I didn't realize CrossRef had an API. That will be helpful in troubleshooting DOIs that fail to resolve for me. Thanks for your offer. I'll definitely reach out once I've accumulated some more questions for you.
- quasque 12y ago
  How does CrossRef relate to the DOI Foundation? In particular I am curious as to how the DOI data is shared - for example what caused that DOI to be resolvable on dx.doi.org but not doi.crossref.org?
  - afandian 12y ago
    The DOI foundation is responsible for "making sure DOIs work" (I'm sure there's a better definition than that!). Like DNS, there are a number of Registration Agencies (RAs) who are responsible for registering DOIs. An organisation such as CrossRef (or DataCite) RA will say "we want to become an RA". They join, and can then register their own DOIs. DOIs are persistent identifiers, and the main reason you want those is so you can have a persistent link from one thing to another. A normal hyperlink is subject to link-rot, which is an especially bad problem when you've got printed journals or online 'printed journals'. A DOI is a link that goes via the DOI to redirect to wherever the link is meant to point at this point in history. RAs are responsible for registering DOIs and updating the link redirect data whenever the thing being pointed to moves. RAs exist for different purposes. CrossRef exists to enable linking between scholarly publications, so we register DOIs for scholarly publications (journal articles, books, etc). DataCite exists to enable linking to objects like datasets. CrossRef isn't just an DOI RA, but DOIs are a big part of what we do. In addition to this we store metadata from publishers and then let anyone use our APIs to get that data. The DOI foundation maintains a load of DOI resolution servers. They all do the same job: you click on a link, you're load-balanced to one of the machines, and it replies with the relevant redirect. Normally when you click on a DOI in a browser, you are redirected to the appropriate URL. We introduced 'Content Negotiation' for DOIs, which means you can supply an 'Accepts' header and get more bibliographic information about a DOI. This works with a redirect. Here's an example: curl -L -iH "Accept: text/turtle" http://dx.doi.org/10.5555/515151 http://dx.doi.org/10.5555/515151 That query is answered by one of the DOI servers. It doesn't matter which. You see you're redirected to Location: http://data.crossref.org/10.5555%2F515151 http://data.crossref.org/10.5555%2F515151 This is a CrossRef server and it knows all the publication metadata. This then serves all the bibliographic data. So TL;DR: 1 - The DOI foundation runs the DOI system 2 - CrossRef is an RA for DOIs 3 - Every RA runs its own resolution servers to spread the load 4 - Every resolution server can answer any DOI registered by any RA 5 - If you ask for bibliographic content negotiation on a CrossRef DOI, you'll be redirected to the data.crossref.org server which will give you what you asked for And that DOI that worked on dx.doi.org but not data.CrossRef.org might be because it can take a day for the data to propagate to various systems. Any questions, labs@crossref.org

michaelq 12y ago

OK, I've pushed fixes for the DOIs, and the first two DOIs you listed here are working now.