-
Notifications
You must be signed in to change notification settings - Fork 0
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
Design user experience for search term updates vs. new search #264
Comments
@hackartisan I don't think this use case requires more discussion as you've articulated it. However, the details around how different facets are visualized, designed for interaction, and the parameters that are allowed will require more discussion. We started talking about which facets can have multiple values (i.e., Subjects: "Arts and Culture" AND "Motion Pictures") and which cannot, such as Date ranges. We will need to spend some time on each facet to determine what the behavior will look like and the affordances we can provide for exploration, but those would be in separate tickets. I believe the facet values should change as the user is exploring to provide immediate feedback in the form of search results (as opposed to selecting values and then click "Apply"). This exploration path could also leave breadcrumbs/markers that the explorer can use to retrace their steps (aka, "rewind to"), or provide a way to start over from a blank search or one of the "trailheads" that we may provide as starting points (i.e., "Public Domain"). |
Initial thoughts for main search results page. In this drawing, any changes to the search box would update the search parameter but leave all the others as-is. Changing any parameter would bring the user to page 1 of the new results, regardless of what page they were on. |
@hackartisan this looks good! Q: What happens when you clear the sort option from the current filters? Does it sort by Relevance? Or from Year Newest to Oldest? It's not clear to me what the "off" state is. And I am not sure I would include sort options in the filters list -- the sort dropdown should be persistent on the search results screen to indicate sort state, so I think having it appear in the list would be redundant and potentially confusing unless you foresee the sort dropdown to be hidden at some point. I think it works for the other facets because there may be several different blocks containing interactive facet UIs that will not be persistent because we can only reasonably display one at a time. I kind of feel the same about keywords. What if there are multiple keywords? Do they show up in several filter "buttons" or are they all included in one? If the search bar is persistent, then users can directly change the keyword state in the search input field. Finally, I would also use the word search "filters" over "parameters". But these are relatively minor points. I think this mockup will be really helpful and is close to done. |
If sort isn't included in "clear everything" then if I want to do a new search with the default relevance sorting do I have to click "clear everything" then submit a new search then change the sort? |
To answer your question, relevance is the default. I'm hearing you suggest we need to indicate that? |
Next steps are new wireframes given the discussion at https://docs.google.com/document/d/1hHq82XqYs29iSFnJMTvPKoIBMgk6YQM-95w_vTRvGrM/edit?tab=t.0#heading=h.2qctk0gtsjx |
We've decided to prioritize the first use case, and keep the current behavior wherein submitting a search clears the filters that have been applied |
Summary or User Story
There are two related user stories that we should accommodate in our UI:
We need a UX that accommodates both with clarity and ease of use.
Acceptance Criteria
First step
Make some drawings
The text was updated successfully, but these errors were encountered: