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.
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.