Usability: hold confirmation in staff client is below fold

Bug #1970452 reported by Benjamin Kalish
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Undecided
Unassigned

Bug Description

In the staff client in 3.7.2 when placing a hold the confirmation of success or failure appears in a the holds records table at the very bottom of the screen in the Holds Status column. Unless library staff sets the zoom level in the browser to a very low number or is on a machine with a very large screen this confirmation cannot be seen without scrolling.

To improve usability the confirmation should appear where the user can see it.

I can see two possible approaches:

1. Show the confirmation near the place hold button itself, so that no scrolling is necessary. (Simple and obvious for a single hold, but it's less clear what should happen with multiple holds.)
2. Automatically scroll to the holds record table when the confirmation is shown. (Handles multiple holds well, but we would need to be careful not to create new usability or accessibility issues.)

Perhaps the best approach would somehow combine the two?

Revision history for this message
Michele Morgan (mmorgan) wrote :

I've noticed this as a usability issue as well. Another possible approach could be to add an additional toast to the page indicating success or failure in addition to what already appears in the holds records table.

Marking Confirmed.

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Benjamin Kalish (bkalish) wrote :

I like that! Keep the existing behavior but also add something near the hold button that would give an appropriate confirmation, including the possibility of something like "some holds failed–scroll for details".

tags: added: design
Revision history for this message
Benjamin Kalish (bkalish) wrote :

This is also a problem when placing holds with parts. The menu to select the part appears in the list of holdings where it won't be seen by most users.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.