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

[Bug 10634] New: Use datatables for course details items table
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '13

04 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10634 Bug ID: 10634 Summary: Use datatables for course details items table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We should make the course items table in the course details a datatable to enable searching or sorting. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 8605] New: cs-CZ: Filesystem sent error: No such file or directory
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '13

02 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8605 Priority: P1 - high Change sponsored?: --- Bug ID: 8605 CC: frederic(a)tamil.fr Assignee: koha-bugs(a)lists.koha-community.org Summary: cs-CZ: Filesystem sent error: No such file or directory Severity: blocker Classification: Unclassified OS: All Reporter: black23(a)gmail.com URL: http://translate.koha-community.org/cs/38/ Hardware: All Status: NEW Version: rel_3_8 Component: translate.koha-community.org Product: Koha If we can (download) upload files (from) into translation Project, we get error: Error accessing /home/koha/Pootle-2.1.6/po/38/cs, Filesystem sent error: No such file or directory -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 4823] New: Raw Socket interface failing to accept connections
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '13

02 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4823 Summary: Raw Socket interface failing to accept connections Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: SIP2 AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: colin.campbell(a)ptfs-europe.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 This has been reported on 3M self checkouts in both the US and UK. Sip working ok for days (weeks even) then suddenly the server refuses to accept connections. Restarting sip does not always rectify (immediately) the problem. Suggests the socket gets stuffed (technical term covering a number of possible error conditions). A rare occurence and not easily repeatable. May occur intermittently when the symptom is very poor response time (sip messages are not being responded to, are timing out then server responds on second or third retry) -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 2

[Bug 7420] New: Add max fines to circulation matrix
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '13

02 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7420 Bug #: 7420 Summary: Add max fines to circulation matrix Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: srdjan(a)catalyst.net.nz QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com Capped charge is applied per item. Work to be done: * Add a numeric overduefinescap field to the issuingrules table * Add "Overdue Fines Cap" section at the bottom of the Corculation Rules page, inputs: - item type - patron category - cap in $ or whatever currency * C4::Overdues::UpdateFine() - observe overduefinescap rule when updating overdue charges - leave the charge at overduefinescap if it goes over * create tests How to test: * Check that new field values stick when maintained on the circ rules matrix page * Check that the cap is applied. This is a tricky one. A quick test would be: - set the cap to a value less then the overdue charge - have an overdue item - run fines.pl cronjob - check that the capped charge is applied A more complex test would be to set the cap anywhere between one day charge and two day charges, and run fines.pl cronjob on two consecutive days, but I'm not sure how practical it is, or is it possible to have a testing facility that can push the date forward -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 42

[Bug 10490] New: Overdue fines cap (amount) in circulation rules rounds
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '13

02 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10490 Bug ID: 10490 Summary: Overdue fines cap (amount) in circulation rules rounds Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To test: 1) Add a new circulation rule, give 4.50 for overdue fines cap. > Verify the system saves it to be 5.00 2) Edit an existing circulation rule, give 3.40 for overdue fines cap. > Verify the system saves it to be 3.00 Obviously, that's not good and especially bad because most of our libraries have standardized on 4.50. Maybe there is a problem with the datatype definition in the kohastructure.sql? We have: overduefinescap decimal default NULL, -- the maximum amount of an overdue fine In opposite to: reservecharge decimal(28,6) default NULL, I couldn't test it, but the definition is the same for kohastructure and update database. So a bit worried that we might change the data here on update instead of copying it correctly from the system preference into issuingrules. The feature was added with bug 7420. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 10221] New: hold expiration doesn't show on patron's list of holds
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '13

02 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10221 Bug ID: 10221 Summary: hold expiration doesn't show on patron's list of holds Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All URL: /cgi-bin/koha/circ/circulation.pl?borrowernumber=51 OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com When looking at the patron details in the staff client you don't see the holds expiration date, but you do see all the other dates (placed, suspension) We should see the same here: /cgi-bin/koha/circ/circulation.pl?borrowernumber=51 that we see here: /cgi-bin/koha/reserve/request.pl?biblionumber=3174 When it relates to hold dates. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 10778] New: Store more information in statistics table
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '13

01 Sep '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10778 Bug ID: 10778 Summary: Store more information in statistics table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: mathieu.saby(a)univ-rennes2.fr QA Contact: testopia(a)bugs.koha-community.org Curently, statistic table contains some information about the item and the borrower (http://schema.koha-community.org/tables/statistics.html) For the item : - itemnumber - itemtype - ccode For the borrower - borrowernumber - associatedborrower - and maybe "usercode" (not documented in schemaspy, so I don't know what it means). I think we should store more information for the borrower : if the borrower record is deleted, we will not be able to get the useful informations (categorycode...) with a JOIN. I am not sure of Koha's behavior if the item or biblio is deleted : if the itemnumber and biblionumber is deleted from statistic table, we could also store more information (as homebranch, location, biblio.serial, biblioitems.itemtype) For the borrowers, I think we need : - categorycode - branchcode - sex - sort1 - sort2 and optionally the ability to record 3 or 4 custom fields with a syspref (for example, to store the extended attributes). Do you agree with that ? M. Saby -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 3008] Increase 64k text limit for overdue notice file
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '13

31 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3008 Magnus Enger <magnus(a)enger.priv.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |magnus(a)enger.priv.no --- Comment #1 from Magnus Enger <magnus(a)enger.priv.no> --- Is this still a problem? Sounds like a major problem for large libraries... -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 4876] New: koha-* scripts are not robust
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '13

30 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4876 Summary: koha-* scripts are not robust Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Packaging AssignedTo: lars(a)catalyst.net.nz ReportedBy: lars(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 The Debian packaging contains some scripts in debian/scripts/koha-*, which are written in patchy shell. They work, but do not handle errors very well, and often cannot recover after an error happens. The scripts should be made robust. It might help to rewrite them in perl. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 21

[Bug 10094] New: koha-list should have an --disabled option
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '13

30 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10094 Bug ID: 10094 Summary: koha-list should have an --disabled option Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com CC: robin(a)catalyst.net.nz On writing the tab-completion bash scripts I found that it would be handy to have this option switch. Harmless addition. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15