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

[Bug 35095] New: Bibliographic record from local title only has 245$a
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '26

20 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35095 Bug ID: 35095 Summary: Bibliographic record from local title only has 245$a Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: caroline.cyr-la-rose(a)inlibro.com CC: jonathan.druart+koha(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 The manual says that when creating a local title in the ERM module, a bibliographic record is created with the values from the form being mapped to MARC fields. https://koha-community.org/manual/22.11/en/html/erm.html#create-a-new-local… This is what it says >When you save the title, Koha will also automatically create a bibliographic >record for you with as much of the metadata as possible. We map the KBART >metadata to MARC21 in the following way: - >publication_title = biblio.title >print_identifier = 020$a||020$z||022$a||022$y >online_identifier = 020$a||020$z||022$a||022$y >date_first_issue_online = 866$a (before ‘-‘) >date_last_issue_online = 866$a (after ‘-‘) >num_first_vol_online = 863$a (before ‘-‘) >num_last_vol_online = 863$a (after ‘-‘) >title_url = 856$u >first_author = biblio.first_author >coverage_depth = title_url ? ‘fulltext’ : ‘print’ >notes = $852$z >publisher_name = 260$b However, only the title is actually transferred to the bibliographic record. To recreate: 1. Enable ERMModule 2. Go to E-resource management > e-Holdings > Local > Packages 3. Click New package 4. Enter a package name 5. Click Submit 6. Go to e-Holdings > Local > Titles 7. Click New title 8. Fill out all the fields 9. Click Add to another package 10. Choose the package created previously 11. Click Submit 12. Click the title in the list 13. Click Local bibliographic record (next to Publication title) --> Note the record only has a title 14. Click MARC --> Only tabs 0 and 2 have information, leader and 245$a I don't know if this is by design or not. If it is, the manual should be amended to reflect the reality. If it's a bug, it needs to be fixed. -- You are receiving this mail because: You are watching all bug changes.

1 31

[Bug 31327] New: Can we add color scheme picker to the OPAC.. especially a 'dark mode'?
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31327 Bug ID: 31327 Summary: Can we add color scheme picker to the OPAC.. especially a 'dark mode'? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be great to support a second or more color scheme on the OPAC.. many apps now have 'dark mode' and 'high contrast'. -- You are receiving this mail because: You are watching all bug changes.

1 40

[Bug 37054] New: Allow for custom branch colors in the staff interface header search
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37054 Bug ID: 37054 Summary: Allow for custom branch colors in the staff interface header search Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface 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 The staff interface includes a green bar at the top of almost every page, #header_search.toptab I have been writing custom JavaScript to color this bar differently per branch. It would be much nice if you could just do this in Koha without JS. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 120

[Bug 20638] New: Log actions on API keys
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20638 Bug ID: 20638 Summary: Log actions on API keys Change sponsored?: --- Product: Koha Version: master 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Actions on API keys shoudl be logged and auditable (i.e. who creates the API keys, who revokes, etc). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 95

[Bug 38931] New: Add endpoints for individual credits and debits
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38931 Bug ID: 38931 Summary: Add endpoints for individual credits and debits Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement 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 We have a way to retrieve the account lines using * `GET /api/v1/patrons/:patron_id/account/debits` * `GET /api/v1/patrons/:patron_id/account/credits` but we are missing the individual ones. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 23883] New: sip_cli_emulator.pl - typo in parameter name
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23883 Bug ID: 23883 Summary: sip_cli_emulator.pl - typo in parameter name Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When trying to make a fee payment via sip_cli_emulator.pl, if a payment amount is not passed, the error reports "fee_amount is required for fee_paid", the parameter is actually "fee-amount", not "fee_amount" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 37564] New: bulkmarcimport should not generate real time holds queue updates
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37564 Bug ID: 37564 Summary: bulkmarcimport should not generate real time holds queue updates Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz If we are adding new records there is no need to check the holds queue, the records can't have holds yet -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35

[Bug 38387] New: Automatic item modification at checkin/checkout
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38387 Bug ID: 38387 Summary: Automatic item modification at checkin/checkout Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Same as UpdateLocationOnCheckin and UpdateLocationOnCheckout but more generic and with a UI -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 32453] New: Object methods _result and _resultset methods not available in templates
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32453 Bug ID: 32453 Summary: Object methods _result and _resultset methods not available in templates Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org There are times where it would be really useful to be able to access the underying result or resultset within out templates. However, Template Toolkit itself disallows this, but you can disable this feature by setting the $Template::Stash::PRIVATE package variable to a false value. $Template::Stash::PRIVATE = undef; # now you can thing._private The alternate would be to rename _result and _resultset or just provide non-prefixed aliases as result and resultset respectively. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 38270] New: Add MARCXML options to ElasticsearchMARCFormat
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38270 Bug ID: 38270 Summary: Add MARCXML options to ElasticsearchMARCFormat Change sponsored?: --- Product: Koha Version: Main 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org As noted on bug 27365, Elasticsearch search results don't get fetched correctly if a MARCXML record cannot be serialized in the compact ISO MARC 2709 format. One reason it might not be able to be serialized is due to 1 MARC field containing more than 9999 bytes or a whole record containing more than 99999 bytes. The change to be provided here will store MARCXML instead of ISO MARC 2709. -- During development, it may be found that a compressed form of MARCXML is preferred to an uncompressed form to be more comparable with the currently stored ISO MARC. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35