"ITEM_ON_HOLDS_SHELF" event message not specific enough for all use cases

Bug #1077947 reported by Chris Sharp
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Wishlist
Unassigned

Bug Description

The current ITEM_ON_HOLDS_SHELF message wording is "This requested item is currently on the holds shelf", which is intended to prevent hold shelf items from accidentally being checked out. I'm told by one of our library directors that a common use case involves staff pulling an item on hold for *another* patron with a similar/same name and attempting to check the item out to the wrong patron. Staff see the current wording and assume that the system is unnecessarily telling them that the item is on the holds shelf for the patron to whom they are attempting checkout and will override it without realizing that the item is being checked out to the wrong patron. I suggest the following wording change:

"This item is currently on the holds shelf for another patron."

That would be minimal. Ideally, the message would also include the patron for whom the item is intended as well, in which case the wording:

"This item is currently on the holds shelf for Jane Doe (2201100000001)"

would be completely unambiguous.

Evergreen 2.1.1
OpenSRF 2.0.1
PostgreSQL 9.1
Debian squeeze

Revision history for this message
Chris Sharp (chrissharp123) wrote :
Revision history for this message
Ben Shum (bshum) wrote :

I think I like the second option for its specificity. But I can see how the first would be a good place to start too.

Marking as a potential feature for 2.4.

Changed in evergreen:
milestone: none → 2.4.0-alpha
importance: Undecided → Wishlist
status: New → Triaged
Ben Shum (bshum)
Changed in evergreen:
milestone: 2.4.0-alpha1 → 2.4.0-beta
Ben Shum (bshum)
Changed in evergreen:
milestone: 2.4.0-beta → 2.4.0-rc
Ben Shum (bshum)
Changed in evergreen:
milestone: 2.4.0-rc → 2.5.0-alpha
Dan Wells (dbw2)
Changed in evergreen:
milestone: 2.5.0-m1 → none
tags: added: pullrequest
Galen Charlton (gmc)
Changed in evergreen:
status: Triaged → Confirmed
milestone: none → 2.next
Dawn Dale (ddale)
Changed in evergreen:
assignee: nobody → Dawn Dale (ddale)
Revision history for this message
Dawn Dale (ddale) wrote :

"I have tested this code and consent to signing off on it with my name, Dawn Dale and email address, <email address hidden>

Changed in evergreen:
assignee: Dawn Dale (ddale) → nobody
tags: added: signedoff
removed: pullrequest
tags: added: pullrequest
Revision history for this message
Kathy Lussier (klussier) wrote :

Hi Chris,

This looks good, but can you add your signoff the commit? It probably could use a very small release notes entry, but I can add that when I merge the code.

Thanks!
Kathy

Kathy Lussier (klussier)
Changed in evergreen:
milestone: 2.next → 2.12-beta
Revision history for this message
Chris Sharp (chrissharp123) wrote :
Revision history for this message
Kathy Lussier (klussier) wrote :

Thanks Chris! Merging to master for inclusion in 2.12.

Changed in evergreen:
status: Confirmed → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
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.