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

[Bug 36487] New: Add an option to add new conditions for processing failure_code on members/notices.pl
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '24

11 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36487 Bug ID: 36487 Summary: Add an option to add new conditions for processing failure_code on members/notices.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: anni.rajala(a)turku.fi QA Contact: testopia(a)bugs.koha-community.org At the moment on borrowers notices.pl page there is a column "Delivery note" that displays the reason the delivery has failed. The reason is displayed based on the following conditions: [% IF ( QUEUED_MESSAGE.failure_code ) %] [% IF ( QUEUED_MESSAGE.failure_code == "INVALID_BORNUMBER" ) %]Invalid borrowernumber [% borrowernumber | html %] [% ELSIF ( QUEUED_MESSAGE.failure_code == 'NO_EMAIL' ) %]Unable to find an email address for this borrower [% ELSIF (matches = QUEUED_MESSAGE.failure_code.match('INVALID_EMAIL:(\w+)') ) %]Invalid [% matches.0 | html %] email address found [% borrowernumber | html %] [% ELSIF ( QUEUED_MESSAGE.failure_code == 'NO_FROM' ) %]Missing from email address [% ELSIF ( QUEUED_MESSAGE.failure_code == 'MISSING_SMS' ) %]Missing SMS number [% ELSIF ( QUEUED_MESSAGE.failure_code == 'DUPLICATE_MESSAGE' ) %]Message is duplicate [% ELSIF ( QUEUED_MESSAGE.failure_code == 'NO_NOTES' ) %]No notes from SMS driver [% ELSIF ( QUEUED_MESSAGE.failure_code == 'SENDMAIL' ) %]Unhandled email failure, check the logs for further details [% ELSIF ( QUEUED_MESSAGE.failure_code == "UNKNOWN_ERROR" ) %]Unknown error [% ELSE %]Error occurred while sending email. [% END %] [% END %] Sms providers might send back failure_codes outside that list. In those cases "Delivery note" -colum displays the text "Error occurred while sending email" which doesn't give the proper info for the librarian. If it would be possible to add your own ELSIF conditions, we could provide accurate information for the librarians dealing with the failed messages. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 38674] New: OPAC UNIMARC Authorities 340
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '24

11 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38674 Bug ID: 38674 Summary: OPAC UNIMARC Authorities 340 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org UNIMARC Authorities 340 __ $a Social activities: Dr. Alfred A. Dulzon is ... $b Labour activity: Assistant, Senior ... $c Education, qualifications: Doctor of technical sciences ... $c Areas of research activity: pulsed power... $d Publications: candidate dissertation ... $f 1960-2019 $p Contacts: ... Only one subfield (340$a) in the OPAC is output. What needs to be done to display the remaining subfields? https://koha.lib.tpu.ru/cgi-bin/koha/opac-authoritiesdetail.pl?authid=14209 Koha 24.05 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 16694] New: Limit SIP2 auth by patron attribute
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '24

10 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16694 Bug ID: 16694 Summary: Limit SIP2 auth by patron attribute Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: magnus(a)libriotech.no Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org In Scandinavia "more open" (Swedish: "Meröppet", Norwegian: "Meråpent") is a hot issue at the moment. What this means is that patrons can use their card and password/PIN to lock themselves into the library even when staff is not around. Typically, this means that patrons can get access to the library building from 7 am to 11 pm, even if the library is only staffed from 8 am to 5 pm. Typically, SIP2 is used to communnicate between the "more open"-system and the ILS, specifically to authenticate the user with a username and password/PIN. Also, you want the ability to turn "more open" access on and off for patrons. An extended patron attribute with possible values of NULL/empty, 0 or 1 should serve well for this. SIP2 does not have a field for saying "this is a moreopen login", so we need a way to identify a SIP2 user as a moreopen user. My plan is to add another attribute to the login element in SIPConfig.xml to achieve this: <login id="koha" password="koha" delimiter="|" error-detect="enabled" institution="kohalibrary" patron-attribute="MEROPPET" /> "MEROPPET" is then the name of an extended patron attribute which can be set to NULL or 0 (patron should not have access to moreopen) or 1 (patron should have access). This should be flexible enough to allow other, similar schemes to use some other patron attribute. -- You are receiving this mail because: You are watching all bug changes.

1 43

[Bug 38628] New: Item search filters does not work with multiple search fields
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '24

10 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38628 Bug ID: 38628 Summary: Item search filters does not work with multiple search fields Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org When using more than one search field, the datatable filtering does not work. The same resultset is given every time if you are trying to filter. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 33909] New: Improve translation of title tags: Administration
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '24

10 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33909 Bug ID: 33909 Summary: Improve translation of title tags: Administration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Blocks: 33906 This patch will modify administration templates so that translatable strings in the <title> tag are wrapped in the correct translation function, e.g. [% t('Translate me') %] Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33906 [Bug 33906] [OMNIBUS] Improve translation of title tags -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 38660] New: Add pointers to reports documentation for LIMIT functions
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '24

10 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38660 Bug ID: 38660 Summary: Add pointers to reports documentation for LIMIT functions Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de The Koha manual has some great report documentation, but clarifying that using LIMIT with a batch of results will default results to that many displayed AND send that batch through to batch modification would be a great pointer for librarians interested in unlocking report potential but put off by the idea of having to expand their results past the initial 20 each time. The fix in bug 36534 makes this a bit clearer by indicating the number of results to be acted on, but it would be nice to have that suggested somewhere in the documentation so that a librarian new to report writing can find it, especially since many report writers come to SQL as librarians first, not always with a database background beyond what they pick up on the job for report creation. A logical place for this might be within the SQL Report writing tips section. One place might be in the section for #send-report-output-to-batch-modification-tools. Or earlier in the section, under Runtime parameters as a note/example. Open to further suggestion. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 38134] New: Koha::Items::filter_by_for_hold does not work
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '24

10 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38134 Bug ID: 38134 Summary: Koha::Items::filter_by_for_hold does not work Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We noticed that the place hold button is often incorrecty missing in the detail view in the staff interface after upgrading to 23.11.09. This is due to the number of holdable items is incorrectly determined to be 0. But the method filter_by_for_hold incorrectly assumes that Koha::CirculationRules->get_effective_rule can be used to filter on rule value: my $default_rule = Koha::CirculationRules->get_effective_rule( { rule_name => 'holdallowed', rule_value => 'not_allowed', } ); But it cannot: print Dumper($default_rule->unblessed); $VAR1 = { 'categorycode' => undef, 'id' => 268, 'itemtype' => undef, 'branchcode' => undef, 'rule_name' => 'holdallowed', 'rule_value' => 'from_any_library' }; Bug 29087 introduced this change. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 36106] New: Port default PREDUE and DUE notices to Template Toolkit
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '24

09 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36106 Bug ID: 36106 Summary: Port default PREDUE and DUE notices to Template Toolkit Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: roadmap_24_05 Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Blocks: 15278 The following notices need to be updated to use Template Toolkit syntax: DUE (email) DUE (sms) PREDUE (email) PREDUE (sms) These ones should be fairly straightforward. All four notices have nearly identical content, so it makes sense to group them together. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15278 [Bug 15278] [Omnibus] Port default slips and notices from bespoke syntax to Template Toolkit -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 37691] New: Password expiration reset not clear enough
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '24

09 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37691 Bug ID: 37691 Summary: Password expiration reset not clear enough Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: chanel.wheeler(a)yavapaiaz.gov QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Created attachment 170502 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=170502&action=e… password expiration screen When passwords expire, the GUI for changing it isn't clear enough to staff. 1. Some staff don't see the "You must reset your password" string. 2. Those that do see it, don't realize it's a link. 3. They try to enter a new password in the login form which sends them in a loop back to where they are. I just went through this with 59 libraries. It was a flurry of emails all morning. Reset your password really should be a noticeable button and should take the place of the text fields so that they can't get it wrong. Thank you. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 25813] New: Enhance patron expiration in SIP display
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '24

09 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25813 Bug ID: 25813 Summary: Enhance patron expiration in SIP display Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: matthias.meusburger(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Currently, the patron information returned by SIP only shows "PATRON EXPIRED" when the patron card has expired. This patch makes the display more consistant with the Opac display and also complies with the NotifyBorrowerDeparture system preference. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23