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

[Bug 5786] Move AllowOnShelfHolds and OpacItemHolds system preferences to the Circulation Matrix
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '20

25 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5786 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |26287 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26287 [Bug 26287] get_onshelfholds_policy always uses item holdingbranch -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 19287] New: Add ability to mark an item ‘Lost’ from ‘Holds awaiting pickup’ list
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '20

25 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19287 Bug ID: 19287 Summary: Add ability to mark an item ‘Lost’ from ‘Holds awaiting pickup’ list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The BULAC (http://www.bulac.fr/) would like to mark items not found on shelves after patrons’ holds as ‘Lost’ directly from the “Circulation > Holds awaiting pickup” list. We could have a new button on the “Action” columns of the 2 tabs, producing 3 automatic actions : - cancel the hold - notify the patron if the hold was supposed to be available (the notice should be set on the “Tools > Notices and Slips” menu) - set the field “items.notforloan” or “items.itemlost” (define in a system preference) from “0” to a value from the same ‘authorized values list’ and set in another system preference As long as “Change sponsored?” is set on “Seeking developer”, anyone wanting to quote us for the development of such a feature or just ask for more information is welcome to write to us: <sigb(a)bulac.fr>. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 108

[Bug 26203] New: Message enqueued with no to_address when using CanMarkHoldsToPullAsLost for patron without an email address
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '20

25 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26203 Bug ID: 26203 Summary: Message enqueued with no to_address when using CanMarkHoldsToPullAsLost for patron without an email address Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 To recreate: - set CanMarkHoldsToPullAsLost to allow to mark items as lost and notify patron - find a patron with no email address - create an item-level hold for that patron - from the Holds to Pull list, click Mark lost and notify patron - Koha gives contradictory messages "the patron does not have an email address defined" and "the message was enqueued correctly" - notice shows as pending email in patron account but has no to_address in the database We should either fail over to print notice when the patron doesn't have an email address or just not generate a notice at all. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 18349] Possibility to checkout/renew bypassing the circ rules using SCO
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '20

25 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18349 --- Comment #21 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- David, if you think there is a bug can you open a new bug report with a step-by-step plan to recreate the problem? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 5927] Show series information in OPAC search results
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '20

25 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5927 Rogan Hamby <rogan.hamby(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #109033|0 |1 is obsolete| | Status|NEW |Needs Signoff Assignee|chris(a)bigballofwax.co.nz |rogan.hamby(a)gmail.com --- Comment #8 from Rogan Hamby <rogan.hamby(a)gmail.com> --- Created attachment 109070 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=109070&action=e… patch to add 440 and 490 $a and $v to search results -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 5927] Show series information in OPAC search results
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '20

25 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5927 --- Comment #7 from Rogan Hamby <rogan.hamby(a)gmail.com> --- Just realized I left the $v out which was unintended. New patch coming in a moment. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 11299] Add a button to automatically link authority records in cataloguing (AJAX)
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '20

25 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11299 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #109063|0 |1 is obsolete| | --- Comment #138 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 109069 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=109069&action=e… Bug 11299: (follow-up) Skip fields with no 9 subfields To test: 1 - Disable the 'thesaurus' for a controlled field like 600a or 650a 2 - Edit a record and put random data in this field 3 - Try to link, get a JS error 4 - Apply patch 5 - Repeat 6 - No more error, field is not linked (as it has no $9 subfield) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11299] Add a button to automatically link authority records in cataloguing (AJAX)
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '20

25 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11299 --- Comment #137 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- I am still getting the JS error "TypeError: subfield[0] is undefined" * edit 600$a for the default framework, set thesaurus blank * edit a new biblio, default framework, go to 600$a fill in with "a", click the magic button = it's loading endlessly -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11299] Add a button to automatically link authority records in cataloguing (AJAX)
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '20

25 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11299 --- Comment #136 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 109063 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=109063&action=e… Bug 11299: (follow-up) Skip fields with no 9 subfields To test: 1 - Disable the 'thesaurus' for a controlled field like 600a or 650a 2 - Edit a record and put random data in this field 3 - Try to link, get a JS error 4 - Apply patch 5 - Repeat 6 - No more error, field is not linked (as it has no $9 subfield) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11299] Add a button to automatically link authority records in cataloguing (AJAX)
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '20

25 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11299 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Comment #135 is|1 |0 private| | -- You are receiving this mail because: You are watching all bug changes.

1 0