February 2024 - Koha-bugs - lists.koha-community.org

[Bug 32721] New: Allow UserCSS and UserJS at branch level
by bugzilla-daemon＠bugs.koha-community.org 22 May '24

22 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32721 Bug ID: 32721 Summary: Allow UserCSS and UserJS at branch level 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: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be useful to be able to add UserCSS and JS at branch level rather than globally across all OPACs. This will improve customisation and streamline the way we inject the UserJS and UserCSS into the templates. -- You are receiving this mail because: You are watching all bug changes.

1 91

[Bug 22844] New: Simplify the process of selecting database columns for system preferences
by bugzilla-daemon＠bugs.koha-community.org 22 May '24

22 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22844 Bug ID: 22844 Summary: Simplify the process of selecting database columns for system preferences Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- Created attachment 89322 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=89322&action=ed… Screenshot showing column selection in a modal window Right now the process of hand-typing the names of database columns in system preferences like BorrowerMandatoryField is cumbersome and error-prone. I would like to change to a system where the user can select from a predefined list of database columns -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 170

[Bug 28561] New: Order_by triggers a DBIx warning Unable to properly collapse has_many results
by bugzilla-daemon＠bugs.koha-community.org 22 May '24

22 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28561 Bug ID: 28561 Summary: Order_by triggers a DBIx warning Unable to properly collapse has_many results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Make a list, few biblios with multiple items. Check the plack-opac-error.log [2021/06/14 11:51:45] [WARN] Use of uninitialized value $direction in string ne at /usr/share/koha/opac/opac-shelves.pl line 265. [2021/06/14 11:51:45] [WARN] Use of uninitialized value $direction in string ne at /usr/share/koha/opac/opac-shelves.pl line 265. [2021/06/14 11:51:45] [WARN] DBIx::Class::ResultSet::_construct_results(): Unable to properly collapse has_many results in iterator mode due to order criteria - performed an eager cursor slurp underneath. Consider using ->all() instead at /usr/share/koha/Koha/Objects.pm line 335 Koha/Objects Line 335 says: my $result = $self->_resultset()->next(); The warning has to do with the sorting criteria. Disabling the order_by clause removes the warning. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 33693] New: Add ability to batch mark items as lost from checkout screen
by bugzilla-daemon＠bugs.koha-community.org 22 May '24

22 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33693 Bug ID: 33693 Summary: Add ability to batch mark items as lost from checkout screen Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some partners would like the ability to mark items as lost from the checkout screen without having to open each item's record. Possibly from the screen directly, or adding an export to barcode file that could then be used in batch modification tool. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 35448] New: Rephrase: SIP2AddOpacMessagesToScreenMessage description
by bugzilla-daemon＠bugs.koha-community.org 20 May '24

20 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35448 Bug ID: 35448 Summary: Rephrase: SIP2AddOpacMessagesToScreenMessage description Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I think the use was kept by accident here: SIP2AddOpacMessagesToScreenMessage Use [do|don't]send OPAC patron messages in the SIP2 screen message field. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 33930] New: Single record can have too many items for performance
by bugzilla-daemon＠bugs.koha-community.org 20 May '24

20 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33930 Bug ID: 33930 Summary: Single record can have too many items for performance 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: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If a library has a lot of items (1000+) on a single record, such as all of National Geographic on the same record, it will cause slowdowns in the system. Specifically can make (at least) the following things difficult: -searching -loading records -holds Having a limit would be helpful. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 28594] New: Add ability to mark an item as retuned when resolving a claim
by bugzilla-daemon＠bugs.koha-community.org 20 May '24

20 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28594 Bug ID: 28594 Summary: Add ability to mark an item as retuned when resolving a claim 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This is the inverse of bug 27753. While 27753 says we should be able to automatically resolve a claim when checking in an item, we should also be able to automatically mark an item as returned when resolving its claim. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 25843] New: Send patron updates to Staff Review
by bugzilla-daemon＠bugs.koha-community.org 17 May '24

17 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25843 Bug ID: 25843 Summary: Send patron updates to Staff Review Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: joy(a)bywatersolutions.com Using Patron REST API when patrons submit updates to their information (new address, phone, etc) the updates go straight into the database. Can the updates be send to the staff so the changes can be reviewed and accepted? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 22968] New: Adding a column for collection editor name in search results
by bugzilla-daemon＠bugs.koha-community.org 17 May '24

17 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22968 Bug ID: 22968 Summary: Adding a column for collection editor name in search results 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: alexandre.breton(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- It would be useful to add a column to indicate the editor name for collection's titles authorities. It will save some time to the librarian when cataloguing because the only way to verify this is to go in the complete authority and check the area 643. The column could identify the editor or organism making the publication which appears in the field 643, subfield $b in the authority record 130. It could be useful to add this info for search results in bibliographics records and for search results in Authorities module. This improvement could be made as a system preference allowing us to choose which feilds we want to display (it will be more practical for more people then). Thanks, Alexandre -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 20093] New: Add more information in the deleting message for an authority
by bugzilla-daemon＠bugs.koha-community.org 17 May '24

17 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20093 Bug ID: 20093 Summary: Add more information in the deleting message for an authority 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: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, It would be nice if we had more informations in the deleting message for an athorities. At the moment, the message is only : «Are you sure you ant to delete this authority?». The message could contain more informations form the authority record like the notice number and the type of the authority. The message could be : « Are you sure you want to delete the common name authority (for example) (statement of the term) ____ (record number) ___?». Or it could be somthing else. Patrick. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1