March 2004 - Koha-bugs - lists.koha-community.org

[Bug 751] New: Bugzilla should have a HEAD version (Koha 2.2?)
by bugzilla-daemon＠wilbur.katipo.co.nz 16 Mar '04

16 Mar '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=751 Summary: Bugzilla should have a HEAD version (Koha 2.2?) Product: Koha Version: unspecified Platform: PC Status: NEW Severity: normal Priority: P2 Component: bugs.koha.org AssignedTo: chris(a)katipo.co.nz ReportedBy: jferraro(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)lists.sourceforge.net Shouldn't there be a way to specify that a bug exists in HEAD other than the generic 'CVS'? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 750] New: Problems with HEAD
by bugzilla-daemon＠wilbur.katipo.co.nz 16 Mar '04

16 Mar '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=750 Summary: Problems with HEAD Product: Koha Version: CVS Platform: PC Status: NEW Severity: normal Priority: P2 Component: OPAC AssignedTo: chris(a)katipo.co.nz ReportedBy: jferraro(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)lists.sourceforge.net opac-error log: [Tue Mar 16 12:30:40 2004] [error] [client 24.208.177.38] Premature end of script headers: /usr/l ocal/koha/opac/cgi-bin/opac-main.pl Can't locate Net/LDAP.pm in @INC (@INC contains: /usr/local/koha/intranet/modules/ /etc/perl /usr /local/lib/perl/5.8.3 /usr/local/share/perl/5.8.3 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5 .8 /usr/share/perl/5.8 /usr/local/lib/site_perl /usr/local/lib/perl/5.8.2 /usr/local/share/perl/5 .8.2 .) at /usr/local/koha/intranet/modules//C4/Auth.pm line 31. BEGIN failed--compilation aborted at /usr/local/koha/intranet/modules//C4/Auth.pm line 31. Compilation failed in require at /usr/local/koha/opac/cgi-bin/opac-main.pl line 7. BEGIN failed--compilation aborted at /usr/local/koha/opac/cgi-bin/opac-main.pl line 7. [Tue Mar 16 12:33:41 2004] [error] [client 24.208.177.38] Premature end of script headers: /usr/l ocal/koha/opac/cgi-bin/opac-main.pl [Tue Mar 16 14:55:33 2004] [error] [client 69.58.13.236] File does not exist: /usr/local/koha/opa c/htdocs/favicon.ico Missing right curly or square bracket at /usr/local/koha/intranet/modules//C4/Auth.pm line 469, a t end of line syntax error at /usr/local/koha/intranet/modules//C4/Auth.pm line 469, at EOF Compilation failed in require at /usr/local/koha/opac/cgi-bin/opac-main.pl line 7, <DATA> line 42 2. BEGIN failed--compilation aborted at /usr/local/koha/opac/cgi-bin/opac-main.pl line 7, <DATA> lin e 422. [Tue Mar 16 14:55:34 2004] [error] [client 69.58.13.236] Premature end of script headers: /usr/lo cal/koha/opac/cgi-bin/opac-main.pl Missing right curly or square bracket at /usr/local/koha/intranet/modules//C4/Auth.pm line 469, a t end of line syntax error at /usr/local/koha/intranet/modules//C4/Auth.pm line 469, at EOF Compilation failed in require at /usr/local/koha/opac/cgi-bin/opac-main.pl line 7, <DATA> line 42 2. BEGIN failed--compilation aborted at /usr/local/koha/opac/cgi-bin/opac-main.pl line 7, <DATA> lin e 422. [Tue Mar 16 14:56:46 2004] [error] [client 69.58.13.236] Premature end of script headers: /usr/lo cal/koha/opac/cgi-bin/opac-main.pl Missing right curly or square bracket at /usr/local/koha/intranet/modules//C4/Auth.pm line 469, a t end of line syntax error at /usr/local/koha/intranet/modules//C4/Auth.pm line 469, at EOF Compilation failed in require at /usr/local/koha/opac/cgi-bin/opac-main.pl line 7, <DATA> line 42 2. BEGIN failed--compilation aborted at /usr/local/koha/opac/cgi-bin/opac-main.pl line 7, <DATA> lin e 422. [Tue Mar 16 14:56:51 2004] [error] [client 69.58.13.236] Premature end of script headers: /usr/lo cal/koha/opac/cgi-bin/opac-main.pl ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 748] Modfy loan length according to borrower category
by bugzilla-daemon＠wilbur.katipo.co.nz 16 Mar '04

16 Mar '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=748 ------- Additional Comments From shedges(a)athenscounty.lib.oh.us 2004-03-17 07:40 ------- Yes, categoryitem definitely looks to be the most flexible. It might be difficult, however, to load. Seems like you'd need a row for every itemtype for a given categorycode if you wanted to give the categorycode extended loans for all itemtypes. Note that this enhancement might also address bug 289. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 749] New: moditem.pl doesn't do anything
by bugzilla-daemon＠wilbur.katipo.co.nz 16 Mar '04

