Placing holds fails unintuitively when preferred pickup location is disabled via org unit setting opac.holds.org_unit_not_pickup_lib
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
High
|
Unassigned |
Bug Description
If a user has set a preferred pickup location, and that pickup location is disabled via the org unit setting opac.holds.
If the user opens the pickup location dropdown, their preferred pickup location is greyed out and cannot be chosen.
Here's a screencast:
http://
An error message stating that the patron's preferred pickup location is currently unavailable with instructions to choose another would eliminate confusion in this situation, and also avoid system behavior that appears broken.
Changed in evergreen: | |
importance: | Undecided → High |
tags: | added: holds opac |
tags: |
added: circ-holds removed: holds |
Just adding a note that the same behavior occurs for org units that do not have the "can have users" flag enabled. If we provide a message for the situation that Michele described, we should see the same message for those org units that can't have users. I'm not sure how often my scenario would happen in practice, other than for the admin user, but I thought I would just throw it out there as another spot where we could use this message.