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

[Bug 23669] New: Verify if checkouts or reserves requests from ILS-DI periods overlap with existing reserves
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23669 Bug ID: 23669 Summary: Verify if checkouts or reserves requests from ILS-DI periods overlap with existing reserves Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: julian.maurice(a)biblibre.com Depends on: 15261, 23531 Same as BZ15261 but for WebServices Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15261 [Bug 15261] Verify if checkouts or reserves requests periods overlap with existing reserves https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23531 [Bug 23531] ILS-DI doesn't implement needed_before_date and pickup_expiry_date parameters. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 37968] New: Add ability to store branchcode for messages in the queue and send by branchcode
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37968 Bug ID: 37968 Summary: Add ability to store branchcode for messages in the queue and send by branchcode Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We should be able to specify in the message queue who "owns" a message, and filter based on that data. We should limit it to the patron's branchcode for now, with the option to add sysprefs to control who "owns" each notice on a per-notice basis as a later enhancement as each notice has different things associated with it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 37398] New: Date Field changes from mm/dd/yyyy to 0000-00-00
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37398 Bug ID: 37398 Summary: Date Field changes from mm/dd/yyyy to 0000-00-00 Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: eric(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl A typed in value that follows the dateFormat system preference (mm/dd/yyyy) is changed to 0000-00-00 when the item is saved. This was found in 952$w before enabling the dateaccessioned.pl plugin for the subfield. To recreate: -set system preference dateFormat to mm/dd/yyyy -Go to an existing bib record -Edit items -input a date following the specified format (07-17-2024) -save the item -check the item and notice the date has been changed to 0000-00-00 -click back to the bib record -Error 500: Internal server error - Month out of range -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 95

[Bug 33255] New: Update the manual with information on searching with Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '25

23 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33255 Bug ID: 33255 Summary: Update the manual with information on searching with Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Maybe I missed it, but I didn't find any Elasticsearch specific information in the wiki for things like truncation, using indexes, boolean, fuzzy etc. There has recently been a nice blog post about searching that could be a starting point: https://bywatersolutions.com/education/monday-minutes-elastic-search Especially the linked cheat sheet: https://drive.google.com/file/d/17-YVjG6IJKeDmDCKuF7ZYvcTfzDYyxwa/view Some more sources to draw from maybe: https://bywatersolutions.com/education/elastic-searching https://bywatersolutions.com/education/elastic-search-configuration -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 39455] New: Correct "cardnumber" to "card number" (when refering to the patron's card number, unless it's the database column)
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '25

23 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39455 Bug ID: 39455 Summary: Correct "cardnumber" to "card number" (when refering to the patron's card number, unless it's the database column) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de Bug 38979 changed "cardnumber" to "card number". We should change the instances in the manual also. *Note that if this refers to the database column, it should stay "cardnumber". Here are the occurrences (if you have a local copy of the manual, you can do `git grep "cardnumber"` and it will find all the occurrences of the string in all the files). NOTE: I have not filtered the results! Some should stay as is. administration.rst:| LC-cardnumber | 010$a | administration.rst: either "userid" or "cardnumber" are present in the mappings. administration.rst: If auto register is enabled, make sure the "userid" or "cardnumber" administration.rst: If auto register is enabled, make sure the "userid" or "cardnumber" apis_protocols.rst: <cardnumber is="uid" ></cardnumber> circulation.rst:|selfcheckout-logincardnumber| circulationpreferences.rst:cardnumber is scanned instead of an item barcode. circulationpreferences.rst: This should not be enabled if you have overlapping patron cardnumbers circulationpreferences.rst:- cardnumber circulationpreferences.rst: If using 'cardnumber' and enhancedcontentpreferences.rst:- cardnumber images.rst: :alt: Patron's brief information panel showing the patron's name, cardnumber, address, phone number, date of birth and age, email, category, home library, borrowernumber, date of last update and a message in red reading 'Account has been administratively locked'. Under the patron's information are the patron account tabs: Check out, Details (currently selected), Accounting, Routing lists, Circulation history, Holds history, Modification log, Notices, Statistics, and Purchase suggestions. images.rst: :alt: Patron's brief information panel showing the patron's name, cardnumber, address, phone number, date of birth and age, email, category, home library, borrowernumber, date of last update and a message in red reading 'Account has been locked'. Under the patron's information are the patron account tabs: Check out, Details (currently selected), Accounting, Routing lists, Circulation history, Holds history, Modification log, Notices, Statistics, and Purchase suggestions. images.rst: :alt: Holdings tab in a detailed record in the staff interface, the item is marked as checked out, with the name of the patron, their cardnumber and the due date images.rst: :alt: Warning message 'This item has been claimed as returned by' followed by the name and cardnumber of the patron and a button 'Resolve' images.rst:.. |selfcheckout-logincardnumber| image:: images/circ/selfcheckout/selfcheckout-logincardnumber.png images.rst: :alt: Place hold confirmation screen on the OPAC. Shows the patron's name and cardnumber, the title and author of the item to be placed on hold, a dropdown menu to choose the pickup location, a link to show more options and a button 'Confirm hold' images.rst: :alt: Place hold confirmation screen on the OPAC. Shows the patron's name and cardnumber, the title and author of the item to be placed on hold, a dropdown menu to choose the pickup location, a link to hide options, a date field 'Hold not needed after', an option to place the hold on the next available item or a specific item and a button 'Confirm hold' images.rst: :alt: Place hold confirmation screen on the OPAC. Shows the patron's name and cardnumber, the title and author of the item to be placed on hold, a dropdown menu to choose the pickup location, a link to hide options, a date field 'Hold not needed after', an option to place the hold on the next available item or a specific item, the specific item option is selected, and it is followed by a table of the record's items with the following columns: Copy number which contains the copy number as well as the selection box, Item type, Barcode, Home library, Last location, Collection, Call number, Notes and Information. At the botton of the page is a 'Confirm hold' button. images.rst: :alt: SQL field when creating a report from SQL, in the box, SELECT borrowers.ca is typed and suggestions for borrowers.cardnumber and borrowers.categorycode are displayed koha_spelling_wordlist.txt:cardnumber koha_spelling_wordlist.txt:cardnumbers logspreferences.rst: Enabling this system preference allows the tracking of cardnumber changes opac.rst:Patrons registered in this way will not have a cardnumber until assigned opac.rst:their identity before given a cardnumber and the ability to check items opac.rst:generating cardnumbers before providing them to self registered patrons. opac.rst:and add a cardnumber/barcode. opacpreferences.rst: Remember to use the borrowernumber not the patron's cardnumber for patrons.rst: able to search for any part of the patron's name or cardnumber. patronspreferences.rst:Default: firstname\|middle_name\|surname\|othernames\|cardnumber\|userid patronspreferences.rst:- cardnumber patronspreferences.rst:Default: surname\|cardnumber patronspreferences.rst:.. _cardnumberlength-label: patronspreferences.rst: (i.e., ^,Max'). If 'cardnumber' is included in the reports.rst: For example, to have the suggestion for :code:`cardnumber`, you must type reports.rst: SELECT cardnumber, reports.rst:Koha will automatically generate hyperlinks for any report that contains a borrowernumber, cardnumber, itemnumber or biblionumber. reports.rst:- cardnumber: Check out reports.rst: SELECT CONCAT('<a href=\"/cgi-bin/koha/members/boraccount.pl?borrowernumber=',borrowernumber,'\">', cardnumber, '</a>'), surname, firstname reports.rst: - :code:`cardnumber` - The borrower's barcode number queried from Koha. This is what will be visible to the user and comprise the clickable link. reports.rst:After running a report that contains itemnumbers, biblionumbers and/or patron cardnumbers tools.rst: cardnumber, surname, and all fields you have tools.rst:- Choose to match on 'cardnumber' or 'username' to prevent adding of tools.rst:load in a file of cardnumbers (one per line), choose from a :ref:`list of tools.rst:cardnumbers. tools.rst:Once you have the file loaded or the cardnumbers or borrowernumbers entered click 'Continue.' webservices.rst:This service can be used to embed barcode images into slips and notices printed from the browser, and to embed a patron cardnumber into the OPAC, among other possibilities. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 33304] New: Report schedule form time input element attribute type changed to improve valid time value entry
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '25

23 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33304 Bug ID: 33304 Summary: Report schedule form time input element attribute type changed to improve valid time value entry Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: adam.styles(a)esa.edu.au QA Contact: testopia(a)bugs.koha-community.org Created attachment 148518 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=148518&action=e… report schedule start time input fix Hello community, I offer an enhancement for the task scheduler form: /cgi-bin/koha/tools/scheduler.pl via scheduler.tt The time input element currently has an 'text' value for type attribute. This requires a user to enter a valid time string for any scheduled report manually which is no fun. I have created patch in scheduler.tt that changes the type attribute value from 'text' to 'time' which makes the input of valid time easy. This change leveraged standard web form principles of html5 and would be compatible with any modern browser such as chrome, firefox and safari etc. Patch incoming. Thoughts and feedback invited. Thanks. 8-) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 16791] New: Explanation of callnumber.pl plugin
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '25

