https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41400
--- Comment #3 from Mathieu Saby <[email protected]> --- The use case is the one I put down in bug description. Maybe we can imagine an other one, in a 1-branch Koha. At biblio level you can have a value "multi-part document", that make no sense at item level. But I believe the real difficulties are for networks, like in my description. My previous ILS would use distinct fields at items level, for storing "material type" (book etc) and "circulation type" (21 days, 5 days, etc). And an other kind of data at biblio level (aligned with types defined in UNIMARC manual, but that's another story). In Koha we currently don't have the same precision and we "twist" the model, for example by using the collection code in a way that was probably not initially intended. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
