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

[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

[Bug 38851] New: Rephrase OpacRenewalBranch and RESTAPIRenewalBranch to specify that they are about renewals
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '25

04 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38851 Bug ID: 38851 Summary: Rephrase OpacRenewalBranch and RESTAPIRenewalBranch to specify that they are about renewals Change sponsored?: --- Product: Koha Version: Main 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 The descriptions for both OpacRenewalBranch and RESTAPIRenewalBranch system preferences are very vague. I know there is "Renewal" in the system preference names, but for translation, I think it would be best to have it in the description so that it's translated. Also, now that there are two, the sentences could be different to state what they are about. Currently, they both have this description: Use ___ as branchcode to store in the statistics table. OpacRenewalBranch could have this description: Use ___ as branchcode to store in the statistics table for renewals done in the OPAC. RESTAPIRenewalBranch could have this description: Use ___ as branchcode to store in the statistics table for renewals done through the REST API. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 39777] New: ILL History Check does not show in OPAC
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '25

04 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39777 Bug ID: 39777 Summary: ILL History Check does not show in OPAC Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: pedro.amorim(a)openfifth.co.uk Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: tomascohen(a)gmail.com CC: pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 39062] New: Increase length of items.stocknumber (Inventory Number)
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '25

04 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39062 Bug ID: 39062 Summary: Increase length of items.stocknumber (Inventory Number) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org items.stocknumber (labeled as Inventory Number, 952$i, in edit interface) is a field that many libraries use to hold an idiosyncratic bit of local data. For such libraries, the 32 character limit can be an issue. If there's a compelling reason not to increase the size of this field, I haven't thought of or found it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 38142] New: Choose language to report from authority to bibliographic record.
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '25

04 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38142 Bug ID: 38142 Summary: Choose language to report from authority to bibliographic record. Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: matthias.meusburger(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently, when reporting authority field to the bibliographic records, the merge function uses the first matching authority field. However, authorities can provide multiple versions of the same field, with different languages. It would be nice to have a way to select which language to report in the bibliographic record. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 38943] New: Advanced catalog editor's marco modal isn't wide enough
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '25

04 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38943 Bug ID: 38943 Summary: Advanced catalog editor's marco modal isn't wide enough Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The advanced catalog editor's marco isn't wide enough, especially on larger screens. We are using 'modal-lg' but should probably use 'modal-xl'. I have also considered 'modal-fullscreen' but perhaps that is too much. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 38670] New: 773$d doesnt display in record detail page when it should
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '25

04 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38670 Bug ID: 38670 Summary: 773$d doesnt display in record detail page when it should Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: 1. Pick a framework and expose the 773$t ( title ), 773$g ( parts ), and 773$d ( Place, publisher, and date of publication ) 2. Find a record and add some data to each of the fields in step 1. 3. Notice that the 773$d won't display. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 36275] New: The displayed values for Client ID and Secret need copy to clipboard buttons in apikeys.tt.
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '25

04 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36275 Bug ID: 36275 Summary: The displayed values for Client ID and Secret need copy to clipboard buttons in apikeys.tt. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface 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 It would be a quality of life improvement and make the copying less error prone as well. I can't count the number of times I inserted a leading space into a field for an endpoint test w/o noticing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36