https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36789
--- Comment #22 from Thibaud Guillot <[email protected]> --- (In reply to Martin Renvoize from comment #19) > This is the sort of workflow I was alluding to when I said in bug 36915 that > perhaps we don't want to tie the cancellation notice to the delete method > but rather introduce a cancel method instead. > > I'm also not really sure about removing bookings at fulfilment time.. I can > see people wanting to report on those fulfilled and unfulfilled bookings > down the line. > > I was considering instead, adding a status field to bookings to flag that a > booking is in various states... waiting, fulfilled, overdue for pickup, > cancelled.. etc. Then, adding to cleanup_database to ensure we don't have a > runaway table of data. > > Thoughts? Hello Yes, it might be useful to create a cancel method to mark them with a "status". Maybe we can also move bookings to "old_bookings" like holds/old_holds I mean.... For now I'll just quickly rebase the patch if anyone wants to test it and make up their own mind :) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ 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/
