-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Entering an Id at the Web Search should search for the id - and not throw an Exception #7575
Comments
Thanks for your report, can reproduce this. Please note that using the WebSearch for Identifier is not the right way. If you have an Identifier like a DOI or ISBN the right workflow is to use Library -> New Entry. However, if you have a DOI, you can also directly paste it on the maintable Refs #7411 |
I think the useability would much increase if the web search would automatically detect certain identifiers like ISBN and DOI |
@WolfgangFahl We will use Lucene Syntax in our next release. You can have a sneak look at https://builds.jabref.org/pull/7809/merge/. In your concrete case, the query should be |
My own tool Proceedings Title Parser tries to analyze the input of the query and "guess" what the search looks for. I didn't implement a DOI mode yet but intend to do so. When I am at it i hope to share the ideas and code for the solution. |
I think, a "relaxed" parser should be put before the actual Lucene parser. One could try to parse the input string as DOI, ISBN, ... If there is not a match, it is "just" a plain title. This (Adn I see, I reiterate my statement from #7575 (comment)) |
Refs also #7666 |
http://sotsog.bitplan.com/ has the DOI mode now. since i am using python now mostly it would be good to have RESTFul integration with JabRef but as far as i understand JabRef is not web based at this point. |
@WolfgangFahl Side comment: We have to active development streams ongoing:
The most important historical attempt for an online version is surely CloudRef with a concept of a) sharing PDF annotations among others and b) enablement of reviewing of new entries (to enable quality assurance). |
There can be a "pre-processor" / pre-fetch using org.jabref.logic.importer.CompositeIdFetcher. This fetcher both tries to parse the Id. If the id is found, the fetcher is used. If this is done as first step before the current parsing, it should "just" work. |
The code is not in CompositeIdFetcher, but at /src/main/java/org/jabref/gui/importer/fetcher/WebSearchPaneViewModel.java#L81. Tests are in |
Is this issue up for grabs? |
Thankyou! @ThiloteE |
JabRef version 5.3 on Mac OS X 10.15.7 Catalina
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: