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

[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 28924] New: Allow NoIssuesCharge to be determined by patron category
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '25

25 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28924 Bug ID: 28924 Summary: Allow NoIssuesCharge to be determined by patron category Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, all patron categories have the NoIssuesCharge system preference amount applied uniformly. However there are situations where one patron category should have a higher (or lower) threshold, and it would be helpful to set this by patron category. For instance, for libraries that do ILL, items will frequently be marked as long overdue/lost due to the length of time they are checked out, and ILL account will be blocked from use. Being able to set specific patron categories to different NoIssuesCharge would resolve this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 105

[Bug 31608] New: ShowComponentRecords doesn't display components if UseControlNumber is turned on
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '25

25 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31608 Bug ID: 31608 Summary: ShowComponentRecords doesn't display components if UseControlNumber is turned on 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I apologize if this is a duplicate. I'm trying to document the new Components feature, but I'm running into problems when using UseControlNumber. In Bug 30327, the test plan mentions that UseControlNumber can be used or not, but from what I can see, ShowComponentRecords does not work with UseControlNumber. To test: 1. Enable ShowComponentRecords 1.1. Go to Administration > Global system preferences 1.2. Search for ShowComponentRecords 1.3. Choose either staff interface or both 1.4. Save 2. Enable UseControlNumber 2.1. Go to Administration > Global system preferences 2.2. Search for UseControlNumber 2.3. Choose 'Use' 2.4. Save 3. Add 773 $t and $w in the default MARC bibliographic framework 3.1. Go to Administration > MARC bibliographic framework 3.2. Click Actions > MARC structure next to Default framework 3.3. Search for 773 3.4. Click Actions > Edit subfields 3.5. Click on tab 't' 3.6. Check 'Editor' in the 'Advanced constraints' section 3.7. Click on tab 'w' 3.8. Check 'Editor' in the 'Advanced constraints' section 4. Catalog a host record 4.1. Go to Cataloging 4.2. Click on 'New record' 4.3. Fill in the mandatory fields (000, 003, 005, 008, 040$c, 245$a (note this one down), 942$c) 4.4. Enter a number in 001 (and note it down) 4.5. Save (no need to create an item) 5. Catalog a child record 5.1. Go to Cataloging 5.2. Click on 'New record' 5.3. Fill in the mandatory fields (000, 003, 005, 008, 040$c, 245$a, 942$c) 5.4. Fill in 773$a with the title (245$a) of the host record 5.5. Fill in 773$w with the control number (001) of the host record 5.6. Save (no need to create an item) 6. If necessary, reindex 7. Go to the host record --> The child record doesn't appear 8. Change UseControlNumber back to Don't use (steps 2) --> The child record appears -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 30006] New: Article requests: Checkbox for non-commercial use
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '25

25 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30006 Bug ID: 30006 Summary: Article requests: Checkbox for non-commercial use Change 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be nice if there was an option for adding a mandatory additional checkbox to the article requests form in the OPAC that allowed asking for legal requirements. Example: Copies will only be used for non-commercial purposes. Also if there is a fee for the article, there could be a need to have the patron confirm that before submitting the article request. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[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 29127] New: Reminders for Suspended Holds
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '25

21 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29127 Bug ID: 29127 Summary: Reminders for Suspended Holds 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 It would be nice to have either a definable notice or a pesky reminder in the OPAC (or both) when a patron has set a hold, suspended it, and forgot about it. Suspended holds can affect purchase decisions and decisions for patrons to place a hold. It would be great if the OPAC would display a reminder in the holds or like a news or message at the top of the account when an item has been suspended for X amount of days, and a notice that does the same. So, libraries could remind patrons after 6 months, and send a notice after a year. It would also be great if libraries could set if a suspended hold just goes away after a set amount of time, or not at all. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[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