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

[Bug 39287] New: Improve "Show volume" search with a more specialized search index
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39287 Bug ID: 39287 Summary: Improve "Show volume" search with a more specialized search index Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl, michaela.sieber(a)kit.edu Currently the rcn index used to search for volumes contains all $w subfields from 7xx and 8xx linking fields. In some cases this is too broad, even tho we are additionally limiting to monographs. Example: Search volumes will also find - records with a 775$w - other edition - records with a matching 780/785$w - preceeding or succeeding ... A specific index for searching volumes (rcn-volumes) should contain: - 773$w (we still need to limit to monographic, because these could also be analytcal links) - 800$w - 810$w - 811$w - 830$w Once the index is defined we can update the XSLT and the method for determining if the "Show volumes" link should be shown to use it and have a correct result list. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 26423] New: Cannot find patron with no cardnumber attached to hold, if HidePatronName system preference set
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26423 Bug ID: 26423 Summary: Cannot find patron with no cardnumber attached to hold, if HidePatronName system preference set Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: minna.kivinen(a)hamk.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When system preference HidePatronName is set, there is showing only patron cardnumber when looking at title holds. If patron has no cardnumber, there is showing nothing. There is no way to find the patron attached to hold. There should be a link to patron even when no cardnumber. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 30657] New: Make patron attributes available via Template Toolkit in overdues
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30657 Bug ID: 30657 Summary: Make patron attributes available via Template Toolkit in overdues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When using Template Toolkit to fetch patron values, one should be able to fetch patron attribute values. This would be useful both for printing those values into the notice content and for using those values in logic to vary the notices per patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 104

[Bug 35288] New: ApplyFrameworkDefaults add plugin to add more fine grained defaults handling
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35288 Bug ID: 35288 Summary: ApplyFrameworkDefaults add plugin to add more fine grained defaults handling Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)trust-box.at QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The "new" ApplyFrameworkDefaults option is to coarse sometimes ie quite often you also want to apply default values even if then field wasn't empty before e.g. on duplicating a new controlnumber should be generated etc so I suggest (and already wrote) a new plugin hook (see https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33669) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 19524] New: Share patron lists between staff
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19524 Bug ID: 19524 Summary: Share patron lists between staff Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jesse(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries would like to allow arbitrary lists to be used by all librarians with the 'manage_patron_lists' permission. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 36021] New: "Scheduled for automatic renewal" text displays even when not renewable
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36021 Bug ID: 36021 Summary: "Scheduled for automatic renewal" text displays even when not renewable Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: mirjam.vantieghem(a)etf.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Since 23.11, on the checkouts page both in Staff client and OPAC, when a certain item is not renewable, e.g. because it is on hold or max renewals reached, the text "Scheduled for automatic renewal" still appears which is confusing. E.g. In the OPAC it says "Not renewable (on hold)", but right below it, it still says "This item is scheduled for auto renewal." In the Staff client it shows "On hold" and below that "(Scheduled for automatic renewal)". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 38664] New: Tidy the whole codebase
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38664 Bug ID: 38664 Summary: Tidy the whole codebase Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We should tidy our codebase and ensure to keep it tidy. I am suggesting to have patches for 25.05 that will tidy our perl (pl, pm, t), javascript (js, ts, vue) and template (tt, inc) files. We will need: * a pre-commit git hook * a xt test (can be very slow however, needs to be discussed) * configure .git-blame-ignore-revs (see `git blame --ignore-revs-file .git-blame-ignore-revs) * provide a script to ease rebases -- You are receiving this mail because: You are watching all bug changes.

1 124

[Bug 31608] New: ShowComponentRecords doesn't display components if UseControlNumber is turned on
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31608 Bug ID: 31608 Summary: ShowComponentRecords doesn't display components if UseControlNumber is turned on Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I apologize if this is a duplicate. I'm trying to document the new Components feature, but I'm running into problems when using UseControlNumber. In Bug 30327, the test plan mentions that UseControlNumber can be used or not, but from what I can see, ShowComponentRecords does not work with UseControlNumber. To test: 1. Enable ShowComponentRecords 1.1. Go to Administration > Global system preferences 1.2. Search for ShowComponentRecords 1.3. Choose either staff interface or both 1.4. Save 2. Enable UseControlNumber 2.1. Go to Administration > Global system preferences 2.2. Search for UseControlNumber 2.3. Choose 'Use' 2.4. Save 3. Add 773 $t and $w in the default MARC bibliographic framework 3.1. Go to Administration > MARC bibliographic framework 3.2. Click Actions > MARC structure next to Default framework 3.3. Search for 773 3.4. Click Actions > Edit subfields 3.5. Click on tab 't' 3.6. Check 'Editor' in the 'Advanced constraints' section 3.7. Click on tab 'w' 3.8. Check 'Editor' in the 'Advanced constraints' section 4. Catalog a host record 4.1. Go to Cataloging 4.2. Click on 'New record' 4.3. Fill in the mandatory fields (000, 003, 005, 008, 040$c, 245$a (note this one down), 942$c) 4.4. Enter a number in 001 (and note it down) 4.5. Save (no need to create an item) 5. Catalog a child record 5.1. Go to Cataloging 5.2. Click on 'New record' 5.3. Fill in the mandatory fields (000, 003, 005, 008, 040$c, 245$a, 942$c) 5.4. Fill in 773$a with the title (245$a) of the host record 5.5. Fill in 773$w with the control number (001) of the host record 5.6. Save (no need to create an item) 6. If necessary, reindex 7. Go to the host record --> The child record doesn't appear 8. Change UseControlNumber back to Don't use (steps 2) --> The child record appears -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 30327] New: Sort component parts
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30327 Bug ID: 30327 Summary: Sort component parts 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: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org The component parts order seems to be random now. It would be good to sort them so the detail view would be more informative. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 67

[Bug 29441] New: We should make our method returns consistent in Koha::Biblio
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29441 Bug ID: 29441 Summary: We should make our method returns consistent in Koha::Biblio 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We now have a few of 'get_marc_*' accessors in Koha::Biblio, but their returns are really inconsistent. I feel like we aught to try and make them as consistent as possible so future developers can use them without having to dig through the code to see what they return. In `get_marc_notes` we return an array of note strings from the marc record.. these may be selective subfield concatenations and could be in various orders. In `get_marc_host` we return either a Koha::Biblio object or the Biblio object + the subfield g, as a string, from the current records marc21 773 field we used to find the host. In `get_marc_components` we return an array of MARCXML strings. I think we could do better here.. certainly with the `_components` and `_host` routines either consistently returning Koha::Biblio/Koha::Biblios or MARCXML string/strings for example. As for `get_marc_notes`, this is a little different.. we could possibly return an array of MARC::Field objects for later processing, or perhaps we aught to have a second naming scheme for returning strings from MARC/Metadata vs retuning a marc/metadata object/string itself? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13