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

[Bug 33222] New: Checkin message does not display when book is overdue and borrower has manual restriction
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '25

22 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33222 Bug ID: 33222 Summary: Checkin message does not display when book is overdue and borrower has manual restriction Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: janet.mcgowan(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Overview: When a borrower with a manual restriction returns an overdue item the returns.pl page displays the checked in items table showing the summary of returned items but there is no Check in message displayed indicating that the borrower has a restriction. If the same restricted patron returns an item that is not overdue you see the Check in message indicating "Reminder: Patron has an indefinite restriction." (or Reminder: Patron was earlier restricted until 31/03/2023. - if the patron is restricted to a specific date). Steps to Reproduce: User has 1 overdue item (I used special due date to set to date in the past) and 1 item that is not overdue. Create a restriction on the patron record - e.g. indefinite restriction. Return the item that is not overdue - Checkin message shows "Reminder: Patron has an indefinite restriction." Return the item that is overdue - no Checkin message displays. Expected results: the Checkin message showing that a patron is restricted should display when returning an overdue book. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 39913] New: Fully delete patrons when removing due to refused GDPR consent
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '25

21 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39913 Bug ID: 39913 Summary: Fully delete patrons when removing due to refused GDPR consent Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 21336 When cleanup_database deletes patrons based on the PatronRemovalDelay system preference, it sends those patrons to the deleteborrowers table. It seems like it would be more in keeping with user/patron expectations to fully delete those borrowers, skipping deletedborrowers entirely. We're looking at developing a feature for recovering borrowers from deletedborrowers, and we definitely would not want to allow restoration of patrons who declined GDPR consent. That'd be easier to avoid if we just delete them entirely in the first place. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21336 [Bug 21336] GDPR: Handle unsubscribe requests automatically by optional (administrative) lock, anonymize and remove -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 24260] New: REST Self Registration
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '25

21 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24260 Bug ID: 24260 Summary: REST Self Registration Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi Support self registration via REST API -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 30299] New: Create a Registration API to allow for use of email verification when outside systems are registering patrons
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '25

21 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30299 Bug ID: 30299 Summary: Create a Registration API to allow for use of email verification when outside systems are registering patrons Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com CC: tomascohen(a)gmail.com Some discovery systems (Aspen for instance) provide a self registration function. Currently the Koha preference 'PatronSelfRegistrationVerifyByEmail' cannot be utilized via the API. We propose to add two endpoints: 1 - Registration - This will take a borrower object, verify the required/unwanted fields, and create a patron modification request as on 'opac-memberentry.pl' when verification is enabled - The endpoint will take an option to send/suppress the email from Koha so that integrating systems may generate their own - The endpoint will take an optional return URL to be passed through when generating the verification email so the outside system can handle the verification - The endpoint will return the verification token 2 - Verification - The endpoint will accept the token generated above and complete patron creation as in opac-registration-verify.pl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 38693] New: dedup_authorities.pl - Add methods match-subfield and get-subfield
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '25

21 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38693 Bug ID: 38693 Summary: dedup_authorities.pl - Add methods match-subfield and get-subfield Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: olli-antti.kivilahti(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Enables choosing the authority record with the biggest 001 --method="get-subfield=001" Enables choosing the authority record from a specific cataloguing source --method="match-subfield=040.a=FI-NL" With this combination authority records from a national authorities repository can be merged to unofficial local authorities, while also overwriting duplicate old records from the same source. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 37625] New: Update HoldsNeedProcessingSIP system preference description
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '25

21 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37625 Bug ID: 37625 Summary: Update HoldsNeedProcessingSIP system preference description Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The HoldsNeedProcessingSIP is very useful for libraries using SIP, but the system preference description doesn't tell you much. It would be nice to add some more information here about the intermediate status that will be assigned when you set it to "not fulfill" holds immediately. Also "returning" should be updated to "checking in". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 33703] New: Bug in Date of Birth Field Entry
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '25

21 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33703 Bug ID: 33703 Summary: Bug in Date of Birth Field Entry 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: kkrueger(a)cuyahogalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 150894 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=150894&action=e… DateNoSlash_1 Description: When using the Koha Date of Birth field to add a new patron, entering a date without punctuation (/ or -) causes the date to change to an incorrect date. Steps to reproduce: 1. From Koha Patron module > add new patron > patron identity section, Date of birth field, enter a birthdate for 24 May 1964 as 05241964 (DateNoSlash_1.png) manually. 2. Tab or hit enter, and the birth date that is recorded changes to 06/10/1964 or June 10 1964 (DateNoSlash_2.png). Similar behavior happens whenever the date is entered without punctuation. Expected Results: If data is entered in this field without slashes or hyphens, the slashes would be input without changing the intended date. Suggesting here a correction to correctly assign birthdates as entered with or without punctuation. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 120

[Bug 40200] New: Add an ERM data tab to the catalog detail page
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '25

21 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40200 Bug ID: 40200 Summary: Add an ERM data tab to the catalog detail page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: clemens.tubach(a)kit.edu, jonathan.druart(a)gmail.com, jonathan.field(a)openfifth.co.uk, martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, michaela.sieber(a)kit.edu, pedro.amorim(a)openfifth.co.uk When looking at the detail page in the staff interface catalog, we should have have a tab to display information from the ERM module. For example we could display in a little table: - Packages the title is linked to (via erm title - erm resource) - Maybe license information - Maybe agreement information And provide links to these so you can navigate there easily if you have the required permissions. This would allow to tie the catalog and the ERM module closer together. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 38212] New: Optionally allow lost items to fill holds (or not)
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '25

20 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38212 Bug ID: 38212 Summary: Optionally allow lost items to fill holds (or not) Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: catrina(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some Partners would like the ability to exclude Lost items from making holds available, similar to the AllowHoldsOnDamagedItems system preference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 40357] New: Notices and Slips library selection
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '25

20 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40357 Bug ID: 40357 Summary: Notices and Slips library selection Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Currently, if a group of libraries out of the entire selection of libraries need to customize a slip or notice, you have to create a template for each library. It would be more efficient if the templates applied to selected libraries in the template, much like we do for other things in Koha (like attributes). Obviously it would cause issue if more than one copy of a particular template had the same library selected in both, so we could have Koha refuse to save the template with the offending duplicate library if detected. If that were the case, it would need to show which library is being used in a similar template, and which template. The editor could then either give the option to save without the offending libraries, or an option could be given to remove the offending libraries from the other template(s). This workflow would allow us to maintain less templates, and not have to duplicate so much work. Thoughts? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5