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

[Bug 11530] Recalculating a book's total issue count from items.issues or statistics-table with update_totalissues.pl ignores deleted_items.
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11530 Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|gmcharlt(a)gmail.com |nick(a)bywatersolutions.com CC| |lucas(a)bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38815] New: Optionally block local login of accounts set for SSO
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38815 Bug ID: 38815 Summary: Optionally block local login of accounts set for SSO Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Bug 18506 added the ability to completely prevent local login (login using the koha username and password) when using SSO, but many libraries using SSO find it necessary to allow local login for some users or situations -- community borrowers at an academic library, support vendors who lack SSO credentials, etc. If both SSO and local login must be allowed, libraries want to ensure that any given account can only log in one way -- if your account can authenticate via SSO, you should not be able to authenticate via local login. Libraries enforce this by setting NULL passwords in Koha on accounts using SSO, but at the very least any superlibrarian is able to change that password. It would be helpful to be able to flag an account as "SSO only" and thereby force Koha to null the password and keep it null, hiding the Change Password button and the password field from patron edit. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 38814] New: Add helper information to circ rules of system prefs that can impact refund behavior
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38814 Bug ID: 38814 Summary: Add helper information to circ rules of system prefs that can impact refund behavior 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: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com System preferences like NoRefundOnLostReturnedItemsAge and the new NoRefundOnLostFinesPaidAge can create exceptions to circ rule refund settings. It would be nice if the Default lost item fee refund on return policy section of the circulation rules provided either a hint that the preferences may impact refund behavior, or even expose the values in those preferences, as the circ rules table and default holds policy tables do. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 26024] New: Purge undone of zebraqueue in cleanup_database.pl
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26024 Bug ID: 26024 Summary: Purge undone of zebraqueue in cleanup_database.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com Purge script misc/cronjobs/cleanup_database.pl with --zebraqueue DAYS will delete entries from zebraqueue table with done=1 We now start to use Elasticsearch only so entries of zebraqueue with done=0 stay in database. I propose we purge all entries in cleanup_database.pl. Even with zebra, if indexing does not occur after several days (30 by default), there is a problem and one need a full rebuild. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 37738] New: Framework update accessibility for existing installations
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37738 Bug ID: 37738 Summary: Framework update accessibility for existing installations 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: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be nice if updated frameworks were available for download in some way. As frameworks are periodically updated in Koha to stay up-to-date with Library of Congress changes. it becomes difficult for existing installations to know about/receive those updates. While it is possible for existing installations to monitor bugs and see what the changes are, they don't receive those updates in the frameworks with an upgrade. This requires a library to seek out the bugs and do manual updates. There may be a number of ways to alert a library that updates are available and/or provide a download of the new framework. Perhaps there could be an alert in Administration that says updates are available, with a link to download the new framework from somewhere. This way a library can choose whether to overlay or manually update a framework as needed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 38811] New: Clarify "Hide in OPAC" in itemtype configuration
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38811 Bug ID: 38811 Summary: Clarify "Hide in OPAC" in itemtype configuration Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de The manual states: Hide in OPAC: for items that you are suppressing from the OPAC, you can hide their item type from being searched in the OPAC. I think it's not quite correct: you can still search for it, but the option hides the item type from the tab in the advanced search page. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 7376] Transfer limits should be checked at check-in
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7376 --- Comment #141 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> --- Hi, as far as I understand, Comment 126 is about Comment 125 about plan for no_return, which is what I introduced in the follow up, did I miss something ? :) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 32168] New: Editing date/datetime fields without the dateaccessioned.pl plugin can cause errors
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32168 Bug ID: 32168 Summary: Editing date/datetime fields without the dateaccessioned.pl plugin can cause errors Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 When editing items that are date or datetime formatted without the dateaccessioned cataloging plugin it is quite easy to cause an error. To recreate: 1. Make sure some 952 field with dates (datelastseen, dateaccessioned ) are visible in the editor but make sure the dateaccessiond plugin is turned off. 2. Set the date format system preference to mm/dd/yyyy 3. Edit an item and attempt to edit one of the date fields to something in the correct dateformat, like 11/11/2018. 4. You get an error as Koha is expecting the SQL date type format of YYYY-MM-DD. I'm not sure how to best solve this. My first thought is that we should require the dateaccessioned.pl plugin on date fields. Or we could add a hint about format? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 20954] New: Add ability to set syspref overrides in SIP as we can in apache
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20954 Bug ID: 20954 Summary: Add ability to set syspref overrides in SIP as we can in apache Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com We should be able to set system preference overrides for SIP in a similar manner that we do in Apache. It would be great if we could specify those overrides on both a config level, and login level basis. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 38807] New: erm : api field is too short for some data providers
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38807 Bug ID: 38807 Summary: erm : api field is too short for some data providers Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: mathsabypro(a)gmail.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 API Key field in the database is 80 characters. It is too short : some data providers create longer API Key (for example 169 characters for the API Key created by Cyberlibris provider for my institution). -- You are receiving this mail because: You are watching all bug changes.

1 1