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

[Bug 27785] New: Point of sale needs a note field
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '26

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27785 Bug ID: 27785 Summary: Point of sale needs a note field Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org In the patron account, when making a payment, you have a note field. This note field was left off the Point of sale interface. This is REALLY NEEDED. We have a payment type of Check that we offer because, we accept checks. It is this note field where we record the check number. WE REALLY NEED THIS NOTE FIELD! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 40308] New: New Perl Class (Koha::ExternalContent::OCLC) for integrating with OCLC's APIs
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '26

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40308 Bug ID: 40308 Summary: New Perl Class (Koha::ExternalContent::OCLC) for integrating with OCLC's APIs Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: a.roussos(a)dataly.gr QA Contact: testopia(a)bugs.koha-community.org Background information ---------------------- OCLC recently [1] started offering a Linked Data (LD) [2] API [3] that allows looking up Dewey Decimal Classification (DDC) numbers [4] in order to obtain unique URIs/URLs and Descriptions for a particular DDC (or range). In addition to API searches, a smaller subset of the LD can also be browsed online in a hierarchical manner [5]. This is just one from a large set of APIs offered by OCLC [6]. Reasoning behind this Bug report -------------------------------- We believe that Koha users who include DDC numbers in their authority cataloguing would benefit from an integration with the OCLC Dewey LD API that would allow them to easily look up DDCs in exchange for LD URIs/URLs and Descriptions. To this end, we propose the addition of a new Perl Class that will offer this functionality (Koha::ExternalContent::OCLC). Initially, the class will offer functions for issuing API access tokens and for looking up DDC URIs/URLs and Descriptions on the Dewey LD API. In the future, more code be added to the class to allow for integration with more OCLC APIs. This Bug report will also include a command-line tool that will enable users to update their authorities with OCLC Linked Data en masse, useful for authority records that already contain DDC information. Three new authority Framework plugins that will use the functions offered by the new Perl Class will be added as separate Bug reports. These offer the ability to look up DDCs with a single mouse click while inside the Authorities module cataloguing editor. Finally, we propose the addition of four new System Preferences that control the integration with the OCLC Dewey Linked Data API, namely: - OCLCAPIWSKeyClientID: Stores the client ID component of your OCLC API WSKey - OCLCAPIWSKeyClientSecret: Stores the client secret component of your OCLC API WSKey - OCLCDeweyLinkedDataAPI: Basically an On/Off "switch" for the lookup service - OCLCDeweyLinkedDataLanguage: Sets the language of the DDC description to be fetched References: [1] https://www.oclc.org/en/news/releases/2024/20240815-uniform-resource-identi… [2] https://www.oclc.org/en/linked-data.html [3] https://developer.api.oclc.org/dewey-ld [4] https://www.oclc.org/content/dam/oclc/dewey/versions/print/intro.pdf [5] https://entities.oclc.org/worldcat/ddc/ [6] https://www.oclc.org/developer/api/oclc-apis.en.html -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 40489] New: "Sort this list by" has different options for "Private" lists vs "Public" lists
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '26

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40489 Bug ID: 40489 Summary: "Sort this list by" has different options for "Private" lists vs "Public" lists Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Most of the options are the same but "Private" lists has "Copyrightdate" while "Public" lists have "Publication year". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 40312] New: Lists are not sortable
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '26

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40312 Bug ID: 40312 Summary: Lists are not sortable Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: T.Reimann95(a)gmx.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To verify: In staff client, create a list with several items and display it. CLick on a title of a column. Actual Results: no changes Expected Results: The column and the table is sorted Additional Information: started after update on 25.05 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 17772] New: Allow to sort lists by date the record was created
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '26

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17772 Bug ID: 17772 Summary: Allow to sort lists by date the record was created Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Lists in OPAC and staff can be sorted by different fields. It would be nice if we could offer 'date created' as an additional option for sorting. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 39557] New: Normalize MARC21 XML metadata into structured MySQL database tables via Koha Plugin
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '26

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39557 Bug ID: 39557 Summary: Normalize MARC21 XML metadata into structured MySQL database tables via Koha Plugin Change sponsored?: --- Product: Koha Version: Main 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: koha(a)trust-box.at QA Contact: testopia(a)bugs.koha-community.org The proposed plugin (Koha::Plugin::HKS3::NormalizeMARC2DB) aims to normalize MARC21 XML metadata from the biblio_metadata.metadata table into structured MySQL database tables. Currently, MARC21 XML is stored as a single XML blob, making advanced querying, reporting, and integration difficult. This plugin introduces an automatic normalization step triggered by the after_biblio_action hook whenever metadata is added or modified. It splits MARC XML into normalized relational tables fully supporting repeatable fields, subfields, and indicators. Advantages: Significantly simplifies complex querying and reporting of MARC21 data. Enhances data integrity and consistency. Facilitates integration with external reporting tools, analytics, and applications. Improves database performance for MARC metadata queries. Provides clear and structured access to MARC data elements. This approach aligns with best practices for database normalization and can substantially enhance Koha's extensibility and interoperability. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 39732] New: Remove MarcRecordFromNewSuggestion from C4/Suggestions.pm
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '26

