Originally on 2012-02-01
In the distant past, the SPIRES query syntax trigger in user queries was simply the presence of leading find. With #508 and with the in-the-meantime-committed SPIRES syntax guesswork, the trigger can be leading-a, leading-t, space-ps-space, etc. This is clearly not desirable for some sites.
We need a new configuration variable called say CFG_WEBSEARCH_SPIRES_SYNTAX that people could use to configure their sites. For example:0 # SPIRES syntax is switched off; 1leading find is required; 2 # leading SPIRES operator is required; 3space-operator-space is recognised too; 9 = it is always used.
(taken from #431#comment:19 so that it better stands out)
Originally on 2012-02-13
Fixed in branch lmarian-public/FIX_spires_syntax_task_892
Originally by Ludmila Marian email@example.com on 2012-02-14
#CommitTicketReference repository="" revision="67dfd7951ef156128a2f6ece9a6d857bc81e9e90"
WebSearch: configurable SPIRES query syntax
- Adds variable CFG_WEBSEARCH_SPIRES_SYNTAX to configure
the use of SPIRES search syntax. Amends SQPP to use
the new variable in deciding if the SPIRES query parser
is applicable. (closes #892)
- Amends unit and regression tests for SPIRES syntax, to be
executed only if CFG_WEBSEARCH_SPIRES_SYNTAX is set accordingly.
Originally by Ludmila Marian firstname.lastname@example.org on 2012-08-09