https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41307
--- Comment #14 from Matt Blenkinsop <[email protected]> --- Created attachment 210201 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=210201&action=edit Bug 41307: Add status, background_job_id and report period to erm_counter_logs A counter log row was only written after a COUNTER file was stored, so a failed harvest left no trace and a log could not be tied to the job that produced it. This adds to erm_counter_logs: - background_job_id, a foreign key to background_jobs with ON DELETE SET NULL, so a log survives the purge of its job by cleanup_database - report_type, report_year and report_month, the harvested period of a single-month job, so the import logs and the summary can be read per month - status, the outcome of the harvest or import: success, no_usage, no_data, retry or error, with an index for the status filter Existing rows get status success: before this patch a row was only written after a successful import. The counter log API definition gains the same fields. Sponsored-by: Karlsruhe Institute of Technology (KIT) Assisted-by: Sonnet 5 (Anthropic) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