23 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16791 Bug ID: 16791 Summary: Explanation of callnumber.pl plugin Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: nengard(a)gmail.com Reporter: eb(a)efdss.org QA Contact: testopia(a)bugs.koha-community.org Perhaps a brief explanation of what callnumber.pl is meant to do would be a useful addition to the manual. I am not certain what its function is, though I discovered that it doesn’t do what I was hoping it would. See bug 13615 for a long winded query. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 29188] New: Expired serial subscriptions can still receive issues
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '25

23 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29188 Bug ID: 29188 Summary: Expired serial subscriptions can still receive issues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org In the manual, it says "If your serial subscription has expired you won’t be able to receive issues." But that is not actually true. Expired subscriptions can still generate new issues and you can still receive them. To stop a subscription from generating new issues, you have to close it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 31638] New: [DOCS] Log viewer - Expand section and add descriptions for objects and actions
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '25

23 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31638 Bug ID: 31638 Summary: [DOCS] Log viewer - Expand section and add descriptions for objects and actions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org In the manual, there is currently no description or information about how to use the objects and action fields in the log viewer. The section could also be expanded. Resources to help with this: - SQL Reports Library. https://wiki.koha-community.org/wiki/SQL_Reports_Library#action_logs - ByWater Solutions. Monday Minutes : Using the Logs. 18 January 2021. https://bywatersolutions.com/education/to-log-or-not-to-log - Mailing list thread: https://lists.katipo.co.nz/pipermail/koha/2022-September/058489.html Manual reference: https://koha-community.org/manual/22.11/en/html/tools.html#log-viewer -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 30618] New: Important and mandatory select fields not highlighted on additem.pl
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30618 Bug ID: 30618 Summary: Important and mandatory select fields not highlighted on additem.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If one tries to add an item and mandatory or important select field isn't filled, field isn't highlighted like input fields. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3