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

[Bug 14380] New: Overriding fine on renewal will cause duplicate fines
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '15

15 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14380 Bug ID: 14380 Summary: Overriding fine on renewal will cause duplicate fines Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Overriding fine on renewal will cause duplicate fines. Because we use the due date in accountlines.description, and fines.pl uses accountlines.description to uniquely identify fines on update, changing date_due will create duplicate entries in accountlines. select date, amount, description, accounttype, amountoutstanding, lastincrement, timestamp from accountlines where itemnumber = 35540 and borrowernumber = 24990\G *************************** 1. row *************************** date: 2015-05-05 amount: 0.500000 description: O'Connor's annotated criminal codes plus. 05/04/2015 11:59 PM accounttype: F amountoutstanding: 0.500000 lastincrement: 0.500000 timestamp: 2015-06-08 12:42:27 *************************** 2. row *************************** date: 2015-06-08 amount: 4.500000 description: O'Connor's annotated criminal codes plus. 05/26/2015 11:59 PM accounttype: FU amountoutstanding: 4.500000 lastincrement: 0.500000 timestamp: 2015-06-08 02:02:40 2 rows in set (0.00 sec) Looking in old_issues, you can see that the item was renewed, and that date_due does match the second description... only the first accountlines entry is marked woth accounttype 'F' on return, however. select date_due, returndate, lastreneweddate, renewals, timestamp, issuedate from old_issues where itemnumber = 35540 and borrowernumber = 24990\G *************************** 1. row *************************** date_due: 2015-05-26 23:59:00 returndate: 2015-06-08 12:42:27 lastreneweddate: 2015-05-05 00:00:00 renewals: 1 timestamp: 2015-06-08 12:42:27 issuedate: 2015-04-13 09:23:20 To replicate: 1) check out an item 2) let the item go overdue and start accruing fines 3) renew the item 4) let the item go overdue again. Note that a second accountlines entry has been added 5) return the item. Note that only one accountlines entry is marked with accounttype 'F'. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 10591] New: Why do we allow holds on restricted items (952$5=Use restrictions)? Place a hold for reference?
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '15

15 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10591 Bug ID: 10591 Summary: Why do we allow holds on restricted items (952$5=Use restrictions)? Place a hold for reference? 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, it is possible to place a hold on an item marked as Restricted with 952 $5. And you can also confirm the hold, setting it to Waiting status. The code in Circulation.pm (CanBookBeIssued) checks before issuing if an item is restricted and will not permit checkout. So actually, the book is not for loan. It may be available for reference in the library? This may be just unintentional. But if we would have the intention to provide a mechanism to place holds for reference in the library, we probably should deal with the remaining workflow too. How do we registrate that the user received the book for reference, and when do we remove the waiting hold? Do we count these kind of references? Note also that we could have a library building workflow on this possibility, and another developer that some day makes it impossible to reserve restricted items not knowing that. What do you think? Setting this report to In Discussion, hoping for some more feedback. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 12984] New: Improvement of the funds list view - acqui home
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '15

15 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12984 Bug ID: 12984 Summary: Improvement of the funds list view - acqui home Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Bug 11578 improved the funds list view in the administration module. It would be great to have the same improvement on the administration home page. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 10874] New: Incremental fine system for various types of documents and patron categories
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '15

15 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10874 Bug ID: 10874 Summary: Incremental fine system for various types of documents and patron categories Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: library.ltce(a)ltjss.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com bug 6873 (16 Sept 2011) is similar but not resolved till date. our library use this rules for fines and circulation: Circulation periods: books period: 30 days with 2 renewals max journals period: 14 days with 2 renewals max Fines: 1. fine after period, price A 2. fine 30th day after 1. fine, price B 3. fine 14th day after 2. fine, price C (2x price B) 4. fine 14th day after 3. fine, price D (3x price B) 5. next fines we count per day and item. Fine rates varies for patron categories as well as type of documnet. also bug 8776 and 10027 need to be solved as they are related to fine calculation. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 14386] New: Use 856 Ind. 2 to show links to full text and to related resources separately (MARC21)
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '15

15 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14386 Bug ID: 14386 Summary: Use 856 Ind. 2 to show links to full text and to related resources separately (MARC21) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Sometimes a record has a lot of links to catalog enrichments (cover, cover text, toc, abstract, etc.) and also a full text link. With not all links having a nice link text that can get pretty confusing to patrons. In the standard, indicator 2 tells you, which link should be the full text link and which are links to related resources. We should use those to show nice labels for each type. http://www.loc.gov/marc/bibliographic/bd856.html Second Indicator Relationship # - No information provided 0 - Resource 1 - Version of resource 2 - Related resource 8 - No display constant generated -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2696] Fine Payments Should Show What Was Paid For
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '15

15 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2696 --- Comment #8 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- It's still an open bug. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. You are the QA Contact for the bug.

1 0

[Bug 2696] Fine Payments Should Show What Was Paid For
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '15

15 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2696 Indranil Das Gupta <indradg(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |indradg(a)gmail.com --- Comment #7 from Indranil Das Gupta <indradg(a)gmail.com> --- (In reply to Kyle M Hall from comment #6) > (In reply to Katrin Fischer from comment #5) > > Something to look out for when testing the accounts rewrite :) > > I can tell you that the new accounting system tracks and stores every fee > paid for by every payment. If a payment is made that paid 3 fines, it > creates three account_offset rows that link the payment to each of those > fines, along with the amount paid on each! > > When you look at patrons fines, you can even "drill down" to see the entire > history for each fee, and for each payment. So, it this still an open bug or can this be closed? -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug. You are the assignee for the bug.

1 0

[Bug 3333] item status for "not for loan" by item type / item is different
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '15

13 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3333 Nick Clemens <nick(a)quecheelibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nick(a)quecheelibrary.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8685] New: Inventory tool fails in timeout with large CB files
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '15

12 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8685 Priority: P5 - low Change sponsored?: --- Bug ID: 8685 Assignee: gmcharlt(a)gmail.com Summary: Inventory tool fails in timeout with large CB files Severity: normal Classification: Unclassified OS: All Reporter: sophie.meynieux(a)biblibre.com Hardware: All Status: NEW Version: unspecified Component: Tools Product: Koha Inventory tool fails with a timeout if the CB file to process is too large. In fact it doesn't really fails, CB are properly processed, but the user can't see the result because of the timeout occuring before the end of processing. One solution could be to implement background job like in MARC import (BZ1531) Another one could be to add scheduler to plan inventory process like in reports -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 1232] Add Invoice/Credit/Fines Payed For Day on Issues (Print Page) (Print Slip)
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '15

12 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1232 Cab Vinton <director(a)plaistowlibrary.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |director(a)plaistowlibrary.co | |m -- You are receiving this mail because: You are watching all bug changes.

1 0