Bug 11591 - runtime parameter for library groups
Summary: runtime parameter for library groups
Status: REOPENED
Alias: None
Product: Koha
Classification: Unclassified
Component: Reports (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-21 16:59 UTC by Nicole C. Engard
Modified: 2025-08-04 14:13 UTC (History)
6 users (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2014-01-21 16:59:57 UTC
Would be great to have a runtime parameter for groups of libraries as they are set in the libraries & groups menu.
Comment 1 David Cook 2022-12-06 23:04:58 UTC
I don't know what this means, and Nicole hasn't worked on Koha for a long time, so I don't think she'd be able to clarify
Comment 2 Myka Kennedy Stephens 2025-07-31 14:18:24 UTC
I'd like to reopen and clarify since I was about to submit a new bug for this.

The reports module has several runtime parameters that can be used to easily pull a list of values for selecting when running a report. See https://koha-community.org/manual/latest/en/html/reports.html#runtime-parameters.

Library groups are not currently a runtime parameter. Because library groups are stored in the library_groups table instead of as an authorized value, there's currently no way to pull in a list of library groups to select from when running a report. The library staff member running the report needs to know their library's group code and type that into a text entry for any reports that need to pull data from all libraries that are within a library group.

If library groups were added as a runtime parameter, similar to branches or item types, this could be called on in the report and would show up as a drop-down list.

This would be a huge benefit to library consortiums and systems that have multiple groups of branches where reports would need to be run by group instead of by individual branch.
Comment 3 Phillip Berg 2025-07-31 15:06:19 UTC
Yes, for sure having library groups as a parameter is extremely important for just about any multi-branch system.
Comment 4 George Williams (NEKLS) 2025-07-31 19:26:18 UTC
Yes.  This would be a great feature for Koha installation with multiple branches but when Nicole wrote the original bug I think there were only two types of groups - Search Domain groups and Library Property groups.  Groups have expanded now to include 

- Limit patron data access by group (ft_hide_patron_info)
- Limit item editing by group (ft_limit_item_editing)
- Use for OPAC search groups (ft_search_groups_opac)
- Use for staff search groups (ft_search_groups_staff)
- Is local hold group (ft_local_hold_group)
- Is local float group (ft_local_float_group)

So any work on adding runtime parameters for library groups to the Reports module is going to need to include a way to specify which type of group the parameter works with.