-
Notifications
You must be signed in to change notification settings - Fork 129
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
Misspelling tolerant search #338
Comments
While I'm not sure that this is the solution, a fuzzy searching algorithm would be probably the best path forward to meet this: There may be something in the SQL layer that could be implemented: Either way, this is a complicated solution that requires some additional design. |
I'm interested in working on this, but would need an extra pair of hands. (not super experienced in search stuff) |
If a search fails to return results, then perform a secondary closest match search.
For example, I search "iron gollem" and there are no results.
Now the application should try to predict what I was trying to search.
"iron" matches results, so keep it.
"gollem" does not match results, so try to guess an appropriate substitution term.
"gollem" is one character away from a match "golem", and "golem" is a term that yields results.
So now display text like: No matches found, did you mean "iron golem"? And then display matches for "iron golem".
The text was updated successfully, but these errors were encountered: