Skip to content
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

Weird typeahead behavior for controlled vocabularies #122

Open
flaneuse opened this issue Feb 10, 2022 · 0 comments
Open

Weird typeahead behavior for controlled vocabularies #122

flaneuse opened this issue Feb 10, 2022 · 0 comments

Comments

@flaneuse
Copy link
Collaborator

In NIAID guide species controlled vocab: Typing "Homo" in the typeahead lookup correctly lists Homo sapiens somewhere in the list. Once you add a space, however, (e.g. "Homo s"), nothing is found.

I think this is a mapping issue; wildcard Elasticsearch queries break on spaces for keywords. I think you need to switch the ES mapping to an ngram tokenizer to be able to do partial searches with spaces. @juliamullen is implementing this behavior for outbreak's typeahead lookup if you need help setting it up.

Screen Shot 2022-02-09 at 5 03 42 PM

Screen Shot 2022-02-09 at 5 03 21 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant