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

[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

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

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 Fridolin Somers <fridolin.somers(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fridolin.somers(a)biblibre.co | |m --- Comment #8 from Fridolin Somers <fridolin.somers(a)biblibre.com> --- We should add this facet at least for Elasticsearch where it can be configured and disabled via staff interface. -- You are receiving this mail because: You are watching all bug changes.

1 0

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

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 Fridolin Somers <fridolin.somers(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=26839 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11989] Holds Queue Scheduling
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11989 Lisette Scheer <lisetteslatah(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lisetteslatah(a)gmail.com --- Comment #3 from Lisette Scheer <lisetteslatah(a)gmail.com> --- +1 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 12446] Enable an adult to have a guarantor
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12446 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #180 from Owen Leonard <oleonard(a)myacpl.org> --- This seems to be working well. There's just one issue raised by the QA tool: FAIL members/memberentry.pl FAIL critic # Variables::ProhibitUnusedVariables: Got 1 violation(s). -- You are receiving this mail because: You are watching all bug changes.

1 0

[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 30564] New: Prevent user in staff interface from setting incorrect pickup location on item-level hold
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '22

21 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30564 Bug ID: 30564 Summary: Prevent user in staff interface from setting incorrect pickup location on item-level hold Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 When placing a hold in the staff interface, we have one pickup location dropdown at the top of the page for bib-level holds, and then separate dropdowns for the pickup location for an item-level hold. The interface here makes it easy to mistakenly place an item-level hold for the wrong pickup location. To recreate: - go to request.pl - change the pickup location at the top of the form - then pick a specific item and click "Place hold" - Koha ignores the change you made to the bib-level dropdown and maintains the default pickup from the item-level line When one changes the bib-level pickup, Koha should automatically change all the item-level locations to match the new selection. If that would result in an invalid pickup location, the item should instead go to a blank pickup so the user is forced to pick something. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[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