Summary: | group item types together | ||
---|---|---|---|
Product: | Koha | Reporter: | Nicole C. Engard <nengard> |
Component: | Cataloging | Assignee: | Galen Charlton <gmcharlt> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | helen.linda, m.de.rooy |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Nicole C. Engard
2012-06-27 19:44:15 UTC
I am not sure adding another level of complexity to the circulation rules would work out very well - we already have to fix lots of stuff in there :) I think maybe the itemtypes could be used differently? If you make the "itemtype" what determines your circulation rule, in your example "Audiovisual" and maybe use the collection code to differentiate between different types of audiovisuals? |