https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41551
--- Comment #1 from Lisette Scheer <[email protected]> --- Migration Strategy Phase 1: Parallel Implementation (6-12 months) Implement new schema alongside old Create Koha::Role, Koha::Permission classes Build migration tools Create default system roles Add admin UI for role management Bugs: Koha::Permission Koha::Role, Create default system roles, Add admin UI for role management Build migration tools - - including an upgrade wizard? migrate to new ones, make an upgrade wizard for super librarians to set up new/learn new system Update checker Barebone objects by hackfest Submit phase 1 end of cycle for early 26.11 push Phase 2: Dual-Mode Operation (12-18 months) Support both old and new permission systems Add syspref: UseNewPermissionSystem (default: off) Gradually migrate core Koha code to use new API Plugin developers can adopt new system Phase 3: Data Migration (6 months) Automated migration tool: Old Permission → New Role Mapping superlibrarian → Superlibrarian role circulate → Circulation Staff role editcatalogue → Cataloger role etc. Custom permission combinations → custom roles Validation and testing period Phase 4: Deprecation (1-2 years) Mark old system deprecated All new features use only new system Community testing and feedback Phase 5: Removal (Next major version) Remove old tables (userflags, permissions, user_permissions) Remove compatibility layer Clean up documentation Total Timeline: 3-5 years for complete migration -- 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/
