Pushing this code patch to production solved the issue we were experiencing when attempting to sort large numbers of holds on catalog records - sorting alphabetically by patron name to determine as closely as possible specific patron's position in the queue
Pushing this code patch to production solved the issue we were experiencing when attempting to sort large numbers of holds on catalog records - sorting alphabetically by patron name to determine as closely as possible specific patron's position in the queue