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

[Bug 38638] New: Offer the option to set non-priority option when placing multiple holds
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '26

11 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38638 Bug ID: 38638 Summary: Offer the option to set non-priority option when placing multiple holds Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 22789 When placing multiple holds in the staff interface there isn't an option to set the holds as non-priority. As far as I know there's not a technical reason not to include the option? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22789 [Bug 22789] Establish non-priority holds -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 36135] New: Add tool to batch edit pick up dates of holds
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '26

11 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36135 Bug ID: 36135 Summary: Add tool to batch edit pick up dates of holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There are sometimes situations where libraries have to extend their holds pick up dates. We should at same kind of tool for this like "Batch extend due dates". However criteria for dates to extend can be complicated (we've excluded e.g. items with specific state, holds with found status, items on transfer to specific library). So rather than using predefined criteria for holds to edit (at least for the start), tool should have option to upload file of SQL query results. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 269

[Bug 39208] New: printoverdues.sh requires unavailable cli tool
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '26

11 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39208 Bug ID: 39208 Summary: printoverdues.sh requires unavailable cli tool Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexander.wagner(a)desy.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz `printoverdues.sh` relies on `xhtml2pdf` for the conversion of a HTML document to a printable PDF version of said document. At time of writing, this tool dropped out of Debian (bookworm) and Ubuntu stable and sometimes older releases including backports and the like. Debian oldstable still keeps it, but no upstream releases beyond. This may endanger the functionality in Koha upstream. Possible solutions: - Manual installation outside the package management (and bugfixing) of the distribution via `pip`. That would also require a suitable documentation. - Use an alternative tool chain within the distributions (e.g. pandoc, if heading for a swiss army knife of format transformations. For PDF pandoc would require latex as "helper"). Note that `printoverdues.sh` is referred to explicitly in the implementation checklist. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 35246] New: REST API: api/v1/biblios crashes with accept header application/json
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '26

11 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35246 Bug ID: 35246 Summary: REST API: api/v1/biblios crashes with accept header application/json Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl CC: tomascohen(a)gmail.com See also bug 33960. Found it testing there. [2023/11/03 10:33:00] [ERROR] GET /api/v1/biblios: unhandled exception (Mojo::Exception)<<Can't call method "to_api" on an undefined value at /usr/share/koha/Koha/Biblio.pm line 1433.>> => my $json_biblioitem = $self->biblioitem->to_api( $args ); Just testing /api/v1/biblios with Accept=application/json. Note that Accept=application/marc works fine. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 38589] New: The manual should specify that MARC configuration for bundles is the same for MARC21 and UNIMARC
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '26

