#508: Combined SPIRES/Invenio syntax queries
------------------------+----------------------
Reporter: tbrooks | Owner: valkyrie
Type: defect | Status: in_merge
Priority: major | Milestone:
Component: WebSearch | Version:
Resolution: | Keywords:
------------------------+----------------------
Comment (by tbrooks):
Replying to [comment:1 simko]:
> A simple alternative to always passing via SPIRES syntax compatibility
> mode would be to attempt to guess when SPIRES more should used,
> e.g. by looking at the presence of substrings such as
> `space-author-space`, `space-t-space`, `space-ps-space`,
> `leading-a-space` and the like.
I think this is exactly what Valkyrie has implemented already in this
branch.
> Thinking about whether it may be advantageous to keep-and-underline,
> or to abolish, the leading `find`...
Given the stats that Valkyrie reported, showing that a large number of
people were apparently omitting the find, I think respecting their
behavior is easier than forcing them to change. However, we could retain
the "find trigger" for users. More worrisome to me is that the links in
searches like citesummary format and other places with autogenerated
searches (facets? "click here to remove published papers"? similar
controls...) ''must'' mix syntaxes since they must work whether the
initial search that led to this result could have come from either syntax.
(Example:
http://inspirebeta.net/search?p=find%20a%20brooks%2C%20t%20AND%20collection%3Aciteable&rm=citation
from
http://inspirebeta.net/search?ln=en&p=find+a+brooks%2C+t&f=&action_search=Search&sf=&so=d&rm=&rg=25&sc=0&of=hcs
But there are many other conceivable examples.
Since, for this purpose, it is good to ensure that the syntaxes work when
mixed, I see no reason not to let users drop the "find" if they want to.
Hence this ticket.
--
Ticket URL: <http://invenio-software.org/ticket/508#comment:4>
Invenio <http://invenio-software.org>
