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

[Bug 34459] New: Log in MARC record if the record was brought in via z39.50
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '25

31 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34459 Bug ID: 34459 Summary: Log in MARC record if the record was brought in via z39.50 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl For some libraries, it would be helpful to be able to report on and find what records are being brought in via a z39.50 search. If a value or indication could exist in the record, this would be easy for libraries to identify and find. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 30961] New: Table Settings Reports table_reports Group and Subgroup does not work
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '25

31 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30961 Bug ID: 30961 Summary: Table Settings Reports table_reports Group and Subgroup does not work Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In Admin - Table Settings - Reports - table_reports, the Group and Subgroup checkboxes do not hide the respective column in the saved reports page. The Group and Subgroup columns can be hidden from the saved reports page by using the Column Config option there, but they need to be able to be hidden from the Table Settings function. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 32776] New: Choose to convert oldest reserve or all possible reserves to recalls
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '25

31 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32776 Bug ID: 32776 Summary: Choose to convert oldest reserve or all possible reserves to recalls 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 31415 introduces a script to convert reserves to recalls. By default, it will take the oldest reserve on a record and convert it to a recall. We should be able to customise which reserve(s) are converted to recalls. Options may include: - oldest reserve - one reserve for each issued item available to be recalled -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 31415] New: Script to automate converting reserves to recalls
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '25

31 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31415 Bug ID: 31415 Summary: Script to automate converting reserves to recalls 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a record reaches X number of reserves, the library may convert reserves to recalls to prompt patrons to return them sooner. This can be automated with a script. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 35665] New: Should secondary email address be allowed to be used as a CC in notices?
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '25

30 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35665 Bug ID: 35665 Summary: Should secondary email address be allowed to be used as a CC in notices? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org I would say yes to this. Maybe have a checkbox next to the secondary email field to cc notices to this address. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 35320] New: Deleting a patron doesn't use AnonymusPatron to anonymize the circulation history
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '25

30 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35320 Bug ID: 35320 Summary: Deleting a patron doesn't use AnonymusPatron to anonymize the circulation history Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: noemie.labine(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org I was under the impression that when AnonymousPatron is filled with a borrowernumber, deleting a patron (individually or with batch deletion tool) would anonymize their circulation history using AnonymousPatron, but it doesn't. After deleting a or some patrons, the circulation history in the book record shows blank spaces in lieu of the patrons. It would make more sens that when deleting a patron using the batch deletion tool or the delete button in a patron's page, the AnonymousPatron is used to fill the circulation history of the deleted patrons. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 33481] New: EBSCO ws return 415: Content type 'application/octet-stream' not supported
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '25

30 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33481 Bug ID: 33481 Summary: EBSCO ws return 415: Content type 'application/octet-stream' not supported Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Depends on: 32030 ERROR - EBSCO API /vendors/19/packages/3816 returned 415 - Content type 'application/octet-stream' not supported [ERROR] PATCH /api/v1/erm/eholdings/ebsco/packages/19-3816: unhandled exception (Mojo::Exception)<<ERROR requesting EBSCO API /vendors/19/packages/3816 code 415: Content type 'application/octet-stream' not supported>> Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32030 [Bug 32030] Electronic resource management (ERM) -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 30085] New: Improve performance of CanItemBeReserved
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '25

30 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30085 Bug ID: 30085 Summary: Improve performance of CanItemBeReserved 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 30287] New: Notices using HTML renders differently in notices.pl
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '25

30 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30287 Bug ID: 30287 Summary: Notices using HTML renders differently in notices.pl Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org When HTML is switched on for notices (e-mail), it renders differently between the editor, the actual e-mail, and the preview in notices.pl. First, if you don't use <br/> at the end of lines, everything is smushed together in the e-mail. But in notices.pl, it shows the way it was put in the editor. If you use <br/>, it renders correctly in the e-mail, but will show your regular line breaks and the <br/>, spacing everything out weird. It is a real trick trying to properly format an e-mail with html and have it look good everywhere. I think the line breaks are being coded weird. It would sure be nice to have an html editor for the notices, if you turn html on. At the very least, I would like to see more consistency between the three. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 81

[Bug 28656] New: Cancellations should be allowed on paid/partially paid debts
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '25

29 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28656 Bug ID: 28656 Summary: Cancellations should be allowed on paid/partially paid debts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be helpful to be able to still cancel a debt, even if it's already been partially or fully paid or written off. If we update the method to allow this case, we can then use it internally for the refund of lost items found debts and other such use cases... see bug 27946 for such a case. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 39