This issue just came up in a local discussion on aging circs. Although it is indeed a patron privacy issue, I'm thinking it's one that could be made a public security bug.
As a resolution, could we update the accepting_usr field to null when the aged circulation script is run?
This issue just came up in a local discussion on aging circs. Although it is indeed a patron privacy issue, I'm thinking it's one that could be made a public security bug.
As a resolution, could we update the accepting_usr field to null when the aged circulation script is run?