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

[Bug 21458] New: Messaging preferences extension: Hold filled digest
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '22

20 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21458 Bug ID: 21458 Summary: Messaging preferences extension: Hold filled digest Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hi, if borrowers use "Holds to pull" usualy librarians prepare more than one document. Now Koha sends x notices for every hold. It would be better to send digest with all holds together in one e-mail or SMS. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 31120] New: Items will renew for zero ( 0 ) days if renewalperiod is blank/empty value
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '22

20 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31120 Bug ID: 31120 Summary: Items will renew for zero ( 0 ) days if renewalperiod is blank/empty value Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If the rule renewalperiod is the blank empty string instead of being null/undefined or non-existant, Koha will interpret the renewal period as being zero days instead of falling back to the issuelength rule. It makes sense to me that a literal 0 here should make it renew for zero days even though that is nonsensical. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 30878] New: Canceling holds from 'Holds awaiting pickup' should not reset the selected tab
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '22

20 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30878 Bug ID: 30878 Summary: Canceling holds from 'Holds awaiting pickup' should not reset the selected tab Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When canceling holds waiting over X days in "Holds awaiting pickup" view, form submission resets the selected tab to "Holds waiting". This tab reset may cause confusion for the user and lead to unwanted actions. Instead, the user should be returned to the same tab that they began with. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 31204] New: Edit dropdown on results.tt should indicate it is record modification
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '22

20 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31204 Bug ID: 31204 Summary: Edit dropdown on results.tt should indicate it is record modification Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On results.tt there is an option to select records and then, from the toolbar, select edit and choose either 'Batch edit' or 'Batch delete'. Some librarians have found this confusing, thinking it would lead them to 'Batch Item Modification' when instead it leads to 'Batch record modification'. We could make it less confusing by clearly indicating this function takes the user to record modification, not item modification. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 30308] New: bulkmarcimport.pl broken by OAI-PMH:AutoUpdateSets(EmbedItemData)
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '22

19 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30308 Bug ID: 30308 Summary: bulkmarcimport.pl broken by OAI-PMH:AutoUpdateSets(EmbedItemData) 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: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz I was trying to import records and items with bulkmarcimport.pl. The records were added, but no items were saved to the DB. Turning off OAI-PMH:AutoUpdateSets and OAI-PMH:AutoUpdateSetsEmbedItemData fixed the problem. I think this is what happens: 1. bulkmarcimport.pl calls C4::Biblio::AddBiblio on line 461: eval { ( $biblionumber, $biblioitemnumber ) = AddBiblio( $record, '', { defer_marc_save => 1 } ) }; https://git.koha-community.org/Koha-community/Koha/src/branch/master/misc/m… 2. C4::Biblio::AddBiblio has this code: # update OAI-PMH sets if(C4::Context->preference("OAI-PMH:AutoUpdateSets")) { C4::OAI::Sets::UpdateOAISetsBiblio($biblionumber, $record); } https://git.koha-community.org/Koha-community/Koha/src/branch/master/C4/Bib… 3. C4::OAI::Sets::UpdateOAISetsBiblio does this: if (C4::Context->preference('OAI-PMH:AutoUpdateSetsEmbedItemData')) { C4::Biblio::EmbedItemsInMarcBiblio({ marc_record => $record, biblionumber => $biblionumber }); } https://git.koha-community.org/Koha-community/Koha/src/branch/master/C4/OAI… 4. C4::Biblio::EmbedItemsInMarcBiblio does: my ($params) = @_; $marc = $params->{marc_record}; ... _strip_item_fields($marc, $frameworkcode); # ... and embed the current items my $dbh = C4::Context->dbh; my $sth = $dbh->prepare("SELECT itemnumber FROM items WHERE biblionumber = ?"); https://git.koha-community.org/Koha-community/Koha/src/branch/master/C4/Bib… The end result is that item data is stripped from the record that is about to be imported, and no item data is added from the DB, since they are not there yet. Not sure how to fix this. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 31138] New: DataTables is not raising error to the end user
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '22

19 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31138 Bug ID: 31138 Summary: DataTables is not raising error to the end user Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Staff Client Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com DataTables is not raising error to the end user, it's only displaying a generic message in the console. This leads to lot of questions on IRC or the mailing list ("the table is empty"). We can do better and display what went wrong. We could also imagine add a link to the wiki for the more common problems (won't be implemented here however). -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 30458] New: Librarian ( manager_id ) not included in accountline when using "Payout amount" button
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '22

19 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30458 Bug ID: 30458 Summary: Librarian ( manager_id ) not included in accountline when using "Payout amount" button Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 30471] New: Typo in Circulation Rules - Lost item fee refund policy
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '22

19 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30471 Bug ID: 30471 Summary: Typo in Circulation Rules - Lost item fee refund policy Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client 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 setting a rules for a specific branch the default rule is displayed incorrectly To test: 1 - Browse to 'Administration->Circulation and fines rules' 2 - Make sure you are editing 'Standard rules for all libraries' 3 - Set 'Lost item fee refund on return policy' to 'Refund lost item charge and charge new overdue fine' 4 - Swtich to edit rules for a specific library, click on the dropdown for 'Lost item fee refund on return policy' and note default says 'Use default (Refund lost item charge and restore overdue fine)' 5 - Switch default/all libraries rule to 'Refund lost item charge and restore overdue fine' 6 - On specific branch note the default option is now 'Use default (Refund lost item charge and charge new overdue fine)' -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 31202] New: Koha removes optional SIP fields with a value of "0"
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '22

19 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31202 Bug ID: 31202 Summary: Koha removes optional SIP fields with a value of "0" Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Discovered this when trying to send the number of patron holds in a custom SIP field. If the value of a SIP field is "0", that evaluates to false, so any calls to maybe_add with a value of "0" will not get added to the SIP response message. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 31201] New: Pseudonymization.t failing if selenium/patrons_search.t failed before
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '22

19 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31201 Bug ID: 31201 Summary: Pseudonymization.t failing if selenium/patrons_search.t failed before Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: Test Suite Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 25551 Koha_Master/2115 19:52:29 koha_1 | # Failed test 'No tests run for subtest "PseudonymizedBorrowerAttributes tests"' 19:52:29 koha_1 | # at t/db_dependent/Koha/Pseudonymization.t line 211. 19:52:29 koha_1 | Duplicate ID# Looks like your test exited with 255 just after 3. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25551 [Bug 25551] [OMNIBUS] Some tests are failing randomly -- You are receiving this mail because: You are watching all bug changes.

1 15