About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
configuration:autocomplete

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
configuration:autocomplete [2018/12/19 14:04] demiankatzconfiguration:autocomplete [2023/05/08 12:12] (current) – [Ideas for New Handlers] demiankatz
Line 3: Line 3:
 ===== Configuring Suggestions ===== ===== Configuring Suggestions =====
  
-Autocomplete functionality can be enabled, disabled or configured through settings in [[configuration:files:searches.ini]].  Each search type defined in your basic search type drop-down can be assigned its own custom autocomplete handler.  The currently available handlers and configuration details can be found in the comments above the [Autocomplete] and [Autocomplete_Types] sections of [[configuration:files:searches.ini]].+Autocomplete functionality can be enabled, disabled or configured through settings in [[configuration:files:searches.ini]].  Each search type defined in your basic search type drop-down can be assigned its own custom [[development:plugins:autosuggesters|autocomplete handler]]. The currently available handlers and configuration details can be found in the comments above the [Autocomplete] and [Autocomplete_Types] sections of [[configuration:files:searches.ini]].
  
 ===== Building Custom Suggestions ===== ===== Building Custom Suggestions =====
  
-Autocomplete handlers are standard VuFind [[development:plugins|plug-ins]]; more details can be found on the [[development:plugins:autosuggesters]] plugin page.+Autocomplete handlers are standard VuFind® [[development:plugins|plug-ins]]; more details can be found on the [[development:plugins:autosuggesters]] plugin page.
  
 ==== Ideas for New Handlers ==== ==== Ideas for New Handlers ====
Line 13: Line 13:
 The current default autocomplete handler uses a fairly simple Solr lookup.  Here are some more sophisticated approaches which may be worth pursuing: The current default autocomplete handler uses a fairly simple Solr lookup.  Here are some more sophisticated approaches which may be worth pursuing:
  
-The [[http://wiki.apache.org/solr/TermsComponent|TermsComponent]] that is new in Solr 1.4 may be an appropriate Solr search handler to get suggestions from. But left hand truncation is still not possible with that. +  * The [[https://solr.apache.org/guide/solr/latest/query-guide/terms-component.html|TermsComponent]] may be an appropriate Solr search handler to get suggestions from. But left hand truncation is still not possible with that. 
- +  * The [[https://lucidworks.com/post/auto-suggest-from-popular-queries-using-edgengrams/|Using Solr NGrams to Implement Auto-Suggest in Search]] article outlines using EdgeNGrams to set up autocomplete against popular queries parsed from the Solr logs
-On [[http://www.mattweber.org/2009/05/02/solr-autosuggest-with-termscomponent-and-jquery/]] Matt Weber basically describes one way to set up autocomplete fields using TermComponent and JQuery. +  * A more modern approach worth investigating would be to use Solr's native [[https://solr.apache.org/guide/solr/latest/query-guide/suggester.html|Suggester component]], which did not yet exist when VuFind®'s autocomplete logic was originally implemented.
- +
-On [[http://www.lucidimagination.com/blog/2009/09/08/auto-suggest-from-popular-queries-using-edgengrams/]] Jay Hill outlines using EdgeNGrams to set up autocomplete against popular queries parsed from the Solr logs.+
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
configuration/autocomplete.1545228281.txt.gz · Last modified: 2018/12/19 14:04 by demiankatz