Colleagues,
We are making some progress as we wrestle through circulation policy
configurations. Here's the latest issue. We would like to configure more
of our polices at the System org unit level, since our branches have
essentially the same checkout parameters, but for us there is a
If we use the branch level code (ATS-KY for example) as the owning library the
circulating library is the same as the owning library, but it increases the
complexity of the circulation policies.
Don, you can define the policies in terms of systems and it'll work
just fine when the data is
Well, a few thoughts.
Jason is right. You can use your branch level (ATS-KY) in the record and
still set ATS in the policy. That's the most elegant solution. It also
has a long term benefit. This works because of weighting and it allows you
in the future if you need to, to create policies for
