Open koppor opened 6 years ago
In case the query is a valid lucence syntax, use that query. If the query is not a Lucene query, just take each keyword and do an OR search. -- Maybe indicate with a backbround color that the search syntax is not correct.
@koppor created a pr draft about the basic integration of a lucene parser in jabref (#8206).
If the query is not a Lucene query, just take each keyword and do an OR search.
I would argue that an AND search would be more appropriate, except if one field appears twice. So:
author=koppor author=btut
-> OR search
author=koppor title=JabRef
-> AND search
@btut Do you know what Lucene / Elastic search is doing when using "as is"? (Maybe with a reference?)
I would just like to shortly state here that there have been voices to implement fine grained extended search capabilities in issues: #4237, #6185 and #7996. If and how these would be compatible to the chip-view type of search outlined here and in #7806 or the field autocompletion feature in #7423 is something to ponder about.
I just don't want these other topics to be overlooked, forgotten, since Koppor/Jabref and Jabref/Jabref are two different repositories.
@btut Do you know what Lucene / Elastic search is doing when using "as is"? (Maybe with a reference?)
From the lucene documentation: The OR operator is the default conjunction operator.
Note that there was another UI proposal: https://github.com/JabRef/jabref/issues/7423. Maybe the proposal at https://github.com/JabRef/jabref/issues/7423 is a next step, if we got https://github.com/JabRef/jabref/pull/8356 merged.
Currently, we distinguish between basic and grammar-based search.
It was proposed to reimplement the GUI for search as follows:
.
Keywords: search autocompletion javafx
See also discussion at https://github.com/JabRef/jabref/pull/7391#issuecomment-768453050