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

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

[Bug 37280] New: Add a direct link to Stage MARC records from ERM Titles
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '25

13 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37280 Bug ID: 37280 Summary: Add a direct link to Stage MARC records from ERM Titles Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: esther.melander(a)bywatersolutions.com 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 A bulk upload of local titles into the ERM is a bit cumbersome and requires importing titles through Stage MARC records, creating a list from Biblio numbers of the imported titles, and adding the list into titles. It would be far simpler to have a direct link to Stage MARC records to pull the titles into Koha and the ERM. Perhaps similar to the process in Acquisitions. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 29566] New: Convert bundle contents modal to a notice
by bugzilla-daemon＠bugs.koha-community.org 12 Mar '25

12 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29566 Bug ID: 29566 Summary: Convert bundle contents modal to a notice Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We add a simple way to display and print a contents list for bundle items in bug 28854. It would be useful to allow librarians to customise how this list displays and prints; We can achieve that by converting the contents to a notice list other print slips. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 21383] New: Sorting on ILL request table is inaccurate
by bugzilla-daemon＠bugs.koha-community.org 12 Mar '25

12 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21383 Bug ID: 21383 Summary: Sorting on ILL request table is inaccurate 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 In the ILL requests table, values containing numbers are sorted incorrectly. For example, AUB-1, AUB-10, AUB-11, AUB-20, AUB-21 etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 21889] New: Include Staff Client entered Purchase Suggestions with System Preference maxopensuggestions
by bugzilla-daemon＠bugs.koha-community.org 11 Mar '25

11 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21889 Bug ID: 21889 Summary: Include Staff Client entered Purchase Suggestions with System Preference maxopensuggestions Change sponsored?: --- Product: Koha Version: 18.05 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 Currently only Purchase Suggestions made by patrons through the OPAC are the only suggestions counted in the system preference MaxOpenSuggestions. It would be nice if this system preference also connected to the staff client, so a purchase suggestion done on the patrons account by staff alerted the staff that the patron already had the maximum number of purchase suggestion allowed. At this time, even if a patron has maxed out the number of open purchase suggestions on the OPAC, a staff member can still enter more purchase suggestions for that patron through the staff client without knowledge of the maxopensuggestions being reached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 36381] New: "not a tree object" error from Jenkins
by bugzilla-daemon＠bugs.koha-community.org 11 Mar '25

11 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36381 Bug ID: 36381 Summary: "not a tree object" error from Jenkins Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org "not a tree object" warning on Jenkins. It's like the test are not run inside a git repository: koha_1 | error: object directory /srv/jenkins/workspace/Koha_Source/.git/objects does not exist; check .git/objects/info/alternates koha_1 | error: Could not read 3288f3a2129207626916d7a7b49f580c16d097a1 koha_1 | Nothing to critique at t/00-testcritic.t line 18. koha_1 | [18:52:15] t/00-testcritic.t ........................................................... koha_1 | Dubious, test returned 25 (wstat 6400, 0x1900) koha_1 | No subtests run In this case we have t/00-testcritic.t that is failing. But even on green runs we see: koha_1 | error: object directory /srv/jenkins/workspace/Koha_Source/.git/objects does not exist; check .git/objects/info/alternates koha_1 | fatal: not a tree object koha_1 | [18:17:56] t/00-testcritic.t And lot of other "not a tree object" error (I guess everytime we run 'git' commands from tests). -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 17173] New: Quick edit a subfield in frameworks
by bugzilla-daemon＠bugs.koha-community.org 11 Mar '25

11 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17173 Bug ID: 17173 Summary: Quick edit a subfield in frameworks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: System Administration Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There are too many click to jump to the edit form of a specific subfield. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 36143] New: Pop-up window sizes are not consistent
by bugzilla-daemon＠bugs.koha-community.org 10 Mar '25

10 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36143 Bug ID: 36143 Summary: Pop-up window sizes are not consistent Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: In Discussion Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: dcook(a)prosentient.com.au, fridolin.somers(a)biblibre.com, jonathan.druart+koha(a)gmail.com, katrin.fischer(a)bsz-bw.de, martin.renvoize(a)ptfs-europe.com, oleonard(a)myacpl.org It seems we have width+height specifically defined for each window.popup across the code base. These are some of the variants I could find, but there may be others: width=1000,height=600 width=1000,height=375 width=1000,height=575 width=900,height=700 width=800,height=400 width=800,height=550 width=800,height=500 width=700,height=700 width=700,height=600 width=700,height=400 width=700,height=550 This is not great, these should be standardized and configured once, example (values to be discussed): large: 1000 x 600 medium: 800 x 500 small: 700 x 400 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3