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

[Bug 1017] New: Reserve fee in accounts
by bugzilla-daemon＠wilbur.katipo.co.nz 29 Aug '05

29 Aug '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1017 Summary: Reserve fee in accounts Product: Koha Version: 2.2.0 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: normal Priority: P2 Component: Circulation AssignedTo: chris(a)katipo.co.nz ReportedBy: tgarip(a)neu.edu.tr QAContact: koha-bugs(a)lists.sourceforge.net The scipt in Reserves2.pm CreateReserve reads $usth->execute($borrnum,$nextacctno,$fee,'Reserve Charge - $title',$fee); Its printing into accounts as 'Reserve Charge - $title' rather than title itself. Change to $usth->execute($borrnum,$nextacctno,$fee,'Reserve Charge -'. $title,$fee); to actually print the title. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1016] New: Crashed mySql tables
by bugzilla-daemon＠wilbur.katipo.co.nz 29 Aug '05

29 Aug '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1016 Summary: Crashed mySql tables Product: Koha Version: 2.2.0 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: enhancement Priority: P2 Component: Database AssignedTo: chris(a)katipo.co.nz ReportedBy: tgarip(a)neu.edu.tr QAContact: koha-bugs(a)lists.sourceforge.net This is some enhancement you may think about. The other day marc_subfield_table crushed. (How? Don't ask.) Nobody realised and Koha did not complain at all. We went on adding and modifying about 200 biblios without realising anything. Unless you go to see the MarcDetails everything looks fine. We found out on a un-routine Mysql tables check this was the case. What happened was that all the tables were being filled properly but the marc_subfield_table. The cleaning of the database was a little bit messy. It took more than half a day plus reentering all the data. We panicked so much that we added two lines to addbiblio.pl and additem.pl which locks and unlocks all the necessary times momentarily and on error returns you to mainpage.pl with error message "Contact automation for Mysql error". This way no addition or modification of tables is possible untill problem resolved. I know that this is not a common problem and yes I do not know how we managed to crush the table but yes tables do crash so it may be something to consider committing such a control in your script. Even if not committing I'll appreciate any better (faster) way of checking Mysql-health at least for us to use. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 612] Renewal failure gives no feedback
by bugzilla-daemon＠wilbur.katipo.co.nz 29 Aug '05

29 Aug '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=612 ------- Additional Comments From tgarip(a)neu.edu.tr 2005-08-30 03:31 ------- If Chris is going to look into this code here is some more concerns of mine. Currently the renewstatus is only cheking whether the number of renewals is reached to a certain limit and if there is any reserves on the item and nothing else. This script is also used in canbeookbeissued as well. There it does the correct thing of returning 0 or 1. My belief is that when renewing a book all the checks that issuing a book is done should be re-done. The patron may have overdues -fines etc. which the librarian should take into consideration. I personally would prefer to leave this script as it is and instead use the canbookbeissued script here again probably with a $renew flag. This way all the checks will be re-done and we can stop the script asking "This item is issued to this user. Renew Yes/No?". The flag can set this to yes and a proper renewal is accomplished. We are currently being able to renew items on members we would not be able to issue without confirmation. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 926] Many form tags lack method and/or action attributes
by bugzilla-daemon＠wilbur.katipo.co.nz 24 Aug '05

24 Aug '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=926 oleonard(a)athenscounty.lib.oh.us changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From oleonard(a)athenscounty.lib.oh.us 2005-08-25 06:15 ------- All instances of this problem should now be fixed, except in cases where the form tag is in use only to provide a hook for javascripted events. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 971] Incorrect use of term 'keyword' in searching template
by bugzilla-daemon＠wilbur.katipo.co.nz 22 Aug '05

22 Aug '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=971 ------- Additional Comments From oleonard(a)athenscounty.lib.oh.us 2005-08-23 06:57 ------- I think the point here is that what librarians and the public expect, and how they interpret the terminology. I would contend that the term 'keyword' is easily understood and unlikely to cause confusion in this context. I think 'free text' or 'fulltext' would be misunderstood by all but a small population of librarians. That's my perspective as a public librarian. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 660] HTML template bugs
by bugzilla-daemon＠wilbur.katipo.co.nz 22 Aug '05

22 Aug '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=660 oleonard(a)athenscounty.lib.oh.us changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From oleonard(a)athenscounty.lib.oh.us 2005-08-23 06:52 ------- I'm marking this as WONTFIX because the templates have changed so much from the time of this bug posting. It sounds like the poster is referring to an older version of the template. If similar problems still exist, please file a new report addressing specific files. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 998] MARC import fails when no ISBN present in 2.2.2b and 2.2.3
by bugzilla-daemon＠wilbur.katipo.co.nz 21 Aug '05

21 Aug '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=998 koha(a)alinto.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|chris(a)katipo.co.nz |paul.poulain(a)free.fr Severity|critical |normal ------- Additional Comments From koha(a)alinto.com 2005-08-21 12:47 ------- WORKAROUND Bulkmarcimport.pl does not use the same routines as MARC Import from within the cataloguing module. Use of bulkmarcimport.pl instead is an effective workaround for this problem. Bulkmarcimport.pl is not dependent on the fields defined for the framework and, for that reason alone, is a much better choice for importing records into Koha with whatever fields may have been omitted from the Koha MARC framework. Libraries using MARC Koha are often using external cataloguing and then sending files to bulkmarcimport.pl. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 612] Renewal failure gives no feedback
by bugzilla-daemon＠wilbur.katipo.co.nz 20 Aug '05

20 Aug '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=612 ------- Additional Comments From chris(a)katipo.co.nz 2005-08-20 11:02 ------- What happens here is it calls renewstatus in Circ2.pm Which simply returns 1 for ok, 0 for not ok. So the script itself doesnt know why it couldnt renew an item. Simply that it couldnt. So we will have to see how many places renewstatus is used, if it it will break things to pass back more than just 1 or 0. I think returning 1 or 0, and an error string might be the best. Ill work on that ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 997] No MARC subfield sequence specification or subfield repeatability
by bugzilla-daemon＠wilbur.katipo.co.nz 19 Aug '05

19 Aug '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=997 ------- Additional Comments From koha(a)alinto.com 2005-08-20 06:21 ------- The potential data corruption issue is much less significant than it would seem at first. Paul Poulain had anticipated the need and included marc_subfield_table.subfieldorder from the outset of the Koha MARC implementation two years ago. The column does store the subfield sequence. Paul had merely under-appreciated the need to make use of the column for records with which he had been familiar at the time. For those to whom this bug is of concern, the temporary workaround prior to a solution in the future Koha vesion 3.0 is to maintain MARC records in an editor external to Koha. Records may be updated or changed in the external record store with an external editor and then reimported into Koha as may be needed. This has been the practise of the current largest implementation of Koha, the Nelsonville Public Library. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1015] deleteditems table not being populated
by bugzilla-daemon＠wilbur.katipo.co.nz 18 Aug '05

18 Aug '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1015 ------- Additional Comments From chris(a)katipo.co.nz 2005-08-18 12:38 ------- Ah ha Someone has updated the items table, and not updated the deleteditems table. So there is now a column in tems that doesnt exist in deleted items. updatedatabase will need to be fixed ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0