Fast item add / volume copy creation can leave behind empty volume

Bug #1152387 reported by Mark Cooper
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Undecided
Unassigned

Bug Description

Evergreen 2.3.2 -> Master.

This does not happen with the unified volume/copy creator. But if not using the unified interface:

Create a volume/copy via fast item add (volume owner defaults to workstation OU), or via holdings maintenance (volume owner will be the selected OU) -- in the latter case use 'Edit then create'.

In the item editor change the owning/circ library (i.e. effectively switching out the library from under the volume).

Save the copy and see that the original volume owning library has an empty volume, while the 'new' library has the volume + copy as it should.

Delete volume with last copy is enabled so that setting does not prevent this behavior.

This is mostly a problem for fast item add when using the non-unified interface, because with a systemwide cataloging dept. staff often are creating copies for other branches -- not just the workstation OU. It feels as if it should be possible to change the owner/circ lib directly without having to save (accept workstation location as default) and then go back to edit -- although that does work correctly (i.e. changing/updating owner after the copy has been created does not leave behind empty volume).

Similarly creating the volume (fast item add or via holdings maintenance) then canceling the item creation leaves an empty volume behind, regardless of the Delete volume setting.

Ben Shum (bshum)
Changed in evergreen:
status: New → Triaged
Revision history for this message
Tina Ji (tji) wrote :

"Similarly creating the volume (fast item add or via holdings maintenance) then canceling the item creation leaves an empty volume behind, regardless of the Delete volume setting."

I can see creating a volume without a copy is sometimes necessary. One case is that branch A has 2 copies under one volume, while branch B has no copy at all. If you wish to transfer a copy from branch A to B, you will need to create a volume under B without a copy first.

Tina
BC Libraries Co-op

Revision history for this message
Andrea Neiman (aneiman) wrote :

Refers to XUL client

Changed in evergreen:
status: Triaged → Won't Fix
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.