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

[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 16157] New: C4::Koha::GetAuthorisedValues should not handle the selected option
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '25

22 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16157 Bug ID: 16157 Summary: C4::Koha::GetAuthorisedValues should not handle the selected option Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org >From C4::Koha::GetAuthorisedValues # TODO: the "selected" feature should be replaced by a utility function # somewhere else, it doesn't belong in here. For starters it makes # caching much more complicated. Or just let the UI logic handle it, it's # what it's for. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 19889] New: localholdspriority needs exclusions
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '25

22 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19889 Bug ID: 19889 Summary: localholdspriority needs exclusions 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com localholdspriority is great, unless you have a unique or rare collection that is popular. If you have such a collection, and ongoing holds are being placed on it to be picked up at several locations, only the patrons at that library will ever get their hands on it unless a patron is smart enough and willing to pickup the item at that location. I would propose an exclusion preference, that would exclude listed patron categories, item types, formats, or specific items. Any other item criteria or factors that I missed could be added to this list. Currently we have patrons at other libraries that will never get the items they have requested. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 137

[Bug 26227] New: Allow to enter copyright statement for uploaded local cover images
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '25

21 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26227 Bug ID: 26227 Summary: Allow to enter copyright statement for uploaded local cover images Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org We have libraries that need to add a copyright statement to the uploaded local covers. The statements can vary, so need to be image specific. It would be great if this feature could be built into the local cover images feature so that the copyright statement can be easily retrieved for display from the db. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 28322] New: Did you mean feature does not work with Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '25

21 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28322 Bug ID: 28322 Summary: Did you mean feature does not work with Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com Hi all! We just upgraded one of our clients to Elasticsearch and they happened to use the Did you mean feature. It seems Did you mean only works with Zebra. It's trying to connect to Zebra. This is in opac-error.log suggestion: oAuth error: Connect failed (10000) unix:/home/i/koha/alma-test-inlibro/var/run/zebradb/authoritysocket ZOOM: /inlibro/git/koha-alma-test-inlibro/opac/svc/suggestion, referer: http://alma-test.hapax.inlibro.net/cgi-bin/koha/opac-search.pl?q=chat (btw, "chat" is "cat" in french :D ) I think we should at the very least put a warning on the admin page for the Did you mean feature that it only works with Zebra. Otherwise make the feature engine agnostic so that we can use it with either Zebra or ElasticSearch. I don't know if Did you mean with elastic is necessary as there is a bz for autocomplete with ElasticSearch which does practically the same thing. (see bug 27113). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 24412] New: Attach waiting reserve to desk
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '25

19 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24412 Bug ID: 24412 Summary: Attach waiting reserve to desk Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nicolas.legrand(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com, severine.queune(a)bulac.fr Depends on: 24201 When an item is checked in and marked 'Waiting' or already 'Waiting' and there is a desk attached to the session, the item is marked waiting at the current desk of the current library. The information is displayed on the OPAC and on the intranet. The patron can then know at which desk he can retrieve his document. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24201 [Bug 24201] Attach desk to intranet session -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 154

[Bug 25161] New: Can not edit relationship or guarantee of guarantor from the guarantee form
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '25

19 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25161 Bug ID: 25161 Summary: Can not edit relationship or guarantee of guarantor from the guarantee form Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With the introduction of multiple guarantors to guarantees, bug 14570, now in 19.11, the relationship can not be edited from the guarantee from. Previously, a relationship and the actual guarantor could be edited from the guarantee form. Now in 19.11, there is no way to edit or change the guarantor from the guarantee form. The option that exists in 19.11 is to remove the guarantor not to edit. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 27599] New: Fine calculation at checkin should be able reflect return claims
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '25

15 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27599 Bug ID: 27599 Summary: Fine calculation at checkin should be able reflect return claims Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 14697 Here's the existing behavior: 1- checkout item with date due in the past 2- run fines cron to create accruing fine 3- mark item claimed without charging lost fee 4- fines does not change at all when item is marked claimed 5- check item in 6- fine goes from accruing to final as if the claim had never happened If we assume some time passes between step 3 and step 5, that could be a significant difference in the final fine total. Should patrons be charged overdue fines for the period between when an item is Claimed Returned and when it is actually checked in? Should that be configurable per library? Should it in some way depend on the claim resolution status? If we *do* charge the lost fee when an item is marked claimed, then we close the fine at the point of claim and it is not changed if the item is later checked in. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14697 [Bug 14697] Extend and enhance "Claims returned" lost status -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1