Add Crossref.org as source for web search

[matthiasgeiger]

As complained here at the forum the Google Scholar BibTeX quality is not the best. As there are no "good" databases for all research disciplines present in JabRef we should add the crossref.org service to the web search fetchers (we are already using it for DOItoBibTeX).

Implementation should be straightforward but I've currently no time to do it...

REST API Documentation: https://github.com/CrossRef/rest-api-doc/blob/master/rest_api.md
Web search: http://search.crossref.org/

[stefan-kolb]

Wishes for fulltext fetcher will be collected at #2581.

[wujastyk]

Tried out the new crossref fetcher in 4.0.0 beta today, but it gave an error message:

Other fetchers, GVK etc., are working, and the network is fine.

Addition: this is weird. After more trials, I find the crossref fetcher sometimes works. It fails with "Wujastyk, Winternitz, McGuinness" and others; it succeeds with "Wittgenstein, Wriggins, Zysk" and others. I can't find a pattern to the failure.

[matthiasgeiger]

Unfortunately the crossref service is quite unstable 😥 there are quite often some problems at their Server side which prevent correct fetching of entries...

[wujastyk]

That's annoying, of course. But I don't think the instability of Crossref accounts for the problem we're seeing, because some searches (e.g., "zysk") always give a result, and others ("wujastyk") always give an error. Plus, searching for a problem-term at crossref.org itself works fine.

[tobiasdiez]

@wujastyk thanks for the report! There was a problem in our parsing logic which should be resolved now.
Could you please check the build from http://builds.jabref.org/master/. (be advised that some parts are still a bit unstable, especially the groups panel and the entry editor)

[wujastyk]

Yes, that fixed the problem! Many thanks! When I ran JabRef-4.0.0-dev--snapshot--2017-05-03--master--a16e6123d.jar, I had to install the Oracle 8 version of java. It wouldn't run with java-1.8.0-openjdk-amd64. Error message: $ java -jar JabRef-4.0.0-dev--snapshot--2017-05-03--master--a16e6123d.jar Error: Could not find or load main class org.jabref.JabRefMain With Oracle 8, the program ran, but I got these messages, which didn't stop the program working just fine: java -jar JabRef-4.0.0-dev--snapshot--2017-05-03--master--a16e6123d.jar AI: INFO 03-05-2017 15:52, 20: Configuration file has been successfully found as resource 15:52:39.976 [AWT-EventQueue-0] INFO org.jabref.migrations.PreferencesMigrations - Migrating old preferences. 15:52:45.633 [AWT-EventQueue-0] INFO org.jabref.logic.importer.OpenDatabase - Opening: /home/dom/Dropbox/localtexmf/bibtex/bib/biblio4-utf8.bib File: grouptree.fxml not found, attempting with camel case File: grouptree.css not found, attempting with camel case 15:52:48.792 [AWT-EventQueue-0] WARN org.jabref.model.entry.BibEntry - Could not parse date 1982/ ANTLR Tool version 4.5.3 used for code generation does not match the current runtime version 4.7ANTLR Runtime version 4.5.3 used for parser compilation does not match the current runtime version 4.7ANTLR Tool version 4.5.3 used for code generation does not match the current runtime version 4.7ANTLR Runtime version 4.5.3 used for parser compilation does not match the current runtime version 4.7ANTLR Tool version 4.5.3 used for code generation does not match the current runtime version 4.7ANTLR Runtime version 4.5.3 used for parser compilation does not match the current runtime version 4.7ANTLR Tool version 4.5.3 used for code generation does not match the current runtime version 4.7ANTLR Runtime version 4.5.3 used for parser compilation does not match the current runtime version 4.7 ​ ​Best wishes, and thanks again, Dominik​

[koppor]

I think, the installation hint is covered at http://help.jabref.org/en/Installation Am 03.05.2017 23:59 schrieb "Dominik Wujastyk" <[email protected]>:

…

Yes, that fixed the problem! Many thanks! When I ran JabRef-4.0.0-dev--snapshot--2017-05-03--master--a16e6123d.jar, I had to install the Oracle 8 version of java. It wouldn't run with java-1.8.0-openjdk-amd64. Error message: $ java -jar JabRef-4.0.0-dev--snapshot--2017-05-03--master--a16e6123d.jar Error: Could not find or load main class org.jabref.JabRefMain With Oracle 8, the program ran, but I got these messages, which didn't stop the program working just fine: java -jar JabRef-4.0.0-dev--snapshot--2017-05-03--master--a16e6123d.jar AI: INFO 03-05-2017 15:52, 20: Configuration file has been successfully found as resource 15:52:39.976 [AWT-EventQueue-0] INFO org.jabref.migrations.PreferencesMigrations - Migrating old preferences. 15:52:45.633 [AWT-EventQueue-0] INFO org.jabref.logic.importer.OpenDatabase - Opening: /home/dom/Dropbox/localtexmf/bibtex/bib/biblio4-utf8.bib File: grouptree.fxml not found, attempting with camel case File: grouptree.css not found, attempting with camel case 15:52:48.792 [AWT-EventQueue-0] WARN org.jabref.model.entry.BibEntry - Could not parse date 1982/ ANTLR Tool version 4.5.3 used for code generation does not match the current runtime version 4.7ANTLR Runtime version 4.5.3 used for parser compilation does not match the current runtime version 4.7ANTLR Tool version 4.5.3 used for code generation does not match the current runtime version 4.7ANTLR Runtime version 4.5.3 used for parser compilation does not match the current runtime version 4.7ANTLR Tool version 4.5.3 used for code generation does not match the current runtime version 4.7ANTLR Runtime version 4.5.3 used for parser compilation does not match the current runtime version 4.7ANTLR Tool version 4.5.3 used for code generation does not match the current runtime version 4.7ANTLR Runtime version 4.5.3 used for parser compilation does not match the current runtime version 4.7 ​ ​Best wishes, and thanks again, Dominik​ — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2455 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABTafkdAx2NwWLA3FFSbXbqhpX8oFoX1ks5r2PjUgaJpZM4Lhdrn> .

[wujastyk]

Ah yes, it's all explained there. Thanks! :-) ​