User Preferences (UXPROD-1399)

[UXPROD-2414] Customizable search preferences Created: 28/Apr/20  Updated: 10/Dec/21

Status: Blocked
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: User Preferences

Type: New Feature Priority: P4
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Unresolved Votes: 0
Labels: acquisitions, needs-ranking, needs-rmsigreview, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Gantt End to Start
has to be done after UXPROD-1398 User Preferences Open
Epic Link: User Preferences
Development Team: Thunderjet
PO Rank: 12.3
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R3
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

Problem: Search and filter contains a lot of detail in many different applications. Users will tend to use applications differently and having global or app settings for search preferences mean that many users are constantly adjusting filters.

Use cases:

  • Librarian is creating orders and receiving against those orders. When looking at orders they will want to focus on orders that are assigned to them and ready to receive.
  • Librarian is creating invoices and managing orders. This user will want to focus on invoices they have created that are open or paid so they can ask for approvals and close orders.
  • Librarian that is approving invoices will want to focus on orders that have been reviewed

Requirements:

  • User can select the default search filter configuration for a given search area
  • User search preferences are saved and reloaded when they return to the search area
  • User can a update search preferences

Questions:
Could this be implemented in a Stripes component? User preferences will need to be save to an account meaning UXPROD-1398 Open will need to be finished before this can be implemented. One suggestion would be to build this as an add-on for the search component.
Is a search history of for example 10 entries per search box that is presented as a drop-down menu the user can pick from sufficient?

Approach:
Allow users to set search preferences for each search area in folio and save them to their user account.


Generated at Fri Feb 09 00:23:46 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.