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

[Bug 39550] New: RestrictPatronsWithFailedNotices system preference should not be in Patron relationships section
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39550 Bug ID: 39550 Summary: RestrictPatronsWithFailedNotices system preference should not be in Patron relationships section Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I was going to document bug 23295, and noticed the new system preference is under the Patron relationships section. I feel like that's not the right place for it. But there doesn't seem to be a fitting section for it either. Here are some options I thought about 1. Create a "Patron restrictions" section - either with only this one, or we could move a couple of other ones too like useDischarge 2. Place the pref under "General" 2. Place under "Notices and notifications" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 39857] New: OAI expanded_avs option broken
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39857 Bug ID: 39857 Summary: OAI expanded_avs option broken Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 31224 moved OAI to use metadata_record - when doing so the param to expand fields was incorrectly added as: expand_coded_values => $expanded_avs, It should be: expand_coded_fields => $expanded_avs, -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 36431] New: SIP2: Checkin does not show difference between WasTransfered and NeedsTransfer
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36431 Bug ID: 36431 Summary: SIP2: Checkin does not show difference between WasTransfered and NeedsTransfer Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org If you enable AutomaticItemReturn, SIP will trigger an eventual transfer to home branch when checking in. If disabled, it will not but the station receives an alert to notify the user. But the SIP response for both cases is actually the same. The code shows this: if ($messages->{NeedsTransfer}) { $self->{item}->destination_loc($messages->{NeedsTransfer}); $self->alert_type('04'); # send to other branch } if ($messages->{WasTransfered}) { # set into transit so tell unit $self->{item}->destination_loc($item->homebranch); $self->alert_type('04'); # send to other branch } The destination location will be the same in both cases. And the alert number is the same too. How could the SIP station 'know' that the transfer is done already or still needs to? Both SIP responses contains AO holding branch, AQ destination, CT destination and CV 04. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 37273] New: Add ID column to Agreements table in the ERM
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37273 Bug ID: 37273 Summary: Add ID column to Agreements table in the ERM Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Created attachment 168606 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=168606&action=e… ERM ID number appended to agreement name When creating an Agreement or License in the ERM, an ID number is added to the agreement or license name. If it is necessary for the ID number to be visible, it should be in a separate column from the name. Having the ID number appended to the name is a little confusing (see example image). Another option is to hide the hide ID number if it is not needed. -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 32742] New: Patron's lists are not in alphabetical order
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32742 Bug ID: 32742 Summary: Patron's lists are not in alphabetical order 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: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In the patron module, the list under 'Add to patron list' is not in alphabetical order -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 40

[Bug 40570] New: CSVDelimiter syspref will not display "commas" when set to ", "
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40570 Bug ID: 40570 Summary: CSVDelimiter syspref will not display "commas" when set to "," Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration 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 the syspref CSVDelimiter is set to "," koha will tell the user it's actually set to "#". We must not have escaped something properly. To recreate: - set CSVDelimiter to "commas" - reload the page - see the syspref says "#'s" instead - inspect the dropdown, see no value is designated as selected in the html - in reports, SELECT * FROM systempreferences WHERE variable='CSVDelimited' - see the value = , - set CSVDelimiter to "slashes" - reload the page - see the syspref correctly says "slashes" - inspect the dropdown, see "slashes" is selected -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 40514] New: Koha offline circulation tool
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40514 Bug ID: 40514 Summary: Koha offline circulation tool Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: klas.blomberg(a)skovde.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Created attachment 184626 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=184626&action=e… Screen shot The Firefox plugin "Koha Offline Circulation Tool" needs to be "verified" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 25019] New: Non standard initialization in ViewPolicy filter
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25019 Bug ID: 25019 Summary: Non standard initialization in ViewPolicy filter 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The ViewPOlicy filter has its own method for initializing its values, and then using its variables. This should be homogeneous through the filters. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 15461] Add shelving location to holdings table as a separate column
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15461 Fridolin Somers <fridolin.somers(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to main |Needs documenting CC| |fridolin.somers(a)biblibre.co | |m --- Comment #62 from Fridolin Somers <fridolin.somers(a)biblibre.com> --- Enhancement not pushed to 24.11.x -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38647] New: Can't filter holdings table by shelving location
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38647 Bug ID: 38647 Summary: Can't filter holdings table by shelving location Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In 24.05, libraries can no longer filter the holdings table in the staff interface by shelving location since the Home library column is now a drop-down instead of allowing free text entry. As of 23.11, the filtering was free text instead of a drop-down, which meant that libraries could type a library name *or* a shelving location to filter. Additionally, the holdings table search bar doesn't appear to 'read' shelving locations, so libraries can't use that to pinpoint items with a specific shelving location either. This will likely be moot with Bug 15461 - Add staff equivalent for OpacLocationOnDetail, but in the meantime, it isn't user-friendly for libraries who need that column to filter bibs with many holdings. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3