Noting that pickup location updates initiated by a change of preferred pickup location would need to go through the same logic (i.e., open-ils.circ.hold.update.batch) as editing an individual hold's pickup location in the OPAC. That's need to properly handle things like rerouting transits or (depending on settings) preventing the change if the item is on the holds shelf.
As a UX consequence, that means that the OPAC would need to be able to explain if it cannot honor a request to change the pickup location of a given hold.
Noting that pickup location updates initiated by a change of preferred pickup location would need to go through the same logic (i.e., open-ils. circ.hold. update. batch) as editing an individual hold's pickup location in the OPAC. That's need to properly handle things like rerouting transits or (depending on settings) preventing the change if the item is on the holds shelf.
As a UX consequence, that means that the OPAC would need to be able to explain if it cannot honor a request to change the pickup location of a given hold.