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

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

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133089|0 |1 is obsolete| | --- Comment #189 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 142897 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=142897&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. Set a few different numbers for different branches as well. 4) Place a hold on a biblio from the staff client. 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 on the OPAC. Notice that when you change the pick up location, the number of days in the pickup message below the dropdown changes based on the circ rules. 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 13) Test Talking Tech: 13a) Enable TalkingTechItivaPhoneNotification 13b) Go to Tools -> Notices & slips. Add content to the HOLD phone (itiva) notice. 13c) In your terminal, run perl /path/to/koha/misc/cronjobs/thirdparty/TalkingTech_itiva_outbound.pl -o ~/itiva.tmp -w 0 --type=RESERVE Sponsored-by: Catalyst IT Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> -- 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 01 Nov '22

01 Nov '22

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

1 0

[Bug 32058] New: 'Print > Print X' could use clearer labels
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32058 Bug ID: 32058 Summary: 'Print > Print X' could use clearer labels Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We have a 'Print' option in the patron toolbar, it's exposes a number of options all labelled 'Print X'. I would argue as the person has just clicked the 'Print' button to expose the pulldown they already know the options are all 'Print something' so we don't need the 'Print' as part of each label.. I also don't think the existing options are all that clear as to what they're printing... could we rename them more clearly? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 32052] New: Transparency on Hold Cancellations
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32052 Bug ID: 32052 Summary: Transparency on Hold Cancellations Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: christofer.zorn(a)ajaxlibrary.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Hey! It would be really cool if there was better transparency on what happened to our holds and how they were cancelled. I know the system logs when a hold ages out, but having the knowledge that a hold was cancelled by a patron may also be beneficial. Our staff have struggled with knowing how a hold was cancelled. If the hold ages out on the shelf, Koha reports that nicely. However, if a patron or staff member cancels the hold, there is no log kept on that. It would be helpful information for our staff when interacting with a patron to know how the hold was cancelled. Thank you! Chris -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 32053] New: Authority not in database
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32053 Bug ID: 32053 Summary: Authority not in database Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: support(a)libruse.bg QA Contact: testopia(a)bugs.koha-community.org When creating a authority from Authorities, it is not stored in the database -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 32056] New: Database tmpdir check before upgrade
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32056 Bug ID: 32056 Summary: Database tmpdir check before upgrade Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: mengu(a)devinim.com.tr QA Contact: testopia(a)bugs.koha-community.org Hi all, It may an error occur during koha upgrade if tmp directory is not free enough for database. This may lead as if upgrade completes but there may occur lots of problem. Can it be good idea to check free tmpdir area for database need and suggest to increase or change the value before proceeding upgrade? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0