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

[Bug 28863] New: Cancel a Pending Notice
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '26

12 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28863 Bug ID: 28863 Summary: Cancel a Pending Notice 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: rcoert(a)arlingtonva.us QA Contact: testopia(a)bugs.koha-community.org We would like the ability to cancel any notice that is currently "Pending" on the Notices tab in a user's account. Also, a record of which librarian cancelled the notice and date/time stamp would be very useful. Use Case: Item is discharged, hold is trapped, & notice is generated. Staff then realizes that the item is badly damaged and reverts the hold to obtain another copy. However, the notice for the original item is now Pending in the account and the email will be sent - even though the item is not on the Hold Shelf. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 32630] New: Don't delete ILL requests when patron is deleted
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '26

12 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32630 Bug ID: 32630 Summary: Don't delete ILL requests when patron is deleted Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de CC: magnus(a)libriotech.no, martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com There is a FK constraint, that makes it so that when a patron is deleted, the ILL requests linked to the account are deleted as well. This can potentially cause a number of problems: * ILL requests deleted could be pending, in shipment etc. You will have no audit track if there are any problems with transport etc. * You won't be able to do reliable statistics on number of ILL requests etc. especially since adding a request is not even logged. I propose that instead of removing the borrowernumber, we either * leave it * set it to NULL Would love to get some input on this one! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 48

[Bug 23524] New: Can modify/delete funds for locked budgets
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '26

11 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23524 Bug ID: 23524 Summary: Can modify/delete funds for locked budgets Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org What are the allowed actions for a locked budget? Should it be read only? To recreate: 1 - From acqui home click on a budget 2 - Edit the budget and lock it 3 - on admin/aqbudgets.pl notice all funds have an action button 4 - You cannot add, but the button is not disabled 5 - You can modify 6 - You can delete -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 21303] New: XSLT should look in LDR/18 to know whether to add punctuation or not
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '26

11 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21303 Bug ID: 21303 Summary: XSLT should look in LDR/18 to know whether to add punctuation or not Change sponsored?: --- Product: Koha Version: master 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I noticed the XSLT sometimes adds or removes punctuation. If the cataloguers already add the punctuation while cataloguing, this causes double punctuation or no punctuation at all where there should be. For instance, I have a record where there is a period (.) at the end of 100$e. So in MARC, it looks like 100 1# a Goscinny, René, d 1926-1977-, e author. In intranet details, it looks like Goscinny, René, 1926-1977- [author.]. There are two periods (and no comma after the date). In the 260 field, the opposite happens. There is a period at the end of 260$c in MARC, but nothing is appearing in intranet results. 260 ## a Paris : b Gallimard jeunesse, c [2014]. In the intranet details, it looks like Paris : Gallimard jeunesse, [2014] There is no period after the date. MARC21 has a code in LDR/18 to indicate whether or not punctuation has been included in the cataloguing. XSLT should obey this code to determine if it should add punctuation or not. LDR/18 possible codes # - Non-ISBD a - AACR2 c - ISBD punctuation omitted i - ISBD punctuation included n - Non-ISBD punctuation omitted u - Unknown -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 30529] New: Allow all item fields to be set in MARCItemFieldsToOrder
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '26

10 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30529 Bug ID: 30529 Summary: Allow all item fields to be set in MARCItemFieldsToOrder Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The MARCItemFieldsToOrder syspref allows values for a set list of item/order fields to be sent in MARC file used in acquisitions. We should broaden that out to include any item field to support a broader array of workflows. Bug 24334 already suggested adding barcode, but I see no reason not to take that idea further. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 24968] New: Add Syspref controls for cronjobs
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '26

10 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24968 Bug ID: 24968 Summary: Add Syspref controls for cronjobs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 At the simplest it would be nice to have an on/off switch for any cronjob so that libraries can disable cronjobs as needed (during emergency closings etc.) At the most advanced, it could offer the option of controlling all of the parameters for the cronjob, either using a syntax or a new administration area -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 20028] New: Export all petron related personal data in one package
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '26

10 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20028 Bug ID: 20028 Summary: Export all petron related personal data in one package 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: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, josef.moravec(a)gmail.com, katrin.fischer(a)bsz-bw.de, kyle.m.hall(a)gmail.com, magnus(a)libriotech.no, mirko(a)abunchofthings.net, paul.poulain(a)biblibre.com, rbit(a)rbit.cz Blocks: 18081 At least in CVS, maybe in JSON or other machnine readable formats. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18081 [Bug 18081] [omnibus] GDPR (General Data Protection Regulation) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 88

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

10 Feb '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 54

[Bug 27176] New: Using z39.50 with Advanced Editor if fields are out of order, they also display out of order
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '26

10 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27176 Bug ID: 27176 Summary: Using z39.50 with Advanced Editor if fields are out of order, they also display out of order Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: minor 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 When a library uses the z39.50 search through the Advanced editor and imports a record that has marc fields out of order, such as having a 700 field listed first, followed by the 245, then the 008. Importing this record will display the fields out of order in the advanced editor. There is no easy way to re-order these fields in the advanced editor module, but it can be done through the clipboard. Using the basic editor, importing the same file with fields out of order will import correctly. If this record is saved, and then re-opened in the Advanced Editor, the fields are ordered correctly. It would be convenient and consistent to have fields ordered when importing a record through both the advanced editor and the basic editor. A workaround to the library that has imported (through the Advanced Editor) one of these records that have marc fields out of order. Once this record has been saved to Koha, reopened in the Basic Editor, and then opened through the Advanced Editor- the fields will be in the correct order. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 28849] New: Claim Returned should alert at checkout
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '26

10 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28849 Bug ID: 28849 Summary: Claim Returned should alert at checkout Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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: 14697 When checking out an item connected to an unresolved claim, we should alert the user just as we do at checkin. To recreate: - Set ClaimReturnedLostValue - set MarkLostItemAsReturned so that claimed items are marked as returned - check an item out to Patron A - mark that item claimed - check the item out to Patron B - Koha alerts you that it's removed the lost status, but not that there is an unresolved claim - set MarkLostItemAsReturned so that claimed items are NOT marked as returned - mark item as claimed on Patron B's account - check the item out to Patron C - Koha alerts you that the it's removed the item's lost status and asks if you want to end Patron B's checkout, but does not mention the 2 unresolved claims - check the item in - Koha gives a return-claim dialog alert with links to Patron A and Patron B We should give the same alert at checkout, since that's the moment at which Koha first knows this item has been found. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14697 [Bug 14697] Extend and enhance "Claims returned" lost status -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2