[Koha-bugs] [Bug 20194] Display items.ccode as well as both biblioitems.itemtype and items.itype in circulation screens

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Fri Feb 16 13:40:08 CET 2018


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20194

--- Comment #5 from Gaetan Boisson <gaetan.boisson at biblibre.com> ---
We had discussed it internally before submitting this, and came up with the
conclusion that displaying which type is which would be redundant, because we
couldn't think of a scenario where the same list would be used in both
fields.The display would always be something like "book ; long loan" and be
explicit for the librarians because they know the lists they are using.

I am confused about what the use case would be for having the same information
in both biblioitems.itemtype and items.itype. When that is the case, why not
position item-level_itypes to bibliographic level, and leave items.itype empty?

Can you enlighten us on this with more details on the use case where the
information would be the same?

The use case for this enhancement is that quite a few libraries want to qualify
the bibliographic record with a notion of the type of document (book, dvd,
etc.) because then all items attached to this record will obviously have the
same type. This notion will be useful for search. But then some want to be able
to have different circulation rules for the different items attached to the
record, "long loan" and "short loan" for instance. This is the use case for
using both. In that scenario, biblioitems.itemtype is controlled by a separate
authorized value category, not by itemtypes. Some even crazier librarians use
the ccode for an extra level of categorization on the item.

I think this is linked to a terminology issue in Koha that doesn't seem to
bother everyone: what the system calls "item types" can be positioned at the
bibliographic level, in which case it is not about *items* any longer.

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list