-
Notifications
You must be signed in to change notification settings - Fork 18
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
remove GIVpower sort from project search results #1811
Comments
Hmm, I believe we need to update the UI/UX for this. In the current user flow, the "Sort by" option is visible and already has a value, which could be causing some confusion. One option could be to skip the sorting when a search term is entered, or we could add something like a "No order" option in the sort menu. What do you think, @divine_comedian? |
I would recommend we could show an option in the sort drop down that says "Best Match" which refers to closest match to the keyword entered let's use this icon from the DS to be shown along with this option when user is not using search feature we should not show this option. |
OK, I think the best way for us is to use |
"Most Relevant" is also can be a good fit :) |
@divine-comedian Should we adjust the sort to 'best match' when a user performs a search? For example, if a user has sorted by 'newest' but enters a new search term, should we automatically switch the sort to 'best match' or keep it as is? |
yes |
https://staging.giveth.io/projects/all?searchTerm=how&sort=BestMatch
All Acs have been passed |
Based on feedback from users and stakeholders we should further improve how we handle our search results returned on the app.
When a user currently searches for a project on Giveth we take the keywords and look for the closest match. We then sort those results based on the GIVpower of the projects returned. This means the project that might have matched closest to the search query is not returned at the top, and in some cases it is found several pages down, leading users to think the search is broken!
When a user is searching for a project by default we should not apply any sorting to the results, if the user wishes they can apply a sort to it after the initial results have been returned.
@aminlatifi tagging you on this since you have the latest experience in tuning our search queries. Let me know when you can pick this up after your immediate priorities on QACC have settled.
AC
The text was updated successfully, but these errors were encountered: