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

[Bug 20161] New: Show same information for format, material type etc. on the detail page as in the result list
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '25

30 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20161 Bug ID: 20161 Summary: Show same information for format, material type etc. on the detail page as in the result list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org A lot of libraries ask, why there is less information about the material type, format and literary format shown on the detail page than in the result list. I suggest to match both displays and make it possible to hide with CSS as you can already do on the result list (using the same classes). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 31009] New: Claims list take too much times (timeout when you have so many claims) on serials
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '25

30 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31009 Bug ID: 31009 Summary: Claims list take too much times (timeout when you have so many claims) on serials Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org To view claims, when clicked, an SQL query is performed to search for claims by vendor and build a select list. If you have so many claims, it takes too long or even creates a timeout problem. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 25711] New: Add ability to define expiredpickup charge for patron category and item type
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '25

30 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25711 Bug ID: 25711 Summary: Add ability to define expiredpickup charge for patron category and item type Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: minna.kivinen(a)hamk.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com ExpireReservesMaxPickUpDelayCharge allows one charge to be applied to all holds that expire. It would be better to have ability to define this charge in ciculation rules. There can be different charges for different types of materials for different patron categories. Related to this bug report: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18195 Charge for expired holds per patron category -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 166

[Bug 27691] New: allow HTML in Notes output on guided_reports_start.tt
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '25

29 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27691 Bug ID: 27691 Summary: allow HTML in Notes output on guided_reports_start.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some reports have a long and detailed notes section pertaining to a given report. With the html filter it can be very difficult to parse out those notes. Is there any reason we cannot use a $raw filter in this situation? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 34596] New: Items in transit should not show up in the holds queue
by bugzilla-daemon＠bugs.koha-community.org 27 Dec '25

27 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34596 Bug ID: 34596 Summary: Items in transit should not show up in the holds queue Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Libraries have reported that items are still showing up in their holds queue hours after they have been marked as "in transit". Only holds that are ready to be found should be showing up in the holds queue. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 59

[Bug 28702] New: Improve performance of C4/XSLT/buildKohaItemsNamespace
by bugzilla-daemon＠bugs.koha-community.org 27 Dec '25

27 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28702 Bug ID: 28702 Summary: Improve performance of C4/XSLT/buildKohaItemsNamespace Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This subroutine prepares items for XSLT parsing in search results, or opac lists. In bug 23414 it was refactored to use Koha::Items to reduce the number of lookups. In reviewing this code, it can be improved further - it is only called by XSLTParse4Display which is only called in 2 places: C4::Search->searchResults opac/opac-shelves.pl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 47

[Bug 32702] New: Item statuses that block holds should be checked in CanItemBeReserved
by bugzilla-daemon＠bugs.koha-community.org 26 Dec '25

26 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32702 Bug ID: 32702 Summary: Item statuses that block holds should be checked in CanItemBeReserved Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently true holdability is a combination of CanItemBeReserved/CanBookBeReserved and IsAvailableForItemLevelRequest We should either combine these two routines, or ensure they are both called whenever needed. That is a long term goal, and this bug aims to simply move the item status checks to 'CanItemBeReserved' as they should reduce processing for any unavailable statuses to boost performance, and ultimately improve current functionality. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 55

[Bug 26537] New: Search does not work when no term in value_builder/unimarc_field_4XX.pl
by bugzilla-daemon＠bugs.koha-community.org 26 Dec '25

26 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26537 Bug ID: 26537 Summary: Search does not work when no term in value_builder/unimarc_field_4XX.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Cataloguing plugin value_builder/unimarc_field_4XX.pl has an itemtype filter. It does not work when used without a search term. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 55

[Bug 25408] New: CanBookBeReserved should check "opacitemholds" policy
by bugzilla-daemon＠bugs.koha-community.org 26 Dec '25

26 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25408 Bug ID: 25408 Summary: CanBookBeReserved should check "opacitemholds" policy Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com how to reproduce : Set an issuing rule with opacitemholds set to "Force" Make a search and select multiple records Place a hold on those records (using multi-hold records) Verify hold is placed on the record (next item available) where it shouldn't! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 146

[Bug 36261] New: Calculating OpacHiddenItems is too slow in OPAC search
by bugzilla-daemon＠bugs.koha-community.org 25 Dec '25

25 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36261 Bug ID: 36261 Summary: Calculating OpacHiddenItems is too slow in OPAC search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Calculating items and records hidden by OpacHiddenItems it slow. Too slow. Fortunately, I've come up with an optimization which seems to effectively eliminate the overhead added by OpacHiddenItems. Basically, instead of running 1 query per item, I run 1 query per bib to get all hidden items. It's pretty straightforward, but I'd like to battle-test it a bit more. I'm also writing this optimization for an older version of Koha, and I still have more optimizing I want to do, so I'm not going to post my patch just yet... It's coming though! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22