[Bug 23460] New: Be able to specify a default item type, to allow Koha to do things to items that don't have itypes?
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23460 Bug ID: 23460 Summary: Be able to specify a default item type, to allow Koha to do things to items that don't have itypes? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs@lists.koha-community.org Reporter: wizzyrea@gmail.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com We see a lot of item-level_itypes set but no itemtype set for item (225088) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 740. in the logs for various jobs that run. UI Koha doesn't much bother about these kinds of errors, they just junk up the logs but Koha keeps going. Cron Koha is super noisy though, with errors like this. It occurred to me that it might be nice to have a "default" item type, just so we can assume that everything's got an item type and stop seeing these infernal messages. Maybe the one you set up in the onboarder should become the default, and allow people to pick the one they want to have as default from the UI later if they want? We'd only need it so that Koha knows what rules to apply to the item (among many other things that we depend upon itypes for). What do you all think? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23460 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> --- What we do is make the item type mandatory in the frameworks. That way you can't catalog an item without an item type, but you have to consciously pick. With a default that is applied automatically it would be really hard to find cataloguing mistakes. Also, Koha already uses the item type from the framework 942$c as a default 'suggestion' when you catalog a new item and you can add a default in the framework to enforce a default. I am not sure we need an additional setting? Maybe it would be good to change the default frameworks to make item type a mandatory field? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23460 --- Comment #2 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hm, I might have misunderstood (forcing an itemtype in the item vs having a fallback Koha just uses when itemtype empty). But a bit afraid it would require changing a lot of code to make that happen... favoring fixing the data a bit right now. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23460 --- Comment #3 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Katrin Fischer from comment #2)
Hm, I might have misunderstood (forcing an itemtype in the item vs having a fallback Koha just uses when itemtype empty). But a bit afraid it would require changing a lot of code to make that happen... favoring fixing the data a bit right now.
We have made the itemtype mandatory all over Koha since. There is also a bug that breaks the display in the OPAC for records with items missing itemtypes. I wonder if this is still needed? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23460 Liz Rea <wizzyrea@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX CC| |wizzyrea@gmail.com --- Comment #4 from Liz Rea <wizzyrea@gmail.com> --- This does seem better lately due to fixes in other areas. I think we can put this one to bed. Liz -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org