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

[Bug 37670] New: Alert librarian when placing booking on missing item
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37670 Bug ID: 37670 Summary: Alert librarian when placing booking on missing item Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aude.charillon(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It is still possible to place bookings on items marked as missing. It would be nice to show a warning to staff attempting to place a booking to say the item is missing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 38859] New: New bookings notices should be added for existing installs
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38859 Bug ID: 38859 Summary: New bookings notices should be added for existing installs Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We should add the sample notices for bookings placed,cancellation, and modification via a DB rev for existing installs. As of now the library has to create them with no reference -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 36913] New: Booking should take non-for-loan into account
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36913 Bug ID: 36913 Summary: Booking should take non-for-loan into account Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: data-27FC05A3CB97(a)office-dateien.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It appears that bookings are placed on items that are marked as not for loan. This seems to be independent whether holds can be placed on an item or not (positive or negative NOT_LOAN value). There should be an option to prevent this, ideally by having a way to specify which NOT_LOAN values are acceptable for bookings (similar to SkipHoldTrapOnNotForLoanValue). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 38165] New: Add a view to the staff interface to manage bookings of a library
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38165 Bug ID: 38165 Summary: Add a view to the staff interface to manage bookings of a library 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: paul.derscheid(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com At the moment there's no real overview of all bookings in the staff interface. The goal of this bug is to provide one that lets staff modify and cancel bookings as well as transforming them into checkouts. I think a good place for this would just be another section under the Circulation section of the staff interface. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 33523] New: Hold Queue targets items on record level holds that should not fill the hold
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33523 Bug ID: 33523 Summary: Hold Queue targets items on record level holds that should not fill the hold 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: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Holds queue doesn't check if a branch's item can fill the hold if at least one item is available on the record for a bib level hold To recreate: • Have ReservesControlBranch set to "item's home library" • Have at least 2 libraries. • Set the circulation rules so that a patron type can place holds on an item type at library A • Set the circulation rules so that the same patron type cannot place holds on or have any checkouts on the same item type at library B • Make a record with at least 2 items, one at library A and one at library B. • Place a bib level hold for a patron matching the patron type in the rules • Run holds to pull for both branches • The item should only show on Library A's list, but it also shows on library B. Library B doesn't allow checkout of those items for that patron type. The same thing also happens if there are separate item types on the same record, such as a public copy and a staff copy. The staff copy will try to fill the hold even though it can only be held and loaned by staff. Lisette -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 33070] New: Get rid of Koha::Patron->can_edit_item and use can_edit_item_from instead
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33070 Bug ID: 33070 Summary: Get rid of Koha::Patron->can_edit_item and use can_edit_item_from instead Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 20256 introduced a pattern we are trying to avoid for a long time now (old patchset). It should be refactored and cleaned. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 23898] New: New data to share on HEA
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23898 Bug ID: 23898 Summary: New data to share on HEA Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.poulain(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Some ideas of thing that could be shared on HEA for statistics purposes: - adding some statistics like "intranetuserjs yes/no" => yes if there's something, no if it's empty ? (intranetuserjs, opacuserjs, opac & intranet css, opacheader, opacnav, opacbottom). - For sysprefs *XSLT* => we could send "empty/default/local". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 38924] New: Introduce a loan 'Quota' system for Koha
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38924 Bug ID: 38924 Summary: Introduce a loan 'Quota' system for Koha 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries work based on the number of allowed issues in a time period as opposed to the number of simultaneous issues. This enhancement intends to add a per-user, including guarantee/guarantor relations, quota option for setting a fixed number of issues a user is allowed within a specified period. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 274

[Bug 30552] New: Add a way to import circulation rules
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30552 Bug ID: 30552 Summary: Add a way to import circulation rules 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com bug 18392 added a method for exporting the circ table, however, that bug originally requested both import/export - opening this to allow import to be explored in the future -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 39541] New: Do we need to store the whole MARC record in Elasticsearch?
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39541 Bug ID: 39541 Summary: Do we need to store the whole MARC record in Elasticsearch? Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: domm(a)plix.at QA Contact: testopia(a)bugs.koha-community.org Currently the whole MARC Record is stored in the ElasticSearch Record. At the Koha Hackfest 2025 I learned that one reason for this is to be able to search the whole record (Bug 22258). Another reason might be to avoid hitting the DB when displaying search results. But: * We sometime encounter problems with very large records (due to limits with UNIMARC) * The code to store the whole record is rather convoluted (involes encoding/decoding the record, checking for errors, falling back to other encoding methods..) * It bloats the ES index (if it's not needed) So I will investigate: * would displaying search results work without the whole MARC record? * aren't we hitting the DB anyway during displaying search results * in OPAC * in Staff * in API If it seems easy to optionally not add the whole record to the index, I would suggest * Adding a new Option "Don't store" to syspref ElasticsearchMARCFormat * If it is set, skip adding the whole MARC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5