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

[Bug 12656] Send a notice to patrons when their hold was cancelled because it was not picked up
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '20

26 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12656 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |26282 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26282 [Bug 26282] Allow staff to decide if a hold cancellation notice will be sent when cancelling a hold -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12430] Search truncation disables relevance ranking
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '20

26 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12430 Fridolin Somers <fridolin.somers(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fridolin.somers(a)biblibre.co | |m -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6918] Can't place holds on 'on order' items with AllowOnShelfHolds off
by bugzilla-daemon＠bugs.koha-community.org 26 Nov '20

26 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6918 Joonas Kylmälä <joonas.kylmala(a)helsinki.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joonas.kylmala(a)helsinki.fi See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=27058 --- Comment #55 from Joonas Kylmälä <joonas.kylmala(a)helsinki.fi> --- Hi, could you please see bug 27058. I had worked on the same issue before and didn't notice this bug report until now. I have a unit test there too but the bug report is only about on shelf holds = 2 / If all unavailable. There is no syspref for it because the syspref is needed only for the "If any unavailable" case which is more complex. For If all unavailable case the current behaviour is *definitely buggy* because it breaks holds when there is a ordered item, leading to a situation where there is no item available for the patron to checkout and no way for the library staff or patron themselves to place a hold to the book. This leads to a situation where all Koha libraries using If all unavailable need to keep a separate list of holds in "paper notes" or just say to the patron "sorry, come back later" which could be years for popular books. If you don't have any items available for checkout it is clear that a hold must be able to be placed if it it normally would be the case without ordered items (because you can't checkout ordered items because they don't exists yet). I have spend multiple hours thinking the scenarios carefully through, understanding the incorrectly grouped and named functions in C4/Reserves.pm, discussed this problem with 5 different libraries so I ask you also to read the code carefully when reviewing bug 27058. One important thing is that ItemsAnyAvailableAndNotRestricted() is actually two different functions: 1) Do basic checkout availability checks that are not specific to the patron 2) Do basic reservability checks to accomodate hold groups or rules regarding from which branch patron can reserve book (CanItemBeReserved()). So please don't let the incorrectly named function names to stop fixing this bug. There are a lot of other issues around IsAvailableForItemLevelRequest and CanItemBeReserved functions but please let's keep the scope on this particular issue, and on If all unavailable case only in bug 27058. In Bug 27032 I start to refactor these hard-to-understand pieces of code (and yes CanBookBeRenewed has ties to ItemsAnyAvailableAndNotRestricted...). -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14825] Accounts Rewrite Omnibus
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '20

25 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14825 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |24278 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24278 [Bug 24278] Replace Locale::Currency::Format because it's buggy -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14825] Accounts Rewrite Omnibus
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '20

25 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14825 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |17138 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17138 [Bug 17138] UpdateFine() modyfies existing fine records even when there is no need -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 26837] New: Display SMS providers in alphabetical order
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '20

24 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26837 Bug ID: 26837 Summary: Display SMS providers in alphabetical order Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be helpful to display the list of SMS providers on sms_providers.pl in alphabetical order. In addition, when adding/editing a patron record the list of providers should also display in alphabetical order. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 27089] New: Check for required item fields when adding item to order in acquisitions
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '20

24 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27089 Bug ID: 27089 Summary: Check for required item fields when adding item to order in acquisitions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If one is creating item records when adding an order to a basket in acquisitions and has some item subfields set as mandatory, Koha should check for those fields when one clicks "add item" to increase the quantity on the order. Currently, Koha doesn't check for mandatory item fields until one clicks to save the order, at which point it's more complicated to go back and edit the item to add the required values. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 11175] Show the parent record's component parts in the detailed views
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '20

24 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11175 Joonas Kylmälä <joonas.kylmala(a)helsinki.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #113962|0 |1 is obsolete| | --- Comment #100 from Joonas Kylmälä <joonas.kylmala(a)helsinki.fi> --- Created attachment 113964 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=113964&action=e… Bug 11175: Search using double quotes to support Elasticsearch With Elasticsearch if you would use the search string here without the change to double quotes, i.e. (rcn='1234' AND cni='FI-XXX') OR rcn='FI-XXX 1234' then the search would somehow manage to return a record with 001 = 1234 and 003 = FI-XXX. Using double quotes prevents that. Also using parenthesis around the latter part of the OR seems to work: (rcn='1234' AND cni='FI-XXX') OR (rcn='FI-XXX 1234') -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11175] Show the parent record's component parts in the detailed views
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '20

24 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11175 --- Comment #99 from Joonas Kylmälä <joonas.kylmala(a)helsinki.fi> --- If anybody knows why the double quotes are needed with Elasticsearch I would be happy to know :) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11175] Show the parent record's component parts in the detailed views
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '20

24 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11175 --- Comment #98 from Joonas Kylmälä <joonas.kylmala(a)helsinki.fi> --- Created attachment 113962 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=113962&action=e… Bug 11175: Search using double quotes to support Elasticsearch With Elasticsearch if you would use the search string here without the change to double quotes, i.e. (rcn='1234' AND cni='FI-XXX') OR rcn='FI-XXX 1234' then the search would somehow manage to return a record with 001 = 1234 and 003 = FI-XXX. Using double quotes prevents that. Also using parenthesis around the latter part of the OR seems to work: (rcn='1234' AND cni='FI-XXX') OR (rcn='FI-XXX 1234') -- You are receiving this mail because: You are watching all bug changes.

1 0