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

[Bug 36616] New: Ability to stop Complex See Reference authority records from being linked to bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '26

21 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36616 Bug ID: 36616 Summary: Ability to stop Complex See Reference authority records from being linked to bibliographic records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We want to prevent cataloguers from being able to select an authority in the bibliographic edit Catalogue authority plugin if the authority record contains a 260 MARC field. The 260 tag in an authority record indicates that it is a Complex See Reference record and contains an instructional note for the cataloguer. https://www.loc.gov/marc/authority/ad260.html These are typically guidance authorities and not meant to be inserted into the bibliographic record. It would be great to enable a feature that prevented these reference headings from being linked to biblios. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 23641] New: Checkout via camera on phone
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '26

20 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23641 Bug ID: 23641 Summary: Checkout via camera on phone 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Would love it if someone could figure out a way to do checkout on a device via camera. Maybe an option to type, but that might be questionable. Barcode on camera would be better. It would be great if a patron could grab a book and check it out. Barring any issues with the checkout (fines/overdues/holds, etc), it could be a quick in and out scenario for patrons. Those libraries that have security measures could be instructed to a station to deactivate pending checkouts. -- You are receiving this mail because: You are watching all bug changes.

1 43

[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 39331] New: Guarantor relationships not removed when changing patron category from memberentry.pl
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39331 Bug ID: 39331 Summary: Guarantor relationships not removed when changing patron category from memberentry.pl Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When editing a patron in the staff interface the guarantor relationships are being recreated after they are removed The code calls Patron->store - this is where guarantors are removed when category changes - after this we call add_guarantors using the $input from the form To recreate: 1 - Remove age limits from a Child and Adult category in Administration->Patron categories. Ensure Child category can be guarantor and Adult cannot 2 - The above step is to avoid any age checks and form resubmission which removes the guarantor fields 3 - Find/create a child patron 4 - Add a guarantee from the Adult category to the child 5 - Check the DB: SELECT * FROM borrower_relationships WHERE guarantee_id={borrowernumber of child}; 6 - Note the id colum 7 - Edit the child patron to Adult category 8 - Repeat 5 9 - Note the relationship still exists and the id is incremented 10 - Oof! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 39363] New: Warn staff that guarantors are being removed when changing patron category to one that cannot be guarantee
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39363 Bug ID: 39363 Summary: Warn staff that guarantors are being removed when changing patron category to one that cannot be guarantee Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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.m.hall(a)gmail.com >From a discussion on Bug 39331. It would be nice to display some information about the guarantors that will be removed when you switch a patron category to one that cannot be guarantee. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[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 39496] New: Move hardcoded staff-global.scss into variables
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39496 Bug ID: 39496 Summary: Move hardcoded staff-global.scss into variables Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal 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 This is a bug to move hardcoded staff-global.scss into variables -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[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 40144] New: `sip_cli_emulator.pl` warnings
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '26

19 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40144 Bug ID: 40144 Summary: `sip_cli_emulator.pl` warnings Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Whiel debugging tests for 39911 I noticed a couple warnings that are useless (i.e. poor data handling instead of a feature alerting something). The first patch on bug 39911 adds an explicit `die` to emulate a a crash. When running the `sip_cliemulator.pl` script some warnings showed up: ```shell $ ./misc/sip_cli_emulator.pl -a 127.0.0.1 -p 6001 -su tcohen -sp tomasito -l MPL --patron tcohen -m patron_information Attempting socket connection to 127.0.0.1:6001...connected! Use of uninitialized value $hold_mode in string eq at ./misc/sip_cli_emulator.pl line 127. SEND: 9300CNtcohen|COtomasito|CPMPL| Use of uninitialized value $data in concatenation (.) or string at ./misc/sip_cli_emulator.pl line 359. READ: Use of uninitialized value $data in pattern match (m//) at ./misc/sip_cli_emulator.pl line 311. Login Failed! ``` -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17