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

[Bug 27091] New: Document how Elasticsearch is supposed to work and implement respective configurations
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27091 Bug ID: 27091 Summary: Document how Elasticsearch is supposed to work and implement respective configurations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi CC: nick(a)bywatersolutions.com Elasticsearch is very flexible search engine and has many configuration options. We should document our expectations on how it should work and also because then it would allow the users to understand how to form their queries in the best possible way. After documenting the configuration we want based on the expectations we should tune the indexing and search configuration parameters accordingly. The bug 27070 makes the Elasticsearch searches more Zebra like by trying to match search keywords across all fields but is this exactly what we want in the end? What if we have only a number in the search query should we try to query numeric fields then only or also string fields? How should the weights work? For weight documentation we should have an basic configuration for it in our default mappings.yaml file so that we have some idea how it will be used in real world. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 27075] New: "Cancel charge" doesn't seem to appear in po files or on translate
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27075 Bug ID: 27075 Summary: "Cancel charge" doesn't seem to appear in po files or on translate Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Depends on: 24603 I am not sure why, but there appears to be a translation issue with the new "Cancel charge" button on the account in the staff interface. German po files are at 100% but I can't find it searching translate.kc.org. I also can't fit it outside the template using git grep. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24603 [Bug 24603] Allow to cancel charges in patron accounting -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 27057] New: Add the ability to have a Override this entire Checkout transaction when Allowtoomanyoverride is turned on
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27057 Bug ID: 27057 Summary: Add the ability to have a Override this entire Checkout transaction when Allowtoomanyoverride is turned on 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be nice to allow staff to Override an entire Patron transaction when the library is allowing staff to AllowTooManyoverride. Right now, when a staff member is checking out to a patron that has gone over the limit of the number of checkouts, they have to override each checkout. A good example would be, a patron that has just returned all their books in the book drop and now want to checkout more- because the others have not been checked in, they have gone over their checkout total but the library would like to allow this. This enhancement would save a lot of clicking! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 27040] New: Allow definition of default value for NEW_CARD debit type
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27040 Bug ID: 27040 Summary: Allow definition of default value for NEW_CARD debit type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The NEW_CARD debit type is included in a new instal with a default value of $0. It cannot be edited. It would be helpful to give libraries a way to change that default value to whatever they charge for a new card, rather than requiring them to set the amount manually every time a new card fee is added to a patron account. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 20587] New: Add option to delete notices out of message queue via notices tab
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20587 Bug ID: 20587 Summary: Add option to delete notices out of message queue via notices tab 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Sometimes a library creates a notice by accident and wants to delete it before it's sent out with the next run of the messsage queue. It would be nice if we offered a 'delete' link in the notices tab for each message that would allow for that. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 22689] New: Add ability for staff to cancel a SERIAL_ALERT
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22689 Bug ID: 22689 Summary: Add ability for staff to cancel a SERIAL_ALERT Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- The SERIAL_ALERT notice (RLIST notice prior to 18.05: See Bug 19794) is used to send an email to patrons who have subscribed to the alert service via their account. They are notified when a new issue for a subscription arrives. We have users who have left, and whose emails are no longer valid but who have not cancelled their alerts. These are generating quite a number of undeliverable emails, which bounce back. We know no way of cancelling the redundant SERIAL_ALERT via the Koha intranet other than by an SQL delete which we do not want to risk. Ideally there would be a way for staff to kill off these redundant alerts. Perhaps the alert cancellation could be tied to the borrowers.dateexpiry? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 28065] New: "Edit report" option when selecting parameters
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28065 Bug ID: 28065 Summary: "Edit report" option when selecting parameters 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: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org When a report allows the user to fill parameters (with <<Item type|itemtypes>> for exemple), it could be useful to have an option to edit the report on the "phase=Run this report" page where you have to select the different parameters. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 28062] New: Allow batch removal of waiting holds
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28062 Bug ID: 28062 Summary: Allow batch removal of waiting holds 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: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In the "Holds Awaiting Pickup" button in "Circulation", it would be nice if there could be a batch delete function - if a user has to cancel a lot of holds they can only be done one at a time and the screen has to rebuild between each deletion. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 28059] New: Move OPAC news block to new protected area
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28059 Bug ID: 28059 Summary: Move OPAC news block to new protected area Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: estherm(a)sodaspringsid.com QA Contact: testopia(a)bugs.koha-community.org The OPAC news block items should be separated out to a new permission protected area. It is too easy to forever delete OPAC customizations by library staff who otherwise should be able to use the news tool. Our consortium recently experienced this when someone accidentally deleted all the OPAC news blocks. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 28051] New: On upgrade to 19.11, per-item Writeoff got confused with Lost
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28051 Bug ID: 28051 Summary: On upgrade to 19.11, per-item Writeoff got confused with Lost Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: pongtawat(a)punsarn.asia QA Contact: testopia(a)bugs.koha-community.org During upgrade to 19.11, database upgrade script introduced by Bug #22563 (convert "lost" handling) also handle case of normal per-item writeoff like those writeoff generated from lost. So, all patron with normal per-item writeoff will now see additional account line of 'LOST' type. This is due to the following code in updatedatabase.pl: # Find and correct pathalogical cases of L having been converted to W $sth = $dbh->prepare( "SELECT accountlines_id, issue_id, borrowernumber, itemnumber, amount, manager_id FROM accountlines WHERE accounttype = 'W' AND itemnumber IS NOT NULL" ); ... Step to reproduce: 1. Start with Koha 18.05. 2. Create overdue fine on item X for patron A, amount=100. 3. Per-item write-off amount=50 on item X for patron A. This will create 'W' line in accountlines with amount=50 and item=X 4. Upgrade to Koha 19.11 or later (in our case 20.05) 5. Patron A now has an additional 'LOST' with amount=50 and item=X in their accountlines. This additional 'LOST' line is incorrect in this case. Also, I notice that this per-item writeoff is in debit side (red). I don't know if this is correct or not, but shouldn't writeoff be on credit side? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2