mlibrary/search

Allow filters to have a state before searching.

Closed this issue · 5 comments

jonearley commented

Currently any filter change conducts a filtered search. Perhaps it would be best to make filter selections and then apply. Or have a case where some filters set off a search and some need to maintain a state and are then used once a search query or other triggered filter is used.

Example of potential non-immediate searching filters:

  • Checkboxes
  • Institution dropdown

Example of searching filters:

  • Format
  • Language
varnum commented

The latter — “some filters set off a search and some need to maintain a state” — makes more sense to me from an expected behavior viewpoint.

bnhowell commented
jonearley commented

@varnum I agree.

@bnhowell I don't have any data on this. This issue comes from me working to implement the sticky institution filter. When a user changes the default institution from the Catalog landing page it will immediately run a search. I expect this might be odd for some, but it's just how we've setup filters for now. In early beta days all filters were treated the same.

Implementing this would require a rewrite of filters and take at least a few weeks of work.

varnum commented

I agree with @jonearley that the institution filter action feels different from (say) a format, author, date filter. Not a blocker for the public beta, but it's worth thinking about for the longer term.

bertrama commented

Moved to SEARCH-76, SEARCH-77.