October 2024 - Koha-bugs - lists.koha-community.org

[Bug 38178] New: Report pagination is inefficient
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38178 Bug ID: 38178 Summary: Report pagination is inefficient Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org It seems that the pagination for report results might be causing more bloat in time rather than helping in processing. I thought the purpose of paginating the results was to improve processing time, but when I run a hefty report (say, against the statistics table), it takes a long time to process 20 results, and then the same amount of time for each page I switch to. If feels like it is gathering the entire set of results, then only carving out the number of results it is supposed to show. I think pagination is only beneficial if the report is only processing the range of results being shown. Otherwise, it should just show all results. For example, a report of 1000 results being paginated in groups of 20 should, in theory, process in about 1/50th the amount of time it would take to process all 1000 results. But it feels like it is taking the time to process all 1000 results. I get the logistics of this. In order to process pages of all the results, sorted, grouped and ordered properly, the whole result needs to be taken into consideration, then broken down. But with each page change, it has to do this all over again. It seems that when the report is run, the results need to be stored in a way that the paging would refer to the stored results, not re-run the report. I don't think there is a way to run the report for each page, just for that page's section of results. It seems that the report needs to run in its entirety initially, but then we should have a more efficient way of going through the pages of results. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 38152] New: Add "copy to clipboard" feature to barcodes in detail pages
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38152 Bug ID: 38152 Summary: Add "copy to clipboard" feature to barcodes in detail pages Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Often we need to copy barcodes for demos or when testing, but coyping the link is hard and not always works well. It would be nice if we offered an option to copy the barcode to the clipboard, maybe using a little icon or similar that could be added later in other places as well. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 9805] Lost items are un-lost if returned, but not if renewed
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '24

15 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9805 Janet McGowan <janet.mcgowan(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |janet.mcgowan(a)ptfs-europe.c | |om -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 32256] New: self-checkout batch mode
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '24

15 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32256 Bug ID: 32256 Summary: self-checkout batch mode Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: ddaghita(a)mckinneytexas.org QA Contact: testopia(a)bugs.koha-community.org Please enable batch checkouts on self-checkout machines using koha self-checkout module (/cgi-bin/koha/sco/sco-main.pl?). We have patrons place one book at time on the RFID pad to self-checkout. We would ideally like patrons to stack five or more materials at a time so they checkout more efficiently all at once as it does on the koha staff side. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 105

[Bug 35465] New: Ability to select multiple funds for a single order
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '24

15 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35465 Bug ID: 35465 Summary: Ability to select multiple funds for a single order Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: cguenther(a)coloradocollege.edu QA Contact: testopia(a)bugs.koha-community.org Allow multiple funds to be selected for tracking payment on a single order. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 36319] New: Splitting a single item between multiple funds
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '24

15 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36319 Bug ID: 36319 Summary: Splitting a single item between multiple funds Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: liberm(a)uhv.edu QA Contact: testopia(a)bugs.koha-community.org Periodically we run into instances where we need to split the cost of a book or database between two funds. Currently this is not possible in Koha and so we add and subtract money from funds to get the money to match, but it doesn't allow us to track the actuality of how the money was spent for reporting purposes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 38172] New: Can't override renew limit with AllowRenewalLimitOverride on when account is restricted
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '24

15 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38172 Bug ID: 38172 Summary: Can't override renew limit with AllowRenewalLimitOverride on when account is restricted Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When the account is restricted the 'Override and renew' option is not present and the librarian has no option but to select 'Continue without renewing'. The librarian may be tempted to remove the restriction and force through the renewals, but the restriction remains lifted. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 7012] Limit to available does not exclude in-transit items
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '24

15 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7012 Jonathan Druart <jonathan.druart(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |BLOCKED Depends on| |37334 --- Comment #18 from Jonathan Druart <jonathan.druart(a)gmail.com> --- Remote branch pushed, there is a very simple patch that addresses this, but on top of another big work, bug 37334. https://gitlab.com/joubu/Koha/-/commits/bug_7012 Marking as BLOCKED but the remote branch can be tested. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37334 [Bug 37334] Cannot filter holdings table by status -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 7012] Limit to available does not exclude in-transit items
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '24

15 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7012 --- Comment #17 from Jonathan Druart <jonathan.druart(a)gmail.com> --- We can deal with in-transit, but what about withdrawn, lost, damaged (see bug 25375 comment 47). -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 7012] Limit to available does not exclude in-transit items
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '24

15 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7012 Jonathan Druart <jonathan.druart(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Searching |Searching - Elasticsearch Depends on| |25375 Assignee|gmcharlt(a)gmail.com |jonathan.druart(a)gmail.com --- Comment #16 from Jonathan Druart <jonathan.druart(a)gmail.com> --- I can have a look at this, for ES only however. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25375 [Bug 25375] Elasticsearch: Limit on available items does not work -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0