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

[Bug 21336] New: GDPR: Process unsubscribe requests automatically
by bugzilla-daemon＠bugs.koha-community.org 15 May '25

15 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21336 Bug ID: 21336 Summary: GDPR: Process unsubscribe requests automatically Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This should be a follow-up of bug 20819 (adding a consent form). A script (preferably cleanup_database) should take care of the registered refusals (or unsubscribe requests). Based on some preferences and corresponding time frames, we should lock accounts, anonymize patron data and finally remove patron data. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 174

[Bug 20916] New: Add a staging tool to patron import tool
by bugzilla-daemon＠bugs.koha-community.org 15 May '25

15 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20916 Bug ID: 20916 Summary: Add a staging tool to patron import tool Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be great that the tool allowed to see the batches, know what borrowernumber was assigned, if there was a match, see a diff, etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 18317] New: Allow check out of already checked out items trough sip
by bugzilla-daemon＠bugs.koha-community.org 14 May '25

14 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18317 Bug ID: 18317 Summary: Allow check out of already checked out items trough sip Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: marianne.rolfsen(a)kul.oslo.kommune.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We see the need to have the ability to allow already checked out material to be checked out by an another patron automatically when using the automat (sip). Today a patron is not allowed to check out already checked out material when using the automat (sip).(In the staff client you can override this if you scan the barcode). There are several reason for allowing this: Case 1: If a patron, patron no.1, fails to deliver the item properly (the item is still on loan on his account) and the item is placed on the shelf where it belongs. The next patron(no.2) who picks it up and borrows it, can in this way correct the error of patron no.1 without contacting the staff. Today we risk that patron no.1 will receive fines even though he has delivered it. Or even worse patron no.2 has borrowed it (failed to see og ignored the message on the automat) and patron nr. 1 gets the fines. Case 2: If a patron has an item on loan that belongs to another branch, has no renewals left and wishes to borrow it again. He will be able to do so if there are no one on the waiting list. Because we have many branches that are open without any staff present, this feature is even more important. The patrons will be much more self-sufficient - also during the hours when the library is open but without staff. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 47

[Bug 24101] New: Due date to on-site loans according to the calendar and possibility to renew on-site loans
by bugzilla-daemon＠bugs.koha-community.org 14 May '25

14 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24101 Bug ID: 24101 Summary: Due date to on-site loans according to the calendar and possibility to renew on-site loans Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: inkeri.hakulinen+bugz(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We have reading rooms, where patrons can have their on-site loans available for them for a long time - even a year or more! (That is, if no one else needs that item in the meanwhile, and makes a hold for it.) We wish to be able to distinguish the on-site loans from the checkouts they take home. The on-site option is good for this, because it shows clearly to the patrons and to the staff that the loans are on-site. However, we need two improvements to Koha for this. First, we need the option to set the due date automatically according to the calendar and the circulation rules, taking into account the holidays and the loan period that is set to the patron and to the item. In addition, we need the option for the patrons to be able to renew their on-site loans, too. Now the on-site loans are non-renewable, so if the patron needs them longer than what is set to due date originally, it would be good for them to be able to renew the loans themselves through our OPAC. Now the renewal is impossible altogether. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 23232] New: Enable the option to use the onscreen keyboard on the basic cataloguing editor
by bugzilla-daemon＠bugs.koha-community.org 13 May '25

13 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23232 Bug ID: 23232 Summary: Enable the option to use the onscreen keyboard on the basic cataloguing editor 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: koha-bugs(a)lists.koha-community.org, m.de.rooy(a)rijksmuseum.nl, testopia(a)bugs.koha-community.org Depends on: 17178, 23231 Bug 17178 introduced the Mottie on screen keyboard https://github.com/Mottie/Keyboard for the advanced cataloguing screen. It would be helpful to have this option available on the standard editor as well. Catalogers may still have the requirement to enter foreign or special characters when in this mode. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17178 [Bug 17178] Add a popup/keyboard shortcuts for diacritics and symbols in the advanced cataloging editor https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23231 [Bug 23231] We display too many layout options for the onscreen keyboard in the advanced cataloguing editor -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. You are on the CC list for the bug.

1 13

[Bug 17643] New: The bug 3333 breaks intranet search results in column Location
by bugzilla-daemon＠bugs.koha-community.org 12 May '25

12 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17643 Bug ID: 17643 Summary: The bug 3333 breaks intranet search results in column Location Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: christophe.croullebois(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The Bug 3333 corrects in Opac by setting notforloan=1. But it has a side effect on intranet search result page due to the use of authorized value on 'notforloan'. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 27730] New: Innocent changes to framework silently delete bibliographic data
by bugzilla-daemon＠bugs.koha-community.org 09 May '25

