Wishlist: Hold Pull List Potential Copy Count Should Be Reflective of Target Copy Library's Copy Count

Bug #2035900 reported by Elizabeth Davis
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
New
Wishlist
Unassigned

Bug Description

Currently in 3.9 and 3.11, the count of potential copies on the Hold Pull List is reflective of the copy count for the bib the hold is on. It's also based on if a library has hard boundaries. For example, if there are no hard boundaries and the potential copy count will be based on the consortium copy count. If they have hard boundaries, potential copy count it will be based the boundary org depth.

The SPARK consortium does not resource share consortium wide but we do have various smaller resource sharing libraries that would find it helpful to see the number of potential copies to be the number of copies at the currently targeted copy's circulating library or even system. For example, if the targeted copy on the pull list is at a library that has 5 copies on that bib, they would know they could keep looking for another copy to fill that hold. If the pull list says there's 1 potential copy that they can't find, then they know to retarget/find another copy.

Galen Charlton (gmc)
Changed in evergreen:
importance: Undecided → Wishlist
Revision history for this message
Brandt Ensor (baensor) wrote :

Yes, as a new to resource sharing system, it would be very helpful to only see the number of copies we have in our system instead of bib wide. Our staff have been trained the old way when we had hard boundaries and it has been a big change for them to see so many copies and they have had so many questions.

Brandt, Adams County Library System

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

I can see how this would be useful, but I would not want to lose the consortium-wide potential copies count.

I would favor adding an additional column with the target library potentials count.

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.