-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Unable to add entry using DOI #2879
Comments
It seems like it's a |
I can confirm this issue for both As a workaround until the issue is fixed you could use JabFox (https://addons.mozilla.org/en-US/firefox/addon/jabfox/), which still works (and is, at least in my opinion, more convenient than the inbuilt DOI fetcher). |
I can confirm this issue on two of my computer, one computer has a fresh install of the JabRef 3.8.2 installed using the official installer. |
This seems to be a problem on the CrossRef site, as we are just following the documentation here: |
I can confirm this issue on all of my computers. Not only by DOI, but also by adding an entry with Title search. Using ArXiv looks fine. |
It's a problem with all services which rely on crossref.org search. I have opened an issue there and we simply have to wait until the problems are resolved. |
I have the same issue. Apparently, data.crossref is temporarily down. However, doi.org works. ninfito@epsilon:> curl -LH "Accept: application/x-bibtex" https://doi.org/10.1007/s10878-013-9651-7 Is it possible to implement doi.org as a second option (in case crossref fails)? |
Actually why not put a option in the software to choose between doi.org and crossref. |
I noticed (just now) that data.crossref.org works with the appropriate header (without semicolon at the end). ninfito@epsilon:> curl -LH "Accept: application/x-bibtex" https://data.crossref.org/10.1007/s10878-013-9651-7 @Article{Haynes_2013, |
Thanks for investigating, I will check that out.
We already query doi.org for the Doi, however it redirects you to a mirror
which is in this case crossref.org
Am 04.06.2017 9:26 nachm. schrieb "ninfito" <notifications@github.com>:
… I noticed (just now) that data.crossref.org works with the appropriate
header (without semicolon at the end).
***@***.***:> curl -LH "Accept: application/x-bibtex"
https://data.crossref.org/10.1007/s10878-013-9651-7
@Article <https://github.com/article>{Haynes_2013,
doi = {10.1007/s10878-013-9651-7},
url = {https://doi.org/10.1007%2Fs10878-013-9651-7}
<https://doi.org/10.1007%2Fs10878-013-9651-7%7D>,
year = 2013,
month = {aug},
publisher = {Springer Nature},
volume = {30},
number = {3},
pages = {579--595},
author = {Teresa W. Haynes and Michael A. Henning and Lucas C. van der
Merwe and Anders Yeo},
title = {Progress on the Murty{\textendash}Simon Conjecture on diameter-2
critical graphs: a survey},
journal = {Journal of Combinatorial Optimization}
}
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2879 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AATi5O6mAlc2pV1-eYUya-d83b4lYV0Qks5sAwTNgaJpZM4Nstfe>
.
|
Ah I found the problem. In JabRef we still use http instead of https for acesssing DOI which causes the problem |
Any quick fixes for this in 3.8.2? |
@Siedlerchr, I'm not sure if the protocol used (http vs https) is important in order to solve the issue. For example, by forcing the http version 1.0 protocol and banning SSL/TLS negotiations, I still get bibtex (with the appropriate header).
|
@ninfito I changed it to HTTPS, as you can see in the linked PR, and the issue was gone. This should be fixed in the latest 4.0.0 snapshot, available in a couple of minutes. We would like to ask you to use a development build from https://builds.jabref.org/master and report back if it works for you. |
I just installed the latest build from https://builds.jabref.org/master/ : Printout from version:
Still get the same symptoms. Here's the log: Log File
|
2017-06-06 10:10 GMT+02:00 Glenn Bitar <notifications@github.com>:
j
The buld itself is fine, Commit ad69741, but somehow the build did not
update the installer files.
I just restared the build. If the installer contains this commit in its
name it's the right one
|
Not sure how long it usually takes, but they are not up to date yet |
Sorry for the inconvnenience. The auto build did not trigger correctly. The actual build 5dcdd79 contains the fix |
I can confirm that this has been fixed in: |
I can also confirm the fix in
|
@Siedlerchr, I can also confirm that this issue has been fixed. Thank you very much.
|
Thanks @Siedlerchr It is working
|
will there be a fix for 3.8 also? |
Also interested. Any fix for 3.8? |
I'm facing the same issue.
Log says:
|
@c-martinez The DOI/URL doesn't exist. This is not a problem of JabRef. |
https://doi.org/10.17026/dans-xfe-rn2w resolves to https://easy.dans.knaw.nl/ui/datasets/id/easy-dataset:75828 (on a browser) -- you are right, it is not an issue with JabRef itself, rather seems like an issue with the resolved server. The error message got me confused. Thanks! |
JabRef only contacts doi.org for URL/doi resolving, there might be other handlers/resolvers for other specific urls (its complicated) that are not available from doi.org |
You are right -- thanks for your response, I'll see if I can do something on the other end. |
It is pity that the same issue persists in 2019 :( |
@rubel75 Can you provide some details which type of DOI fails? |
The DIO tested was: 10.1038/s41699-019-0102-x |
@rubel75 |
@AEgit |
JabRef version on
Steps to reproduce:
After this, the following error message appears:
Error while fetching from DOI.
Invalid URL
Log is attached below.
Log File
The text was updated successfully, but these errors were encountered: