Remove Branch Requirement from Patron Bulk Change
Allow bulk change to all fields in the bulk change workform when the record set contains patrons from more than one registered branch. Currently, the system requires that a single registration branch must be applied to the patron records before changing the patron code and/or the library assigned blocks. These values are set at the branch level; however, most libraries use consistent patron codes and blocks across branches.
This was previously submitted in the old enhancement process:
"Bulk changing a patron code requires the selection of a registered branch. We request that this requirement be suppressed if all branches can use all patron codes"
Idea Value
It is common at multi-branch libraries to update sets of patron records from more than one branch. The current requirement makes this a lengthy process in which multiple record sets have to be created based on patron branch.
Most of the time, the same patron codes and blocks are used at all branches of a library. When this is not the case, the update could just fail for that record and show as an error in the report. This is already the process when the staff member does not have permission to change patrons from a particular branch.
This would save staff time and allow for timely updates to patron records.
-
AdminWes Osborn (Admin, Innovative) commented
If this can't be implemented, the Leap patron bulk change process should make it clearer that you must change the patron's registered branch. Right now that is pretty unclear, whereas in the client it would give you a more specific error message.