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

[Bug 39329] New: Scroll to top does not move focus to a sensible place
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '25

14 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39329 Bug ID: 39329 Summary: Scroll to top does not move focus to a sensible place Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Accessibility Assignee: koha-bugs(a)lists.koha-community.org Reporter: jake.deery(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, oleonard(a)myacpl.org The scroll to top button should return focus to the same place as the page load focuses. As we use a skip to main content button in Koha, we should probably have scroll to top focus on that by default, with the possibility to pass in an element id or class as an override. This has come up in a recent customer accessibility audit. Something to mull over! Jake. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 33635] New: CSV export display broken diacritics in Excel
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '25

14 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33635 Bug ID: 33635 Summary: CSV export display broken diacritics in Excel Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: clemens.tubach(a)kit.edu, gmcharlt(a)gmail.com, michaela.sieber(a)kit.edu This has been a re-occurring support issue: When using one of Koha's many CSV download options, the exported CSV file doesn't open as UTF-8 in Excel, resulting in broken diacritics. LibreOffice doesn't show the issue. The only way to fix it right now is not to open the file directly, but to use the import functionality in Excel as it lets you pick the encoding and separators. This means a lot of extra steps and clicks, which make the CSV export functionalities in Koha hard to use. It turns out that Excel will import the CSV correctly, if we convert the encoding of the exported CSV file from UTF-8 to UTF-8-BOM. Problematic CSV exports include: * Exporting a basket summary page as CSV * Using CSV profile based exports in general, including: lists, basket, lost items report * ... Can we 'fix' the encoding to use BOM? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 12270] Create a directory for templates shared with opac and intranet
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '25

14 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12270 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |dcook(a)prosentient.com.au Resolution|--- |DUPLICATE --- Comment #2 from David Cook <dcook(a)prosentient.com.au> --- *** This bug has been marked as a duplicate of bug 35716 *** -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 10060] Allow adding a branch parameter to the web-based self check to indicate library its used at
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '25

14 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10060 --- Comment #32 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Christopher Brannon from comment #30) > I would love to see this happen. We've moved over to Koha's self check out > and we are losing stats because of it. Something like this should have > happened years ago. We noted this problem in 2012 when we started with Koha. > > This is a annoying limitation for consortiums. Agreed -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10060] Allow adding a branch parameter to the web-based self check to indicate library its used at
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '25

14 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10060 --- Comment #31 from David Cook <dcook(a)prosentient.com.au> --- When I have a moment, I'll take a look at my local code again. While we have a solution that works well for our multi-branch libraries, I doubt the Koha community will accept our code as is. But I can share what we've got, and collaborate with folk to make a community acceptable version. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10060] Allow adding a branch parameter to the web-based self check to indicate library its used at
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '25

13 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10060 --- Comment #30 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- I would love to see this happen. We've moved over to Koha's self check out and we are losing stats because of it. Something like this should have happened years ago. We noted this problem in 2012 when we started with Koha. This is a annoying limitation for consortiums. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 22531] New: Allow for multiple requests to partners and display partners in audit log
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '25

13 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22531 Bug ID: 22531 Summary: Allow for multiple requests to partners and display partners in audit log Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Target Milestone: --- Currently, when an ILL request is sent to partners it is not possible to send to further partners, should the first partner not be able to fulfil the request. A better approach would be to allow the "Place request with partners" option to be selected even when this action has already taken place. This will allow the user to try multiple partners subsequently. As such, we should log which partners a request has been sent to and this information should be displayed in the "Display request log" functionality added in Bug 20750 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 54

[Bug 39057] New: Add additional fields to ILL requests
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '25

13 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39057 Bug ID: 39057 Summary: Add additional fields to ILL requests Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com There is currently a kind of additional fields for ILL request, but it can be different for each request. This is not the behavior we have elsewhere in Koha. A library should have the ability to define additional fields in /admin/additional-fields.pl with the same options as ERM additional fields (searchable or not, repeatable, linked to a authorized value...) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 38817] New: JS error when viewing subfield structure
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '25

13 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38817 Bug ID: 38817 Summary: JS error when viewing subfield structure Change sponsored?: --- Product: Koha Version: Main 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Noticed when testing something else. Uncaught Sortable: `el` must be an HTMLElement, not [object Undefined] To recreate: 1. Go to Administration > MARC bibliographic framework 2. Pick any framework and MARC structure 3. Pick any subfield and View subfield Notice the console error. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 27444] New: Allow reports to use the calendar to count open/closed days based on the calendar
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '25

13 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27444 Bug ID: 27444 Summary: Allow reports to use the calendar to count open/closed days based on the calendar Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When writing reports related to fines or overdue notices, one runs into difficulties based on how Koha holidays are stored. There's no good way for SQL to calculate out how many days within a given span were open days. So if you're using the calendar to calculate when to send overdue notices at 10 open days past the due date, there's no way to get SQL to tell you which items should have gotten an overdue notice today. This becomes more of an issue as we use the patron emailer more, since the patron emailer relies upon a report. If one wanted to use the patron emailer to send a fourth overdue notice, one would not be able to calculate when to send that notice using the Koha calendar. I'm not sure what the solution is here. Maybe some syntax one could use in a report to ask Koha to generate a value? So you could say something like: WHERE timestampdiff(days,date_due,curdate()) = <<opendays:date_due,curdate()>> ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3