#502: Advanced search hangs with SPIRES syntax
------------------------+----------------------------
Reporter: tbrooks | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: WebSearch | Version:
Resolution: | Keywords: INSPIRE syntax
------------------------+----------------------------
Comment (by simko):
This happens because the search interfaces generally pay more
attention to values selected in drop-down selection boxes than to the
special query syntax typed in the input boxes. (The theory being that
if people took the trouble to select something form the UI menu, it
should be preferred.) This theory is especially bad in case the
drop-down box value is effectively unchanged by the user, since still
on the default value. As is the case here.
Note that in the current case, removing `m1=a` effectively removes the
drop-down selection value, as if nothing were selected by the user
from the drop-down offer, which solves the problem since this leads to
a different query interpretation: (1) With forced matching type
`m1=a`, meaning to match all of the words, the SPIRES query gets
interpreted as an Invenio Boolean query for the word `"ji,` AND the
word `c*` AND the word `r*`, working badly. (2) Without forced
matching type, the SPIRES query gets parsed as an Invenio author query
for `ji, c* r*`, working as wanted.
A quick and simple solution to this problem would be to disregard any
matching types in the SPIRES query syntax handler.
A somewhat less quick but still simple and desirable solution would be
to generally prefer special syntax typed by the user in the input
boxen when opposed to the selected values from the drop-down boxen,
whenever possible. I'll ticketize this one separately.
--
Ticket URL: <http://invenio-software.org/ticket/502#comment:1>
Invenio <http://invenio-software.org>
