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

[Bug 20307] New: Language overlay for authorized values
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20307 Bug ID: 20307 Summary: Language overlay for authorized values 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 Depends on: 14100 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14100 [Bug 14100] Add base to make item types, branch names, sysprefs values and authorised values translatable -- You are receiving this mail because: You are watching all bug changes.

1 147

[Bug 38460] New: Enable translations for authorised values (alternative)
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38460 Bug ID: 38460 Summary: Enable translations for authorised values (alternative) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com Depends on: 38136 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38136 [Bug 38136] Refactor database translations (alternative) -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 36271] New: Bookings should respect circulation rules for max loan periods
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36271 Bug ID: 36271 Summary: Bookings should respect circulation rules for max loan periods 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, bookings are on/off at the item level, but the booking period is entirely open meaning an item can be booked for any period. We should refine this to allow libraries to control the maximum length an item can be booked for. During the original development, I suggested perhaps we should set the maximum to the loan length of the item times the max renewals from the circulation rules.. However, I didn't get much feedback as to whether this was appropriate or whether people wanted a distinct rule for these items or another alternative. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 75

[Bug 37354] New: Bookings should respect circulation rules for max loan periods
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37354 Bug ID: 37354 Summary: Bookings should respect circulation rules for max loan periods 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: caroline.cyr-la-rose(a)inlibro.com, david(a)davidnind.com, fridolin.somers(a)biblibre.com, gmcharlt(a)gmail.com, katrin.fischer(a)bsz-bw.de, kkrueger(a)cuyahogalibrary.org, kyle.m.hall(a)gmail.com, laurence.rault(a)biblibre.com, nick(a)bywatersolutions.com, testopia(a)bugs.koha-community.org, thibaud.guillot(a)biblibre.com Depends on: 34440 +++ This bug was initially created as a clone of Bug #36271 +++ The original bug for this took on a life of its own and became broader in scope adding a series of circulation rules for the bookings system I've cloned it here to propose my original more limited-in-scope solution using existing circulation rules for loan length * renewals count. --------------------------------------------------------------- Currently, bookings are on/off at the item level, but the booking period is entirely open meaning an item can be booked for any period. We should refine this to allow libraries to control the maximum length an item can be booked for. During the original development, I suggested perhaps we should set the maximum to the loan length of the item times the max renewals from the circulation rules.. However, I didn't get much feedback as to whether this was appropriate or whether people wanted a distinct rule for these items or another alternative. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34440 [Bug 34440] Add warm-up and cool-down periods to bookings -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 63

[Bug 38547] New: Improve the code for the MARC ordering process
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '26

23 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38547 Bug ID: 38547 Summary: Improve the code for the MARC ordering process 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 are some improvements needed to the code in bug 34355 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 26867] New: Holds to Pull should use cn_sort
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '26

23 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26867 Bug ID: 26867 Summary: Holds to Pull should use cn_sort Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Staff Client 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 To recreate: - create three bibs, each with one item. those items should have these call numbers: -- JC43 .G6 1890 -- JC330 .F74 2000 -- JC480 .R63 2006 - place an item level hold on each item - go to Holds To Pull, sort by call number - notice items are order incorrectly, going 330, 43, 480 - use a report to pull the cn_sort values for your 3 items, confirm that ordering by cn_sort in your report correctly orders them 43, 330, 480 We should use cn_sort here to get them in the correct order. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 19442] New: add patron attributes into the patron card creator
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '26

22 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19442 Bug ID: 19442 Summary: add patron attributes into the patron card creator Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 Work to be done: 1 - Add the ability to define fields as attribute.CODE in the card creator template 2 - When these codes are found replace them with the correct value for the patron -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 38345] New: Remove support for OpenSearch
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38345 Bug ID: 38345 Summary: Remove support for OpenSearch Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Truth is our test suite has been exploding consistently when trying to launch OpenSearch: * https://jenkins.koha-community.org/job/Koha_Main_OS2/ * https://jenkins.koha-community.org/job/Koha_Main_OS1/ This has some precedent discussion on [issue 429](https://gitlab.com/koha-community/koha-testing-docker/-/issues/429) in `KTD` project issues. We are not going to remove it, I guess. But some noise is needed as people using OpenSearch in production don't seem to care we are not being able to run the test suite, so probably promising some 'OpenSearch support' that we cannot guarantee in any way. And if there's a problem with OpenSearch, we (devs) cannot launch a working environment to fix/test. My two cents on this matter. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 70

[Bug 38368] New: Background jobs: Batch item record deletion to list failed/succeeded items
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38368 Bug ID: 38368 Summary: Background jobs: Batch item record deletion to list failed/succeeded items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: hanna.ikonen(a)sivistys.mikkeli.fi QA Contact: testopia(a)bugs.koha-community.org Currently background jobs do not list on visible record the items which have been handled. This causes issues especially when the background job fails, for example in batch item record deletion. Trying to solve which items have been worked with, you need to use several different reports. That means a lot of work hours, especially if, for example, the failed background job contains a lot of deleted items. My proposition is, that the background job -list would show which items were handled in the background whether it has failed or not. It would also be helpful if it showed information why it has failed/which item has caused the failure. It would standardize the information/notification system with the other batch processing jobs which list the things that have been worked on. To test: 1. Go to Administration and click Manage Jobs. 2. Select Status as "Failed" and Type "Batch item record deletion". 3. Open a failed background job. 4. Report only lists the job as failed, while "Detailed messages" is empty”. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 34166] New: Show total price in table of suggestions
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34166 Bug ID: 34166 Summary: Show total price in table of suggestions Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org For determining if a suggestion is accepted the price can play a big role. Sometimes libraries will have a separate custom status for items that need to wait for available funds. It would be great if Koha showed the total price of the suggestion in the table. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26