Version control system for back office configuration
A version control system for back office configuration tables, pipes, normalization rules etc.
For files like Custom HTML, CSS, JS, PDS etc. we can manage change history and revert to older versions by using version control systems like Git, Subversion etc. For configuration managed via the web back office and database this is not possible, but it is a vital feature of professional system management. This will become more important in a full SaaS environment.
Stacey van Groll commented
This idea has been under review for almost 5 years.
Manu Schwendener commented
Under review since February 2016?
Lucas Koster commented
How long will this idea be under review? Already 9 months?
Keren Stiles commented
Great idea. We currently do this by logging our configuration changes in a spreadsheet, but it's easy to forget to record changes that way. Having version control within the back office would be much better.
Matthias Einbrodt commented
Great idea. There is also a similar (at least I think) idea for Alma: http://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/9595131-there-should-be-a-way-for-institutions-to-share-no