November 2020 - Koha-bugs - lists.koha-community.org

[Bug 7607] Advanced search: Index and search term don't match when leaving fields empty
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '20

06 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7607 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #112964|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 26951] New: Add the ability to hide Collection Codes on the OPAC
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '20

06 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26951 Bug ID: 26951 Summary: Add the ability to hide Collection Codes on the OPAC 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently, there is no way to hide a whole Collection code from the OPAC. A library can hide items in a collection, but this Collection Code will still appear on the Advanced Search page. It would be nice to add the ability to hide entire Collection codes through the Authorized Value setup of the Collection codes itself. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 15448] OPACHiddenItems show in OPAC when patron places a hold on a specific item
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '20

06 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15448 Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew(a)bywatersolutions.com --- Comment #13 from Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> --- +1 on this! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 12586] Record matching rules - Required match checks doesn't work with MARCXML
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '20

06 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12586 Fridolin SOMERS <fridolin.somers(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|victor(a)tuxayo.net |fridolin.somers(a)biblibre.co | |m --- Comment #19 from Fridolin SOMERS <fridolin.somers(a)biblibre.com> --- I will try to work on this -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 26945] New: new arrival plugin not working
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '20

06 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26945 Bug ID: 26945 Summary: new arrival plugin not working Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: ujjwalguptax202(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org when i was trying to show my new arrival books on opacmainuserblock via plugin i used both plugin by bywatersolution and carousel but none of them working in my koha version 20.05 can you guys please helpme with proper step by step guide in new version 20.05 please -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 26936] New: sip2 allows the checkin the item was already checkin
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '20

06 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26936 Bug ID: 26936 Summary: sip2 allows the checkin the item was already checkin Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: Linux Status: NEW Severity: critical Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: ujjwalguptax202(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com sip2 allows the checkin the item was already checkin -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 7882] Add ability to move and reorder fields and subfields in MARC editor
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '20

06 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7882 Father Vlasie <fv(a)spots.school> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fv(a)spots.school --- Comment #71 from Father Vlasie <fv(a)spots.school> --- This feature does not work in Safari (tested with version 14). Perhaps we could have the older arrow system for browsers that do not support this otherwise some users are without a method to reorder subfields. Thank you! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '20

05 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #103425|0 |1 is obsolete| | --- Comment #140 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 113211 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=113211&action=e… Bug 8367: Add holds_pickup_period circulation rule So that pickup delay can have a different value per patron category, item type or branch. To test: 1) Update database, restart services 2) Set ReservesMaxPickUpDelay syspref (if not already set) 3) Edit your circulation rules and set a value under 'Holds pickup period (day) that is DIFFERENT from ReservesMaxPickUpDelay 4) Place a hold on a biblio 5) Check in an item from that biblio and confirm the hold as waiting 6) Confirm the expiration date is calculated using the 'Holds pickup period' value instead of the ReservesMaxPickUpDelay syspref 7) Revert the waiting status and delete the hold 8) Re-place the hold on the biblio 9) Create a holiday with a date that will overlap with the 'Holds pickup period' 10) Check in an item from that biblio and confirm the hold as waiting 11) Confirm the expiration date is calculated using the 'Holds pickup period' value AND considers the special holiday 12) Confirm tests pass t/db_dependent/Holds/WaitingReserves.t I've also added this to the TalkingTech_itiva_outbound.pl cronjob, I'm not sure how to test this. Please test properly if you can, otherwise maybe put some warns in and confirm the correct expiration date is calculated. Sponsored-by: Catalyst IT -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '20

05 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Patch doesn't apply |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7607] Advanced search: Index and search term don't match when leaving fields empty
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '20

05 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7607 --- Comment #33 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Nick Clemens from comment #31) > (In reply to Jonathan Druart from comment #28) > > To prevent the values to be sent maybe we could disable the elements instead > > of removing them from the DOM. What do you think? > > It seems to work either way - I am not sure if there is any advantage in one > method over the other, but I trust the RM What's the effect when hitting the "Back" button in the browser? I have a feeling that removing the elements might work better than disabling them in that context, but I'm not 100% sure off the top of my head. (Just thinking of different scenarios.) -- You are receiving this mail because: You are watching all bug changes.

1 0