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

[Bug 20271] New: Merge deleted/old tables with their "alive" cousins
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '25

03 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20271 Bug ID: 20271 Summary: Merge deleted/old tables with their "alive" cousins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P1 - high Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: boutrosboutrosboutros(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In Koha's DB, instead of having a "soft" deletion of entries by flagging the deleted one as so, the rows in the db is actually deleted, but only after a new row in a different table is inserted. Koha's DB is relational, so there is a cascade of links between each object: a biblio is referred by many items, and each item is referred by issues, holds, messages. E.g.: when a row in the item table is moved from "items" to "deleted_items", then all the references from holds, transfers and so on will be broken. The suggested more orthodox approach to this would be to add a "deleted_at" column, which is normally null unless the row is deleted, then it set to the timestamp of when it was deletion. This means that the row is still there and will still be referred by other tables, but it just won't be shown in the relevant lists. This would improve the maintenance of Koha in many ways (e.g.: the auto_increment id on those tables caused lots of issues when you add an item and delete it immediately after. the next new item will have the same itemnumber as the previously deleted one, clashing with it in many ways). This bug is about merging the all these tables: deletedborrowers => borrowers deletedbiblio => biblio deletedbiblioitems => biblioitems deletedbiblio_metadata => biblio_metadata deleteditems => items old_issues => issues old_reserves => reserves -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 383

[Bug 20269] New: Allow selecting default collate rule
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '25

03 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20269 Bug ID: 20269 Summary: Allow selecting default collate rule Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org For some languages, the default collate rule set in kohastructure.sql, utf8_unicode_ci, doesn't work correctly. For example, Finnish alphabet expects the alphabet to sort abc...xyzåäö, but the unicode_ci rule doesn't handle the åäö right. Instead, we need to use the swedish_ci rule. It would be nice to be able to define the default collate rule during install. Problem can be seen for example when you go catalogue a new record and have frameworks starting with 'ä' or 'ö', those will sort incorrectly. On the database, you can test this with: insert into biblio_framework (frameworkcode, frameworktext) values ('TEST', 'Äänikirja'); -- Note where the 'Äänikirja' is located select * from biblio_framework order by frameworktext collate utf8_unicode_ci; -- And then the correct order, with 'Äänikirja' last: select * from biblio_framework order by frameworktext collate utf8_swedish_ci; -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 28911] New: Bcrypt settings are required for pseudonymization but are not set on upgrade
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '25

02 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28911 Bug ID: 28911 Summary: Bcrypt settings are required for pseudonymization but are not set on upgrade Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 24151 added a way to pseudonymize patron transactions. It added a new config to koha-conf <bcrypt_settings> This is added for new installs, but not for upgraded sites, and there are no instructions on the syspref or elsewhere for adding To recreate: 1 - Spin up a 20.05 (checkout 20.05.x and reset_all in kohadevbox) 2 - Upgrade to master (checkout master, updatedatabase) 3 - Enable pseudonymization 4 - Attempt a checkout 5 - boom you can manually add the settings by running the command below: htpasswd -bnBC 10 "" password | tr -d ':\n' | sed 's/$2y/$2a/' And pasting the results into <bcrypt_settings> in the config -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 29145] New: Allow patrons to have overdue items that would not result in debarment when removing overdue debarments
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '25

02 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29145 Bug ID: 29145 Summary: Allow patrons to have overdue items that would not result in debarment when removing overdue debarments 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: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The default behavior when returning an item, is to check if a patron is debarred, in that case check if the patron has any other overdue items left, and if not to lift the debarment. One might argue that it would be more logical to lift the debarment on the same conditions on which the Patron was debarred, so if the patron is in a state that would not cause debarment, the patron should not be debarred. That is: only if the patron has items that are overdue enough to cause restriction/debarment the debarment should be maintained. This patch provides a system preference, that if set instead of checking for any delayed items on returning an item, uses the delay used for restrictions to check for items exceeding that limit, and if none are found lifts the debarment. (Stefan Berndtsson at Gothenburg University library is the original author of this patch). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 94

[Bug 26058] New: Add ability for AllowHoldsOnPatronsPossessions to be limited by item type, collection code or shelving location
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '25

02 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26058 Bug ID: 26058 Summary: Add ability for AllowHoldsOnPatronsPossessions to be limited by item type, collection code or shelving location Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be useful to be able to limit the AllowHoldsOnPatronsPossessions system preference by item type, collection or shelving location. For instance, we have multiple volumes of graphic novels attached to the same bib record so we have AllowHoldsOnPatronsPossessions set to Allow. We have hotspots and laptops and would like to prevent patrons from being able to place holds on them when they already have one checked out. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 29098] New: Double confirm running resource intensive Overdues report
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '25

02 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29098 Bug ID: 29098 Summary: Double confirm running resource intensive Overdues report Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Very large libraries still have the option to run the resource intensive overdues.pl with no filters, even when the syspref is on to require filters before running it. I propose a confirmation message to ensure users know that the thing they are requesting is very resource intensive and may not complete, as we don't want to take away the functionality but I do think people should really be sure they know what they are doing when they click through with no filters on this page. Other solutions to this problem welcome - my requirements are - the option to run the full report should still be available, as it is now - users should be duly warned and forced to confirm that they really want to do this when the no-filter case is requested. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 22330] New: Transfer limits should be respected for placing holds in staff interface and APIs
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '25

27 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22330 Bug ID: 22330 Summary: Transfer limits should be respected for placing holds in staff interface and APIs Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- Branch transfer limits are respected for placing holds in the OPAC but nowhere else. This should be remedied. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 28905] New: Make it possible to hide export column in table configuration in checkouts
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '25

26 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28905 Bug ID: 28905 Summary: Make it possible to hide export column in table configuration in checkouts 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When ExportCircHistory is enabled, there is an extra column "Export" visible in the table of checkouts on the details and checkouts tabs in staff. This column/functionality is not needed often and it would be great if it could be set to hidden by default via the table configuration options. At the moment the column is explicitly set so it cannot be hidden/toggled. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 28072] New: Z39.50/SRU servers would be a great addition to Mana KB
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '25

26 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28072 Bug ID: 28072 Summary: Z39.50/SRU servers would be a great addition to Mana KB Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Mana-kb Assignee: koha-bugs(a)lists.koha-community.org Reporter: jrobb(a)sekls.org CC: alex.arnaud(a)biblibre.com It would be very helpful if Mana KB allowed libraries to share, search, and import targets for copy cataloging. It could be added to Koha's Z39.50/SRU servers administration page. Search filters might include type of library, language, maybe a way to find a target with specialized collections like medical or law. It might also be good to have a way to handle targets that stop working - like a way to test them prior to import and/or a way to flag them for review/removal. There are various websites around where you can pick up new targets, but often you have to trial and error your way to identify if the target works at all, and if the target has the kinds of records you're seeking. Having those categorized better and imported at the push of a button would save time and effort. With enough collaboration from the Koha community, this could also lead to a much more robust centralized collection of targets than anything currently available. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 21551] New: Automatically update guarantee when updating guarantor
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '25

26 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21551 Bug ID: 21551 Summary: Automatically update guarantee when updating guarantor Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com It would be great if an update to a guarantor's contact information also updated all guarantees. It appears there used to be code for this, but it didn't work and was removed. See bug 15653. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15653 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7