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

[Bug 15516] Allow to place a hold on first available item from a group of titles
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15516 --- Comment #518 from Pedro Amorim <pedro.amorim(a)openfifth.co.uk> --- (In reply to David Cook from comment #517) > Created attachment 185135 [details] [review] > Bug 15516: (follow-up) fix holds API > > This patch adds a missing hold_group_id definition in holds API > > Test plan: > 0. Apply the patch > 1. Rebuild swagger > redocly bundle --ext json api/v1/swagger/swagger.yaml \ > --output api/v1/swagger/swagger_bundle.json > 2. Run unit tests: > prove t/db_dependent/api/v1/holds.t Hi David, I had already added that in my follow-up patch I believe. Comment 509. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 40599] New: Catalog concern, only allow staff account should be assigned
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40599 Bug ID: 40599 Summary: Catalog concern, only allow staff account should be assigned 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: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently, we can assign a catalog concern to any Koha account. It would help to only show and allow staff account (it could be all staff account, or linked to a specific permission) as these are the persons able to correct the problem. To reproduce : 1- Activate system preference CatalogConcerns (or OpacCatalogConcerns) 2- Create a catalog concern a- from the staff interface, go to a bibliographic record, click on "New" then "New catalog concern", fill in the title and click on "Submit". b- from the OPAC, go to a bibliographic record, click on "Report a concern", fill in the title and click "Submit" (you must be logged in). 3- Go to Cataloging, then Catalog concerns (there is also a link on the main page is there are concerns open). 4- Select a concern and click on "Details" 5- On the box change assignee, check that you can search for any account, even non staff account. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15516] Allow to place a hold on first available item from a group of titles
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '25

06 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15516 --- Comment #517 from David Cook <dcook(a)prosentient.com.au> --- Created attachment 185135 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=185135&action=e… Bug 15516: (follow-up) fix holds API This patch adds a missing hold_group_id definition in holds API Test plan: 0. Apply the patch 1. Rebuild swagger redocly bundle --ext json api/v1/swagger/swagger.yaml \ --output api/v1/swagger/swagger_bundle.json 2. Run unit tests: prove t/db_dependent/api/v1/holds.t -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 37514] New: Batch patron modification should have renewal as option
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '25

05 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37514 Bug ID: 37514 Summary: Batch patron modification should have renewal as option Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Batch patron modification would be a logical place to include an option to renew selected accounts. Currently the account expiry date can be modified there, but that only updates the account without being an actual renewal. For libraries that don't want to automate account renewal, it would be nice to have a way to renew in batch that isn't messing with patron imports. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 37621] New: Add possibility to auto-renew patron registration with modification request
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '25

05 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37621 Bug ID: 37621 Summary: Add possibility to auto-renew patron registration with modification request Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To replicate: 1. A patron receives a message in their OPAC account their account is about to expire. A custom message says to please update their account. 2. Staff receive a patron modification notification. 3. At this point staff have to go to each patron account to manually renew the account. It would be nice if the update patron records table could have a registration expiration date column. It would also be nice if there was a checkbox to also renew the registration when approving the change request. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 15516] Allow to place a hold on first available item from a group of titles
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '25

05 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15516 Lynn Uhlman <lynn.uhlman(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lynn.uhlman@bywatersolution | |s.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9762] Log circulation overrides
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '25

05 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9762 --- Comment #80 from Hammat wele <hammat.wele(a)inlibro.com> --- Created attachment 185118 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=185118&action=e… Bug 9762: (follow-up) Add branchcode to Log circulation and add some override confirmations in action logs, fix typos -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 37407] New: Fast Add / Fast Cataloging from patron checkout does not checkout item
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '25

04 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37407 Bug ID: 37407 Summary: Fast Add / Fast Cataloging from patron checkout does not checkout item Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To replicate: 1. Go to any patron checkout screen 2. Enter a barcode that is not in the system 3. Click on the "Add using Fast Cataloging" in Barcode not found warning 4. Enter bib/item info and click on Save 5. You are returned to the patron checkout screen but it is not checked out The bib record and item record are created, but staff will need to scan the item again in order to check it out. Since this is the workflow a lot of libraries use for ephemeral items, magazines, etc, this will add a lot of clicks and cause confusion. Worked as expected as late as 23.11.05 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 38652] New: Adjust SeparateHoldings preference to create third holdings tab for branches in library group.
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '25

04 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38652 Bug ID: 38652 Summary: Adjust SeparateHoldings preference to create third holdings tab for branches in library group. Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: sspohn(a)oslri.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This enhancement proposes to adjust the SeparateHoldings system preference and the record display in the Staff Interface (/cgi-bin/koha/catalogue/detail.pl) to make it possible, using “library_group”, to display items from multibranch members of a consortium. This adjustment would create an option third tab that would display holding from other members of a library_group. Current options for SeparateHoldings: Don’t Separate “0” Separate “1” We propose: Don’t Separate “0” Separate (2 columns) “1” Separate (3 columns) “2” Behavior: No change to Don’t Separate “0” or Separate (2 columns) “1”. IF Separate (3 columns) “2” AND IF loggedInLibrary is member of a library_group THEN alter /cgi-bin/koha/catalogue/detail.pl as follows: Display a third tab between the first “homebranch” tab and the third “all other items” tab. The new second tab should display items holdings from other members of the library_group. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 8214] Create a bound with function
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '25

04 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8214 --- Comment #16 from ashley.day(a)rcm.ac.uk --- I am really glad I found that this bug has been reopened! The instance above that Katrin described in 2017 is exactly the situation we have in my library. We have items that were privately bound eons ago in our reference collection and then an exactly identical item as the one within the bound volume on the lending shelves. I was always taught (although this could be incorrect) that bound-with volumes are really horizontal relationships, not vertical, as Heather and Helen have aptly described for analytics/parent-children. The current linking functionality on Koha does not adequately portray the difference between the analytics and bound withs. I too used the Voyager workflow on bound withs as Helen details and it was much simpler and quicker. -- You are receiving this mail because: You are watching all bug changes.

1 0