June 2026 - Koha-bugs - lists.koha-community.org

[Bug 42753] New: item-api-client.js: items.get() should accept headers parameter instead of hardcoding x-koha-embed
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42753 Bug ID: 42753 Summary: item-api-client.js: items.get() should accept headers parameter instead of hardcoding x-koha-embed Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com ItemAPIClient.items.get(id) hardcodes x-koha-embed: '+strings' in the request headers. This should be passed through from the caller (like getAll already does) so different consumers can request different embeds. Current: get: id => this.httpClient.get({ endpoint: 'items/' + id, headers: { 'x-koha-embed': '+strings' }, }), Should be: get: (id, params = {}) => this.httpClient.get({ endpoint: 'items/' + id, ...params, }), Callers that need +strings would pass it explicitly: APIClient.item.items.get(id, { headers: { 'x-koha-embed': '+strings' } }) This follows the same pass-through pattern used for bundled_items.add(). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 42758] New: Resending notices needs more information
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42758 Bug ID: 42758 Summary: Resending notices needs more information Initiative type: --- Sponsorship --- status: Product: Koha Version: Main 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 CC: martin.renvoize(a)openfifth.co.uk When you resend a notice, the only change to the information on the notice is the updated column. This does not show any reason for the resend or how many times it is resent, or if anything changed from the last time (like the address). It would be helpful if resends were nested and showed the address it was sent to for each attempt. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 42712] New: Error when making a suggestion with only the suggestions_create permission
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42712 Bug ID: 42712 Summary: Error when making a suggestion with only the suggestions_create permission Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org TO recreate: 1. Setup a staff user with suggestions_create but none of the other permissions for suggestions. 2. Go to suggestion/suggestion.pl and create a new suggestion/ 3. Once the suggestion is submitted your are redirected back to suggestion/suggestion.pl and will see a pop-up: "Something went wrong when loading the table. 200: OK. " -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 41997] New: Default suggester is not passed by the suggestion creation form
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41997 Bug ID: 41997 Summary: Default suggester is not passed by the suggestion creation form Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Steps to reproduce, only on main. 1 - Open a form creation suggestion. 2 - With code explorer, notice that there is: <input type="hidden" id="suggestedby" name="suggestedby" value="" /> in the code 3 - Apply patch 4 - With code explorer, notice that there is: <input type="hidden" id="suggestedby" name="suggestedby" value="51" /> in the code 5 - Submit form, notice the suggester is properly written -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 34134] New: When viewing an authority details page the search bar is defaulted to the current records authority type
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34134 Bug ID: 34134 Summary: When viewing an authority details page the search bar is defaulted to the current records authority type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This was true in previous versions, but is less visible now. To recreate: 1 - Search authorities for "John" 2 - Click on "Uniform title: Jack Johnson" 3 - View the details page, ooooh 4 - Decide to search for John again 5 - This time you get one result? 6 - Click the settings in the search box 7 - Note you have been defaulted to 'Uniform title' authority type -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 18583] New: Add the ability to merge multiple authorities
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18583 Bug ID: 18583 Summary: Add the ability to merge multiple authorities Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Since bug 8064 it is possible to merge multiple bibliographic records at once, it would be nice to be able to do the same thing with authority records. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 42266] New: Spelling: URL is an abbreviation
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42266 Bug ID: 42266 Summary: Spelling: URL is an abbreviation Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Keywords: Academy Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Found while translating: Url: %s koha-tmpl/intranet-tmpl/prog/en/modules/admin/usage_statistics.tt:217 -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 37557] New: Hiding whole fields in MARC bibliographic frameworks
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37557 Bug ID: 37557 Summary: Hiding whole fields in MARC bibliographic frameworks Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bibliotheca(a)klastervyssibrod.cz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I based a new MARC bibliographic framework on the default one and don´t need most of the fields there, but do not want to delete them, because it´s possible that I´ll want to use them in the future, so I would rather just hide them. But unluckily it´s only possible to hide the subfields one by one and the whole field disappears only after I hid all of the corresponding subfields - which takes very much time to do and is pretty tedious. So what I suggest is to make it possible to hide whole fields in a MARC bibliographic framework with one click (or even to be able to select more of them at once and then hide them all) without having to hide all the subfields one by one first. (By hiding I mean to uncheck all the visibility options by a subfield, or to check the "Flagged" option there.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 42752] New: Add additional patron cardnumber generation strategies to Koha::AutoNumber
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42752 Bug ID: 42752 Summary: Add additional patron cardnumber generation strategies to Koha::AutoNumber Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Bug 22707 introduced Koha::AutoNumber, a generic strategy framework for patron cardnumber (and future item barcode) generation. The framework is designed to be extended by adding new Koha::AutoNumber::* subclasses that override _next_from() and, where needed, db_max(). Three additional strategies have been identified as useful for Koha libraries: 1. Codabar / CLSI The traditional North American library card standard. 14-character format with a Codabar check character. Many libraries still hold physical card stock in this format. Algorithm::CheckDigits supports Codabar, making the implementation straightforward. 2. Prefixed sequential A fixed text prefix followed by a zero-padded sequential counter, e.g. 'LIB0001234' or 'BRANCH001'. Useful for libraries that issue staff cards, student IDs, or branch-coded patron identifiers. Would require one additional system preference for the prefix string. 3. Annual sequential A year prefix followed by a sequential counter, e.g. '2026001234'. Mirrors C4::Barcodes::annual for item barcodes. Useful for academic libraries that issue cohort-coded patron cards. Each strategy is a self-contained subclass; no schema changes are required. Strategies can be implemented and submitted independently. See also: Bug 22707 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 19958] New: Allow the system preference AutoMemberNum to include a combination of numbers and letters when creating a new barcode
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19958 Bug ID: 19958 Summary: Allow the system preference AutoMemberNum to include a combination of numbers and letters when creating a new barcode Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently the system preference "automembernum" only allows for the patron's barcode to default the card number field on the patron addition screen to the next available card number (for example, if the largest currently used card number is 26345000012941, then this field will default to 26345000012942). It would be nice for the library to choose the format of the barcode (for example : system preference autobarcode). Then a library could choose to include letters and numbers to their patron's barcode instead of just numbers. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6