https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37052
--- Comment #14 from David Cook <[email protected]> --- I'm starting to think that "module-based" permission policies might not be a bad idea. Here's a thought on columns for a "perm_policies_reports" table for the Reports module: policy_id (autonumber), report_id (nullable), report_group (nullable), borrowernumber (nullable), categorycode (nullable), action, effect (ie allow/deny). The nullable columns allow for great flexibility but we'd probably want to be careful with our coding. For instance, something like the following could be used to allow executing reports to everyone: 1, null, null, null, null, 'execute_reports', 'allow' Although we'd have to decide whether this refers to just the staff interface or all interfaces. Maybe we need another column for "interface". Alternatively, I suppose we could also do: policy_id (autonumber), policy_json (JSON/LONGTEXT) But it means we'd need to embrace vendor-specific JSON functions for querying, and I do think MariaDB and MySQL have some differences in JSON support, so maybe that's not practical after all. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
