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

[Bug 40049] New: csv or spreadsheet export option for POS summaries
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '25

02 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40049 Bug ID: 40049 Summary: csv or spreadsheet export option for POS summaries Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Point of Sale Assignee: koha-bugs(a)lists.koha-community.org Reporter: hdunne-howrie(a)westminster.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk As well as a 'print' option we would also like to see a 'download' option on POS summaries that allows for download of the report to csv or open spreadsheet format, i.e. something that will allow us to open in excel -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 40289] New: Links to single result searches misleading
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '25

02 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40289 Bug ID: 40289 Summary: Links to single result searches misleading Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: david.roberts(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Logging on behalf of a new Koha customer: When looking at a biblio record which has a linked heading (author, editor, translator), Koha will present other books with the same heading (i.e. all the books edited by the same person); however, if there are no other books with the heading, it does not look like it responds at all: click on it, and it reverts back to the record from which the user is clicking on. This is correct behaviour as per every other search in Koha, but as it looks to the end user like the search hasn't done anything, the customer thinks this is a poor user experience and would like it to be clearer that there is only the one result found. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 32441] New: Localuse is recorded in statistics but not recreated in pseudonymized_transactions
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32441 Bug ID: 32441 Summary: Localuse is recorded in statistics but not recreated in pseudonymized_transactions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The pseudonymization feature creates a parallel to the statistics table without identifiable patron data. This allows one to then use cleanup_database to delete old entries in statistics to remove that patron data. However, the statistics table also contains records of local use. That data only exists in statistics. It is not duplicated in pseudonymized_transactions, and so is lost if statistics are deleted using cleanup_database. Bug 32440 suggests teaching cleanup_database to not delete localuse entries. This bug suggests putting localuse entries into pseudonymized_transactions, even though no patron is involved. That's a bit illogical, but has the benefit of keeping all of this data together. Meanwhile, Bug 16122 suggesting keeping a local use count in the item record. That would alleviate this issue somewhat, but specific transactional data would be preferable to a running count. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 24841] New: REST API should check if patron is restricted/debarred
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24841 Bug ID: 24841 Summary: REST API should check if patron is restricted/debarred Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no Bug 17247 "ILS-DI HoldTitle and HoldItem should check if patron is restricted" adds checks to see if the patron is restricted before a hold is placed. These checks are added to C4::ILSDI::Services::HoldItem() and C4::ILSDI::Services::HoldTitle(). As far as I can tell, the same checks are missing from the REST API, specifically for "POST /api/v1/holds". Koha::REST::V1::Holds::add() does call C4::Reserves::CanItemBeReserved() and C4::Reserves::CanBookBeReserved(), but as far as I can tell, those subs do not check if the patron in question is debarred. Am I missing something or is this a bug? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 34478] Full CSRF protection
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34478 Fridolin Somers <fridolin.somers(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|36155 | Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36155 [Bug 36155] Improve perfs of suggestion.pl when there are many budgets -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 32974] New: Allow different limits for hold the shelf holds vs holds on checked out items
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32974 Bug ID: 32974 Summary: Allow different limits for hold the shelf holds vs holds on checked out items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: rkuiper(a)roundrocktexas.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We would like to see a function in Koha where the hold limit is separated into two limits. One limit for on-the-shelf holds and another limit for holds on items checked out. Currently, we can allow or not allow on-the-shelf holds. We would like to see this expanded to specify the number of holds allowed if we have on-the-shelf holds turned on. Then there would be a separate limit that is for items that are checked out or on order. The reason for separating these is so we can manage staff time on the holds to pull list and still allow patrons to put holds on popular items and items that are new to the library. Our plan would be to allow something like 7 holds for on-the-shelf holds and allow unlimited holds for checked out and on order items. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 34478] Full CSRF protection
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34478 Fridolin Somers <fridolin.somers(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |36155 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36155 [Bug 36155] Improve perfs of suggestion.pl when there are many budgets -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35170] New: Make long overdue item type options configurable in interface
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35170 Bug ID: 35170 Summary: Make long overdue item type options configurable in interface Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Being able to set the item type options: 'itemtype=s' => $itemtype 'skip-itemtype=s' => $skip_itemtype, Via the staff interface would be really helpful for users being able to update their longoverdue settings without needing to edit the command line. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 29505] New: Add syspref to allow to place multiple holds on same item
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29505 Bug ID: 29505 Summary: Add syspref to allow to place multiple holds on same item Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 40280] New: BorrowerUnwantedField by patron category or branch (as well as system wide)
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40280 Bug ID: 40280 Summary: BorrowerUnwantedField by patron category or branch (as well as system wide) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: hdunne-howrie(a)westminster.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We want to be able to add in an exemption for BorrowerUnwantedField settings depended on patron category or branch. We have some users for which we need some fields to display to add in changes to our new patron form but we need them not to show for other user types. For this we need an exemption to BorrowerUnwantedField by patron category or branch -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1