26 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39732 Bug ID: 39732 Summary: Remove MarcRecordFromNewSuggestion from C4/Suggestions.pm Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23990 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 41371] New: Title should be recorded to accountlines.description when expired reservation fee is created
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '26

26 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41371 Bug ID: 41371 Summary: Title should be recorded to accountlines.description when expired reservation fee is created Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: anni.maki-mantila(a)turku.fi QA Contact: testopia(a)bugs.koha-community.org Currently when expire_holds.pl cron creates an expired reservation fee, the description in accountlines-table is left blank. If the biblio title would be saved to description field, we could use it in ACCOUNT_PAYMENT and ACCOUNT_WRITEOFF -notices. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 37829] New: Allow additional fields for bookings
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '26

26 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37829 Bug ID: 37829 Summary: Allow additional fields for bookings Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.derscheid(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Directly from LMSCloud's requirements: > As a Koha library, we want to be able to use configurable additional fields for bookings in order to enable patrons to provide additional information with bookings like the persons who need to be informed when the material is available or a contact person of the institution. > The additional fields will be editable and stored with the booking and should be also available in booking notifications. I think this is interesting because these use-cases seems like a perfect fit for the bookings feature. For example when working with schools or something of the like. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 39872] New: Patron club holds - autocomplete does not work
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '26

26 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39872 Bug ID: 39872 Summary: Patron club holds - autocomplete does not work Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When placing a hold for a patron club, the autocomplete for the patron club does not work in the same way that searching for a patron does. The text on the clubs tab says "Enter club ID or partial name". I would expect this to work the same way or similar to the patron autocomplete. What happens instead: 1. If there is only one club that matches, the hold details page is populated with the club details and members. 2. If there is more than one matching club, or you press search without any search text, it lists the available clubs. To replicate: 1. Create a patron club: 1.1 Go to Tools > Patrons and circulation > Patron clubs 1.2 Add a club template: . + New club template . Name: BOOK . Description: Template for book clubs . Save 1.3 Add a club: . + New club > BOOK . Name: SCIFI . Description: Science fiction book club . Save 2. Add a patron to the club: 2.1 Go to a patron's record, for example Mary Burton 2.2 Go to Details > Clubs tab 2.3 Click + Enroll for the SCIFI club 2.4 Click Finish enrollment to complete the enrollment 3. Place a hold for a club: 3.1 Go to any record with items, for example 'The hydrogen sonata' (biblionumber = 333) 3.2 Place a hold: Place hold 3.3 Click the clubs tab 3.4 Note that the instructions say "Enter club ID or partial name" 3.5 Start typing science or sci 3.6 Note that no values are shown, like search for a patron name does on the patrons tab 3.7 Click search 3.8 Since there is only one club, it populates the hold details page and lists the club members 3.9 Note that if you don't type anything and click search, you get a list of all clubs to choose from -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2