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

[Bug 38558] New: Typo: Accounting preferences - "to to"
by bugzilla-daemon＠bugs.koha-community.org 06 May '25

06 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38558 Bug ID: 38558 Summary: Typo: Accounting preferences - "to to" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Documentation 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: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de In the Accounting preferences chapter, under AccountAutoReconcile (https://koha-community.org/manual/latest/en/html/accountspreferences.html#a…) "credits are automatically used to to reduce the owed amounts" to to -> to -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 39822] New: Add Multi-Piece Functionality to Checkout
by bugzilla-daemon＠bugs.koha-community.org 06 May '25

06 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39822 Bug ID: 39822 Summary: Add Multi-Piece Functionality to Checkout 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: jjayne(a)luzernelibraries.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The purpose of multi-disk / multi-circ / multi-piece checkout is to avoid having to place a barcode on every disk in a series. This is usually applied to sets in which the individual components could be considered part of the set or alternatively be considered a standalone item (i.e: a television or movie series season with multiple DVDs or a set of 70's Music CDs packaged in one box). Managing multi-disk checkouts typically involves tagging the entire case with a single barcode. No individual disk should be tagged due to interference. A single barcode ensures the entire set can be tracked. This approach requires staff to open the case at check-in to verify all disks are present. It also allows for multi-circ statistics to be logged (i.e: Season 1 of Game of Thrones with 6 disks would qualify; 1 checkout with 6 items counted as statistical checkouts). It would be beneficial to create an editable field in the marc record to place the number of disks or pieces and have it tied to the circulation statistics of those items. Thank you for your consideration. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 39836] New: Vendor contact object under specified
by bugzilla-daemon＠bugs.koha-community.org 05 May '25

05 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39836 Bug ID: 39836 Summary: Vendor contact object under specified 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Bug 38010 slipped in the use of the `aqcontacts` table by defining `contacts` to be of type array. This should be specified in the spec and validated. Noted this when looking at the Vue code using it and figured the (wrong/my opinion) DB column names were used as-is. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 28760] New: Granular restrictions
by bugzilla-daemon＠bugs.koha-community.org 05 May '25

05 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28760 Bug ID: 28760 Summary: Granular restrictions 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be great if restrictions has more options. It would be great if we could restrict specific item checkouts or holds on a patron, if needed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 35049] New: Add ability to choose which status is included in MaxOpenSuggestions
by bugzilla-daemon＠bugs.koha-community.org 05 May '25

05 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35049 Bug ID: 35049 Summary: Add ability to choose which status is included in MaxOpenSuggestions Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org This is following a discussion between me and Aude on https://gitlab.com/koha-community/koha-manual/-/merge_requests/739 A client asked me if their custom status was included in the count for MaxOpenSuggestions. After testing, I found that only "Pending" suggestions were counted. This was fine with my client as it is what they wanted. But Aude raised the question that maybe some libraries might want their custom statuses to be included in the count. My client did ask me in the inital request that if the suggestions with custom statuses were included in MaxOpenSuggestions, if it was possible to "add an exception" to make it not count... I think it depends on the workflow of the library. If the status is s step after the suggestion has been analysed and decided upon, it probably should not count in MaxOpenSuggestions. But if it's a status for open suggestions waiting for analysis by another staff member (for example), it probably should count. I was thinking a system preference might be added, similar to the ILLHiddenRequestStatuses syspref, to let the library choose which statuses count in MaxOpenSuggestions. By default, only 'Pending' counts. To test: 1. Change MaxOpenSuggestions to 2 2. Go to Adminsitration > Authorized values > SUGGEST_STATUS and add a custom status 3. Log in to the OPAC as a patron 4. Make 2 suggestions --> A message should indicate that you cannot make any more suggestions as you have reached the maximum permitted 5. In the staff interface, go to Acquisitions > Suggestions 6. Change the status of one of the suggestions to the custom status 7. Go back to the OPAC --> You should now be able to make a suggestion -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 18298] New: Enforce password complexity
by bugzilla-daemon＠bugs.koha-community.org 05 May '25

05 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18298 Bug ID: 18298 Summary: Enforce password complexity Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries would want to add the option to Koha to enforce a strong password policy. That policy would mean that passwords should include both upper and lower case characters one or more numbers. -- You are receiving this mail because: You are watching all bug changes.