11 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38589 Bug ID: 38589 Summary: The manual should specify that MARC configuration for bundles is the same for MARC21 and UNIMARC Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de In the manual, the item bundle section (https://koha-community.org/manual/latest/fr/html/circulation.html#circulati…) states "The bundle functionality will only be displayed if you create a catalogue record with the Leader, (000 MARC tag) position 7 set to ‘c’ for Collection." and displays a picture from MARC21 framework This exact configuration setting is working for UNIMARC ("c" in pos.7 of leader), but this is not obvious as many settings in Koha are MARC-flavour-dependant -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 31925] New: AutoCreateAuthorities needs to preserve subject heading thesaurus to not create duplicate authority records
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '26

11 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31925 Bug ID: 31925 Summary: AutoCreateAuthorities needs to preserve subject heading thesaurus to not create duplicate authority records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: nick(a)bywatersolutions.com Depends on: 30280 Bug 30280 taught the linker that "650 _ 0 $aFeminism" and "650 _ 7 $aFeminism$2sao" are not the same heading, so a bib record containing the latter should not be linked to the authority record which matches the former. However, AutoCreateAuthorities just creates LCSH authority records from anything, no matter what the values of indicator 2 and subfield 2 are. As a result, if you have an LCSH authority record for a term, and you import/create a non-LCSH term in a bib record and save it, AutoCreateAuthorities will create a new duplicate LCSH authority record and link to that. Every single time, a new duplicate. Steps to reproduce: 1. Use ElasticSearch, since the patch for bug 30280 only expected to work there, and in fact broke linking on Zebra, bug 31924. 2. Enable the preferences AutoCreateAuthorities, AutoLinkBiblios, CatalogModuleRelink 3. Edit any bib record, add a 650 tag, set the second indicator to 7, type Feminism in subfield a and type sao in subfield 2. 4. Save the record, edit it again, note the authority record id in subfield 9 of the Feminism heading. 5. Edit any other bib record, add a 650 tag, set the second indicator to 7, type Feminism in subfield a and type sao in subfield 2. 6. Save the record, edit it again, note the authority record id in subfield 9 of the Feminism heading. The two authority record ids should be the same, since the headings are identical, but instead one will be linked to, say, 1708 and the next to 1709, an identical duplicate record. Rather than setting position 11 of field 008 in the authority record to "a" for LCSH, AutoCreateAuthorities should have set it to "z" for Other and put sao in subfield f of field 040 (and for non-7, non-0 values of indicator 2, it should be setting 008/11 to the correct letter for that indicator value). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30280 [Bug 30280] Support authority records with common subject headings from different thesaurus -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 84

[Bug 32940] New: [Bug 30280 follow-up] Subject-heading-thesaurus-conventions search field missing in Zebra
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '26

11 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32940 Bug ID: 32940 Summary: [Bug 30280 follow-up] Subject-heading-thesaurus-conventions search field missing in Zebra Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P2 Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: frank.hansen(a)ub.lu.se, katrin.fischer(a)bsz-bw.de In the bug 30280 a new searchfield Subject-heading-thesaurus-conventions has been introduced for ElasticSearch (indexing 040 $f of an authority record). This searchfield is used in C4::Heading::_search with an alias thesaurus-conventions (introduced with the same bug and defined only in Koha/SearchEngine/Elasticsearch/QueryBuilder.pm). At the same time, neither Subject-heading-thesaurus-conventions nor thesaurus-conventions are defined for Zebra. As a result, while performing a linking (with link_bibs_to_authorities.pl for instance) of a biblio 6XX field with 2nd indicator == 7 and proper $2 (e.g. 650 _7 $a Ekonomia $2 DBN) with Zebra engine we get: error: Unsupported Use attribute (114) thesaurus-conventions Bib-1 On the other hand, according to the stable Zebra configuration (for 15 years or so) Koha inserts 040 $f into the Subject-heading-thesaurus index, as goes there 008/11 byte, transformed in the following way: a => lcsh b => lcac c => mesh d => nal k => cash n => notapplicable r => aat s => sears v => rvm So, maybe ES should go the same way? If for some reasons no, the Koha part should be modified accordingly. It seems that changes made in Koha in favour of the ES should always be very carefully checked in Zebra context... Now the linking feature in Zebra does not work in most cases (also described in the bug 32916). Seeing the comment at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30280#c58, I understand that the enhancement is still not mature enough. So, I am wondering that it has been accepted in the released version (22.11.00)... Was this not by mistake? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 16994] New: Import and export MARC modification templates
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16994 Bug ID: 16994 Summary: Import and export MARC modification templates Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Configuring a complicated MARC modification template can be a tedious job, so it would be nice to be able to import and export them the way we can with MARC frameworks. This would also facilitate sharing between libraries. -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 27113] New: ElasticSearch: Autocomplete in input search
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27113 Bug ID: 27113 Summary: ElasticSearch: Autocomplete in input search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: ivan.dziuba(a)inlibro.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 302

[Bug 22730] New: Not possible to set default value for patron attributes
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22730 Bug ID: 22730 Summary: Not possible to set default value for patron attributes 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: rhouk(a)ottumwapubliclibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- It would be helpful to be able define default values for patron attributes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11