As I understand it, this bug is for when AllowHoldPolicyOverride setting silently overrides holds that should be blocked by the Default Holds Policies by Item Type table. This is huge problem for us. It will require hundreds more circ rules for our 59 libraries to make up for the Default Holds Policies table not being respected. If the interface would tell the staff person that only an override can allow the hold and gives them the button to do so that would be an acceptable compromise.

Hi Chanel, it's a general override. The circ rules won't block a hold either if its explicitly overriden, neither does the max holds settings etc. If you don't want this to be possible best would be to keep the preference off.

Hi Katrin, libraries often get permission from other libraries to override the blocked hold and in those cases it's ok so we need the override system setting. That said, the system shouldn't automatically be ignoring the Default Holds table.

I think at the moment it's just not a very "differentiated" override. It's a "override all possible limitations". If you want to differentiate different cases, this would definitely need development.