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

[Bug 34482] New: Improve MARC21 7xx linking fields in bibliographic records [Omnibus]
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '26

07 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34482 Bug ID: 34482 Summary: Improve MARC21 7xx linking fields in bibliographic records [Omnibus] Change sponsored?: --- Product: Koha Version: 22.11 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 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 30295] New: Send a notification when a recall is manually cancelled
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30295 Bug ID: 30295 Summary: Send a notification when a recall is manually cancelled 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 The process would be: 1. Recall is cancelled by library staff or the requester. 2. Notification of the recall cancellation is sent via email and SMS to the recall requester. So it would be exactly the same as the HOLD_MANUAL_CANCEL notice that we currently have for reserves, only relevant to recalls. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 111

[Bug 34460] New: Patron category should regulate if account can have permissions
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34460 Bug ID: 34460 Summary: Patron category should regulate if account can have permissions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Permission management would be simpler if there were a setting in patron categories that indicate whether that category of patron can have permissions. - If no, that option would not appear in the patron menu. - If patron category is changed to a category that does not allow permissions, any existing permissions should be cleared when change is saved. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 33711] New: Refine the token passing mechanisms introduced in bug 23336
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33711 Bug ID: 33711 Summary: Refine the token passing mechanisms introduced in bug 23336 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: martin.renvoize(a)ptfs-europe.com CC: koha-bugs(a)lists.koha-community.org, tomascohen(a)gmail.com Depends on: 23336 Bug 23336 introduces an API workflow for checkouts by adding two endpoints.. one for availability that creates a token for confirmations that can then be used by the checkouts endpoint to verify that availability has been checked. Whilst I think the availability endpoint is worthwhile in it's own right, I think we could also send back the token in the 409 pre-condition failed response of the checkouts endpoint so one could use that single endpoint for double duty in the right circumstances. I also think we could work on how the confirmation token is sent to the endpoint.. it's currently a simple query param but may lend itself to being part of the x-koha-overrides header or another header? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23336 [Bug 23336] Add an API endpoint for issuing an item to a patron -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. You are on the CC list for the bug.

1 10

[Bug 31099] New: [DOCS] Export data tool - setup so database and configuration data can be downloaded
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31099 Bug ID: 31099 Summary: [DOCS] Export data tool - setup so database and configuration data can be downloaded 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 Add information to the manual on how to set up Tools > Export data so that the database and configuration backups are enabled and shown. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 30657] New: Make patron attributes available via Template Toolkit in overdues
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30657 Bug ID: 30657 Summary: Make patron attributes available via Template Toolkit in overdues 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When using Template Toolkit to fetch patron values, one should be able to fetch patron attribute values. This would be useful both for printing those values into the notice content and for using those values in logic to vary the notices per patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 103

[Bug 24483] New: When batch deleting patrons, report who was not deleted and why
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24483 Bug ID: 24483 Summary: When batch deleting patrons, report who was not deleted and why Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When using the batch patron deletion tool, patrons are not deleted if: - They have current checkouts - They have a non-zero balance - They are the guarantor to another patron - They are of a patron category of type staff But Koha never specifically tells the user which borrowers out of their defined pool for deletion are not deleted or why. To test: - Create a patron list - Add to that list one patron for each of these conditions: -- one patron with an item checked out -- one patron with a non-zero balance -- one patron who is a guarantor -- one patron in a staff category -- one patron not meeting any of the conditions above - Go to batch patron deletion, attempt to delete all patrons on your list - Koha tells you 1 patron will be deleted Ideally, Koha would give a list of which patrons will not be deleted and why. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 19037] New: Circulation and fine rules test tool
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19037 Bug ID: 19037 Summary: Circulation and fine rules test tool Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Add a test tool for circulation and fine rules. The point of the tool is to display the effective issuing rule that matches item, patron and branch. Add a REST API endpoint to query effective issuing rules by given parameters. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 78

[Bug 18783] New: Allow automatic claims for serials
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18783 Bug ID: 18783 Summary: Allow automatic claims for serials Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Serials Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com -- You are receiving this mail because: You are watching all bug changes.

1 53

[Bug 32636] New: More info with batch patron deletion
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32636 Bug ID: 32636 Summary: More info with batch patron deletion 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org When batch deleting patrons, it tells you how many patrons will be deleted. It would be great if it also told you how many patrons fit your parameters, but are being skipped because they have active loans or fees. Better yet, if that piece of information could link to a report showing which patrons are skipped and why, that would even be helpful. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4