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

[Bug 38033] New: Koha::Biblio->record does not return items
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '24

29 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38033 Bug ID: 38033 Summary: Koha::Biblio->record does not return items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 33083 Koha::Biblio->record introduced by Bug 33083 seems to be a straigtforward alias for Koha::Biblio::Metadata->record but it does not pass the parameters to $self->metadata->record call. This may lead to misunderstandings and possible bugs. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33083 [Bug 33083] Handle generic collection of records methods -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 27753] New: Automate resolution of return claim when checking in an item
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '24

29 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27753 Bug ID: 27753 Summary: Automate resolution of return claim when checking in an item 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 When an item has been marked Claims Returned and is later checked in, it would be good to let Koha automatically resolve that claim. We'd need a way to tell it which resolution status to go to. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 82

[Bug 35402] Update the OPAC and staff interface to Bootstrap 5
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '24

29 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |38285 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38285 [Bug 38285] Replace instances of obsolete Bootstrap class "pull-right" -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '24

29 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173605|0 |1 is obsolete| | --- Comment #131 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Created attachment 173608 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173608&action=e… Bug 8137: Add 'global checkout limits' table The aim here is to avoid the accumulation of checkouts possibilities through the rules of the various branches, in order to have a global quota. Test plan: 1) Apply this patch 2) Run updatedatabase script and rebuild schema, restart_all.. 3) On circulation rules page you will find a new table "Global checkout limits". 4) If you enter values, they will overwrite the existing values, creating limits for all branches combined. 5) Test it by set a "current checkouts allowed" to 2 on "standard rules section" and set a "global" maxissueqty to 1. Normally 1 is the new limit for now. 6) You can also add a "current checkouts allowed" on other branches and see that you can't accumulate checkouts (you can also delete "global" values and see that if you have 3 on a branch and 2 on other, you can perform 5 checkouts in total. 7) Note that on specific branch circulation rules page the table cannot be modified, but just shown as a reminder. If main matrix is empty on specific branch the table is hidden by default (cause if none values it's referred to standard rules). Sponsored-by: BibLibre Signed-off-by: Lisette Scheer <lisette(a)bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '24

29 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #170411|0 |1 is obsolete| | --- Comment #130 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Created attachment 173605 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173605&action=e… Bug 8137: Add 'global checkout limits' table The aim here is to avoid the accumulation of checkouts possibilities through the rules of the various branches, in order to have a global quota. Test plan: 1) Apply this patch 2) Run updatedatabase script and rebuild schema, restart_all.. 3) On circulation rules page you will find a new table "Global checkout limits". 4) If you enter values, they will overwrite the existing values, creating limits for all branches combined. 5) Test it by set a "current checkouts allowed" to 2 on "standard rules section" and set a "global" maxissueqty to 1. Normally 1 is the new limit for now. 6) You can also add a "current checkouts allowed" on other branches and see that you can't accumulate checkouts (you can also delete "global" values and see that if you have 3 on a branch and 2 on other, you can perform 5 checkouts in total. 7) Note that on specific branch circulation rules page the table cannot be modified, but just shown as a reminder. If main matrix is empty on specific branch the table is hidden by default (cause if none values it's referred to standard rules). Sponsored-by: BibLibre Signed-off-by: Lisette Scheer <lisette(a)bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35402] Update the OPAC and staff interface to Bootstrap 5
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '24

29 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 Martin Renvoize (ashimema) <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|37912 | Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37912 [Bug 37912] Catalog concerns - Broken link under concern title -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35402] Update the OPAC and staff interface to Bootstrap 5
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '24

29 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 Martin Renvoize (ashimema) <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |37910 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37910 [Bug 37910] Minor spacing issues in the catalog concerns page -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35402] Update the OPAC and staff interface to Bootstrap 5
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '24

29 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 Martin Renvoize (ashimema) <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |37912 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37912 [Bug 37912] Catalog concerns - Broken link under concern title -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38234] Remove unused vulnerable jszip library file
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '24

28 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38234 --- Comment #13 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Martin Renvoize (ashimema) from comment #11) > Passing QA.. but I have a question. > > Should we also remove reference to it on the about page? Whilst we no > longer reference it directly anywhere, we do use the embedded version inside > datatables itself.. should we drop our about reference or keep it in this > case? (In reply to Jonathan Druart from comment #12) > I've decided to keep it as we were actually still using it, indirectly. Yeah, I'd say we keep the reference in the about page, as Jonathan says. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38098] New: Field visibility persists despite unchecking staff interface visibility in framework
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '24

28 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38098 Bug ID: 38098 Summary: Field visibility persists despite unchecking staff interface visibility in framework Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To replicate: 1. Have a sample record that displays the 082 in the staff interface, bibliographic detail view in the default framework. Ensure the record has data in the 082. 2. Edit the default framework and uncheck the box for staff interface visibility in the appropriate subfields. 3. Refresh the bibliographic detail view and see the 082 is still visible in the bibliographic detail view. I think the visibility of this field and many others are controlled by the XSLTDetailsDisplay rather than the visibility settings in the Framework. The XSLT style sheet is not accessible to the end user unless they have backend access. I would expect the visibility settings in the Framework to control the display, as implied by having the option in the first place. It would be much simpler for the end user to be able to adjust visibility in the framework and to have that setting actual do what it says. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5