Circulation limit sets seem to require circ mod or location or limit group

[Blake GH]

EG 3.1

Looking at this excerpt from action.item_user_circ_test

SELECT INTO items_out COUNT(DISTINCT circ.id)
                  FROM action.circulation circ
                    JOIN asset.copy copy ON (copy.id = circ.target_copy)
                    LEFT JOIN action.circulation_limit_group_map aclgm ON (circ.id = aclgm.circ)
                  WHERE circ.usr = match_user
                    AND circ.circ_lib IN (SELECT * FROM unnest(context_org_list))
                    AND circ.checkin_time IS NULL
                    AND (circ.stop_fines IN ('MAXFINES','LONGOVERDUE') OR circ.stop_fines IS NULL)
                    AND (copy.circ_modifier IN (SELECT circ_mod FROM config.circ_limit_set_circ_mod_map WHERE limit_set = circ_limit_set.id)
                        OR copy.location IN (SELECT copy_loc FROM config.circ_limit_set_copy_loc_map WHERE limit_set = circ_limit_set.id)
                        OR aclgm.limit_group IN (SELECT limit_group FROM config.circ_limit_set_group_map WHERE limit_set = circ_limit_set.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.