Summary: | Expand library group feature 'Is local hold' group to subgroups for local holds priority | ||
---|---|---|---|
Product: | Koha | Reporter: | Lisette Scheer <lisette> |
Component: | Hold requests | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | anneli.osterman, gmcharlt, trevor.diamond |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39989 | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Bug Depends on: | 20747 | ||
Bug Blocks: |
Description
Lisette Scheer
2025-05-23 21:28:18 UTC
My cooperative of 42 libraries would also appreciate the ability to nest hold groups, similar to the initial example. Rather than think of it in terms of group and subgroup (which implies just two levels), I would prefer a way where we can "order" the groups in terms of nesting. Or would it make more sense to rank the various groups to which a library belongs in terms of ascending size. So the smallest group gets the first considerations, and continuing up in size until the request is filled or every library in the system is eligible. If the ranking is automatically applied through this kind of logic, there's a lower hurdle to using the feature, but if there are two groups of a similar size, it would be random which is considered "first". You could have more control of the order if there was additional group feature of "priority" like we see for item groups, which lets you control the order they appear. |