Summary: | item-level_itypes checks need to be refactored | ||
---|---|---|---|
Product: | Koha | Reporter: | Galen Charlton <gmcharlt> |
Component: | Architecture, internals, and plumbing | Assignee: | Galen Charlton <gmcharlt> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | katrin.fischer, m.de.rooy, mathsabypro |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
Description
Galen Charlton
2013-05-31 17:19:05 UTC
I think there has been some work to make use of the biblio level itemtype for display in the result lists even when item level itemtypes are being used. So I am not sure it will work for everyone to only use the itype from the level set in the system preference. Maybe we could return 3 values? Both itemtypes for biblio and item level and the one to be used for circulation logic? As our libraries participate in a union catalog where the records are imported/updated automatically into Koha, we don't set bilbio level itemtypes at all. In light of that... how about no syspref at all? What I mean is that we make *both* biblio- and item-level item types visible. For the sake of clarity, I'll call the biblo-level ones "material types". For circulation rules, *both* the item type and the material type could be taken into account by adding a material type column to issuingrules (and on upgrade, populating it based on the value of the syspref). For OPAC display, allow icons to be associated with both material types and item types. I would love to change this title to : item-level_itype checks need to be removed |