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

[Bug 38726] New: marc vs. MARC in admin-home.tt
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38726 Bug ID: 38726 Summary: marc vs. MARC in admin-home.tt Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 38611] New: Change 'Staff' to 'Staff interface' in HTML customization locations
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38611 Bug ID: 38611 Summary: Change 'Staff' to 'Staff interface' in HTML customization locations Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When you go to Tools > HTML customizations > New entry and look at the possible locations, they are separated in "OPAC" and "Staff". Staff can be ambiguous in translation since it can mean the library staff. Usually, "Staff interface" is used to mean the interface. I propose we change "Staff" to "Staff interface" in the HTML customization locations to make it easier to translate correctly. Alternatively, we could add translation context, but I feel like "Staff" is simply a shortcut for "Staff interface" and not an actual term we should use. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 37427] New: Searching for an empty string for clubs in an item's hold tab is not allowed
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37427 Bug ID: 37427 Summary: Searching for an empty string for clubs in an item's hold tab is not allowed Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: samalau(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To reproduce: 1) have some patron clubs 2) find a bib 3) Click Holds, then Clubs 4) Without entering any text, press the search button 5) Note that the list of clubs is not shown. However, when searching for a patron with an empty string, it returns the entire list of patrons. I think it would be useful if club searching followed this same functionality. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 37360] New: Add 'Protected Status' as one of the things that can be updated via Batch Patron Modification tool
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37360 Bug ID: 37360 Summary: Add 'Protected Status' as one of the things that can be updated via Batch Patron Modification tool Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.auld(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The new 'Protected Status' characteristic is something that could usefully be included as editable via Batch Patron Modification. Please consider adding. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 53

[Bug 37311] New: Tone down the SMTP servers administration page
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37311 Bug ID: 37311 Summary: Tone down the SMTP servers administration page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Information about the current configuration is shown as an informational dialog, and default server and debugging status are highlighted in red as if it were an error needing attention. I think the page could be restyled to convey the information without the implicit demand for action. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 37934] New: Extend length of API Key, requestor ID and customer ID for data providers
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37934 Bug ID: 37934 Summary: Extend length of API Key, requestor ID and customer ID for data providers Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com API Key, requestor ID and customer ID are defined as varchar(80). We had reports that this can be not enough in some cases. Suggestion is to extend to varchar(255). https://schema.koha-community.org/24_05/tables/erm_usage_data_providers.html -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 37364] New: Improve creation of 773 fields for item bundles regarding MARC21 245 and 264
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37364 Bug ID: 37364 Summary: Improve creation of 773 fields for item bundles regarding MARC21 245 and 264 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 Depends on: 29560 1) I think we should adjust to also take RDA records using 264 into account here. At least for us these are now the majority of records. + # Publication + if ( $host_field = $marc_host->field('260') ) { + my $s = $host_field->as_string('abc'); + if ($s) { + $sfd{d} = $s; + } + } 773$d is not repeatable, so we should avoid to create 2 entries. Maybe check for existence of 264 first and then fallback to 260 if the first is not found? 260 and 264 are both repeatable. I assume this either uses the first or last entry - can you tell? Ideally it might be good to prefer the entry with first indicator = 3 (current/latest), if it exists: https://www.loc.gov/marc/bibliographic/bd264.html 2) This should take $n$p into account as well, as otherwise a multi-part work will not be distinguishable from the title: + # Title + if ( $host_field = $marc_host->field('245') ) { + my $s = $host_field->as_string('ab'); + if ($s) { + $sfd{t} = $s; + } + } I think this could just be changed to: abnp for the subfield list. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29560 [Bug 29560] Add option to create MARC links when adding items to bundles -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 46

[Bug 38650] New: We should only fill title level or specific item holds when a patron checks out an item
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38650 Bug ID: 38650 Summary: We should only fill title level or specific item holds when a patron checks out an item Change sponsored?: --- 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Follow up to bug 14549 - we handled the case here to fill a patron's reserve when they get another copy, however, we didn't cover the case where their reserve is title level. To recreate: 1 - Place a hold for patron A on item #1 of a record 2 - Place a hold for patron B on item #2 of a record 3 - Issue item #2 to patron A - their hold on item #1 is filled incorrectly -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 17338] New: waitingreserves.pl should keep you on the same tab when cancelling a hold
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17338 Bug ID: 17338 Summary: waitingreserves.pl should keep you on the same tab when cancelling a hold 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When you cancel a hold on the Hold(s) over tab, and the process is done, it puts you back on the Hold(s) waiting tab. It should keep you on the same tab. It would also be nice if the search box is used that it would keep the focus. We use the following jQuery to help streamline the cancelling process: //Default Holds awaiting pickup to Holds over tab $("#holdso form[action='waitingreserves.pl']").attr("action","waitingreserves.pl#holdsover"); if (window.location.href.indexOf("cgi-bin/koha/circ/waitingreserves.pl#holdsover") > -1) { $("form[action='waitingreserves.pl']").attr("action","waitingreserves.pl#holdsover"); } setTimeout(function() { $("#holdso_filter input").focus(); },10); //End default tab -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 39056] New: Do not copy preferred_name to new patron when using Duplicate
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39056 Bug ID: 39056 Summary: Do not copy preferred_name to new patron when using Duplicate Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com When using the Duplicate button from a patron's record, we make a new patron with some of the original patron's info. We bring the surname to the new patron, but not the firstname. Following that logic, we shouldn't copy preferred_name, either. Currently on main the preferred_name *is* copied to the new patron. In the long run this probably wants something like the PrefillGuaranteeField syspref, but in the short term we should just exclude preferred_name. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21