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

[Bug 38390] New: Add 'subscriptions+count' embed to vendors endpoint
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '25

25 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38390 Bug ID: 38390 Summary: Add 'subscriptions+count' embed to vendors endpoint Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: kyle(a)bywatersolutions.com, matt.blenkinsop(a)ptfs-europe.com, testopia(a)bugs.koha-community.org, tomascohen(a)gmail.com Depends on: 38011 Blocks: 38010 This was created as a need for the Vendors Vue rework.. we initially tried to go all the way and allow embedding 'subscriptions', but that proved a larger piece of work. For the Vendors UI we only actually need the count of subscriptions for now so we can just embed that. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38010 [Bug 38010] Migrate vendors to Vue https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38011 [Bug 38011] Add a foreign key link between vendors and subscriptions -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 38011] New: Add a foreign key link between vendors and subscriptions
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '25

25 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38011 Bug ID: 38011 Summary: Add a foreign key link between vendors and subscriptions Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org There is a FIXME to add a foreign key between vendors and subscriptions -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 44

[Bug 38389] New: Add 'subscriptions' embed to vendors endpoint
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '25

25 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38389 Bug ID: 38389 Summary: Add 'subscriptions' embed to vendors endpoint Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Depends on: 38011 Blocks: 38010 We should be able to embed subscriptions in the vendors endpoint Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38010 [Bug 38010] Migrate vendors to Vue https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38011 [Bug 38011] Add a foreign key link between vendors and subscriptions -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 35370] New: There should be a system preference to disable checking for holds when issuing an item
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '25

24 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35370 Bug ID: 35370 Summary: There should be a system preference to disable checking for holds when issuing an item 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some library systems want the patron with an item in hand to always be able to checkout the item. It should be possible to configure Koha to ignore holds when issuing items -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 34309] New: Add new preference to set rules for updating damaged status on checkin
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '25

24 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34309 Bug ID: 34309 Summary: Add new preference to set rules for updating damaged status on checkin Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be great if like UpdateNotForLoanStatusOnCheckin we had a similar UpdateDamagedStatusOnCheckin. Some libraries would like to have their damaged statuses for say, mending, come off automatically when an item is checked in. Lisette -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 18239] New: Add Open Document export option to items search
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '25

24 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18239 Bug ID: 18239 Summary: Add Open Document export option to items search Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org For libraries using Excel the CSV export often shows some problems: Umlauts/diacritics are broken, because UTF-8 is not detected automatically and the separators are not recognized with all data appearing in one line. What works really will, also with Excel, is the Open Document format that was added for exporting reports. It would be nice if this option could also be added to the items search in the staff interface. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 38193] New: Add cancellation_reason field to bookings table
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '25

24 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38193 Bug ID: 38193 Summary: Add cancellation_reason field to bookings table Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.derscheid(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In line with other modules, we'd like to specify a reason for a cancellation, either free text or an authorised value. Then we want to use it when cancelling and within the cancellation notice. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 34883] New: Regression in Patron Import dateexpiry function
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '25

24 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34883 Bug ID: 34883 Summary: Regression in Patron Import dateexpiry function Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: jake.deery(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hello all, We are seeing issues in our import_patrons.pl which is causing issue for our academic customer base. In versions prior to 22.11, running import_patrons.pl would cause the dateexpiry to either: — get set based on the contents of the dateexpiry in the CSV file; or — get left as the value already in Koha This worked well for our academics, because they could opt when to update the dateexpiry rather than sending them over every night (e.g. if a student exited a course early, they could be expired in the LMS to prevent them from accessing the services). In 22.11, the update-expiration and expiration-from-today flags have been added to the script. I believe the logic behind these flags is to update the dateexpiry based on enrolment plus user category duration, or today plus user category duration. This probably works great for most libraries, but it isn't necessarily desirable for Colleges. The option still exists to set dateexpiry from the CSV, by not passing the aforementioned flags. However, the dateexpiry now gets set to the following, when using this: — get set based on the contents of the dateexpiry in the CSV file; or — get left as the value already in Koha As you can see, this is a clear regression. Could we please look to remediate this, so I can pass on some good news to our affected customers? Many thanks, Jake Deery PTFS Europe -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 36383] New: Add option to set open booking days
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '25

24 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36383 Bug ID: 36383 Summary: Add option to set open booking days 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With the new bookings module, there is work being done on 34440 to add prep days on either end of the booking to allow the library to gather materials for sending. In some libraries bookings is its own system/department, and is not open every day of the week. It would be helpful to be able to define "booking days" similar to 'curbside hours' and to take these into account when bookings are being placed. i.e.: A booking is being placed to begin on a Monday, it requires 2 warm up days, the bookings dept is closed on weekends. The booking period will need to include the Thursday and Friday of the week before. Similarly, a booking ending on Friday would need cooldown days on Monday and Tuesday -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 38591] New: Add a new ILL status "Available in library"
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '25

23 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38591 Bug ID: 38591 Summary: Add a new ILL status "Available in library" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com A status "Available in library" (or "Received") should be useful to better monitor the progress of the transaction As I understand it, the current workflow (if you check out ILL items) is : - NEW : new request created by a patron or a librarian - REQ : request validated by the library and send to a document provider - CHK : document received by the library and checked out to the patron - RET : document checked in by the patron - COMP : end of transaction. document sent back to the document provider I think it could better be : As I understand it, the current workflow (if you check out ILL items) is : - NEW : new request created by a patron or a librarian - REQ : request validated by the library and send to a document provider - AVA : document received by library, availalable for check out => at THAT stage we can send a message to the patron asking them to come to the library - CHK : document and checked out to the patron - RET : document checked in by the patron - COMP : end of transaction. document sent back to the document provider -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3