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

[Bug 19518] New: Document per-site .psgi files
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '24

03 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19518 Bug ID: 19518 Summary: Document per-site .psgi files Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: magnus(a)libriotech.no Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org koha-plack uses /etc/koha/plack.psgi by default, but it can also use /etc/koha/sites/${instancename}/plack.psgi if one is present. This should be documented in the manpage of koha-plack and the usage embedded in the script. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 21359] New: Add RDF support to OAI-PMH harvester
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '24

02 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21359 Bug ID: 21359 Summary: Add RDF support to OAI-PMH harvester Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The OAI-PMH harvester is set up to import only MARC records into Koha. The goal of this enhancement would be to allow RDF records to be imported into Koha as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 28009] New: Provide better feedback on import
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '24

29 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28009 Bug ID: 28009 Summary: Provide better feedback on import Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com There's a FIXME about extended attributes exception handling. With the work from bug 27857 and friends, we should be able to remove that FIXME and provide better feedback to the end user. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 21893] New: Batch Modify button in report with itemnumber only includes titles in first page of results
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '24

29 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21893 Bug ID: 21893 Summary: Batch Modify button in report with itemnumber only includes titles in first page of results Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 19233 added the ability to push report results into item batch modification when the report includes a column of itemnumbers. However, only items on the first page of item results will be pushed to batch modification -- if the report results include 1200 items and the report page is set to display 1000 rows per page, only the first 1000 items will be batch modified. Koha is clear that it's only modifying those 1000 items, but it still creates extra work, especially since the Rows Per Page dropdown on report results doesn't include an option for All. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 25393] New: Create separate No Automatic Renewal Before rule
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '24

29 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25393 Bug ID: 25393 Summary: Create separate No Automatic Renewal Before rule Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com Koha currently applies the No Renewal Before value to both manual and automatic renewal. Libraries that use a mix of manual and automatic renewal often don't want the same behavior between them - they want manual renewal to be possible earlier in the checkout even if automatic renewal doesn't happen until closer to the due date. We could address this by maintaining separate No Renewal Before values. For what it's worth, we already acknowledge this possibility when leaving No Renewal Before blank. For a manual renewal, no value in No Renewal Before allows renewal immediately. For an automatic renewal, no value in No Renewal Before does not allow renewal until the due date. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 67

[Bug 28980] New: Add temporary passwords which must be reset after first login
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '24

29 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28980 Bug ID: 28980 Summary: Add temporary passwords which must be reset after first login Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be great if passwords could be marked as temporary, so that staff users could set temporary passwords for borrowers, and those borrowers would have to reset their password on their 1st successful login. This would prevent staff users from re-using the same simple password across a range of users and having those same simple passwords persist over time. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 29046] New: Allow libraries to specify email order for "AutoEmailPrimaryAddress"
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '24

28 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29046 Bug ID: 29046 Summary: Allow libraries to specify email order for "AutoEmailPrimaryAddress" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com At the moment, Koha::Patron->first_valid_email_address is hard-coded to go "email", "emailpro", and then "B_email". Libraries should be able to specify their own preference (at least since historically email was "Home" and emailpro was "Work" and many non-public library Koha databases would rather privilege emailpro over email). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 58

[Bug 21638] New: Allow reporting of holds cancelled by cancel_expired_holds.pl and ExpireReservesMaxPickUpDelay
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '24

27 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21638 Bug ID: 21638 Summary: Allow reporting of holds cancelled by cancel_expired_holds.pl and ExpireReservesMaxPickUpDelay Change sponsored?: --- Product: Koha Version: 18.05 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 ExpireReservesMaxPickUpDelay is set to Allow, waiting holds are automatically cancelled by cancel_expired_holds.pl. But, generally, libraries still need to physically remove those items from their hold shelf and check them in to guarantee there are not pending holds or transfers to be triggered. A report to identify these items is imperfect and cannot definitively distinguish a hold cancelled by the cron from a hold cancelled by an employee. Bug 14134 established behavior that displays holds which *will* be cancelled by the next run of the cron on the "holds over" tab in Holds Awaiting Pickup, but doesn't allow staff to see which holds have already been cancelled. It'd be great if the cron could email a list of cancelled holds. Additionally, reporting would be improved by the introduction of a new value in old_reserves.found for items cancelled by the cron (maybe E for expired). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 26317] New: Misleading choices from reports error when runtime parameter is named incorrectly
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '24

26 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26317 Bug ID: 26317 Summary: Misleading choices from reports error when runtime parameter is named incorrectly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: - create a new report from SQL - enter "SELECT <<whatever|whatever>>" and try to save - Get an error "Errors found when processing parameters for report: whatever: The authorized value category (whatever) you selected does not exist." - Error provides two options, "Save Anyway" or "Edit SQL" - Click Edit SQL, get taken to an empty report "Edit SQL" wants to take you back to the previously saved version of your report. But if you've ended up at this error from a brand new report that's never been saved, then the "Edit SQL" button is going to take you to a blank report, trashing whatever you've just written. If we can't retain that SQL through the error on an unsaved report, then we should remove the Edit SQL button when working with a report that hasn't been saved yet. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 28404] New: Improve calendar tool management
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '24

26 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28404 Bug ID: 28404 Summary: Improve calendar tool management Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org 1. It would be great if libraries could delete holidays from the calendar tool. Because they can’t be deleted by our library we end up with lots of old holidays in the table and sometimes incorrect entries. 2. Holidays display in date ascending order which means the oldest ones are listed first. When you have a long list of old holidays this means you have to do a lot of scrolling to get to the current year. It would be very useful if the holidays could sort in year descending order and within each year the dates would sort in date ascending order. This would put the most current dates at the top of the table for quicker viewing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5