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

[Bug 29191] New: Linking biblio headings to authorities doesn't work with subdivisoins
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '25

28 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29191 Bug ID: 29191 Summary: Linking biblio headings to authorities doesn't work with subdivisoins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Linking biblio headings to authorities fails if there is subdivision(s) to search. Test plan (Unimarc example): - AutoCreateAuthorities On - BiblioAddsAuthorities On - add a subject in a biblio: 606 $aArt $xHistory => new authority is created - reindex authorities if Zebra search engine - add same subject in an other biblio: 606 $aArt $xHistory => again, a new authority is created Heading helper adds the subdiviion name in the search term. So the entire search query for mathing authorities is "Art generalsubdiv History" I'm looking for a fix, but i need someone to explain me why we add something which is similar to metada in the search term. This is done both for MARC21 and UNIMARC in C4::Heading::UNIMARC::_get_search_heading and C4::Heading::MARC21::_get_search_heading -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 38960] New: Checking in a waiting hold only records a local use
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '25

27 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38960 Bug ID: 38960 Summary: Checking in a waiting hold only records a local use Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This behavior has changed from 24.05. If you check in a waiting hold, it is supposed to pop up with the hold modal and let you know it is already waiting, and give you the option to confirm again or cancel the hold. On 24.11, it just records a local use. This ain't good! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 24226] New: Advanced editor - drops subfields/punctuation when manually linking authority records
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '25

27 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24226 Bug ID: 24226 Summary: Advanced editor - drops subfields/punctuation when manually linking authority 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: mkstephens(a)lancasterseminary.edu QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In the basic editor, it is possible to manually search for an authority record and link to it while preserving the original punctuation in the bibliographic record. It is also possible to search for and link to a broader heading and the additional subfields will remain intact in the bibliographic record. If you try to do either one of these things in the advanced editor using ctrl+shift+L to get to the authority search, once you link to the authority record that you select the MARC field you are editing will be rewritten to match the corresponding field in the authority record. It would be very nice if the advanced cataloging editor would simply append the authid in $9 and leave the rest of the MARC field alone. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[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 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