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

[Bug 40837] New: Give more information about UNIMARC configuration
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '25

29 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40837 Bug ID: 40837 Summary: Give more information about UNIMARC configuration Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)openfifth.co.uk, david(a)davidnind.com, philip.orr(a)lmscloud.de I think the manual should include additional information, probably in the installation section. It would be useful for readers to point out that cataloging framework and indexes are based on the UNIMARC defined by IFLA and do not take into account the modifications commonly implemented in different countries using the format (France, Italy, Portugal...), and that adaptations may need to be made by libraries or support companies. Unlike Marc21, there are multiple variants of UNIMARC, and no one uses IFLA UNIMARC as is, so the default config of Koha is not suitable out of the box. For example in France and Italy the use of field 359 is not the same. There is an even greater need for adaptation in countries that do not use UNIMARC directly, but rather national formats based on UNIMARC with variations (Russia, Slovenia, Korea, etc.). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 18024] New: Adding a "genres and kinds" search in Authorities module
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '25

29 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18024 Bug ID: 18024 Summary: Adding a "genres and kinds" search in Authorities module Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: alexandre.breton(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org Another little enhancement for the Authorities module 1) Go to Authorities module 2) Clic on "New from Z39.50" 3) Observe in the search window that we don't have a place to search by genres (novel, science-fiction, roman, poetry, etc.) It will be very convenient if we can have an additionnal search option by literary "genres and kinds" to help target the good records when searching. Then it will find all records with the same authority (zone 155) from the RVML. Thanks again, Alexandre from CCSR -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 39992] New: Update UNIMARC frameworks to UNIMARC Bibliographic Format Manual 1.1.0
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '25

29 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39992 Bug ID: 39992 Summary: Update UNIMARC frameworks to UNIMARC Bibliographic Format Manual 1.1.0 Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl UNIMARC Bibliographic Format Manual 1.1.0 has been endorsed bu IFLA https://repository.ifla.org/items/cd4be6b4-46a6-43e7-86bf-d14a5cfed916 We should update bibliographic framework in Koha. I will take care of it. After that, Zebra and Elasticsearch will probably need a fix in other bugs. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 26198] New: koha-sip --enable should also have --raw_port and --telnet_port options
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '25

29 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26198 Bug ID: 26198 Summary: koha-sip --enable should also have --raw_port and --telnet_port options Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com You should be able to provide --raw_port and --telnet_port options to koha-sip --enable, since only 1 Koha instance will be able to use the hard-coded defaults of telnet 8023 and raw 6001. On servers running multiple instances of Koha, you'll want to be able to set up the Koha SIP server with different TCP ports (or the SIP server won't work for those instances). (Note that this isn't an issue if you only run 1 Koha on your server, or if you use 1 Koha per 1 container to provide separate network namespaces.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 40007] In the Budget section under Acquisition Module - the END DATE must be greater than the START DATE.
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '25

29 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40007 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Koha |Acquisitions QA Contact| |testopia(a)bugs.koha-communit | |y.org Group|Koha security | Product|Koha security |Koha Assignee|chris(a)bigballofwax.co.nz |koha-bugs(a)lists.koha-commun | |ity.org --- Comment #2 from David Cook <dcook(a)prosentient.com.au> --- Changing this to a normal bug since there's no indication how it's a security bug -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 27557] New: Add the ability to display the error that caused a 500
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '25

29 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27557 Bug ID: 27557 Summary: Add the ability to display the error that caused a 500 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 26048 >From bug 26048 comment 19: """ Yesterday I was thinking we could have a syspref to display/hide the error (not the stacktrace). Or enable it by default for superlibrarian. What do you think (on its own bug report of course)? """ >From bug 26048 comment 30: """ But in most production situations I don't think that we'd want to show system generated error messages. It's not a good look. """ Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26048 [Bug 26048] PSGI Koha does not use custom ErrorDocument pages -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 39259] New: SQL reports should allow Common Table Expressions
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '25

29 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39259 Bug ID: 39259 Summary: SQL reports should allow Common Table Expressions Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: schodkowy.omegi-0r(a)icloud.com QA Contact: testopia(a)bugs.koha-community.org Common table expression in MySQL is a syntax like this: WITH cte1 AS (SELECT a, b FROM table1), cte2 AS (SELECT c, d FROM table2) SELECT b, d FROM cte1 JOIN cte2 WHERE cte1.a = cte2.c; However, in Koha/Koha/Report.pm, there's func is_sql_valid: } elsif ( $sql !~ /^\s*SELECT\b\s*/i ) { push @errors, { queryerr => 'Missing SELECT' }; } It should be changed to SELECT|WITH, otherwise it won't allow these nice queries, instead having you to do an ugly workaround like this: SELECT * FROM ( WITH cte1 AS (SELECT a, b FROM table1), cte2 AS (SELECT c, d FROM table2) SELECT b, d FROM cte1 JOIN cte2 WHERE cte1.a = cte2.c ) AS dt; -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 41127] New: Unneeded Permission required when adding child record.
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '25

28 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41127 Bug ID: 41127 Summary: Unneeded Permission required when adding child record. Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To replicate: 1. Set EasyAnalyticalRecords to don't show and UseControlNumber to Use. Enable ShowComponentRecords to show in both staff and OPAC. 2. Create a patron with permissions to login into the staff interface. Grant all cataloging permissions except edit_items and edit_items_restricted. 3. Before logging as the example patron, prepare a bibliographic record. Add a child record with an attached item. The title of the child record should be: 245##$aTitle$p1967-1968 4. Login as the example patron. Find the prepared bibliographic child record and click Edit > Edit as new (duplicate). 5. Edit the record so the duplicate child record has a title like: 245##$aTitle$p1968-1969 6. Save. Note the user will be prompted to confirm saving because the system detects the new child record as a duplicate. Confirm the save. The user is logged out. 7. Relogin as the example patron and find the parent record. Click on Components and see there are now two child records. Koha did save the record, but inappropriately logged out the user. I would not expect the cataloger to need the edit_items permission because the user is not editing an item, but duplicating a bibliographic record. 8. Repeat the steps but grant the example patron the edit_items permission. See that the user is able to add a new child record and is not logged out. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 30411] New: Add separate shelving location column to Holds Queue
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '25

28 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30411 Bug ID: 30411 Summary: Add separate shelving location column to Holds Queue 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: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be useful, especially with Bug 29015, for shelving location to be its own column in the Holds Queue. This would allow for more flexibility in how libraries view and sort their queues, especially if it's configurable in Table settings. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 15461] Add shelving location to holdings table as a separate column
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '25

28 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15461 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=41126 -- You are receiving this mail because: You are watching all bug changes.

1 0