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

[Bug 17510] New: marc modification templates ignore subfield $0
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '20

02 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17510 Bug ID: 17510 Summary: marc modification templates ignore subfield $0 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org We have realized that Koha MArc modification templates ignore subfield 0, it is not very common used subfield, it is working with subfields greater than 0 We have create a template for adding 773$0 (host biblionumber in analytics) but the template doesn't get the subfield and only stores main tag 773. Checked in: Koha 3.22 & 16.05.05 Debian 8 and plack enabled TEST Go to Tools --> MARC modification templates Create one rule. Add/Update field 773 0 with value 'demo' save it you can check that subfield is not appearing in the descrption, if you edit it appears, but when you try to execute thah template, and try to previwe the marc you get internal error and get the following log. This action is not implemented yet at /usr/share/koha/lib/Koha/SimpleMARC.pm line 169. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 25694] New: Add ability to delete a Marc Modification Template when viewing
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '20

02 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25694 Bug ID: 25694 Summary: Add ability to delete a Marc Modification Template when viewing Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently, the ability to delete a Template in Marc Modification templates only exists from the marc_modification_templates.pl, however, it would be nice to have the ability to delete the template, when you are looking at the actions of that template. If you accidentally make two templates of the same name and want to delete one, it is hard to be sure which one you are deleting from the list of the templates without seeing the actions of each one. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 25845] New: Cannot limit system logs to 'api' interface
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '20

02 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25845 Bug ID: 25845 Summary: Cannot limit system logs to 'api' interface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 22600 added the 'api' interface to the system, we should also add this as a limit in the tools -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 22106] New: Column settings needs to include OPAC and Intranet holds (requests) tables
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '20

30 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22106 Bug ID: 22106 Summary: Column settings needs to include OPAC and Intranet holds (requests) tables 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 Target Milestone: --- The hold request tables need to be included in the Column settings. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 20342] New: Fix table locking issue, progress bar not updating, and allow use of plack for Stage MARC Import
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '20

30 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20342 Bug ID: 20342 Summary: Fix table locking issue, progress bar not updating, and allow use of plack for Stage MARC Import Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Have you ever seen this error? DBD::mysql::st execute failed: Deadlock found when trying to get lock; try restarting transaction [for Statement "INSERT INTO import_record_matches (import_record_id, candidate_match_id, score), Have you ever noticed your progress bar during stage for import jumps from 0% to 100% with no updates in between? Would you like stage-marc-import.pl to work under plack? If you answered yes to any of the following questions, this bug is for you! During uploads of large records using matching rules, we were getting 'Failed to submit form' popups on the marc record importer. First, I noticed that the parent process of stage-marc-import.pl wasn't returning the job id via ajax until the child process had completed. This works fine for smaller files as they process fast. For large files ( and in particular when using matching rules ) the process takes *much* longer. It appears that $.ajax will resubmit the form if it doesn't get a response back in a given time ( I would estimate that to be about 30 seconds or so ). This causes a *second* instance of stage-marc-import.pl to be run. So now we have two processes both running transactions on the same table for the same batch id. I believe this is what is causing the Deadlock. So, the crux of the matter is that for whatever reason, the parent process will not output until the child process has gone away. Hours of research entailed. The final answer is that the child process must be detached from the parent process. I tried doing this via setsid() but it did not help. Finally, I found that using Net::Server::Daemonize did! After I had my solution, I decided to see if stage-marc-import.pl and background-job-progress.pl could now be run under plack, and it appears that they can! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 24780] New: 952$i stocknumber does not display in batch item modification
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '20

29 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24780 Bug ID: 24780 Summary: 952$i stocknumber does not display in batch item modification Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When trying to edit items via batch item modification, the subfield i does not display. To recreate, add a value to 952$i, then add that barcode to the batch item modification function. You will see the value display in the item summary across the top of the screen, but the $i does not show in the edit section below. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 25810] New: Stage MARC records for import progress meter sticks at 0%
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '20

29 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25810 Bug ID: 25810 Summary: Stage MARC records for import progress meter sticks at 0% Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: Boze.1(a)nd.edu QA Contact: testopia(a)bugs.koha-community.org Created attachment 106031 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=106031&action=e… Gateway time-out error during staging records This is somewhat similar to bug 1816 and bug 18719. We are using Koha 18.11 and upgrading to 19.11, and experience it in both versions. We are importing large sets of biblios on a quarterly basis, around 70,000 records broken into files of 10,000. In the "Stage MARC for import" tool, after clicking the "Stage for import" button, the progress meter sticks at 0%. After about 90 seconds a popover message displays with a "504 Gateway Timeout" and an error saying that the import of records failed. The page doesn't update further, although after waiting a sufficiently long period of time, the "Staged MARC management" tool shows that the records have been staged. We are using nginx as a load balancer, which is what I suspect causes the gateway timeout error. If the progress meter were receiving data to update it, this would probably prevent the timeout and the page would finish uninterrupted. I'm attaching an image of the error. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 25665] New: test t/db_dependent/Circulation.t fails on a specific date
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '20

28 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25665 Bug ID: 25665 Summary: test t/db_dependent/Circulation.t fails on a specific date Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org 2020-06-02 == Test plan == Warning: changing the system time to something too far in the past will disrupt HTTPS & TLS so you will have errors if you try to browse the web in parallel. And other software(like email clients) might pop errors. Nothing to worry about. 1. Set system date to 2020-06-01 (time: somewhere during that day) 2. prove t/db_dependent/Circulation.t 3. "All tests successful." 4. Set system date to 2020-06-02 (time: somewhere during that day) 5. prove t/db_dependent/Circulation.t 6. Fail 7. Set system date to 2020-06-03 (time: somewhere during that day) 8. "All tests successful." master : doesn't happen 19.11.x: doesn't happen 19.05.x: happens (v19.05.11) -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 25037] New: Add support for multiple checkout types
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '20

28 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25037 Bug ID: 25037 Summary: Add support for multiple checkout types Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com This is a blocker to Bug 24101. As of now we have two checkout types, a normal checkout and an on-site checkout type. In order to target circulation rules to a specific checkout type, the issues table must have information on which type of checkout it is. On-site checkout is currently determined by a boolean value in issues.onsite_checkout database column. For supporting multiple checkout types, we should convert this column into a generic checkout_type field. This Bug also sets an easy-to-extend base for further checkout types. In theory a library could define any types of checkouts dynamically, but support for that is outside the scope of this Bug. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 79

[Bug 25089] New: Add checkout_type to circulation rules
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '20

28 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25089 Bug ID: 25089 Summary: Add checkout_type to circulation rules Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com This is a follow-up to Bug 25037. In that Bug we enabled issues to contain data on its checkout type. In this Bug we will add support for defining circulation rules for those types. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 88