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

[Bug 11897] Stock Rotation for Koha
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '17

09 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11897 Alex Sassmannshausen <alex.sassmannshausen(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #63063|0 |1 is obsolete| | --- Comment #104 from Alex Sassmannshausen <alex.sassmannshausen(a)ptfs-europe.com> --- Created attachment 65715 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=65715&action=ed… Bug 11897: Add Stock Rotation atomic update schema. * installer/data/mysql/atomicupdate/stockrot_tables.sql: New file. * installer/data/mysql/kohastructure.sql (stockrotationrotas) (stockrotationstages, stockrotationitems): New tables. * installer/data/mysql/sysprefs.sql: Add Stockrotation sysprefs. * installer/data/mysql/userflags.sql: Add Stockrotaiton userflag. * installer/data/mysql/userpermissions.sql: Add Stockrotation userpermissions. * koha-tmpl/intranet-tmpl/prog/en/modules/admin/preferences/circulation.pref: Add Stockrotation menu. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7595] Add branchcode to accountlines
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '17

09 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7595 Kyle M Hall <kyle(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|Failed QA |RESOLVED --- Comment #52 from Kyle M Hall <kyle(a)bywatersolutions.com> --- This is too old to rework. Closing out. Will start fresh. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15524] Set limit on maximum possible holds per patron by category
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '17

09 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15524 Kyle M Hall <kyle(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff --- Comment #8 from Kyle M Hall <kyle(a)bywatersolutions.com> --- (In reply to Owen Leonard from comment #7) > In my test I set the hold limit for DVDs to 10, and the "Maximum total holds > allowed (count)" for patron type "Juvenile" to 5. > > I placed holds for a patron with that patron category until the number > exceeded 5 and then exceeded 10. Neither hold limit appears to be working. Just tested and everything is working for me! It's especially odd that the existing rule isn't working since I didn't touch that code. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14803] Rental and fine fees are not updating on circulation screen
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '17

09 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14803 --- Comment #38 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Sorry, last test report was partially nonsense: 1) Check out an item 2) Verfiy it shows as checked out 3) Verify the amount has been updated (OK!) 4) Renew item from the table 5) Verify the amount has been updated (OK!) 6) Check in the item from the table BUT: Instead of seeing the success message the checkout vanishes instantly. Without the patch, the checked-in items remain visible, highlighted in yellow showing the success message. With the patch they vanish immediately. I think we need to keep the former behavior. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14803] Rental and fine fees are not updating on circulation screen
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '17

09 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14803 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #37 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- 1) Check out an item 2) Verfiy it shows as checked out 3) Renew item from the table 4) Verify the amount has been updated (OK!) 5) Check in the item from the table 6) Verify the amount has been updated (OK!) BUT: Instead of seeing the success message the checkout vanishes instantly. Without the patch, the checked-in items remain visible, highlighted in yellow showing the success message. With the patch they vanish immediately. I think we need to keep the former behaviour. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14803] Rental and fine fees are not updating on circulation screen
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '17

09 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14803 Srdjan Jankovic <srdjan(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #63230|0 |1 is obsolete| | --- Comment #36 from Srdjan Jankovic <srdjan(a)catalyst.net.nz> --- Created attachment 65698 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=65698&action=ed… bug 14803: KOHA.Checkouts js object * Use javascript to: - update fines/checkouts info - show/hide checkouts form and messages * Created svc/patron/fines -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14803] Rental and fine fees are not updating on circulation screen
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '17

09 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14803 Srdjan Jankovic <srdjan(a)catalyst.net.nz> 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 14803] Rental and fine fees are not updating on circulation screen
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '17

09 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14803 Srdjan Jankovic <srdjan(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #60630|0 |1 is obsolete| | --- Comment #35 from Srdjan Jankovic <srdjan(a)catalyst.net.nz> --- Created attachment 65697 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=65697&action=ed… Bugfix: added missing use Koha::Account -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14803] Rental and fine fees are not updating on circulation screen
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '17

09 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14803 Srdjan Jankovic <srdjan(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #60629|0 |1 is obsolete| | --- Comment #34 from Srdjan Jankovic <srdjan(a)catalyst.net.nz> --- Created attachment 65696 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=65696&action=ed… Bug 14803: Reload checkouts table on renewal svc/checkouts: get real rental charges for patron, rather than itemtype indication -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12566] Duplicate checks for Self Registered borrowers
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '17

09 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12566 --- Comment #4 from Liz Rea <liz(a)catalyst.net.nz> --- I agree with Emma, this needs to be at least as robust as the staff client duplicate borrower checking. I envision some scenarios as follows: Let's just say we have a user who has registered a year or two ago, and can't remember they did. This person registered in the library, using a paper form, and their data was input into the system by a librarian based on the fields required in the staff interface. I'm going to assume for the sake of the exercise, that the library allows users to reset their own password by email. This person now comes to the library website, and has forgotten their username/password. They don't remember that they have even used the library website before (maybe they haven't). This user cannot accomplish what they want to without an account, so they decide to register. Sensible. User registers online, using the form specified by the library. Koha will then check those required fields and look for a user in the existing database that matches to some great extent, i.e. if we ask for 10 items of information, let's say if 6 match and one is an email address in any of the address fields, we have a suspected duplicate user. At this point, we can do one of several things: 1. suggest to the user that maybe they've already registered, please go to the library (which one?) because sorry we can't resolve this online. This is ok, but pretty bad service for a modern web app. 2. If we have a matching email address in any of the email fields (configurable?), and a strongly suspected duplicate, send an email with password recovery instructions to the matching email account. The user may not have access to this account - but that isn't our problem. It is much better than sending them away! Something like "We noticed you were trying to register, but we think you might already be registered with the library. Would you like us to email you information on how to recover your account?" If accepted, the email would help them reset their password and take them through the "forgotten password" workflow. If the user declines, send them to the library for in-person help. Alternately, we could If we have a strongly suspected duplicate, but no email address in any collected email field, we would not offer to send anything - "We can't register you online, sorry." 3. add the user but flag it with MANY FLAGS AND BLINK TAGS as PROBABLY DUPLICATE and note which borrower, and put it in the patron modification queue for a librarian to merge with the existing user. We will want to prefer the username and password that the user has just created with the new registration so they can still log in. There are other scenarios but I don't really have clearance to think about them right now. I do welcome discussion. Cheers, Liz -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0