https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43752 --- Comment #1 from Philip Orr <philip.orr@lmscloud.de> --- At Hackfest 2024 and again at KohaCon 2026 we talked about simplifying Koha's system preferences. Here are my notes copied verbatim from Mattermost: - It's not sustainable long term to have sysprefs that are only used by one library and that have to be added to every Koha installation. - If a syspref that turns an entire module in Koha on or off is not on, then all related permissions should be hidden too, since they are useless anyway. Although Katrin has a plus of having them there: you can prefill with the correct values and then later turn on the module with prefilled values filled in.. - one suggestion was a simple general configuration page similar to circ rules. [how it was done for ILL sysprefs for example] - It was mentioned that some support companies were losing tenders because Koha is too complicated for small libraries - We should also be considering libraries that don't have support companies - another suggestion was "only show preferences for basic configuration" and then if the library wants "advanced configuration", they can turn it on and see the rest - some smaller pain points are "preferences that rely on each other", like one syspref that turns on a module and another one that controls whether to show it in the OPAC. That could be just one pref: "turn on in staff / turn on in opac / turn on in both / off" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43752 --- Comment #3 from Philip Orr <philip.orr@lmscloud.de> --- pros and cons here: https://lite.framacalc.org/913f878fze-anyy please add your thoughts! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.