On Fri, Jan 15, 2016 at 10:06 PM, Agnes Rivers-Moore wrote:
> If there were two codes in the item - one designed for setting rules,
> and one for statistics, the issuing rules table could be less detailed.
That's how we use collection codes, for what it's worth. Our
collection
Comments -
I am glad someone is taking this on. It has been growing more cumbersome and
needs help.
Radical suggestion - perhaps we are asking too much of a single 'item type'
code and 'borrower category' code.
The system currently uses these codes for both setting rules and for
statistical
The backend and frontend of the circulation/policy rules in Koha have been
extended and stretched to the point where they cause a fair amount of
issues and frustration. Many librarians and developers are uncertain when
default rules are applied, and the very large number of possible settings
makes
3 matches
Mail list logo