Bring Acquisitions behavior in line with FOLIO defaults
Problem
Due to a variety of reasons, including acquisitions-specific requirements and early limitations in Stripes, some areas of acquisitions behave differently from established general FOLIO behavior. These inconsistencies can lead to varying behavior from user to user, potentially complicating data sharing and troubleshooting.
“Durable” filters
In most FOLIO apps, when a user logs out, selected filters are cleared and must be reset with every new session. When copying URLs for certain faceted searches, this approach ensures consistency from user to user.
In Acquisitions apps, filters carry forward from session to session, so that when a URL is copied and pasted, the user’s saved filters are applied to that URL, resulting in inconsistent results. The workaround for this issue is to include a command to clear filters in the URL.
Desired outcome
All apps within FOLIO should behave consistently, drawing upon Stripes components and avoiding app-specific components as much as possible
Users should have some mechanism to allow filters to be applied by default without having to reset them from session to session
Shared URLs should result in consistent outcomes
Approach
Preliminary feedback suggests that this is best handled via personalized settings.
It should be implemented in a way that avoids lots of individual, detailed settings.
There needs to be more clarification between “remembering the last filters used” and “use default filters.”
Default filters seem to be heavily favored over “memory”
“Memory” can be important within a given session (i.e. when moving among multiple records in multiple apps to accomplish a given task) BUT it should also be temporary.
SIGs will provide additional feedback and identify use cases
If a URL is shared that contains predefined filters, it should ideally not create “filter memory” that could potentially disrupt another user’s work.
More clarity into what filters are currently selected would be desirable.