https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38291 --- Comment #54 from David Cook <dcook@prosentient.com.au> --- (In reply to Andrew Fuerste-Henry from comment #40)
This use case also relies on knowing whether or not a given group has the "use for record source locking" feature enabled, so that one can only tie a record source to a library group that is set to be used for record sources. Any future use of this API will want to function similarly, filtering to only groups that are relevant to the issue at hand.
You're conflating things a bit here. The user does not need to know if a given group has a "use for record source locking" feature. They just need to know which groups are available for record source locking. They're two different but related ideas.
I suppose that could be handled by putting a query in the API request ("list the groups that are set to use for record source locking") rather than getting all groups and all the data about each of them.
I think you've missed my point all together. One use case is management of Koha configuration (even if that management is just the R in CRUD or view action). Your use case is getting the library groups available for a particular action. -- You are receiving this mail because: You are watching all bug changes.