Users without UPDATE_VOLUME perm can orphan copies in the copy/volume editor
Bug #1580242 reported by
Chris Sharp
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Found in PINES. Staff with the UPDATE_COPY permission but not the UPDATE_VOLUME permission attempting to use the unified copy/volume editor to edit a call number receive two click through error messages. The first is a PERM_FAILURE for UPDATE_VOLUME. The other is : error in stash and close, acn_id = -1
Rather than the expected behavior when the error messages are acknowledged where the call number is not edited, the copy is disassociated with the bib record and a pre-cat like record is created with TCN -1 and no title.
See the attached screenshot for an example.
Evergreen 2.9.1
OpenSRF 2.4.1
PostgreSQL 9.4
Ubuntu 14.04 LTS
Changed in evergreen: | |
status: | Confirmed → Won't Fix |
To post a comment you must log in.
Adding a link to a possibly related bug:
https:/ /bugs.launchpad .net/evergreen/ +bug/1253732
which is in turn related to:
https:/ /bugs.launchpad .net/evergreen/ +bug/1040686
Perhaps a simple solution to some of the issues related to the unified editor always creating a new volume record would be to add a check that the new volume actually exists prior to trying to transfer the item to it.
Also worth noting here is that 1040686 is fixed in webby, so this issue may be as well.