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

Search tolerance for minor typographical errors and formatting variations #3881

Closed
1 task done
thu3n opened this issue Jun 17, 2024 · 2 comments
Closed
1 task done

Comments

@thu3n
Copy link

thu3n commented Jun 17, 2024

Description

I am frequently frustrated when minor typographical errors or formatting issues result in incorrect search results. For example, if I search for "Evie " (with a trailing space), the search results are significantly different compared to searching for "Evie". Similarly, small spelling mistakes such as "Avie" instead of "Evie" lead to irrelevant results. The first image are display the correct movie first. Second image don't display it at all.
image
image

Desired Behavior

The search algorithm should be enhanced to:

Handle Extra Spaces: Allow for extra spaces before, after, or within search terms without significantly altering the results. Additionally, including the option to filter results by year would help narrow down search results effectively, in the example of movie, Evie 2024 would help to get the correct movie.

Tolerate Spelling Mistakes: Be tolerant of common spelling mistakes or typographical errors, returning results that closely match the intended search term.

Incorporate Predictive Text: Use predictive text or fuzzy logic to guess the user's intended search term even if there are minor mistakes.

Be Context-Aware: Understand the context of the search term to provide the most relevant results despite small variations in input.

Additional Context

Enhancing the search algorithm in this manner would significantly improve the user experience by reducing the frustration caused by minor errors in search queries. This feature would be highly valuable in ensuring users can find what they are looking for even if their input is not perfectly accurate.

Code of Conduct

  • I agree to follow Overseerr's Code of Conduct
Copy link

stale bot commented Feb 1, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Feb 1, 2025
@thu3n
Copy link
Author

thu3n commented Feb 1, 2025

Bump

@stale stale bot closed this as completed Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant