Provide a quick option for staff to place another hold on the same title

Bug #1423922 reported by Kathy Lussier
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Wishlist
Unassigned

Bug Description

This idea came up at one of our holds meetings earlier this week as an easy workflow improvement for staff who are placing holds on behalf of patrons. Quite often when a new title from a bestselling author is added to the catalog, staff need to place holds for multiple patrons who have a standing request for titles from this author. By adding a "place another hold on the same title" link to the holds success screen, we can save some clicks for staff. The link may also be useful when placing holds for book clubs. This link will only appear when logged into the client.

Working branch is forthcoming

Tags: pullrequest
Revision history for this message
Kathy Lussier (klussier) wrote :
tags: added: pullrequest
Revision history for this message
Mike Rylander (mrylander) wrote :

Kathy, this looks neat. Question: would we want to propagate the hold type and target from the original hold, rather than forcing type=T and the full bib? Of course, I'm not sure how much more work that would actually take, or if there's enough info available in that success interface to do that.

Revision history for this message
Kathy Lussier (klussier) wrote :

Yes, I think that's a good idea, and it looks perfectly doable. I'll poke at it.

Revision history for this message
Kathy Lussier (klussier) wrote :

Removing pullrequest while I try to figure out why some parameters aren't being maintained with the mkurl I'm using.

tags: removed: pullrequest
Revision history for this message
Kathy Lussier (klussier) wrote :

Slapping the pullrequest back on now that I've figured out why my parameters weren't propagating. I force pushed the changes to my working branch. I don't know if there will be many situations where staff use this link for copy- or volume-level holds, but I also adjusted the labeling to provide an accurate description of what's happening in each case.

tags: added: pullrequest
Revision history for this message
Ben Shum (bshum) wrote :

Pushed to master for 2.8 beta.

Changed in evergreen:
status: New → 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.