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

[Bug 23213] New: OPAC check mimimum payment threshold from payment plugin
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '20

14 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23213 Bug ID: 23213 Summary: OPAC check mimimum payment threshold from payment plugin Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Blocks: 20211 Target Milestone: --- Add the ability in OPAC to check if the plugin has a minimum payment threshold. If the amount that the patron is lower than the threshold declared by the plugin then payment is not allowed. For example, if PayPal is going to charge $2 for every transaction, don't allow payments through that plugin to be less than $3. The logic to determine the minimum threshold is hold in the plugin itself. Plugins that defines a threshold should declare a new hook named Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20211 [Bug 20211] Guarantor/Guarantee and payments ideas [OMNIBUS] -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 21872] New: Elasticsearch indexing faster by making it multi-threaded
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '20

14 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21872 Bug ID: 21872 Summary: Elasticsearch indexing faster by making it multi-threaded Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi CC: ere.maijala(a)helsinki.fi, glasklas(a)gmail.com The record prosessing in misc/search_tools/rebuild_elastic_search.pl happens currently single threadeadly, it could be made multithreaded to take full advantage of multicore systems. <ere> says on IRC following about this: "[..] a simple way would be to add start offset and skip count to the indexing script so you could run multiple in parallel" So in the line "while ( my $record = $next->() ) {" the next->() function gets called and that should be possible to multithread. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 83

[Bug 26437] New: New Tools Editor should have a save and continue option
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '20

14 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26437 Bug ID: 26437 Summary: New Tools Editor should have a save and continue option Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice if there was an option in the news tool editor to save changes but also be able to continue editing that particular news item. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 10744] ExpireReservesMaxPickUpDelay works with hold(s) over report
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '20

14 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10744 Emmi Takkinen <emmi.takkinen(a)outlook.com> 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 10744] ExpireReservesMaxPickUpDelay works with hold(s) over report
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '20

14 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10744 Emmi Takkinen <emmi.takkinen(a)outlook.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #106446|0 |1 is obsolete| | --- Comment #10 from Emmi Takkinen <emmi.takkinen(a)outlook.com> --- Created attachment 110031 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=110031&action=e… Bug 10744 - ExpireReservesMaxPickUpDelay works with hold(s) over report Hold(s) over -report at circ/waitingreserves.pl doesn't work because ExpireReservesMaxPickup removes reserves from the koha.reserves-table to the koha.old_reserves-table. This patch adds a new column koha.reserves.pickupexpired telling when/if the reserve has got it's pickup duration expired. This date is used to pull old reserves to the waitingreserves-view. syspref 'PickupExpiredHoldsOverReportDuration' controls how many days after expiration old reserves are displayed on the report, and the values respect Koha::Calendar holidays To test: 1) Apply patch. 2) Enable 'ExpireReservesMaxPickUpDelay'. 3) Set some value to 'ReservesMaxPickUpDelay' and 'PickupExpiredHoldsOverReportDuration' (e.g. 2 and 7). 4) Find or create hold(s) waiting pickup and set their expiration date so it exceeds 'ReservesMaxPickUpDelay' but not 'PickupExpiredHoldsOverReportDuration'. 5) Confirm hold(s) are moved to 'Holds waiting over ...' list. 6) Run misc/cronjobs/holds/cancel_expired_holds.pl. 7) Confirm hold(s) are still displayed on the list. 8) Confirm from db that hold(s) have 'pickupexpired' set same as 'expirationdate'. 9) Set new value to 'PickupExpiredHoldsOverReportDuration' so it no longer covers hold(s) expiration date(s). 10) Confirm that hold(s) are no longer displayed in waiting list Also prove t/db_depentent/Koha/Old.t -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10744] ExpireReservesMaxPickUpDelay works with hold(s) over report
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '20

14 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10744 --- Comment #9 from Emmi Takkinen <emmi.takkinen(a)outlook.com> --- Created attachment 110030 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=110030&action=e… Bug 10744: DO NOT PUSH! Schema change -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 26433] Control number search option missing from SRU mapping options
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '20

14 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26433 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED --- Comment #3 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Ok, it's ok for bibliographic, but missing for authority search. Sorry for the early morning confusion. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 26433] Control number search option missing from SRU mapping options
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '20

14 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26433 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hi Marcel, this was about the Controlnumber being a new separate field on the form, but not showing up in the mappings form. But I just realized this is ok in master, just not in 18.11. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 26433] Control number search option missing from SRU mapping options
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '20

14 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26433 --- Comment #1 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- I used rec.id but it goes via Local-number to 999's biblionumber. In my case the same as control number, but not always. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 15435] MARC21: Include subfields n and p in Series volume information
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '20

13 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15435 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|gmcharlt(a)gmail.com |katrin.fischer(a)bsz-bw.de -- You are receiving this mail because: You are watching all bug changes.

1 0