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

[Bug 37618] New: Select patron's, then item's home library by default for pickup location when creating bookings
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '26

09 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37618 Bug ID: 37618 Summary: Select patron's, then item's home library by default for pickup location when creating 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 When working with many bookings per day, always selecting the pickup location can become cumbersome. I'd suggest using the patron's home library as a preselection within the pickup library field in the bookings creation modal and to fall back onto the item's home library if the patron's home library is not available. Would you also consider this a sane default? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 36509] New: Add option to search authority records by ID
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '26

09 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36509 Bug ID: 36509 Summary: Add option to search authority records by ID Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz 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 13

[Bug 42156] New: Staging and matching authorities with bad characters can fail
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '26

09 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42156 Bug ID: 42156 Summary: Staging and matching authorities with bad characters can fail Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We have some protections on bibliographic records with bad characters to avoid dying, however for authorities we don't do the same. Importing records with invalid characters can kill the matching jobs during staging -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 37449] New: Authority matching using Elasticsearch on 'Number' fields fails
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '26

09 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37449 Bug ID: 37449 Summary: Authority matching using Elasticsearch on 'Number' fields fails Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The query created for authority search always uses `.ci_raw`.. but that doesn't exist for all search field types, including 'Number'. Fridolin added ci_raw for type 'Std Number' in bug 31695 because of this, but I'm not sure that's the right approach globally. We found this when attempting to add a 001 match rule.. local-number defaults to type 'Number' and this never matches anything because 'Number' doesn't include a ci_raw to search against. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 37762] New: Expand ILL to allow for Supplying Agency/Lending Library workflows
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '26

09 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37762 Bug ID: 37762 Summary: Expand ILL to allow for Supplying Agency/Lending Library workflows Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com Currently Koha's ILL module allows for the Koha library to be a borrowing library/institution but does not currently allow for the Koha library to be a supplying agency/lending library. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 114

[Bug 36893] New: Shibboleth Login not honouring branch selector
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '26

09 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36893 Bug ID: 36893 Summary: Shibboleth Login not honouring branch selector Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: ryan.henderson(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org A client of ours has recently installed Shibboleth SSO into their staff client. They have asked us to help honour the branch selector on the staff login screen but Shibboleth is ignoring this from what we can see and is only logging staff into their default branches. We think this would be a nice enhancement to the authentication module, to help people login to their requested branches. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 41264] New: Hold pickup location changes not logged when made from patron record
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '26

09 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41264 Bug ID: 41264 Summary: Hold pickup location changes not logged when made from patron record Initiative type: --- Sponsorship --- status: 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com To recreate: - enable Holds Log - place a hold - change its pickup location from the bib record - change its pickup location from /cgi-bin/koha/circ/circulation.pl - change its pickup location from /cgi-bin/koha/members/moremember.pl - search action logs for your hold - confirm only the pickup location change from the bib has been recorded -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 39503] New: Linker should always respect thesaurus with LinkerConsiderThesaurus on
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '26

09 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39503 Bug ID: 39503 Summary: Linker should always respect thesaurus with LinkerConsiderThesaurus on Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: MARC Authority data support Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl, nick(a)bywatersolutions.com With bug 30280 and subsequent patches we attempt to respect the thesaurus indication when linking with LinkerConsiderThesaurus on. However, there are still cases when we link wrong. Example: biblio: 650 _1 $a Philosophy [thesaurus: Library of Congress Children's and Young Adults' Subject Headings] will be linked to an authority 008/11 = a [Library of Congress Subject Headings] 150 __ $a Philosophy if 008/11 = b [Library of Congress Children's and Young Adults' Subject Headings] 150 __ $a Philosophy is missing in the system. This is obviously wrong--we should not link to a authority record belonging to a different thesaurus. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 33277] New: Correctly handle linking subfields with no defined thesaurus
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '26

09 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33277 Bug ID: 33277 Summary: Correctly handle linking subfields with no defined thesaurus 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This is a follow-up to bug 33159, which is a followup to bug 30280 Currently we are handling all subfield other than 6XX as if they are lcsh - this doesn't work in all scenarios. When a record has 008 character 11 =n - "Not applicable" the match won't go through -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 100

[Bug 41714] New: MARC21 authorities thesaurus link hardcoded
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '26

09 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41714 Bug ID: 41714 Summary: MARC21 authorities thesaurus link hardcoded Initiative type: --- Sponsorship --- status: 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org UNIMARC heading mapping to thesaurus is read from the MARC bibliographic frameworks. On the other hand, MARC21 has them hardcoded in `C4::Heading::MARC21`. This has the side effect of not letting the linker tools honor the linking configuration from the frameworks. For example, if you define your own thesaurus `CEPAL_TOPIC` which you maintain with your own tools/process, and link it to `650$a`, running the linker will still look for `TOPIC_TERM` yielding bad results. We should have an implementation that: * Allows opting in to a UNIMARC-like behavior * Has a fallback mechanism for not-configured mappings so we wouldn't expect behavior change besides the frameworks-defined mappings * It doesn't reinvent the wheel on an old library -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 59