Circulation limit sets seem to require circ mod or location or limit group
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Undecided
|
Unassigned |
Bug Description
EG 3.1
Looking at this excerpt from action.
SELECT INTO items_out COUNT(DISTINCT circ.id)
It appears that one of those three things needs to be present in the limit set definition. But if none of them are specified, the count of matching circulations returns 0. Some libraries need ALL circulations to debit the max out limit. The example I am working from is a circulation policy for juvenile=true.
It could be considered a bug that the UI doesn't enforce one of those three things to be specified. But I am proposing that we allow none to be specified and if none are, then Evergreen will assume all circulations.
tags: | added: admin-pages |
tags: | added: circulation |