Ou setting cat.require_call_number_labels = FALSE does not work with multiple items

Bug #2052742 reported by Michele Morgan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
New
Undecided
Unassigned
3.11
New
Undecided
Unassigned

Bug Description

With cat.require_call_number_labels set to FALSE, a user can save items with blank call number labels if there is a prefix set.

When editing multiple items with call number prefixes and blank labels, the user cannot save the items. The Save buttons remain disabled.

Revision history for this message
Beth Willis (willis-a) wrote :

We have noticed the same issue when editing *individual* items if these steps are followed in the angular holdings editor:

--Delete the existing call number
--Scan/enter a new barcode
--Apply a holdings template that includes a call number prefix

--Note that the "Apply/Save" buttons are inactive.

In order to save holdings in this scenario, it is necessary to edit the barcode or to enter (and immediately delete) a value in the call number field. These extra steps are inefficient and prone to error.

If the order of actions is changed to either of the following, the "Apply/Save" buttons are active:

--Apply a holdings template that includes a call number prefix
--Delete the existing call number
--Scan/enter a new barcode

OR

--Scan/enter a new barcode
--Apply a holdings template that includes a call number prefix
--Delete the existing call number

But, for some of our libraries, these are the most logical nor preferred order of actions.

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

Thanks to Jane Sandberg, here is a working branch that assures the ou setting is resolved before it's consulted:

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/mmorgan/lp2052742-race-condition-in-save-check

user/mmorgan/lp2052742-race-condition-in-save-check

We have tested this locally and it fixes the issue for us.

Changed in evergreen:
milestone: none → 3.12.3
tags: added: pullrequest
Changed in evergreen:
milestone: 3.12.3 → 3.12.4
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.