https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41306 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Date picker for data |Date picker for data |harvesting should ask not |harvesting should not ask |ask to choose a day |to choose a day -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41306 Michaela Sieber <michaela.sieber@kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew.auld@openfifth.co.uk | |, clemens.tubach@kit.edu, | |katrin.fischer@bsz-bw.de, | |michaela.sieber@kit.edu Priority|P5 - low |P1 - high Severity|enhancement |major --- Comment #2 from Michaela Sieber <michaela.sieber@kit.edu> --- Not only is it best practice to perform harvesting on a monthly basis, there are also processing issues in Koha when multiple harvesting runs are carried out on a daily basis within a single month, because Koha aggregates the data instead of overwriting it. We therefor recommend to adjust the date picker in the user interface to allow only months (not days) as suggested Update importance to major. FYI: We can not confirm that the day is mandatory in COUNTER 5.1 which is the current release since January 2025 and obligatory for all providers. The COUNTER standard (R5 as well as R5.1) only requires months: "Reports MUST be provided monthly." "The reports MUST allow the report consumer the flexibility to specify a date range, in terms of months" (see https://cop5.countermetrics.org/en/5.1.0.1/05-delivery/index.html) We therefor recommend to adjust the date picker in the user interface to allow only months (not days) as suggested -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41306 --- Comment #3 from Jan Kissig <bibliothek@th-wildau.de> --- The API though says Begin_Date string<date> End_Date string<date> with example: "Begin_Date": "2022-01-01", "End_Date": "2022-03-31", see: https://countermetrics.stoplight.io/docs/counter-sushi-api/oyshu9qe9aeof-pr-... says Just tested 2 platforms with: begin_date=2025-11 and end_date=2025-11 and the response always included "Report_Filters": { "Begin_Date": "2025-11-01", "End_Date": "2025-11-30" }, So they fill up the 'missing' days. When testing the same with begin_date=2025-12-01 and end_date=2025-12-31 the response remained the same. In general I think it could be dangerous to limit both dates in the query to "YYYY-MM" format and maybe it should be allowed to send dates in "YYYY-MM-DD" or "YYYY-MM" format -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41306 --- Comment #4 from Michaela Sieber <michaela.sieber@kit.edu> --- Hey Jan :-) I think there is a misunderstanding here. This bug is about the user interface and what the user is allowed to input. The user should only be able to select a month, because according to the standard, no other option is possible anyway. You are right that the API allows specifying dates down to the exact day, but that doesn’t make sense, since the standard only supports monthly time specifications in terms of content. The COUNTER standard (R5 as well as R5.1) only requires months: "Reports MUST be provided monthly." "The reports MUST allow the report consumer the flexibility to specify a date range, in terms of months." (see https://cop5.countermetrics.org/en/5.1.0.1/05-delivery/index.html) And this is the definition for the date range (Begin_Date + End_Date): "Beginning and end of the reporting period. Note that the COUNTER API allows the format yyyy-mm for the API path parameters, which must be expanded with the first/last day of the month for the report header. For the tabular reports these filters are included in the Reporting_Period header instead of the Reporting_Filters header for easier reading." (see https://cop5.countermetrics.org/en/5.1.0.1/03-specifications/03-counter-repo...) -- You are receiving this mail because: You are watching all bug changes.