[Bug 10385] New: item-level_itype checks need to be refactored
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10385 Bug ID: 10385 Summary: item-level_itype checks need to be refactored Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt@gmail.com Reporter: gmcharlt@gmail.com Checks on the item-level_itypes system preference are scattered throughout the code, and there have been a large number of bugs concerning cases where such a check is missing. I propose checks of this system preference be moved as far down the stack as possible. Specifically, all routines that fetch items from the database should check the syspref to determine the correct item type column and return it via (say) an "item_type" key in the response, to distinguish it from 'itemtype' and 'itype'. The only code that would see 'itype' or 'itemtype' would be code directly related to modifying items. Further, the syspref would be checked in as few places as possible. I further propose pinning down the semantics of the item-level_itypes as follows: - when ON, the item type is *always* taken from items.itype for all display and circulation purposes - when OFF, the item type is *always* taken from biblioitems.itemtype In particular, the current behavior of GetItem (fetch the itype from the item if it's not blank, otherwise fall back to the biblioitem itemtype), would be modified. Related bugs include: - Bug 7491 - Bug 7492 -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10385 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- 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. -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10385 --- Comment #2 from Galen Charlton <gmcharlt@gmail.com> --- 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. -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10385 mathieu saby <mathieu.saby@univ-rennes2.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mathieu.saby@univ-rennes2.f | |r -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10385 Nicole C. Engard <nengard@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nengard@gmail.com -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org