[Bug 11043] New: rename biblioitems.itemtype
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11043 Bug ID: 11043 Summary: rename biblioitems.itemtype Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: gmcharlt@gmail.com Reporter: mathieu.saby@univ-rennes2.fr QA Contact: testopia@bugs.koha-community.org I find biblioitems.itemtype confusing. In discussions about itemtypes, I often had to ask which kind of itemtype it was about : "biblioitems.itemtype" or "items.itype". It is an other issue, but zebra conf is confusing too, as in MARC21 the fields mapped with "biblioitems.itemtype" and "items.itype" are mapped with the same zebra index, whereas in UNIMARC 2 different indexes are used (biblioitems.itemtype = 099t = ccode index ; items.itype = 995r = itype index) I think it is not normal, and should be fixed in an other bug. biblioitems.itemtype is not about item, but about document, so what I would propose here is to rename biblioitems.itemtype to biblioitems.doctype or maybe biblioitems.kohadoctype (as document type can also be retreived from MARC fields non specific to Koha, like 210$b in UNIMARC) Any opinions? -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11043 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 not every library is treating the biblio level itemtype as a document type currently, so there might be different ideas and workflows involved here. What I always thought was that item-level itypes was being used as a different way to define circulation rules. Our libraries don't use the biblio level itype at all, apart from it being set to a default value, as the itemtype being picked in the item form will then preset to this. -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11043 --- Comment #2 from mathieu saby <mathieu.saby@univ-rennes2.fr> --- There may be different way of using those fields, but in some templates, biblioitems.itemtype is translated as "document type". In reports maybe. I suspect the name biblioitems.itemtype dates back to the old days of pre-marc Koha, when you could have 1 biblio for x biblioitems. This is no longer the case, so in a bibliographic point of view, biblioitems table is used to describe documents (FRBR Manifestation), never items. So documenttype may be more accurate. Mathieu -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11043 --- Comment #3 from mathieu saby <mathieu.saby@univ-rennes2.fr> --- In my library, in biblioitems.itemtype we put 'book', 'cd' etc and in items.itype 'long loan', 'normal loan' And we use items.itype for circulation rules. Mathieu -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11043 --- Comment #4 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I think you can only do that, when you change the mapping? So that you are not using the itemtypes authorised value list for both (like it is the default for MARC21 at least). -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11043 --- Comment #5 from mathieu saby <mathieu.saby@univ-rennes2.fr> --- Yes, 2 different lists. Because our vendor tell us it was possible I presume. For circulation rules, if the rules are the same for DVD and CD, we did not want to duplicate them. So we can have biblioitems.itemtype = DVD items.itype = SHORT and biblioitems.itemtype = CD items.itype = SHORT Mathieu -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11043 --- Comment #6 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- It is totally possible, but I think this is the kind of customizations that we will have to be really careful about when we change how this works. -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11043 --- Comment #7 from mathieu saby <mathieu.saby@univ-rennes2.fr> --- (In reply to Katrin Fischer from comment #4)
I think you can only do that, when you change the mapping? So that you are not using the itemtypes authorised value list for both (like it is the default for MARC21 at least).
HMM I understand now why in Zebra, Marc21 is indexing both information in the same index, while in UNIMARC we use ccode for biblioitems.itemytpe (ccode seems quite a bad choice). Making this more uniform could be interesting I think. Because some changes could be unseen for Marc21 ppl, while they will break configs of unimarc ppl. And as the concept of "type of documents" and "type of items" are easily understandable by everone, and not specific to a marcflavor, I don't see why the indexing should be different. I would appreciate to have the opinion of unimarc ppl, for example from Biblibre. Mathieu -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org