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

[Bug 21052] New: New patron card printer profile won't save if paper bin is empty
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '26

15 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21052 Bug ID: 21052 Summary: New patron card printer profile won't save if paper bin is empty Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor 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 When adding a new printer profile in the patron card creator tool, you can save without entering a paper bin, but it will not create a new entry in the database. There is no error, the field is not marked as required. To test: - Add a new printer profile - Fill in description, leave other fields unchanged - Save - Verify that the new printer profile doesn't appear in the list and hasn't been created -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 23817] New: Searching by patron phone number is contingent on how it was entered
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '26

15 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23817 Bug ID: 23817 Summary: Searching by patron phone number is contingent on how it was entered Change sponsored?: --- Product: Koha Version: 18.11 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 If a library chooses to enter their patron phone numbers in as xxx-xxx-xxxx when creating the patron record; then when the phone number is searched with the filters, the library must always use hyphens when searching or the search will not work. It would be nice that the number could be searched in the filters with either hyphens or no hyphens and the library would get the same results. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 66

[Bug 23005] New: Specify notice language for vendors
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '26

14 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23005 Bug ID: 23005 Summary: Specify notice language for vendors Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: mbarham(a)birzeit.edu QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- right now, there is no way to specify notices language for vendors. (it is available for Patrons) it will be great if this will be added. regards -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 20336] New: Add a generic way for Koha::Object(s) to call logaction as required
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '26

14 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20336 Bug ID: 20336 Summary: Add a generic way for Koha::Object(s) to call logaction as required Change sponsored?: --- Product: Koha Version: master 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: tomascohen(a)gmail.com 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 3

[Bug 30144] New: Add support for EDI GIR:LVT, Servicing instructions, segment
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '26

14 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30144 Bug ID: 30144 Summary: Add support for EDI GIR:LVT, Servicing instructions, segment 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We allow for free text instructions in the EDI FTX segment now, taken from the vendor notes field. But this is at the order level, it would be helpful to add support for the LVT segment at the line level. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 123

[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 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

[Bug 27635] New: Add option for patron to view archived suggestions on the OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27635 Bug ID: 27635 Summary: Add option for patron to view archived suggestions on the OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 22784 added the ability to archive suggestions on the staff interface. It would be nice to allow patrons to view their archived suggestions -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 21272] New: Marc import should warn about mis-matched branch and item-type fields in 952 during marc import.
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21272 Bug ID: 21272 Summary: Marc import should warn about mis-matched branch and item-type fields in 952 during marc import. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When importing a record that has homebranch (952$a), holding branch (952$b) or item type (952$y) populated, but not matching values in branches.branchcode or itemtypes.itemtype, koha will indicate that items were not imported (via the count of imported items), but not why. This causes frequent confusion among new users. It would be nice to offer mappings between detected branches / item types and the branches and item types already in the system. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 110