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

[Bug 6758] Capture membership renewal date for reporting purposes
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '17

25 Apr '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6758 Kyle M Hall <kyle(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |Needs Signoff -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 6758] Capture membership renewal date for reporting purposes
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '17

25 Apr '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6758 --- Comment #4 from Kyle M Hall <kyle(a)bywatersolutions.com> --- Created attachment 62697 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=62697&action=ed… Bug 6758 - Update Schema Files -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 6758] Capture membership renewal date for reporting purposes
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '17

25 Apr '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6758 --- Comment #3 from Kyle M Hall <kyle(a)bywatersolutions.com> --- Created attachment 62696 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=62696&action=ed… Bug 6758 - Capture membership renewal date for reporting purposes -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 6758] Capture membership renewal date for reporting purposes
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '17

25 Apr '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6758 Kyle M Hall <kyle(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 6758] Capture membership renewal date for reporting purposes
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '17

25 Apr '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6758 Kyle M Hall <kyle(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|priyanka.nk(a)osslabs.biz |kyle(a)bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 6758] Capture membership renewal date for reporting purposes
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '17

25 Apr '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6758 Kyle M Hall <kyle(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WORKSFORME |--- CC| |kyle(a)bywatersolutions.com Status|CLOSED |REOPENED --- Comment #2 from Kyle M Hall <kyle(a)bywatersolutions.com> --- It is far more efficient and far easier to have the column in the borrowers table than to join on the action logs for reporting purposes. I din't think this should be closed since Savitra specifically mentions a column for date renewed . -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 18380] New: Current location in OPAC not visible
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '17

25 Apr '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18380 Bug ID: 18380 Summary: Current location in OPAC not visible Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: vimal0212(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 61823 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=61823&action=ed… Staff client Koha version 16.11.06. After saving record current location visible in staff client. Current location in OPAC not visible. Please check the screenshot with this mesage. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 5260] Add option to send an order by e-mail to the acquisition module
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '17

25 Apr '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5260 Lari Taskula <lari.taskula(a)jns.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|18494 | Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18494 [Bug 18494] Fix Letters.t (follow-up of 5260) -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 5260] Add option to send an order by e-mail to the acquisition module
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '17

25 Apr '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5260 Lari Taskula <lari.taskula(a)jns.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |18494 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18494 [Bug 18494] Fix Letters.t (follow-up of 5260) -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 14598] itemtype is not set on statistics by C4::Circulation:: AddReturn
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '17

25 Apr '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14598 --- Comment #141 from Gwendal JONCOUR <gwendal.joncour(a)univ-rennes2.fr> --- Created attachment 62682 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=62682&action=ed… Set itemtype on stats - Rennes 2 version Well... I start to run your script on our database and when I checked the mysql queries called in the loop, I saw they took 70s each to be executed. Extrapolating from that, the 300k loops will take a little more than eight months to run. It will be a pretty long downtime for a production update :-\ I make my own version of this update function looping on itemtype and call serately items tables and biblioitems tables. On our database, it took 1h20m to update (for info, we have "item-level_itypes" parameter on so the script rarely call the biblioitem query). -- You are receiving this mail because: You are watching all bug changes.

1 0