-
Notifications
You must be signed in to change notification settings - Fork 3
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
different results between roadoi & unpaywall #13
Comments
That's interesting. I wasn't aware that results can differ. Could you submit an issue here?https://github.com/Impactstory/unpaywall |
I found an explanation on the oaDOI.org FAQ website. It says:
|
This is still proving to be a troublesome issue for me, I'm interested in a CUP journal called 'Oryx' but roadoi results don't always match reality or that of what the Unpaywall browser plugin indicates e.g. This article has a 'green padlock' with the browser plugin but is_oa = FALSE with roadoi / oaDOI API.
|
Can confirm that the API does not return an open access version for this DOI. https://api.unpaywall.org/v2/10.1017/s0030605309990706?email=YOUR_EMAIL According the Unpaywall FAQ, the extension does a live check.
|
Thanks, I've also reported it over at the impactstory repo ourresearch/oadoi#104 |
For http://doi.org/10.1016/j.tree.2012.08.021 I get different results when using
roadoi
& unpaywall.org . Why? In theory they both use the same source API : https://oadoi.org/roadoi gives is_free_to_read FALSE and oa_color_lang "closed"
but unpaywall.org gives it a green tab (actually it should probably be a blue tab?)
How and why do roadoi and unpaywall differ sometimes?
The text was updated successfully, but these errors were encountered: