[
https://issues.apache.org/jira/browse/SOLR-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833566#action_12833566
]
Jan Høydahl commented on SOLR-1316:
-----------------------------------
Found this excellent article on usability of auto suggest:
http://blog.twigkit.com/search-suggestions-part-1/
A bit more talking about use cases could help us assert that we're solving the
right problem :)
One complex use case could be:
* First display at most 0-1 suggestion if some terms are mis-spelled.
* Then display 0-3 suggestions from the categories field, ordered by most docs
in that category
* Then display 0-10 generic suggestions based on fields "title,keywords"
ordered by relevancy and tf/idf
Yet another use case (for shopping sites) is:
* First display 0-3 actual products, if there is an exact match on product
name. These suggestsion are of type "instant result", and must return to
frontend all data necessary to display a preview of the instant result.
Clicking this suggestion takes the user directly to product page.
* Then display 0-10 suggestions from an index (separate Solr core?) containing
actual user queries, with offensive content filtered out, sort by relevancy,
boost by frequency
One way to back the suggest from user query log is through a full-blown solr
core, where you in addition to the terms also index meta data such as usage
frequency. Your auto suggest query could then benefit from all of Solr's power
in ranking etc.
Do complex scenarios like this belong within one request to one instance of
autosuggest component? Would be very powerful. Or is it better to require users
to build a proxy between frontend and Solr which issues multiple requests to
multiple autosuggest URLs and/or queries to ordinary indices?
> Create autosuggest component
> ----------------------------
>
> Key: SOLR-1316
> URL: https://issues.apache.org/jira/browse/SOLR-1316
> Project: Solr
> Issue Type: New Feature
> Components: search
> Affects Versions: 1.4
> Reporter: Jason Rutherglen
> Assignee: Shalin Shekhar Mangar
> Priority: Minor
> Fix For: 1.5
>
> Attachments: suggest.patch, suggest.patch, suggest.patch, TST.zip
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Autosuggest is a common search function that can be integrated
> into Solr as a SearchComponent. Our first implementation will
> use the TernaryTree found in Lucene contrib.
> * Enable creation of the dictionary from the index or via Solr's
> RPC mechanism
> * What types of parameters and settings are desirable?
> * Hopefully in the future we can include user click through
> rates to boost those terms/phrases higher
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
