Funnelback logo

Documentation

Query completion (collection.cfg)

Description

This option can be used to enable or disable Funnelback's query completion feature. When set to 'enabled', query completion will be performed, while any other value (normally 'disabled') will disable query completion.

Query Completion Details

Funnelback's system for suggesting query completions as the searcher types characters into the search box relies on both Javascript functions in the user interface and an efficient back-end (padre-qs.cgi) for making suggestions in response to a partial query.

Suggestions can either come from the collection Spelling Suggestions, Best bets, or from a custom CSV file.

Spelling Suggestions

Using the Spelling Suggestions file allows out-of-the-box suggestions from the collection data without any configuration step required. This file is built by the build_spelling_index program which can be instructed to derive suggestions from various sources and to apply user-controllable criteria for inclusion. Suggestions are only included if they match the collection and are given a weight based on frequency of occurrence. Typical sources of suggestions are the corpus lexicon (single words), document annotations (such as anchortext, clicked queries, etc.), document titles and possibly other metadata fields.

QueryCompletionPublicUI.png

Best bets

Using the Best bets file allows to quickly build a suggestion list using the Best bets editor.

Please not that only Exact query match best bets will be considered.

Custom CSV data

Using a custom CSV file as a suggestion source allows you to build your own suggestions and include extra data not present in the collection. This mode also enable complex suggestions to be displayed (HTML fragments, Javascript callbacks, etc.) and complex actions to be performed when a suggestion is selected (Run a query, open a URL, run a Javascript function, etc.).

QueryCompletionExtendedPublicUI.png

For more information about custom CSV data, please see the CSV Data section.

Scoped Query Completion

Query completion will be automatically scoped for each profile to prevent suggesting queries that would show no results in that profile. This works using the query processor options specified in the padre_opts.cfg file for the profile (if there is one). If the padre_opts.cfg file is not present, then query completion suggestions are not scoped.

If a profile contains scope query processor options such as gscopes in its padre_opts.cfg file, query completion suggestions are only generated for queries that return results once that scoping is applied.

Note that rich query completion suggestions are never scoped - they will always be suggested to the user. To have profile specific rich suggestions, you can also put a query_completion.csv file in the profile directory. These suggestions will only be applied to that profile.

Default value

query_completion=disabled

Examples

To turn on query completion:

query_completion=enabled

See Also

top ⇑