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

[Bug 17511] New: Authority linking subfield
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '25

27 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17511 Bug ID: 17511 Summary: Authority linking subfield Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: stefan.berndtsson(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently Koha links authority records and bibliographic records using subfield 9. What is the reason behind this choice? According to the MARC21 specification, subfield 0 is "Authority record control number or standard number", which seems more logical. Usually 9 is a locally defined field, and Libris, the National Union Catalogue in Sweden, uses subfield 9 for various other things already. What would it take to make the linking subfield into a configurable option? -- You are receiving this mail because: You are watching all bug changes.

1 49

[Bug 34420] New: Add GET endpoint for listing library groups
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '25

27 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34420 Bug ID: 34420 Summary: Add GET endpoint for listing library groups 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: lucas(a)bywatersolutions.com CC: tomascohen(a)gmail.com It would be pretty handy if there was a REST API endpoint that listed library groups. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 26998] New: XSLT: In some cases () are erroneously removed from the link text (773 and others)
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '25

27 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26998 Bug ID: 26998 Summary: XSLT: In some cases () are erroneously removed from the link text (773 and others) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org In some cases in the XSLT we have a translate function on the link text instead of the link itself (where it's supposed to be used). These cause that () in the text are not displayed and should be removed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 18081] New: New EU General Data Protection Regulation 2018
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '25

27 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18081 Bug ID: 18081 Summary: New EU General Data Protection Regulation 2018 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Next year (2018) all EU countries must apply new regulations about data protection. So let's talk how to prepare Koha for this. More about regulation in english: http://www.privacy-regulation.eu/en/index.htm Mailing debate: http://lists.koha-community.org/pipermail/koha-devel/2016-November/043314.h… Main questions: - how protect private data of borrowers (Qvarn etc.) - how connect people into Koha by secure way (https/SSL, Gloo etc.) - how protect APIs access (better documentation, best practise etc.) - how drive access to private data in system (new set of permissions?) - how to track security accidents and "damage" (more logs and analyse tool?) - how to offer better support for automatic anonymization/delete of non-active borrowes and their data from system - how to declare/certify Koha as system that protect private data and respect EU regulations This topis is very important for all libraries with Koha from EU countries. But data protection and security are universal topics at this time. It can be competetive advantage for Koha too. Mike -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 53

[Bug 39614] New: Export catalog as CSV doesn't honor branch limitations
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '25

27 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39614 Bug ID: 39614 Summary: Export catalog as CSV doesn't honor branch limitations Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: Identify some records with multiple branch holdings. In tools, set up a CSV profile with a combination of bibliographic and item fields, for example: 001|952$c|952$a|952$f|952$7|245 >From Cataloging -> Export data, export either a bibliographic range or list of biblionumbers. Select one library branch and select "Remove items not owned by selected libraries" checkbox. Export as CSV using your CSV profile. See that file includes branches other than the one you selected. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 27378] New: Enable compliance with EU Cookie Legislation via cookie consent
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '25

27 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27378 Bug ID: 27378 Summary: Enable compliance with EU Cookie Legislation via cookie consent 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: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org This bug proposes to add the ability for a site to comply with EU Cookie Legislation if required, through the use of cookie consent. Cookie use that requires consent involves the use of "non-essential" cookies. For the implementation of this bug, we are considering all cookies set by Koha itself to be "essential", and therefore not requiring consent. "Non-essential" cookies will potentially be anything else, for example, Google Analytics tracking. This bug will provide the following: - Allow an admin to define code that requires consent to run (e.g. code that results in a non-essential cookie being set). Along with a name & description for that code, and the ability to specify whether that code requires consent before running, both in the OPAC and staff interface. - Allow a user to see exactly which cookies (essential & non-essential) may be set and which non-essential cookies they can consent to if they wish. The detail of the cookies in use is definable by a site admin. - Allow a user to consent to any non-essential cookies. - Allow a user to see which non-essential cookies they have consented to and, subsequently, remove consent if they wish. - Prevent the running of any code that causes a non-essential cookie to be set unless the user has explicitly consented to it. -- You are receiving this mail because: You are watching all bug changes.

1 249

[Bug 38729] New: Linker should consider diacritics
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '25

26 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38729 Bug ID: 38729 Summary: Linker should consider diacritics Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Authority data support Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Currently, Koha linker does not pay attention to the diacritics while linking--the decision about linking is taken based on the results of search in the search engine (be it Zebra or Elasticsearch) which are diacritics insensitive. As a consequence, "Brückner, Karl" could be erroneously linked to "Bruckner, Karl", in case when "Brückner, Karl" did not exist in the authority file, or no link would be made in case when both "Brückner, Karl" and "Bruckner, Karl" existed in the authority file and LinkerModule is set to 'default'. -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 38992] New: Add ability to see link to staged MARC file when viewing bib record & item details
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '25

26 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38992 Bug ID: 38992 Summary: Add ability to see link to staged MARC file when viewing bib record & item details Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: jeremy.evans(a)ukhsa.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When viewing a bibliographic record and associated items it would be useful to have a link back to the staged MARC file that loaded that record into the catalogue. At the moment it is not always obvious how/why that record is in the catalogue if there is no linked order in the acquisitions tab. The record modification history log also does not show this information which would normally show who catalogued it originally. The link to the stage file should ideally also allow the other records in that file to appear as a list of search results. Possibly have a new Staged file tab for this information ? Or if could go under the acquisitions tab - there may or may not also be an associated order. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 38920] New: Add ability to view all item templates outside of item editing screen
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '25

26 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38920 Bug ID: 38920 Summary: Add ability to view all item templates outside of item editing screen Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be helpful to have the ability to see all of a library's item templates, and be able to click into each to see what it includes, outside of the edit item screen. Having to click into each drop-down option from the item editing screen isn't intuitive or efficient, and makes it more likely that someone will accidentally modify a template that they only meant to view. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 39647] New: Koha incorrectly says MARC import staging failed if all bibs were skipped due to matching rules
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '25

26 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39647 Bug ID: 39647 Summary: Koha incorrectly says MARC import staging failed if all bibs were skipped due to matching rules Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: emily.lamancusa(a)montgomerycountymd.gov Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When staging a MARC file for import, one might choose to ignore the incoming record if a match is found in the catalog, but still process items - for example, when purchasing additional items for existing bib records. Currently, the MARC staging background job measures its progress based on how many bib records were processed, and does not account for item processing in its progress measurement at all. If 0 record were processed, it is assumed that the import failed and displayed as such. However, this is incorrect in the case where the incoming records were supposed to be ignored at the bib level and only items should be added. It is confusing to staff when they see an error message seeing that the import staging failed, when in fact it went through as intended. -- You are receiving this mail because: You are watching all bug changes.

1 1