April 2026 - Koha-bugs - lists.koha-community.org

[Bug 29392] New: Add plugin hooks before merging biblios or authorities
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '26

28 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29392 Bug ID: 29392 Summary: Add plugin hooks before merging biblios or authorities Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org For when we want to modify the final record of a merge operation -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 41358] New: action logs info column should always store JSON
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41358 Bug ID: 41358 Summary: action logs info column should always store JSON Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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(a)bywatersolutions.com In C4/Circulation.pm: # Log the checkout if ( C4::Context->preference('IssueLog') ) { my $info = $item_object->itemnumber; if ( defined($confirmations) || defined($forced) ) { $info = to_json( { issue => $issue->issue_id, branchcode => $issue->branchcode, itemnumber => $item_object->itemnumber, confirmations => $confirmations, forced => $forced }, { pretty => 1, canonical => 1 } ); } logaction( "CIRCULATION", "ISSUE", $patron->borrowernumber, $info, ); } It appears there is a way, if $forced and $confirmations is undef, to store just the itemnumber. If we are going to store JSON it should always be JSON. Storing the itemnumber sometimes and a JSON object other times makes reporting really hard. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 58

[Bug 29099] New: Add support for item bundles in the inventory tool
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29099 Bug ID: 29099 Summary: Add support for item bundles in the inventory tool 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 I chose to split out the inventory tool additions from the bundles bug.. that bug was already big enough ;) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 61

[Bug 23909] New: SCO allows to check out items with Waiting state if AllowItemsOnHoldCheckoutSCO
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23909 Bug ID: 23909 Summary: SCO allows to check out items with Waiting state if AllowItemsOnHoldCheckoutSCO Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org Currently SCO module allows to check out items with Waiting state if AllowItemsOnHoldCheckoutSCO is enabeld. Waiting items should not be able to be checked out unless librarian overrides because the notifications of an item available for pickup might have already been sent. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 75

[Bug 42180] New: Add borrower lookup tool to SIP2 Account Creation
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42180 Bug ID: 42180 Summary: Add borrower lookup tool to SIP2 Account Creation Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: eric(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org With the move to storing the sip accounts in the database rather than in SIPconfig.xml I think it would be nice to have a borrower account lookup tool in the SIP account creation form rather than the standard textbox. Currently, the field "Staff userid for SIP2 authentication" does have a tooltip that explains the userid needs to match an existing account, but the ability to search and find it would help eliminate a possible point of human error. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 31092] New: Upon importing batch records, if a full MARC record is found, only append the items; do not overlay a full MARC record
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31092 Bug ID: 31092 Summary: Upon importing batch records, if a full MARC record is found, only append the items; do not overlay a full MARC record Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: balestrieri(a)monterey.org QA Contact: testopia(a)bugs.koha-community.org When receiving items from our vendors, the full MARC records are sent in batches for import. We would like the ability to have koha only overlay our brief "on order" records that already exist in the system, not our full records already in our system. Currently, the only choice is to overlay ALL or NO records (choices are "Replace, Add, or Ignore") and to append the items, depending on the matching rule used (most users currently match on ISBN when importing books, audiobooks). Apparently, other ils systems have the ability to determine which existing records are brief and which existing records are full, and you can choose to only overlay the brief MARC records, leaving the full MARC records in tact, appending only the items. I understand the definitive markers are in the leader of the marc record. The leader will show the level of marc record it is. Most loaders will have a function to put this as one of the criteria. An example of an incoming Leader: =LDR 01429pam a2200385 i 4500 Position 17 is the encoding level. The above encoding level is blank, so it is a full level record. Encoding levels: Blank - full level record 1 - full level record 2 – less-than-full level record 3 – less than full level record 4 - less than full level record 5 – less than full level record 6 - less than full level record 7 – less than full level record 8 – less than full level (this is a prepublication record) It would be most convenient if koha would have an internal matching rule that allows for the user to overlay only existing records where levels 2-8 are in position 17 on the MARCs, ignoring any records with a "blank" or "1" in position 17 on existing MARCS, with the ability to still append all items. Right now, many of us in aquisitions need to create separate vendor accounts to order "added/existing" items only to avoid the constant overlaying of full MARC records in koha. We know any items arriving from these accounts already have full records in our system, so the vendor does not send full MARCs for any items ordered from these accounts. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 35090] New: Additional fields - marcfield of type 'get' doesn't work in serial subscriptions
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35090 Bug ID: 35090 Summary: Additional fields - marcfield of type 'get' doesn't work in serial subscriptions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: julian.maurice(a)biblibre.com, katrin.fischer(a)bsz-bw.de, martin.renvoize(a)ptfs-europe.com Depends on: 10855 To reproduce, k-t-d: 1) Add a new subscription additional field, visit: http://localhost:8081/cgi-bin/koha/admin/additional-fields.pl?tablename=sub… 2) Add a name, set MARC field '942$c' and MARC field mode = 'Get value from MARC record'. Hit 'save'. 3) Add a new subscription serial, visit: http://localhost:8081/cgi-bin/koha/serials/subscription-add.pl 4) Input a biblionumber with data in it, e.g. '112'. Click 'Next' and 'Ok' on the alert box. 5) Notice the MARC field does not contain any data. 6) Fill in all mandatory fields. Hit 'Test prediction'. Hit 'save'. 7) Notice how the subscription screen does not show any MARC field. 8) Notice how nothing is saved in the database: select * from additional_field_values; I think step 5) should display the data since I believe that is the intended behavior. Anyone able to confirm this? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10855 [Bug 10855] Custom fields for subscriptions -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 29769] New: Claim return status cannot be changed without checking item in
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29769 Bug ID: 29769 Summary: Claim return status cannot be changed without checking item in 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: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With the addition of bug 24279, libraries can no longer change the status of a claim return without checking the item in, which is not a desired behavior. Example: a library sets an item to claims return, looks for the item for three months per policy, item is not found, status needs to be changed from Claim to Lost so the patron is billed for the item. In this scenario, the item should not be checked in to clear the claim status. Marking the claim as resolved does not allow the status to be changed either. Perhaps this could be a setting with Claims Return system preferences as to whether staff are permitted to change the claim/lost status of an item from moredetail.pl? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 38014] New: Migrate from Font Awesome to Bootstrap Icons
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38014 Bug ID: 38014 Summary: Migrate from Font Awesome to Bootstrap Icons 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: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Font Awesome has moved a larger number of their icon options behind their paywall. With V6 we can no longer use the outline/unfilled versions. I propose moving to the bootstrap icon set https://icons.getbootstrap.com, which is fully open source and has a similar icon font to FA. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 31099] New: [DOCS] Export data tool - setup so database and configuration data can be downloaded
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '26

27 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31099 Bug ID: 31099 Summary: [DOCS] Export data tool - setup so database and configuration data can be downloaded Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org Add information to the manual on how to set up Tools > Export data so that the database and configuration backups are enabled and shown. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6