1 91

[Bug 13664] Add password strength plugin
by bugzilla-daemon＠bugs.koha-community.org 05 May '25

05 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13664 Jonathan Druart <jonathan.druart(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also|https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=18298 | --- Comment #77 from Jonathan Druart <jonathan.druart(a)gmail.com> --- (In reply to Martin Renvoize (ashimema) from comment #76) > > *** This bug has been marked as a duplicate of bug 18292 *** I guess you meant bug 18298. *** This bug has been marked as a duplicate of bug 18298 *** -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38651] New: Koha MARC Framework Issue: Default Framework Fields Loading Instead of Selected Custom Framework (24.05)
by bugzilla-daemon＠bugs.koha-community.org 05 May '25

05 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38651 Bug ID: 38651 Summary: Koha MARC Framework Issue: Default Framework Fields Loading Instead of Selected Custom Framework (24.05) Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mehmet.akgul(a)mirakil.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hello Koha Community, I am encountering an issue related to MARC framework behavior in Koha version 24.05. Here is the detailed explanation of the problem: Background: We have a custom framework called Kitap Çerçevesi (MRB), which is assigned to all of our bibliographic records. The frameworkcode field in the biblio table confirms that all records are linked to the MRB framework. No records use the Default Framework (Varsayılan Çerçeve). Issue Description: When I edit a bibliographic record, the MRB framework is shown as selected in the "Change framework" dropdown menu. However, the fields displayed in the editing interface are from the Default Framework (Varsayılan Çerçeve), not from MRB. This behavior persists even though the records are correctly assigned to the MRB framework in the database. What We Tried: Ensured that all records are linked to MRB in the frameworkcode field. Attempted to reconfigure and minimize the Default Framework's fields to ensure MRB would load correctly. Restarted the Koha services (Plack, Apache). Exported and re-imported the MRB framework to refresh its configuration. Checked log files (plack-error.log) but did not find any related errors. Observed Behavior: The editing interface always loads the fields from the Default Framework (Varsayılan Çerçeve), regardless of the selected framework. Selecting MRB again from the dropdown menu does not refresh the fields to the correct framework. Steps to Reproduce: Create a bibliographic record using a custom framework (e.g., MRB). Save and edit the record. Observe that the fields loaded in the editing interface belong to the Default Framework instead of the custom framework, even though the dropdown menu indicates the custom framework is selected. Request for Help: Is this a known issue or bug in Koha 24.05? Are there any configuration changes or patches that can resolve this behavior? If this is not a bug, could you suggest any solutions or workarounds to force Koha to load the correct framework fields in the editing interface? Thank you for your help and support! Best regards Mehmet Faruk Akgul Mirakil Data Processing -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 33985] New: Add the ability to integrate electronic signatures
by bugzilla-daemon＠bugs.koha-community.org 05 May '25

05 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33985 Bug ID: 33985 Summary: Add the ability to integrate electronic signatures 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com A library would like to be able to integrate electronic signatures into Koha. This could be a way that the patron could sign digitally and this signature would be captured in Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 39819] New: Additional performance improvements for when loading borrower relationships.
by bugzilla-daemon＠bugs.koha-community.org 05 May '25

05 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39819 Bug ID: 39819 Summary: Additional performance improvements for when loading borrower relationships. Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com >From Nick via Bug 39644: I think there is more cleanup to be done here. relationships_debt is only called twice in the code base: once in moremember.pl once in Koha::Patron->is_patron_inside_charge_limits (which is also called in moremember) The two calls are: - moremember: $patron->relationships_debt( { include_guarantors => 0, only_this_guarantor => 1, include_this_patron => 1 } ); - is_patron_inside_charge_limits: $patron->relationships_debt( { include_guarantors => 1, only_this_guarantor => 0, include_this_patron => 1 } ); The difference being that the first returns only the single patrons fine + their guarantees, the latter returns the patron and thier gusarantees and the guarantees other guarantors The first being a subset of the second, we should be able to return this additional info from "is_patron_inside_charge_limits" and avoid a double call. Additionally, moremember does checks against "NoIssuesChargeGuarantorsWithGuarantees" and "NoIssuesChargeGuarantees" - both of which are checked inside "is_patron_inside_charge_limits" so we can simply use values we are already calculating and not calculate them again -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5