wishlist: Did you mean? Multi word, single class search suggestions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
This work is sponsored by the Evergreen Community Development Initiative, with development work performed by Equinox.
This is the next phase of the larger "Did You Mean" search suggestions project, following on bug 1893997 which implemented single word single class suggestions.
This part of the project implements multi word single class search suggestions in staff and OPAC interfaces.
This includes:
* Bibliographic-based search suggestions for multiword and phrase searches in a single search class
* Search suggestions from authority 4xx fields (variant terms) within a specific search class like author or subject
* Configuration options for each search class as well as an expansion of configuration options as compared the previous Did You Mean implementation
Full specifications can be seen here: https:/
A community branch will be shared once partner testing is complete.
Changed in evergreen: | |
status: | New → Confirmed |
tags: | added: didyoumean |
Changed in evergreen: | |
assignee: | nobody → Galen Charlton (gmc) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
The top three commits of the linked branch embody this development:
https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ miker/lp- 1997485- multi-term- did-you- mean
From the commit message and release notes:
Expanding on the previous single-class, single-term search suggestion development, this feature provides suggestions for single-class searches with multiple terms.
* The Library Settings that were previously used to control the global behavior of search suggestions have been moved to search class configuration fields. This was done because the data in each search class benefits from different setting values.
* If a patron's search brings back a suggestion that matches an authority variant heading, the system will provide the main heading as a suggestion as well, along with spelling-corrected suggestions.
* Quoted phrases in user input require strict term order and adjacency for the phrase portion of the suggestion generated for the phrase(s), whereas unquoted input (or the portion that is not quoted) does not.
MARC Search/Facet Class (config. metabib_ class) field additions:
* variant_ authority_ suggestion Whether this class should attempt variant authority suggestions based on search- class/browse- axis mapping transfer_ case Whether suggestions should retain user-supplied letter case skip_correct Only supply suggestions to misspelled words suggestion_ verbosity Setting that controls the amount of effort, and therefore time, spent on suggestion generation edit_distance Maximum average per-word edit distance when evaluating suggestions word_option_ count Maximum alternate suggestions per word threshold Maximum hit count beyond which suggestions are not provided use_threshold Minimum number of times a suggestion must exist in the corpus distance_ weight Weight of the keyboard distance similarity metric; 0 avoids calculation costs
* symspell_
* symspell_
* symspell_
* max_phrase_
* suggestion_
* max_suggestions Maximum suggstions to present
* low_result_
* min_suggestion_
* pg_trgm_weight Weight of the trigram similarity metric; 0 avoids calculation costs
* soundex_weight Weight of the soundex similarity metric; 0 avoids calculation costs
* keyboard_