http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7710
--- Comment #85 from Katrin Fischer <[email protected]> --- Hm. Trying to think of a use case: serial record with multiple items - each representing a bound volume of issues for a specific year. You need to get 2 articles from 2 different years - so you want to place holds on 2 different items and want both of them to be filled. For me the case of a record level + item level holds on the same record doesn't make much sense. I can't think of a use case. Maybe multiple holds should only be allowed item level? A warning if you already have an item level hold, that you need to cancel it first, to set another item level hold? Looking at the first description of the feature and the current patches I feel like things have drifted apart - especially about the use of the enumchron field (comment#0) - I didn't spot that in the current patches? How will it be possible to limit the multiple holds on records where it makes sense? I think having this as a circ rule or being tied to some other condition (enumchron) would be really good to make it more generally useful. As a circulation rule we could combine it with the option to enforce item level holds. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://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/
