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

[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 19887] New: Two Factor Authentication: Google Authenticator
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19887 Bug ID: 19887 Summary: Two Factor Authentication: Google Authenticator 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 Easy two-factor solution for users with smartphones. Google Authenticator and Perl: https://blog.darkpan.com/article/6/Perl-and-Google-Authenticator.html https://debian-administration.org/article/729/Implementing_two_factor_authe… https://github.com/j256/perl-two-factor-auth -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 29893] New: ElasticSearch Config UI deletes mappings
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29893 Bug ID: 29893 Summary: ElasticSearch Config UI deletes mappings Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: domm(a)plix.at When using the Elasticsearch UI /cgi-bin/koha/admin/searchengine/elasticsearch/mappings.pl to edit search mappings one can quite easily delete a lot of mappings by mistake. To reproduce: * go to /cgi-bin/koha/admin/searchengine/elasticsearch/mappings.pl * click on the "Authorities" Tab * You should see ~ "67 entries" * enter "Heading-Main" into the search field, you now see ~8 entries ("filtered from 67 entries" * Click "save" Button * Go again to the "Autorities" Tab * You now see ~ "8 entries" * All the other entries have been deleted! What obviously happens is that all entries that where filtered due to the search are not submitted to the backend on save. The backend now interprets the missing entries as entries that shall be deleted. And happily deleted them! This totally breaks the search index (after the next index run, or when adding single items), as (eg in the auth-index) "authtype" is no longer indexed. I currently don't have a 21.11 or later version at hand, so maybe this has already been fixed? To fix this bug we would either have to un-hide the filtered entries before submitting the form; change the backend to not deleted missing entries (which means that the delete-action would have to be implemented a bit different); something else? I guess that the first fix is easier, and would also make sense with regard to how that form works. Greetings, domm -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 40

[Bug 23092] New: Transfers should record 'requested' as well as 'sent' and 'arrived' dates.
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23092 Bug ID: 23092 Summary: Transfers should record 'requested' as well as 'sent' and 'arrived' dates. 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- The transfers system is very much tied to the Holds/Reserves features at the moment, but slowly some other subsystems are starting to use it too (Stock Rotation, Rotating Collections). For full audit purposes we should record the 'requested' date along with the 'sent' and 'arrived' dates. Currently stock rotation misuses 'sent' to mean 'requested', so the item may have not actually been picked off the shelf, captured at checkin, and put into physical transit to the next library. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 59

[Bug 23112] New: Circulation of ILL items
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23112 Bug ID: 23112 Summary: Circulation of ILL items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com Target Milestone: --- The ILL framework we have supports the tracking of ILL requests well, but once the item has arrived at the library there isn't a clear workflow for lending it to the end user. https://wiki.koha-community.org/wiki/ILL_Circulation_RFC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 123

[Bug 25029] New: AllowPatronToControlAutorenewal needs to have a disable setting
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25029 Bug ID: 25029 Summary: AllowPatronToControlAutorenewal needs to have a disable setting Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 The AllowPatronToControlAutorenewal has a Staff or Stand and Patron setting, but it needs to be a master disable switch as well. With it in the staff only position, staff still see a switch for auto renewal in the patron settings, despite that nothing is set in the circulation rules. It would be ideal if AllowPatronToControlAutorenewal had a Disable setting that: * hid the "Allow auto-renewal of items" choice in the Library Management settings for the patron. * hid the three columns in the circulation rules that deal with Auto Renewal. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 20398] New: Remove search result highlighting
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '22

20 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20398 Bug ID: 20398 Summary: Remove search result highlighting 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: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Search result highlighting is broken and has been broken for a long time: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11270 Adding insult to injury there is no way to deactivate it on the staff interface. We are so used to see it that we don't pay attention, but new users notice it, and complain. It would be good to remove it until it is fixed. (As a general rule i think features that aren't entirely functional shouldn't make it into the release until they are actually ready.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 57

[Bug 29474] New: Automatic renewals cronjob is slow on systems with large numbers of reserves
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '22

20 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29474 Bug ID: 29474 Summary: Automatic renewals cronjob is slow on systems with large numbers of reserves Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When a site has many holds the automatic renewals cron can take a long time to run This is increased if the system preference 'AllowRenewalIfOtherItemsAvailable' is set to allow -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 70

[Bug 22333] New: Replace duplicated code in CanBookBeRenewed with GetSoonestRenewDate
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '22

20 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22333 Bug ID: 22333 Summary: Replace duplicated code in CanBookBeRenewed with GetSoonestRenewDate Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- There is some duplicated code between CanBookBeRenewed and GetSoonestRenewDate. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17