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

[Bug 26815] New: QueryFuzzy should also fuzzy Elasticsearch searches when set to "try"
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26815 Bug ID: 26815 Summary: QueryFuzzy should also fuzzy Elasticsearch searches when set to "try" Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com When set to "Try" QueryFuzzy should try to Fuzzy searches on Elastic without making staff and patrons always add a ~ after each search term. Elastic has support for fuzzy search https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-f… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 35766] New: Allow staff to adjust privacy settings for patron
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35766 Bug ID: 35766 Summary: Allow staff to adjust privacy settings for patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com Okay, right off the bat, let me make this clear. I am not asking for staff to control whether they can see patron history. What I am asking is for a setting to allow staff to set the privacy setting for the patron. We have need for our homebound patrons to retain history so that the check for previous checkouts works. Some, if not most, of the homebound patrons may not be tech savvy enough to go into their account and turn this on. We can default the homebound patron to retain this setting, but we have no way within the patron account to flip the switch for existing patrons. I am pretty sure this was by design. If it is of concern, a compromise might be to have a "Request to turn on history" email sent to the patron, in which they can click a link to confirm consent. Maybe also a reject, in which the link to request in the patron account would show the date the request was last rejected. Staff would have the option to request again, and if rejected again, the date would be updated. Thoughts? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 29739] New: Add a staff counterpart for OPACURLOpenInNewWindow
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29739 Bug ID: 29739 Summary: Add a staff counterpart for OPACURLOpenInNewWindow Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The OPAC XSLTs respect pref OPACURLOpenInNewWindow when opening URLs. Would be nice to have something like StaffURLOpenInNewWindow in staff? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 29800] New: Add option to calculate fines when an item is marked lost
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29800 Bug ID: 29800 Summary: Add option to calculate fines when an item is marked lost 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We have the system preferences CalculateFinesOnReturn and CalculateFinesOnBackdate to make Koha calculate overdue fines as an item is returned, either in place of or in addition to the fines cron. However, if one marks an item as lost and has MarkLostItemAsReturned enabled, the issue will be ended without an overdue fine being calculated. We should add the option to calculate an overdue fine at the moment of marking an item lost. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 33606] New: Access to ERM requires parameters => 'manage_sysprefs'
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33606 Bug ID: 33606 Summary: Access to ERM requires parameters => 'manage_sysprefs' Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com CC: jonathan.druart+koha(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 Since bug 33408 we are fetching sysprefs from svc/config/systempreferences, but this script requires parameters => 'manage_sysprefs' -- You are receiving this mail because: You are watching all bug changes.

1 71

[Bug 32791] New: Log4perl configuration files need a tool for updating on package upgrade
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32791 Bug ID: 32791 Summary: Log4perl configuration files need a tool for updating on package upgrade 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Typically, we update existing log4perl.conf files using debian/koha-common.postinst but it's making that file grow way too much and it's difficult to test. Instead, let's provide a CLI tool that we can more easily test and update without touching debian/koha-common.postinst directly. It should hopefully simplify maintenance. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 32489] New: Add check out date, number of renewals, numbers of overdue days in list of overdues
by bugzilla-daemon＠bugs.koha-community.org 14 Jun '26

14 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32489 Bug ID: 32489 Summary: Add check out date, number of renewals, numbers of overdue days in list of overdues 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: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In circ/overdue.pl it could be useful to add for each line - the check out date - the number of renewals - the number of overdue days (today - due date) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 27105] New: Add checkout notes from staff client
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '26

13 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27105 Bug ID: 27105 Summary: Add checkout notes from staff client Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com AllowCheckoutNotes allows patrons to add notes for a specific checkout from OPAC. It could be useful we could have the same feature on Staff client. Librarians could add some useful informations for checking (annotated or highlighted text before the checkout, book already damaged, needs a new label after the return, etc.). A good feature to have less litigation with patrons when checking books with some problems ! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 30680] New: Behavior due to MARC Overlay Rules should be reflected in Diff view when staging MARC batches for import
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30680 Bug ID: 30680 Summary: Behavior due to MARC Overlay Rules should be reflected in Diff view when staging MARC batches for import Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 14957 To recreate: - create a rule on /marc-overlay-rules.pl to protect the 050 tag when staging for MARC import - export a record from your collection and remove the 050 outside of Koha - reimport that record, matching your incoming record to the one already in your collection - confirm the Diff view on manage-marc-import.pl says the 050 will be deleted - complete import, confirm the 050 was retained We should somehow denote when a field will not be impacted due to an overlay rule. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 [Bug 14957] Write protecting MARC fields based on source of import -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 38527] New: Add logging of reports (created, run, changed and deleted)
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38527 Bug ID: 38527 Summary: Add logging of reports (created, run, changed and deleted) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: inkeri.hakulinen+bugz(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org For GDPR reasons it would be good to have Koha to log the use of reports. I suggest that the log should include data about -who created which report and when and what the sql was -who run which report and when and what the sql was (the actual sql that was run, since sometimes you choose / fill in some parameters when you run the report) -who changed which report and when and how the sql was changed (before & after) -who deleted which report and when and what the sql was -probably also the updates to the report descriptions would be good to log? However, the results of the reports should not be saved into logs, of course. This addition would bring transparency about the use of the reports. That would be important for preventing misuse of customer data. Now Koha doesn't collect so detailed data, and it would be easy to collect customer data without a trace in the logs. This data would of course be helpful also in cases, when someone accidentally changes a report so that it doesn't work anymore. You could detect the old report from the logs. Also this would help solving crashes that happened due to running too heavy reports. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7