[Bug 38869] New: Keep previous versions of Notices/Slips
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38869 Bug ID: 38869 Summary: Keep previous versions of Notices/Slips Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs@lists.koha-community.org Reporter: dcook@prosentient.com.au QA Contact: testopia@bugs.koha-community.org It would be very interesting to be keep a version history for Notices/Slips. I imagine there must be lots of libraries that curse saving a new version of a Notice/Slip only to realise that they've horribly broken it? It would be especially useful with bug 11583 -- 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=38869 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=11583 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38869 Magnus Enger <magnus@libriotech.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |magnus@libriotech.no -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38869 Alexander Wagner <alexander.wagner@desy.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexander.wagner@desy.de --- Comment #1 from Alexander Wagner <alexander.wagner@desy.de> --- Sounds like holding the nocites and slips in a `git` would be a nice idea. One could then use the perl-apis to populate the db from there. I implemented a similar procedure for our automatic setup in j2k. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38869 Lisette Scheer <lisette@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lisette@bywatersolutions.co | |m --- Comment #2 from Lisette Scheer <lisette@bywatersolutions.com> --- Could we update the notices log to use the diff Kyle added and then somehow use that to recreate/rollback? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38869 --- Comment #3 from David Cook <dcook@prosentient.com.au> --- (In reply to Alexander Wagner from comment #1)
Sounds like holding the nocites and slips in a `git` would be a nice idea. One could then use the perl-apis to populate the db from there. I implemented a similar procedure for our automatic setup in j2k.
I think adding another dependency and moving part might be overkill in this case. -- 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=38869 --- Comment #4 from David Cook <dcook@prosentient.com.au> --- (In reply to Lisette Scheer from comment #2)
Could we update the notices log to use the diff Kyle added and then somehow use that to recreate/rollback?
I'm not familiar with the diff, but I was pondering a bit about the action_logs. For each notice, we'd want to quickly and easily be able to see how many revisions there were for a notice. For that, I think we'd need a table in itself. But in theory that table could point to the action_logs. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38869 --- Comment #5 from Alexander Wagner <alexander.wagner@desy.de> --- (In reply to David Cook from comment #3)
(In reply to Alexander Wagner from comment #1)
Sounds like holding the nocites and slips in a `git` would be a nice idea. One could then use the perl-apis to populate the db from there. I implemented a similar procedure for our automatic setup in j2k.
I think adding another dependency and moving part might be overkill in this case.
Well, IMHO it would be a very generic dependency (not sure if one even has to `apt get` it manually these days) and allow for a very generic solution generally applicable that might come in handy at various other locations probably some not yet on the radar. But of course there are other ways to handle diffs. -- 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=38869 --- Comment #6 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- We do have a ReportsLog that is quite nice and could serve as a possible example. The action logs also allow to copare and see diffs. And we can now store JSON diffs as well. I think maybe this could be solved with what we already use in other places. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org