Interface for Suggester

[sunspot]

Interface for Suggester

[unimatrixZxero]

+1

[doppleware]

+1

[otobrglez]

+1

[adampope]

+1

[oki]

+1

[Bodhisattva2-0]

+1

[nz]

Related to #43, in that Suggester and Spellchecker are the same thing. I see some +1s in here, but we would need a much more fleshed out idea of what people want out of a Suggester in order to start driving API and usage docs before this can be tackled.

Any takers who want to help design this?

[scottillogical]

+1

[23tux]

+1

[sdhull]

@nz I'd be happy to help in any way I can. I was also ready to throw a +1 on here, as this is exactly the functionality we find ourselves needing at my office, all with a similar use case.

We basically want to help users fill out fields in forms. Suppose we have a "Favorite food:" field, and a use types "pi", we want to show them autosuggest options like "pie", "pizza" and "pinenuts", ordered by popularity.

favorite_food would be a column (not unique, obviously) in our users table. So a maybe reasonable API for access would be something like User.autosuggest(:favorite_foods, params[:query]), though I don't really care if it's attached to the user or not. Maybe it makes sense just to do Sunspot.suggest :favorite_foods, params[:query].

I'd get started trying to implement this in a fork, but the linked Solr docs read kind of like latin to me, so I'm not really sure how to get started with that...

[ma2kubo]

Evernote was unable to submit your note for the following reason:

The emailed note was received, but Evernote did not understand the email address. It may have been mistyped, or the user may not exist. Please check to make sure the address was properly entered.

Original message information:
From: Steve <[email protected]>
Delivered To: [email protected]
All recipients: sunspot/sunspot <[email protected]>
Subject: Re: [sunspot] Interface for Suggester (#123)

To prevent excessive emails, you may not receive another error reply for the next 360 minutes.

• The Evernote team