October 2023 - Koha-bugs - lists.koha-community.org

[Bug 21342] New: how to generate comparative statement of book sellers in koha
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21342 Bug ID: 21342 Summary: how to generate comparative statement of book sellers in koha Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: bashir486(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Often libraries, obtain quotations for books from various vendors and make comparative statement and send the order to book sellers who quoted the lowest price. This is a common practice by rules in Pakistan. This feature is lacking in acquisition module. There is option to track and enter the quoted price of the book seller but no option is available to make or generate the comparative statement of various book sellers in koha. Kindly update that feature in future or suggest a tailored report for this action to perform. Best regards -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 21328] New: Purchase Suggestions View by Hierarchical Group
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21328 Bug ID: 21328 Summary: Purchase Suggestions View by Hierarchical Group Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Allow staff to setup to view purchase suggestions for the entire hierarchical group at once. Some libraries have multiple branches but people at the main branch do all the ordering. Currently they have to click through 7 branches to see if branch B has even 1 purchase suggestion. It would be great if they could see all for the hierarchical group they belong to. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 21265] New: Additional step at end of onboarder to enable HEA
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21265 Bug ID: 21265 Summary: Additional step at end of onboarder to enable HEA Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To make it easy for libraries to enable sharing via HEA we should add another step to the end of the onboarding tool to ask about HEA and allow libraries to enable it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 21240] New: Tables with lot of columns should have autoWidth turned off
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21240 Bug ID: 21240 Summary: Tables with lot of columns should have autoWidth turned off Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org For instance, on patron's categories: On master: https://snag.gy/m8xJdG.jpg With 'bAutoWidth': false, # in categories.js: https://snag.gy/lzVm5P.jpg -- You are receiving this mail because: You are watching all bug changes.

1 5

[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 27121] New: Merge items
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '23

02 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27121 Bug ID: 27121 Summary: Merge items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl As it exists for bibliographic records, it could be great if we could have a new feature to merge items (especially useful after merging records for exemple). When we can face duplicate of items with both incomplete datas, instead of editing one and copy-paste the missing informations coming from the second item, we could have a form to check which datas coming from each items we want to keep after merging. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[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