-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
backend suggest api endpoint should provide basic suggestions #118
Comments
the backend should provide an api call which gets a (possibly partial) search term and returning a list of suggestions the main thing to determine for this issue is where it gets the suggestions from I think for this iteration we can take is based on whatever data we have in our Elasticsearch - which currently means all the BHP data. In the future when we move to Clearmash we will still need to have some of the data stored in Elasticsearch to use for autosuggest (for example, we will keep the list of places and list of family names in our local instance with some migration) |
@OriHoch Just make sure not to pull information from "databases" other than the ones mentioned by @TheGrandVizier above, cause there are things like "donors" etc. that we mustn't use. |
… mongo to es script to allow reuse
…ich can be used to reindex ES data
merged + deployed to test see release notes for details |
@TheGrandVizier - sorry, not ready for testing yet, need to run indexing for elasticsearch |
now it's deployed |
some examples on test: |
As the user is typing a search term, provide a list of suggestions that begin with what the user is typing.
Must suggest items of all types that are ours:
It should provide up to 5 suggestions as "Starts with".
If there is an exact match, suggest the exact match.
Future-proofing (bonus points): Add support for 5 items as "Sounds like".
The text was updated successfully, but these errors were encountered: