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

[Bug 31635] New: Empty title for current result in opac results browser
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '22

29 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31635 Bug ID: 31635 Summary: Empty title for current result in opac results browser Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org This is very minor, but I noticed it when working on bug 31634. When using OpacBrowseResults, there are result number buttons at the top of the results browser. If you hover over those result numbers, it says 'View record "[title]"'. But if you hover over the current result number, it only says 'View record ""' (with nothing between the double quotes). To test: 1. Make sure OpacBrowseResults is enabled 1.1. In Koha staff interface, go to Administration > Global system preferences 1.2. Search for OpacBrowseResults 1.3. If necessary, change to 'enable' and click 'Save all OPAC preferences' 2. In OPAC, search for a term that will give you a couple of results and view the results browser 2.1. In Koha OPAC, search for BFF 2.2. Click on one of the titles to access the opac-detail page 3.3. Click 'Browse results' 3.4. Hover over the number buttons at the top of the results browser --> When you hover over another result, it says 'View record "[title]"' -- OK --> When you hover over the current result, it says 'View record ""' -- should say the title -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 31915] New: Add floating toolbar to item search
by bugzilla-daemon＠bugs.koha-community.org 23 Dec '22

23 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31915 Bug ID: 31915 Summary: Add floating toolbar to item search 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be great if the edit button, the select and export options above the item search results page could be moved into a floating toolbar. Libraries often end up using the 'back' button in the browser that doesn't work here. We could improve this by having the 'Edit search' button always visible. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 31887] New: Search on MARC field does not work in Elasticsearch mappings table
by bugzilla-daemon＠bugs.koha-community.org 23 Dec '22

23 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31887 Bug ID: 31887 Summary: Search on MARC field does not work in Elasticsearch mappings table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In Elasticsearch mappings table, in tabs with MARC fields, searching using DataTable search field does not work for MARC fields / subfields. This is because cell contains an input HTML tag with MARC data in attribute value. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 30237] New: Rename and rephrase AutoEmailOpacUser system preference
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '22

22 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30237 Bug ID: 30237 Summary: Rename and rephrase AutoEmailOpacUser system preference Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 27812, 29005, 30214 With the changes from bugs 27812, bug 29005, and bug 30214 we will have a much cleaner and secure feature than before that will work in a much more predictable way. So I think this would then be a good moment to add documentation to the pref: IS: AutoEmailOpacUser [Send|Don't send] an email to newly created patrons with their account details. COULD BE: AutoEmailNewUser (switch Opac with New) [Send|Don't send] an email to newly created patrons, including verified self registrations. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27812 [Bug 27812] Remove the ability to transmit a patron's plain text password over email https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29005 [Bug 29005] Add option to send ACCTDETAILS notice for new patrons added via patron imports https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30214 [Bug 30214] Send ACCTDETAILS notice for new patrons added via self registration -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 49

[Bug 30608] New: Add the column picker modal to DefaultPatronSearchFields
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '22

22 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30608 Bug ID: 30608 Summary: Add the column picker modal to DefaultPatronSearchFields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 With bug 30576 it becomes more important to ensure we don't get errant data in this preference (with a bad column name included here, we will break patron searching). We should add the column picker modal to this system preference. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 28550] New: Text on overduerules.pl should explain how triggers are selected
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '22

22 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28550 Bug ID: 28550 Summary: Text on overduerules.pl should explain how triggers are selected 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 28549 The onscreen text on the overdue notice and status triggers page should explain which branch will get used. Right now, that defaults to issuing branch, but a flag in the cron can be set to make it use item homebranch instead. I've made this bug depend on 28549, which proposes moving that control into a syspref. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28549 [Bug 28549] Add a system preference to duplicate --frombranch flag in overdue_notices.pl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 31157] New: overdue_notices.pl --frombranch option should be available as a system preference
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '22

22 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31157 Bug ID: 31157 Summary: overdue_notices.pl --frombranch option should be available as a system preference Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz On a multi-tenant system it is understandable for one client to want one options for the --frombranch and another to want another. However, as the overdue job is run under cron.daily it's not trivial to change it on a per instance basis.. We should expose this option at the UI level. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 28549] New: Add a system preference to duplicate --frombranch flag in overdue_notices.pl
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '22

22 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28549 Bug ID: 28549 Summary: Add a system preference to duplicate --frombranch flag in overdue_notices.pl 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The overdue_notices cron allows one to specify whether the issuing branch or item homebranch should be used to select the triggers to follow. We should allow this choice in a system preference so one can change it without commandline access. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 32242] New: The job has not been sent to the message broker: (Wide character in syswrite ... )
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '22

22 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32242 Bug ID: 32242 Summary: The job has not been sent to the message broker: (Wide character in syswrite ... ) 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org The full version: [2022/11/17 08:51:39] [WARN] The job has not been sent to the message broker: (Wide character in syswrite at /usr/lib/x86_64-linux-gnu/perl-base/IO/Handle.pm line 200.) at /usr/share/koha/Koha/BackgroundJob.pm line 147. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 40

[Bug 31061] New: OPACSuppress does not work properly with Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 22 Dec '22

22 Dec '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31061 Bug ID: 31061 Summary: OPACSuppress does not work properly with Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com OPACSuppress is system preference to hide records in OPAC search by adding a limit in search query. With Zebra, this limit is : not Suppress=1 https://git.koha-community.org/Koha-community/Koha/src/commit/244b847a08bf6… With Elasticsearch this limit is currently quite different : suppress:false https://git.koha-community.org/Koha-community/Koha/src/commit/244b847a08bf6… Main problem is that in default framework we define Suppress search field on 942$n with authorized values YES_NO. This generates records with 1 for YES and 0 for NO. But a boolean for Elasticsearch is not a perl boolean. So only missing subfield means false : https://www.elastic.co/guide/en/elasticsearch/reference/6.8/boolean.html Records with 0 are hidden ! Another side-effect : We whould like to have several MARC fields with 'suppress' search field. To distinguish several causes of hidden at OPAC. Any of those fields having 1 must hide at OPAC. So syntax 'NOT(suppress:1)' is more correct. I propose we change to have the same behavior as Zebra. Change 'suppress' search field to not remove boolean type. Change QueryBuilder to use 'NOT(suppress:1)'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14