March 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 26058] New: Add ability for AllowHoldsOnPatronsPossessions to be limited by item type, collection code or shelving location
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '25

01 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 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 21551] New: Automatically update guarantee when updating guarantor
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '25

25 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

[Bug 27804] New: Convert register transactions table to a single ajax driven datatable
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '25

25 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27804 Bug ID: 27804 Summary: Convert register transactions table to a single ajax driven datatable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client 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 Currently, the transactions list on the register details page for point of sale functionality is loaded as two tables, one for recent transactions since the last cash up and a second for historical transactions. It would be nice to have that table combined and run using ajax calls and the API. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 27791] New: Add 'fixed price' and 'variable price' options to debit types
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '25

25 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27791 Bug ID: 27791 Summary: Add 'fixed price' and 'variable price' options to debit types Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client 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 Currently, in the point of sale system, we allow inline editing for both "Price" and "Quantity" of items being sold. This means that, even though a default price can be added to an item, staff can always override that price at point of sale by editing it. Some libraries would prefer for this to be an explicit option so for certain items the price is fixed, whilst for others the price may be variable and require staff input to get right. Use case examples: * Pencil - You may have a stock of pencils to sell, a pencil has a fixed price of £1 and staff should not be able to charge more or less.. 'Fixed price' * Book - You may sell off your old stock.. rather than entering a debit type for each and every book you sell you want to have one debit type and to enter a price at the point of sale as advertised on the book itself.. 'Variable price' We could even adapt the workflow this way to actually request the price in a modal that appears between the 'Add' button being pressed and the item appearing in the 'This sale' table. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 27780] New: Add ability to set a customised default sort order for sale items
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '25

25 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27780 Bug ID: 27780 Summary: Add ability to set a customised default sort order for sale items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client 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 The 'Items for purchase' table on the point of sale page can be sorted by code or description. However, it would be beneficial to have 'popular' items appear at the top to prevent the requirement for searching for these items. We have a few options: * We could attempt to calculate this popularity dynamically. * We could add a user-definable sort field in debit types. * We could add a 'popular' flag to the debit types and then sort on 'popular + code/description'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 23046] New: Add tax handling to accounts
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '25

25 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23046 Bug ID: 23046 Summary: Add tax handling to accounts Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- We should have the ability to assign tax rates to the various charges a patron can incur. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 24599] New: Add endpoints for bulk processing of holds
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24599 Bug ID: 24599 Summary: Add endpoints for bulk processing of holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com As highlighted by bug 24410, we need a way to handle bulk submission of holds via the API. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4