[Bug 41307] New: Automatically indicate when a harvest job is completed (successfully or with an error)
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41307 Bug ID: 41307 Summary: Automatically indicate when a harvest job is completed (successfully or with an error) Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart@gmail.com Reporter: mathsabypro@gmail.com QA Contact: testopia@bugs.koha-community.org CC: jonathan.druart@gmail.com, jonathan.field@openfifth.co.uk, martin.renvoize@openfifth.co.uk, matt.blenkinsop@openfifth.co.uk, pedro.amorim@openfifth.co.uk In /erm/eusage/usage_data_providers when you run an import for a data source, the list of corresponding jobs is displayed above the table ("Job for report type DR has been queued. Check job progress.") It would be nice if this information were automatically updated once the job is completed ("Job for report type DR is completed. Check job details.") This may not be technically possible ? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41307 --- Comment #1 from Mathieu Saby <mathsabypro@gmail.com> --- I see this information will be added in the widget on the ERM home page https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39320 But it could be added too in erm/eusage/usage_data_providers page -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41307 Michaela Sieber <michaela.sieber@kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew.auld@openfifth.co.uk | |, clemens.tubach@kit.edu, | |michaela.sieber@kit.edu --- Comment #2 from Michaela Sieber <michaela.sieber@kit.edu> --- As far as I can see the widget only displays if the job is still running or completed / cancelled. What you would like to see is the error code and message. This is the SQL-Statement which gives you the option to find the background jobs type erm_sushi_harvester that ended with an error (for example if no data were available or if the request was queued, etc.) : SELECT CONCAT('<a target="_blank" href=\"/cgi-bin/koha/admin/background_jobs.pl?op=view&id=',bj.id,'\">', bj.id, '</a>' ) AS "Job-ID", bj.enqueued_on AS 'Date/time', CONCAT('<a target="_blank" href=\"/cgi-bin/koha/erm/eusage/usage_data_providers/', JSON_VALUE(bj.data,'$.ud_provider_id'), '\">', JSON_VALUE(bj.data,'$.ud_provider_id'), '</a>' ) AS "Provider-ID", JSON_VALUE(bj.data,'$.ud_provider_name') AS 'provider name', JSON_VALUE(bj.data,'$.report_type') AS 'Report', JSON_VALUE(bj.data,'$.begin_date') AS 'report begin_date', JSON_VALUE(bj.data,'$.end_date') AS 'report end_date', JSON_VALUE(bj.data,'$.messages[0].code') AS 'error code', JSON_VALUE(bj.data,'$.messages[0].message') AS 'error message' FROM background_jobs bj WHERE type='erm_sushi_harvester' AND JSON_VALUE(bj.data,'$.messages[0].type')='error' /* #All jobs with type error in data column, e.g. No Usage Available for Requested Dates (3030) or Usage Not Ready for Requested Dates (3031) or Fatal - Service Not Available (1000) or Error - Requestor Not Authorized to Access Service (2000) */ AND DATE(bj.enqueued_on) BETWEEN <<from|date>> AND <<to|date>> ORDER BY bj.enqueued_on DESC -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41307 Michaela Sieber <michaela.sieber@kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=41223 --- Comment #3 from Michaela Sieber <michaela.sieber@kit.edu> --- We need more information about the harvesting jobs and store them for example in the existing database table for erm_counter_logs. Relevant information are error codes, harvested month, background-job-ID. This would also be the groundwork for a Retry management of harvesting jobs that were finished with error codes like 1011 = "Report Queued for Processing" or 1020 = "Client has made too many requests" See also Bug 41223 -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org