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

make Ambiguous/Unmatched results clearer to user if no unique results returned #514

Open
katiestahl opened this issue Jul 30, 2024 · 1 comment
Labels
frontend good first issue Good for newcomers priority:low Low priority

Comments

@katiestahl
Copy link
Contributor

If a user searches terms and there are no unique search results, they are met with this page:
Screenshot 2024-07-30 at 10 07 36 AM

This may cause a user to think that there were no search results at all. If there are ambiguous or unmatched results, we should either

  1. automatically make that the selected tab
  2. add a CTA to the "None of your search terms returned unique matches." that lets the user know that there are ambiguous/unmatched results. ex: "None of your search terms returned unique matches. Click here to see ambiguous/unmatched results."

Option 1 pros:

  • fewer clicks for the user
  • eliminates possibility that they think there are no results at all
    Option 1 cons/considerations:
  • might be confusing/not clear to the user that there were no regular search results returned (if this is the case, we may want to consider adding a notification on the ambiguous/unmatched results page)

Option 2 pros:

  • makes it clear that there are still search results, just not unique search results
    Option 2 cons:
  • still requires the user to take some additional action to view the search results

other considerations:

  • don't display ambiguous/unmatched tab if no ambiguous or unmatched terms?
  • display some sort of number or icon in the ambiguous/unmatched tab text to communicate to the user that there are results on that tab
@katiestahl katiestahl added good first issue Good for newcomers frontend priority:low Low priority labels Jul 30, 2024
@mcannon068nw
Copy link
Contributor

Per meeting, we definitely agree that there is room for more visual indicators here. One idea that was mentioned was (like your last bullet point) some sort of numbered display on the tabs to indicate the presences of results. We should look into this more and work with Josh to figure out good approaches

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
frontend good first issue Good for newcomers priority:low Low priority
Projects
None yet
Development

No branches or pull requests

2 participants