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

[Bug 21577] New: Enable Koha to act as Shibboleth identity provider
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '23

19 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21577 Bug ID: 21577 Summary: Enable Koha to act as Shibboleth identity provider 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org For us it is important now, as we are going to append our Koha to national project which aims to enable users to use "all" libraries from one place. Maybe this could be implemented using Net::SAML2::IdP -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 23846] New: bad iso 2709 record silently results in broken marcxml
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '23

19 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23846 Bug ID: 23846 Summary: bad iso 2709 record silently results in broken marcxml Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P3 Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: dominique(a)leducq.net QA Contact: testopia(a)bugs.koha-community.org Created attachment 94419 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=94419&action=ed… iso 2709 with problematic record The (UNIMARC) ISO 2709 record in the attached file (26080509.txt) seems to have a problem : the 009 field should contain an ARK identifier but seems to be something else, with a subfield separator in it. When imported into koha, it is said to be imported all right, but when trying to access the notice, we get the following error message : Invalid data, cannot decode object (id=9865, format=marcxml, schema=UNIMARC) Investigating, I found that the marcxml in biblio_metadata.metadata is broken : the content of the <controlfield tag="009"> element is a verbatim copy of the 009 field, including the (non-printable, 0x1F) subfield separator (cf line 9 of the attached marcxml) When I deleted this element in the database, all seems to work fine. I think either the record should be rejected alltogether, with an explicit error message, or the erroneous field should be droped. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 32243] New: BackgroundJob: Leave encoding to Net::Stomp
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '23

19 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32243 Bug ID: 32243 Summary: BackgroundJob: Leave encoding to Net::Stomp 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Question: Should we actually use Net::Stomp::Client ? Further info: If $Net::STOMP::Client::Frame::UTF8Header is true, the module will use UTF-8 to encode/decode the header part of the frame. If $Net::STOMP::Client::Frame::UTF8Body is true, the module will: [etc] -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 30656] New: Introduce worker_manager daemon
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30656 Bug ID: 30656 Summary: Introduce worker_manager daemon 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 Depends on: 27783 We have a simple worker script and we now start up two workers working through two distinct queues. However, as noted in bug 27783, it would be greatly beneficial to have a worker manager that could spawn parallel workers and use a config to define the number of workers and what those workers can work upon. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27783 [Bug 27783] Introduce background job queues -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 32450] New: Make it possible to exclude debit types from charges counted for circulation restriction (noissuecharge)
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32450 Bug ID: 32450 Summary: Make it possible to exclude debit types from charges counted for circulation restriction (noissuecharge) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: michaela.sieber(a)kit.edu We do have several permissions that are about what is counted for noissuecharge, the dynamic restriction for circulation. * ManInvInNoissuesCharge = All manual invoiceable debit types * RentalsInNoissuesCharge = Exclude hold charges * HoldsInNoissuesCharge = Exclude rental charges This all comes from a time when Koha's debit types were hardcoded, but had no 'home' in the database. Now that they have their own database table we could move them to a flag for each debit type. This was triggered by a discussion by making a certain debit type not count towards the circulation restriction, but our current system is to inflexible in that regard. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 70

[Bug 24574] New: Broken MARC records cause "invalid data, cannot decode object" on ISBDdetail and MARCdetail pages.
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24574 Bug ID: 24574 Summary: Broken MARC records cause "invalid data, cannot decode object" on ISBDdetail and MARCdetail pages. 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: rudolfbyker(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Broken MARC records cause "invalid data, cannot decode object" on ISBDdetail and MARCdetail pages. Although this is fixed on the /cgi-bin/koha/catalogue/detail.pl page (see Bug #23425 ), it's still not handled gracefully on these pages: /cgi-bin/koha/catalogue/ISBDdetail.pl /cgi-bin/koha/catalogue/MARCdetail.pl Use case: Some of our staff have to update books. They use "cataloging search", enter the barcode, then click the title of the book. This takes them directly to the MARCdetail page. To fix the MARC data, they need to work around the problem by editing the URL and replacing "MARCdetail.pl" with "detail.pl". Since most of our staff is not very technically apt, this is a problem. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 30182] New: background_jobs.status should be an ENUM
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30182 Bug ID: 30182 Summary: background_jobs.status should be an ENUM 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 31090] New: Background jobs needs highlights and searchability
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31090 Bug ID: 31090 Summary: Background jobs needs highlights and searchability Change sponsored?: --- Product: Koha Version: 21.11 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 It would be great if background jobs actually highlighted what was changed in the records. It would also be great if we could search the jobs. Right now the search bar only searches the list of jobs, but not the contents. If you are searching for a job that modified a certain record, you have to do a lot of manual scanning for this modification, if it exists. If the search bar searched contents, that would be a tremendous help. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 31336] New: In-progress background jobs give incorrect progress message
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31336 Bug ID: 31336 Summary: In-progress background jobs give incorrect progress message 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: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 31245 If one loads the background job details page (background_jobs.pl) for a job that has started but not yet completed, Koha shows a message of "No items modified." We should give an accurate message along the lines of "This job is still in progress." A completed job lists all of the modified items/bibs/whatever. I'm ambivalent about whether or not we need to list the already-modified records when loading this page for an incomplete job. To recreate: 1 - write a report, SELECT itemnumber FROM items. With the default dev data, that's 961 items. 2 - use your report to send all of those to batch mod. The page will take a while to load 3 - while your batch mod page is loading, open background_jobs.pl in another tab and have it ready to go 4 - modify something in all 961 records -- add a public note or something -- once you submit this job it should take about 45 seconds to complete 5 - BEFORE THE JOB IS DONE - reload background_jobs.pl, see your job is listed and shows status=started. click to the details view for your job, see it shows a message of "No items modified." Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31245 [Bug 31245] Job detail view for batch mod explode if job not started -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 31580] New: Koha::BackgroundJob->finish should consider the 'failed' case
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31580 Bug ID: 31580 Summary: Koha::BackgroundJob->finish should consider the 'failed' case Change sponsored?: --- Product: Koha Version: unspecified 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org See bug 27421, which introduces it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4