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

[Bug 25150] New: Accessibility: 2.4.10 Section Headings
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '24

19 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25150 Bug ID: 25150 Summary: Accessibility: 2.4.10 Section Headings Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org There are a large number of cases where we are not adhering to the Section Heading guidelines for a AAA accessibility rating. Headings should be incremental, this bug serves as a collector to find and fix cases of this rule being broken. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 16846] New: Move patron related code to Koha::Patron
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '24

19 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16846 Bug ID: 16846 Summary: Move patron related code to Koha::Patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 70

[Bug 35100] New: Items assigned to StockRotation do not advance if a reserve is triggered before the initial transfer
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '24

18 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35100 Bug ID: 35100 Summary: Items assigned to StockRotation do not advance if a reserve is triggered before the initial transfer 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 I have not recreated personally, but we have found evidence of this multiple times on a site using stock rotation Scenario: 1 - Item is added to stock rotation 2 - The cronjob creates a 'StockRotationAdvance' transfer 3 - The item is checked in, which initiates the transfer, however, a hold is triggered 4 - The hold is confirmed, which cancels the StockRotationAdvance 5 - The item is checked out and returned 6 - The stock rotation cronjob eventually calls Koha::StockRotationItem->needs_advancing which looks for all StockRotationAdvance transfers, ordered by date arrived 7 - The only one has a NULL date arrived 8 - The date arrived is put into dt_from_string, which returns today when given null 9 - The date object above then calls 'delta_days' from dt_from_string() 10 - The number of days from NOW to NOW is always 0 11 - The item does not advance until manually forced -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 94

[Bug 34473] New: "Holds Waiting Over..." is not matching the ReservesMaxPickupDelay syspref
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '24

18 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34473 Bug ID: 34473 Summary: "Holds Waiting Over..." is not matching the ReservesMaxPickupDelay syspref Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Holds are being marked as problematic even before they reach the number of days set in the ReservesMaxPickUpDelay syspref. Library Example: The ReservesMaxPickUpDelay syspref is set to mark holds as problematic at 10 days. Today is August 3rd and yet it is showing holds with expiration dates of August 1st and August 2nd in the Holds Waiting Over 10 days tab at /cgi-bin/koha/circ/waitingreserves.pl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 35539] New: Remove 'bulk' column from categories table
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '24

18 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35539 Bug ID: 35539 Summary: Remove 'bulk' column from categories table 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: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: fridolin.somers(a)biblibre.com, gmcharlt(a)gmail.com, jonathan.druart+koha(a)gmail.com, katrin.fischer(a)bsz-bw.de, kyle.m.hall(a)gmail.com, martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, tomascohen(a)gmail.com Looking at the code (first commited 17 years ago) the "bulk" column in the 'categories' table appears to not be utilized anywhere in the code. Is anyone able to confirm? I suggest we remove this if that is the case. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 47

[Bug 31161] New: OAI-PMH - Add ability to exclude suppressed records in output
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '24

18 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31161 Bug ID: 31161 Summary: OAI-PMH - Add ability to exclude suppressed records in output Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.field(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org At the moment, if a record is suppressed in Koha it will still appear in the results set of an OAI-PMH query. It would be great to have an option to exclude a record if 942$n is set to suppress. That way OPAC suppression would be reflected in the OAI output. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 94

[Bug 17729] New: Move IsItemOnHoldAndFound to Koha::Holds
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '24

18 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17729 Bug ID: 17729 Summary: Move IsItemOnHoldAndFound to Koha::Holds Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 29560] New: Add option to create MARC links when adding items to bundles
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '24

18 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29560 Bug ID: 29560 Summary: Add option to create MARC links when adding items to bundles Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Bug 28854 adds the ability to bundle items together for circulation as collections. It may be useful to optionally allow the action of adding an item into a bundle to trigger the creation of MARC field links in the constituent items biblio. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 71

[Bug 34423] New: (proof-of-concept) Bugzilla could look better with a new skin
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '24

18 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34423 Bug ID: 34423 Summary: (proof-of-concept) Bugzilla could look better with a new skin Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: bugs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: jake.deery(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Hello, I've been experimenting with Bguzilla5 for a few projects, and have got stuck in with the skinning system. As a side project, and side product of this, I've put together a Koha 22.11-inspired skin, the CSS of which can be found at the Gitlab URL below: https://gitlab.com/jahdobble/koha-bz-new-skin I've also put together a few screenshots, so one might look on what it may look like: https://gitlab.com/jahdobble/koha-bz-new-skin/-/tree/main/screenshots I give these files with an Apache 2 licence, but if this needs changing to match Koha's licence, I can do this easily. Please do offer feedback, and submit patches. This proof of concept is free to be either adopted, adapted, or ignored entirely. Many thanks, Jake Deery -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 21729] New: When reverting a hold the expirationdate should be reset?
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '24

18 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21729 Bug ID: 21729 Summary: When reverting a hold the expirationdate should be reset? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 See bug 21608 and bug 21611 - existing behvaiour from 17.11 is restored by those bugs - but it is possible we should consider broader options for what happens when a hold is reset from 'found' status -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 77