August 2018 - Koha-bugs - lists.koha-community.org

[Bug 21204] New: Move C4::Acquisition code to the Koha namespace
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21204 Bug ID: 21204 Summary: Move C4::Acquisition code to the Koha namespace Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 21193] New: Develop a procedure for handling minified CSS at release only
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21193 Bug ID: 21193 Summary: Develop a procedure for handling minified CSS at release only Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Since bug 19474 we have a build toll for css and can build minified or readable versions, we shoudl integrate this into the release pipeline so developers can commit only the readable version. >From bug 19474: Could we imagine to have a staff-global.css and staff-global.min.css It would depend on the dev_install config flag, devs will use .css whereas production installations will use .min.css The .min.css would be generated only on releasing (and will avoid to pollute the git log). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 21187] New: GDPR: Force patrons password renew
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21187 Bug ID: 21187 Summary: GDPR: Force patrons password renew Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: vfernandes(a)keep.pt QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Under the auspices of the recently issued European legislation regarding data privacy (GDPR), the Portuguese government has issued a series of mandatory requirements, as well as general recommendations, for software applications that are implemented under the umbrella of public bodies (RCM 41/2018). Since Koha is mostly used by municipalities and universities in Portugal, some of these mandatory requirements need to be address by Koha implementers in Portugal. We believe that this requirement is also useful for the community at large. Here’s a description of the requirement. *** Requirement description *** The application MUST ensure that the user changes his password frequently. If the user doesn’t change is password it should be impeded from using the application until he does so. Having a setting where one can define the number of days until a password becomes invalid is necessary. The recommendation is 6 months for standard users, and 3 months for administrators. *** Scope *** Only applicable for passwords managed by Koha. When using a centralized authentication system, this task should be managed by the central authentication system. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 21143] New: Mechanism added to permit merging of items
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21143 Bug ID: 21143 Summary: Mechanism added to permit merging of items Change sponsored?: --- Product: Koha Version: 17.11 Hardware: PC OS: Windows Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: emjhet(a)pa.net QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl For enhancement in item maintenance -- it would be helpful at times to be able to merge item records just as we do bibliographic records -- be able to select the fields that we want from each of the items and merge into one. For example, our library has an older copy of an item that has been lost and replaced before the lost item was deleted. It would be nice to take the circulation history of the lost item and merge it onto the new item. This would be possible if all of the fields of the 952 were able to be merged. One could select that the 952$l (total checkouts), 952$m (total renewals), and 952$n (total holds) of the lost item be used on the replacement item. This would help to remind us WHY we chose to replace the item, since it hasn't circulated since being purchased! (isn't that always the way!) This would be much more efficient than deleting the newer item and modifying the lost item with all the information for the current copy. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 21119] New: Add option to repeat order line fields for next order
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21119 Bug ID: 21119 Summary: Add option to repeat order line fields for next order Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: cunha(a)monterey.org QA Contact: testopia(a)bugs.koha-community.org It would be very handy to be able to repeat fields from one item order to the next the way new items in cataloging can be repeated, so if you are ordering 20 items from a vendor that all have the same price and fund code you wouldn't have to re-key every item. Also would be nice if on completion of receiving an invoice there was a "receive another" button to receive another invoice from the same vendor, as they often come in bunches. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 21118] New: Highlighting of search terms in the 500 fields
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21118 Bug ID: 21118 Summary: Highlighting of search terms in the 500 fields Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When a search term is entered into Koha, it will search the Marc 5xx fields. This will retrieve the results where the search term is found in the 5xx fields. However, the highlighting does not appear when this term is found in the Marc 5xx fields. It would be nice to show the highlighting throughout the Koha record. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 21014] New: Availability of hidden items showing in OPAC
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21014 Bug ID: 21014 Summary: Availability of hidden items showing in OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 76552 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=76552&action=ed… Availability of withdrawn item is displayed Can someone try this and confirm or invalidate this as a bug? If I have two items on one record, one of which is hidden as per OpacHiddenItems, the availability still shows in the OPAC results list. Here are the steps I'm following: 1- Go to Administration > Global system preferences 2- Search for OpacHiddenItems 3- Add the following value to OpacHiddenItems: withdrawn: [1] 4- Save your system preferences 5- In the search bar at the top, click on the "Search catalog" tab 6- Search for anything 7- Find a record with two items, or add an item to a record 8- Add the withdrawn status to one of the two items, the other has to be available 9- Go to OPAC 10- Search for the record (a broad search to make sure you get to the results list, not the record details) 11- Check the availability of the items <-- for me, here, it says 1 available and 1 withdrawn (see screen capture opachiddenitems1.png) 12- Click on the title to open the record details 13- Check the items <-- there should be only one, the withdrawn item is hidden (see screen capture opachiddenitems2.png) -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 21007] New: Add new patron column for date of last successful login attempt
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21007 Bug ID: 21007 Summary: Add new patron column for date of last successful login attempt Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: bibliwho(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The (deleted)borrowers tables includes a column for failed login attempts (login_attempts). A similar column for date of last successful login would help libraries identify which patrons are & are not taking advantage of the extra features available through their personal accounts. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 20405] New: enhanced messaging preference should always be on
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20405 Bug ID: 20405 Summary: enhanced messaging preference should always be on Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In order to be able to define "enhanced messaging preferences" for each patron category, and also each patron, a system preference needs to be activated. There is a separate system preference to de-activate it at the opac, which makes a lot of sense, but i think on the staff interface it should always be on, it is up to the administrator to set it up then, without having to find a system preference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 20449] New: Noise triggered by Archive::Extract during installation
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20449 Bug ID: 20449 Summary: Noise triggered by Archive::Extract during installation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com 2018/03/20-01:52:32 Starman::Server (type Net::Server::PreFork) starting! pid(26334) Binding to UNIX socket file "/var/run/koha/kohadev/plack.sock" Setting gid to "1001 1001" Setting uid to "1001" Database update needed, redirecting to Installer. Database is 17.1200020 and Koha is 17.1200021 at /home/vagrant/kohaclone/C4/Auth.pm line 721. Could not dup 'STDIN': Invalid argument at /usr/share/perl5/Archive/Extract.pm line 152. Could not restore 'STDIN': Invalid argument at /usr/share/perl5/Archive/Extract.pm line 152. By upgrading to 0.80 of Archive::Extract, this problem went away. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3