Precat owning library should not be editable

Bug #1849334 reported by Elaine Hardy
84
This bug affects 16 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Medium
Unassigned

Bug Description

In the XUL client, the owning library for the precat record(s) was not editable by library staff. In the web client, the owning library can be edited by library cataloging staff within item status. This creates a number of issues with the individual item records including transit, checkin, and processing problems.

The owning library (which in PINES case is the consortium (PINES) should not be editable by library staff.

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Chris Sharp (chrissharp123) wrote :
tags: added: pullrequest
Revision history for this message
Ruth Frasur Davis (redavis) wrote :

I've tested this and consent to signing off on it with my name, Ruth Frasur (rfrasur) and email (<email address hidden>).

tags: added: signedoff
Changed in evergreen:
milestone: none → 3.5-alpha
Michele Morgan (mmorgan)
Changed in evergreen:
milestone: 3.5-beta → 3.5.0
Changed in evergreen:
milestone: 3.5.0 → 3.5.1
Changed in evergreen:
milestone: 3.5.1 → 3.5.2
Revision history for this message
Jane Sandberg (sandbergja) wrote :

Thanks for the branch, Chris! It does work in preventing staff from editing the precat owning library. However, there is a confusing feature in the UI: when staff attempt to modify the precat details in Item Status, they get the "Item(s) successfully modified toast", even though the items were not modified.

I wonder if the Perl code could throw an event if a staff member tries to edit an item with a call number with ID < 1, and then we could teach the AngularJS holdings editor to respect that event before sending the Broadcast channel (or it could send a failure notice along through the broadcast channel?). But that could also be split apart into its own separate bug.

Changed in evergreen:
milestone: 3.5.2 → 3.6.1
Changed in evergreen:
importance: Undecided → Medium
Changed in evergreen:
milestone: 3.6.1 → 3.6.2
Changed in evergreen:
milestone: 3.6.2 → 3.6.3
Changed in evergreen:
milestone: 3.6.3 → 3.6.4
Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

Confirmed this is still an issue in 3.7

Changed in evergreen:
milestone: 3.6.4 → 3.7.2
Revision history for this message
Bill Erickson (berick) wrote :

+1 to having the API enforce the policy. Removing pullrequest pending consensus.

tags: removed: pullrequest signedoff
Revision history for this message
Elaine Hardy (ehardy) wrote :

I am going to file another bug report as soon as I know more but it is also possible to merge the precat record with another bib record. One of our cataloger just did it. Chris was able to restore it.

Revision history for this message
Elaine Hardy (ehardy) wrote :

Well, that's embarrassing. Not only is there a bug for the merging precats, I tested and signed off on it. https://bugs.launchpad.net/evergreen/+bug/827356.

tags: added: precats
no longer affects: evergreen/3.4
no longer affects: evergreen/3.5
Changed in evergreen:
milestone: 3.7.2 → none
milestone: none → 3.7.3
no longer affects: evergreen/3.6
Changed in evergreen:
milestone: 3.7.3 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.