09 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27730 Bug ID: 27730 Summary: Innocent changes to framework silently delete bibliographic data Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: major Priority: P3 Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: ian.bays(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you copy and change a framework and either delete a subfield in the new framework or mark the subfield tab as "ignore", then any bib data with data in that subfield, when saved in the new framework will be silently destroyed with no option to undo. Test Plan to confirm behaviour: 1. Create bib record in default framework with minimal data, but add tag 365 (as it has a number of subfields all visible) and populate subfields a through h with "fa" through "fh". Save the record and with sql check the contents of the metadata. (I found this SQL gives enough information substituting the correct bib number of the saved record: select tagfield, tagsubfield, frameworkcode, tab, hidden, (select ExtractValue(metadata, '//datafield[@tag="365"]/subfield[@code>="a"]') from biblio_metadata where biblionumber = 37002 and (select frameworkcode from biblio where biblionumber = 37002) = marc_subfield_structure.frameworkcode) tv from marc_subfield_structure where frameworkcode in ('', 'TEST') and tagfield = '365'; ) 2. Copy the default framework to a TEST framework and set (say 365$b to tab ignore and delete 365$d). (I used export the default framework to a csv, create new TEST framework and import from the saved default csv) 3. Edit the bib record and change framework to TEST framework (settings > change framework) and save the record. 4. Run the SQL again and observe the data from subfields b and d have both disappeared from the metadata. If you were to rerun these tests you may need to reload memcache to ensure the newly changed frameworks are picked up. I understand it has been broadly known by some long-term Koha users that deleting a subfield from the framework has this effect, but both these situations potentially cause bib data to be silently and permanently delated from the database. Many users will be unaware and may not discover the problem for some time. Potential solutions might include: a) For subfields not in the framework or with tab "ignore" allow the data to be saved as is on saving for edit; b) When selecting "change framework" detect if data would be lost and alert the user with an option to back out of the change without losing data; c) Do not allow deletion of a subfield from a framework and do not allow the "ignore" option for the tab. If a field is to be ignored but hidden there are plenty of visibility options in the framework. NB: The current delivered default framework has 13 subfields set to the "ignore" tab. I cannot see what purpose these serve as no data can survive within them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 26500] New: Automatic renewals show incorrect count of renewals allowed when CircControl is set to "the library you're logged in at"
by bugzilla-daemon＠bugs.koha-community.org 08 May '25

08 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26500 Bug ID: 26500 Summary: Automatic renewals show incorrect count of renewals allowed when CircControl is set to "the library you're logged in at" 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 When CircControl is set to "the library you're logged in at," the Renew column in the patron checkouts table will show the count of permitted renewals based on the library you're logged in at. This is correct for manual renewals, since those are the rules that will be enforced. However, for automatic renewals this can mean we're showing the user an incorrect number. To recreate: - Create an All Libraries rule that allows 10 renewals - Create a rule for branch A that allows 1 renewal - Creare a rule for branch B that allows 99 renewals - Check an item out from Branch A, set to auto-renew - While logged in as Branch A, confirm Koha tells you you have 1 renewal available - Log in as Branch B, see you have 99 renewals - Log in as Branch C, see you have 10 renewals - Set No Renewal Before to allow renewal immediately - run the auto_renew cron, item renews once - run the auto-renew cron again, confirm too_many error because only 1 renewal is allowed -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 18315] New: authentication and authorization refactoring
by bugzilla-daemon＠bugs.koha-community.org 07 May '25

07 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18315 Bug ID: 18315 Summary: authentication and authorization refactoring Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: oha(a)oha.it QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Currently, C4::Auth is responsible to do session management, authentication and authorization. There is no clear separations between them, and the authentication is not modular, making it increasingly harder to maintain and/or introduce no authentication integrations. I was experimenting on this for a while, and I managed to put together few commits in a branch. It started as a proposal, but turned out to be working in _most_ of my tests. here more details: I completely removed any need for CGI and CGI::Session while maintaining a fork-exec aproach to the scripts. (This made it easier to implement Koha::Middleware::Session, Koha::Session::DB and ::KohaCache) Koha::Middleware::Session inject a session object in the Plack request, and invoke Koha::Auth if any authentication tokens are available. Koha::Auth has a list of modules which will be invoked in turn and could be enabled/disabled plack.psgi is changed as well, it has enabled the new Middleware and the applications used are no longer Plack::App::CGIBin but Koha::Middleware::App. here few of the things i want to do to simplify the interaction with the current "legacy" code: I didn't change the scripts or any other module at all, instead I tried to hijack C4::Auth methods to rely on Koha::Session and Koha::Auth. This make it simple to switch back to the previous plack.psgi OR using apache and the normal cgi-bin. authentication should happen upfront, before the script is even started. script will have to verify authorization. authentication MUST be modular, possibly having different systems cooperate. (Some serious discussions must be around this point, especially about accounting and authority) what needs to be done: permissions should be reintroduced. right now permissions are read for the user and set in the template, but no checks are perform on requests. (should be fairly simple to do) reintroduce the code related to shib, cas and any other. more testing, especially for the installer (there is lots of code regarding the web installer which isn't there anymore) -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 18298] New: Enforce password complexity
by bugzilla-daemon＠bugs.koha-community.org 05 May '25

05 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18298 Bug ID: 18298 Summary: Enforce password complexity Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries would want to add the option to Koha to enforce a strong password policy. That policy would mean that passwords should include both upper and lower case characters one or more numbers. -- You are receiving this mail because: You are watching all bug changes.

1 91