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

Import reference by DOI #25

Closed
larsgw opened this Issue Jan 3, 2017 · 6 comments

Comments

Projects
2 participants
@larsgw
Owner

larsgw commented Jan 3, 2017

This is the easiest by just looking it up in Wikidata, but papers there are limited.

Edit: I take this back, by the way. It's just that I hadn't heard of Crossref, Citoid or DOI content negotiation yet, and that I was really impressed by the Wikidata API.

@larsgw larsgw added the enhancement label Jan 3, 2017

@zuphilip

This comment has been minimized.

Show comment
Hide comment

zuphilip commented Feb 11, 2017

@larsgw larsgw added this to TODO in Version 0.3 Feb 11, 2017

@larsgw larsgw moved this from TODO to In Progress in Version 0.3 May 8, 2017

@larsgw

This comment has been minimized.

Show comment
Hide comment
@larsgw

larsgw May 23, 2017

Owner

Well I didn't know about the CrossRef API when I posted this. I think I'll use that, as the response seems to be CSL-JSON (the format Citation.js uses internally), so it won't have to be parsed.

Owner

larsgw commented May 23, 2017

Well I didn't know about the CrossRef API when I posted this. I think I'll use that, as the response seems to be CSL-JSON (the format Citation.js uses internally), so it won't have to be parsed.

@larsgw larsgw self-assigned this May 23, 2017

@zuphilip

This comment has been minimized.

Show comment
Hide comment
@zuphilip

zuphilip May 23, 2017

Actually, you can also use content negotiation which will be redirected through doi.org and CSL-JSON is supported by CrossRef, DataCite and mEDRA, e.g.

curl -LH "Accept: application/vnd.citationstyles.csl+json" https://doi.org/10.1126/science.169.3946.635

See http://citation.crosscite.org/docs.html

zuphilip commented May 23, 2017

Actually, you can also use content negotiation which will be redirected through doi.org and CSL-JSON is supported by CrossRef, DataCite and mEDRA, e.g.

curl -LH "Accept: application/vnd.citationstyles.csl+json" https://doi.org/10.1126/science.169.3946.635

See http://citation.crosscite.org/docs.html

@larsgw

This comment has been minimized.

Show comment
Hide comment
@larsgw

larsgw May 27, 2017

Owner

Update

  • async (with the fetch api) works in both node.js and browser
  • sync works in node.js (after a lot of debugging, turns out the relevant dependency drops headers after redirects and the option to turn that off is only documented in sub-dependencies)
  • sync in browser doesn't work yet, but hey, the error handling does! (#51)
  • test cases added, one (sync) fails in browser
  • other bugs surfacing (#50)

Update 2

Sync in browser is still not fixed, looks like a CORS problem, but the Access-Control-Allow-Origin: * is present. Great, CrossRef doesn't actually output correct CSL-JSON, just something that looks very much like it (and is possibly from an older specification) nope.

  • Publication types don't follow the newest specification
  • Field values don't follow specifications
  • Custom fields are added (fine by me, but documenting that couldn't hurt)
  • Probably more, still looking at things
Owner

larsgw commented May 27, 2017

Update

  • async (with the fetch api) works in both node.js and browser
  • sync works in node.js (after a lot of debugging, turns out the relevant dependency drops headers after redirects and the option to turn that off is only documented in sub-dependencies)
  • sync in browser doesn't work yet, but hey, the error handling does! (#51)
  • test cases added, one (sync) fails in browser
  • other bugs surfacing (#50)

Update 2

Sync in browser is still not fixed, looks like a CORS problem, but the Access-Control-Allow-Origin: * is present. Great, CrossRef doesn't actually output correct CSL-JSON, just something that looks very much like it (and is possibly from an older specification) nope.

  • Publication types don't follow the newest specification
  • Field values don't follow specifications
  • Custom fields are added (fine by me, but documenting that couldn't hurt)
  • Probably more, still looking at things

@larsgw larsgw referenced this issue May 28, 2017

Closed

Random Bugs Vol 1 #50

10 of 10 tasks complete
@larsgw

This comment has been minimized.

Show comment
Hide comment
@larsgw

larsgw May 30, 2017

Owner

Corresponding issues in the Crossref API repo: CrossRef/rest-api-doc#221, CrossRef/rest-api-doc#222

Owner

larsgw commented May 30, 2017

Corresponding issues in the Crossref API repo: CrossRef/rest-api-doc#221, CrossRef/rest-api-doc#222

@larsgw

This comment has been minimized.

Show comment
Hide comment
@larsgw

larsgw Jul 18, 2017

Owner

Update 3

  • The HTTP -> HTTPS issue seems to be fixed, I'm waiting for confirmation.
  • I am writing, implementing and testing some code to
    1. transform known Crossref DOI deviations (from CSL) to proper CSL
    2. transform known standard deviations (from CSL) to proper CSL
    3. drop unsupported props
  • Consequentially, most stuff should work in a short while
Owner

larsgw commented Jul 18, 2017

Update 3

  • The HTTP -> HTTPS issue seems to be fixed, I'm waiting for confirmation.
  • I am writing, implementing and testing some code to
    1. transform known Crossref DOI deviations (from CSL) to proper CSL
    2. transform known standard deviations (from CSL) to proper CSL
    3. drop unsupported props
  • Consequentially, most stuff should work in a short while

@larsgw larsgw closed this in 1e60543 Jul 22, 2017

@larsgw larsgw moved this from In Progress to Done in Version 0.3 Jul 22, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment