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

[Bug 30591] New: Cannot add patron
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '22

22 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30591 Bug ID: 30591 Summary: Cannot add patron 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: manojshahu07(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 133617 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133617&action=e… not allowed to create new patron Even though we are created 11 patron categories. Getting below error While adding a new patron There are no patron categories defined. An administrator must define at least one patron category. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 19886] New: Two Factor Authentication: Yubikey
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '22

22 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19886 Bug ID: 19886 Summary: Two Factor Authentication: Yubikey Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org We need to add support for Two Factor Authentication, because password isn't enough against hackers or unathorised acess. Yubikey is USB hardware FIDO U2F Secure Static Passwords smart card (PIV) Yubico OTP Code Signing OpenPGP OATH-TOTP OATH-HOTP Challenge-Response https://www.yubico.com/product/yubikey-4-series/ Yubikey Perl support https://developers.yubico.com/yubico-perl-client/ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 10734] Add Publication Date Facet in Searching
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '22

22 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 --- Comment #9 from Séverine Queune <severine.queune(a)bulac.fr> --- (In reply to Fridolin Somers from comment #8) > We should add this facet at least for Elasticsearch where it can be > configured and disabled via staff interface. +1 ! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 30593] New: Should we switch from Modular Crypt Format to PHC string format
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '22

22 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30593 Bug ID: 30593 Summary: Should we switch from Modular Crypt Format to PHC string format 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org When we switched from MD5 to Bcrypt we updated our storage to use Modular Crypt Format.. a new scheme now exists with minor improvements called PHC String Format. Switching to PHC should allow us to support newer crypt cyphers easily, including argon2 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 10734] Add Publication Date Facet in Searching
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '22

22 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 pierre.genty(a)biblibre.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pierre.genty(a)biblibre.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13412] Allow configuration of auto-created authorities
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '22

22 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13412 Victor Grousset/tuxayo <victor(a)tuxayo.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Patch complexity|--- |Small patch -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 21494] New: No checkin notice created for offline circulation checkins
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21494 Bug ID: 21494 Summary: No checkin notice created for offline circulation checkins Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com When using the KOCT plugin for offline circulation, checkout notices are created correctly, but checkin notices are no longer created. To test: - Check out an item via KOCT - Send to Koha and process it there - Verify that the checkout is on the account and a checkout notice has been generated - Check in the item via KOCT - Send to Koha and process it there - Verify that the item is no longer on the account but NO checkin notice has been generated This is quite a problem for libraries using the offline circulation plugin as they rely on the emails to inform the patrons. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 25977] New: Koha Offline Circulation tool to handle trigger for sending necessary notices after successful .koc upload
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25977 Bug ID: 25977 Summary: Koha Offline Circulation tool to handle trigger for sending necessary notices after successful .koc upload Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: tgoatley(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The Koha Offline Circulation tool(s) does not trigger Notices after a successful .koc file upload. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 13412] Allow configuration of auto-created authorities
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13412 Shi Yao Wang <shi-yao.wang(a)inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |shi-yao.wang(a)inLibro.com Status|Failed QA |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13412] Allow configuration of auto-created authorities
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13412 Shi Yao Wang <shi-yao.wang(a)inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #99710|0 |1 is obsolete| | --- Comment #7 from Shi Yao Wang <shi-yao.wang(a)inLibro.com> --- Created attachment 133607 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=133607&action=e… Bug 13412: Allow configuration of auto-created authorities This patch add 2 new system preferences: - GenerateAuthorityField667 - GenerateAuthorityField670 When Koha creates authority records from biblios, use these preferences instead of the hard-coded "Machine generated authority record." and "Work cat." values. Test plan: 1. Make sure AutoCreateAuthorities and BiblioAddsAuthorities are enabled in the system preferences 2. Go to Home › Cataloging › Add MARC record and add a new record 3. Fill in the required fields and add a name in the 100$a field. Note the name, and add the new record. 4. run rebuild_zebra.pl -a 5. Go to Home › Authorities and search for the name you entered in 100$a 6. Select details and look at the 667 and 670 fields. They should default to the hard-coded values. 7. Apply patch, run update database 8. Edit the new GenerateAuthorityField667 and GenerateAuthorityField670 system preferences 9. Do 2-6 . Now the 667 and 670 fields should be what you entered in the system preferences. Thanks for testing Signed-off-by: Bernardo Gonzalez Kriegel <bgkriegel(a)gmail.com> Works well, no errors -- You are receiving this mail because: You are watching all bug changes.

1 0