16 Mar '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=749 Summary: moditem.pl doesn't do anything Product: Koha Version: 2.0.0 Platform: PC Status: NEW Severity: major Priority: P2 Component: Catalogue AssignedTo: chris(a)katipo.co.nz ReportedBy: shedges(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)lists.sourceforge.net moditem.pl does not save any of the changes to the database. It looks like moditem.pl sends the current data to moditem.tmpl, where it can be changed on the screen, but the 'save' button makes no changes to the database. Also note that moditem.pl does not have an $inputs{"itemwithdrawn"}, so no value is being passed to the template, and that the name in the template is "withdrawn" instead of "itemwithdrawn." Actually, this whole thing is so messy, it might be better to forget moditem and build the capability of setting lost and withdrawn flags into additem.pl ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 748] Modfy loan length according to borrower category
by bugzilla-daemon＠wilbur.katipo.co.nz 15 Mar '04

15 Mar '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=748 chris(a)katipo.co.nz changed: What |Removed |Added ---------------------------------------------------------------------------- OS/Version| |All ------- Additional Comments From chris(a)katipo.co.nz 2004-03-16 09:24 ------- If we used the categoryitem table, Then we can specify the loanlength per itemtype per borrower type. This might be the most flexible way ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 748] New: Modfy loan length according to borrower category
by bugzilla-daemon＠wilbur.katipo.co.nz 15 Mar '04

15 Mar '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=748 Summary: Modfy loan length according to borrower category Product: Koha Version: CVS Platform: PC Status: NEW Severity: enhancement Priority: P2 Component: Circulation AssignedTo: chris(a)katipo.co.nz ReportedBy: shedges(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)lists.sourceforge.net It would be nice to control loan length based on the category of borrower, as well as the type of item. That way, staff or teachers could keep items longer than 'regular' borrowers. One way to do this might be to add a "loanlengthfactor" column to either the borrowers table or the categories table. If staff could keep items twice as long as other borrowers, then the loan length factor would be '2'. If a loan was meant to be (almost) permanent, the loan length factor could be '99'. If the normal loan period was two weeks, but children's librarians can keep things three weeks, then the factor would be '1.5', etc. While the sticky due date already makes such things possible, it would still be nice to have this automatically calculated by borrower category. Circ2.pm would need to retrieve the loan length factor from the appropriate table. Then in the issuebook function in Circ2.pm, insert a line (after current line 771) that recalculates the loan length based on the loan length factor -- like $loanlength=$loanlength*($patroninformation->{'loanlengthfactor'}). I notice also that there is some hard-coding of borrower categories in Circ2.pm (starting at line 614). Perhaps my simple suggestion could be made more complex to handle this as well. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 747] New: OPAC barcode search doesn't work
by bugzilla-daemon＠wilbur.katipo.co.nz 12 Mar '04

12 Mar '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=747 Summary: OPAC barcode search doesn't work Product: Koha Version: CVS Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: OPAC AssignedTo: chris(a)katipo.co.nz ReportedBy: oleonard(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)lists.sourceforge.net I never tried it before, because we took it out of our template, but it looks like the OPAC's barcode search doesn't work. I get no results for a barcode I know exists. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 746] New: Separate interface for patron notes
by bugzilla-daemon＠wilbur.katipo.co.nz 12 Mar '04

12 Mar '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=746 Summary: Separate interface for patron notes Product: Koha Version: CVS Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Members AssignedTo: chris(a)katipo.co.nz ReportedBy: oleonard(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)lists.sourceforge.net We use patron notes pretty often for communicating information between staff members about particular patrons. It would be good for us to be able to add/edit/delete patron notes via a separate interface. I picture a link or button on the patron record (available in both members and circulation) which pops up a window for entering or editing the notes. It'd be good to also have a 'delete' link or button alongside so that the note could be deleted with a click. This kind of interface would save the steps of opening the patron's record, clicking to modify it, editing/deleting the note, submitting, and confirming. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 745] New: subjectsearch.pl not templated
by bugzilla-daemon＠wilbur.katipo.co.nz 11 Mar '04

11 Mar '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=745 Summary: subjectsearch.pl not templated Product: Koha Version: 2.0.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Catalogue AssignedTo: chris(a)katipo.co.nz ReportedBy: a.c.li(a)ieee.org QAContact: koha-bugs(a)lists.sourceforge.net subjectsearch.pl is not templated, but it seems to be also unused. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 744] New: Add new supplier allows blank supplier information
by bugzilla-daemon＠wilbur.katipo.co.nz 11 Mar '04

11 Mar '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=744 Summary: Add new supplier allows blank supplier information Product: Koha Version: 2.0.0 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: Acquisitions (Full) AssignedTo: chris(a)katipo.co.nz ReportedBy: a.c.li(a)ieee.org QAContact: koha-bugs(a)lists.sourceforge.net If I go to Add new supplier and then save without entering anything, a blank supplier record is created. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0