It also provides a convenient way to mimic a Google-like search, where all terms are ANDed, as opposed to Lucene's default OR modifier.
This HTML form provides examples on the usage of luceneQueryConstructor.js. An interface similar to Google's Advanced Search form is shown here.
luceneQueryConstructor works by assuming a certain naming convention of form fields to obtain the necessary information to construct the query.
NB:Unless otherwise specified, all uses of the word
field should be assumed to mean form input fields and not Lucene document fields.
The input form field is expected to be the same name as the Lucene Field. For example, if you have a Document with fileName as a Field, and you'd like to provide field-searching on this field, then introduce a form field like so:
<input type="text" name="fileName">
<input type="hidden" name="fileNameModifier" value="+|+">
The value of the modifier field is in the form <term modifier>|<group modifier>. Let me explain.
Looking at the form above, we see fields that provide
However, also consider the relationship between these groups of fields. Assuming Google's Advanced Search interface, we're effectively saying that we want all of the terms in the AND search field AND at least one of the terms in the OR search field AND none of the terms in the NOT search.
So, if the AND, OR and NOT search fields all have the values of foo bar, then an appropriate search query which fulfills the requirements would be
+foo +bar +(foo bar) -foo -bar
+(+foo +bar) +(foo bar) -foo -bar
The following matrix provides modifiers and their effects on queries:
|Boolean modifier||Form value||As term modifier||As group modifier|
|AND||+||+term1 + term2 ...||+(...)|
|OR||(single space)||term1 term2 ...||(...)|
|NOT||-||-term1 -term2 ...||-(...)|
|no modifier||0||term1 term2 ...||no grouping|
With this knowledge, we know that the value of the AND field modifier needs to be +|0 for the first query and +|+ for the second query, the values of the NOT field modifier and the OR field modifier are -|0 and |+ (it's an empty space before the |) in both queries respectively.
Well, that's all I have to say for now. There are more topics to be covered, such as construction of phrase searches, non-field searches, multiple list box selections, radio buttons etc, but right now I'm not even sure if anyone will read this much! :-) Anyway, there's always the code.