The Settings screen in the Querying section of the Admin UI provides options to control how user queries are interpreted by LucidWorks Search and how results are displayed to users. Use this screen to make changes to those settings. Note that some of the settings in the Admin UI will only apply if the "lucid" query parser (see below) is used.
The following options are also available.All of these settings can also be configured with the Settings API.
|Parameter||Settings API Attribute Name||Description|
|Default Sort||default_sort||Defines how results will be sorted automatically for users. Users can change the sort option while viewing the results of their search. The default is relevance, other options are date and random.|
|Query Parser||query_parser|| Selects the query parser to be used for parsing queries. By default, LucidWorks Search uses the Lucid Query Parser (lucid). Other options are dismax, edismax, and lucene. For information about other available query parsers, see Query Parser Options.
|Spell-check||spellcheck||Will use an index of terms to suggest possible alternate spellings to users above their search results. By default, this parameter is turned on (and the index will be created when new content is added). Fields must be selected to be used for spell checking; by default, the author, body, description, and title fields from crawled documents will be used.|
|Show "find similar" links||show_similar||For each query result, displays a link to a query for similar results. By default, this parameter is turned on.|
|Display facets||display_facets||Displays facets (groupings of documents by common elements such as category or author) for results. By default, this parameter is turned on.|
|Unsupervised feedback||unsupervised_feedback||Enables automatic unsupervised feedback of all user queries. Unsupervised feedback is a relevancy tuning technique that analyzes documents returned by a user's query and uses the top 5-10 terms from those documents and re-executes the query with those terms added. By default, this feature is disabled. For more information, see Unsupervised Feedback Options.|
|Unsupervised feedback emphasis||unsupervised_feedback_emphasis||There are two options that determine how unsupervised feedback will affect user queries: relevancy or by recall. For more information, see Unsupervised Feedback Options.|
|Include stop words in searches||query_time_stopwords||Enables specialized stopword handling. By default, this parameter is turned on. To modify the list of stopwords, see Stop Words.|
|Auto-complete||auto_complete|| Will suggest possible query terms to users via a drop-down menu in the query box. By default, this parameter is turned on, however the index must be created with the "Generate autocomplete index" activity scheduled via the Indexing Settings screen. See Auto-Complete of User Queries for more information about configuring Auto-Complete.
|Boost recent||boost_recent||Boosts the relevance scoring of more recent documents. By default, this parameter is turned on.|
|Use synonyms|| query_time_synonyms
||Allows the use of synonyms when returning query results. By default, this parameter is turned on. For more information about modifying the list of synonyms, see Synonyms. This parameter will only work if the 'lucid' query parser is selected as the default or specifically used in the search request.|
|Enable click tracking and boosting||click_enabled||The Click Scoring Relevance Framework allows administrators to incorporate user clicks into LucidWorks' relevance ranking algorithm. There is only one step to enable Click Scoring; however, a boost data file must be created by scheduling and running the "Process click logs" activity in the Indexing Settings screen . After running that activity boost data will be available for use in relevance calculations if this box has been enabled. User queries and associated document clicks are logged to the $LWE_HOME/data/logs/click_<collection>.log file. For more information about Click Scoring, see Click Scoring Relevance Framework.|
When you have finished editing the settings, click Update Settings.
|Fields Must Be Configured To Support Query Settings|
Many of the above query settings require corresponding index configurations for each field that should be used for that functionality. For example, if spell-check is enabled for user queries, fields should be selected to populate the spell-check index. This applies to: