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

[Bug 3007] Remove untranslated unimarc_field_700-4 value builder
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3007 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version(s)| |23.11.00 released in| | Status|Passed QA |Pushed to master -- You are receiving this mail because: You are watching all bug changes.

1 0

[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 8838] Digest option for HOLD notice
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8838 Emily Lamancusa <emily.lamancusa(a)montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact| |emily.lamancusa@montgomeryc | |ountymd.gov Status|Signed Off |Failed QA CC| |emily.lamancusa@montgomeryc | |ountymd.gov --- Comment #44 from Emily Lamancusa <emily.lamancusa(a)montgomerycountymd.gov> --- Excited to see this enhancement move forward! Just a few fixes needed: - reserves.t needs a minor rebase - The update should include a default SMS notice as well, to prevent the worst-case scenario where a customer may not be notified of their waiting holds at all if the library doesn't specify an SMS template. Plus a few trivial typoes, etc: - Typo in the dbrev query to insert the default email template: Waiting since: [% hold.waitingdate %]:\r\n should be: Waiting since: [% hold.waitingdate %]\r\nWaitng at: [% hold.branch.branchname %]:\r\n - Typo in sample_notices.yml line 1789 - "Waitng" - Remember to tidy :) -- You are receiving this mail because: You are watching all bug changes.

1 0

[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 35089] New: Background worker: Should prefetch-count be activemq.prefetchSize ?
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35089 Bug ID: 35089 Summary: Background worker: Should prefetch-count be activemq.prefetchSize ? 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 >From IRC: marcelr: Joubu: Should prefetch-count be activemq.prefetchSize in worker script? See https://metacpan.org/pod/Net::Stomp versus https://www.rabbitmq.com/stomp.html It seems that we should use the CPAN name instead of the Stomp plugin directive? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[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

[Bug 34836] New: OPAC ISBD or MARC view blows up with error 500
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '23

18 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34836 Bug ID: 34836 Summary: OPAC ISBD or MARC view blows up with error 500 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Bug 34694 added check on $patron var for opac-detail.pl Since Bug 30846 also impacts ISBD and MARC views, same check should be made. -- You are receiving this mail because: You are watching all bug changes.

1 35