April 2003 - Koha-devel - lists.koha-community.org

[Bug 247] New: we should split city and state in borrower info
by bugzilla-daemon＠wilbur.katipo.co.nz 01 Apr '03

01 Apr '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=247 Summary: we should split city and state in borrower info Product: Koha Version: CVS Platform: PC Status: NEW Severity: normal Priority: P2 Component: Members AssignedTo: chris(a)katipo.co.nz ReportedBy: pate(a)eylerfamily.org QAContact: koha-devel(a)lists.sourceforge.net > I would argue very strongly for separating City > and State in the database as > well. Any time you combine two different kinds > of data, you're creating a > potential problem for yourself down the road. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 246] New: can we add a "postal code" for borowers
by bugzilla-daemon＠wilbur.katipo.co.nz 01 Apr '03

01 Apr '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=246 Summary: can we add a "postal code" for borowers Product: Koha Version: CVS Platform: PC Status: NEW Severity: normal Priority: P2 Component: Members AssignedTo: chris(a)katipo.co.nz ReportedBy: pate(a)eylerfamily.org QAContact: koha-devel(a)lists.sourceforge.net Could we add a "Postal Code" field to the borrowers table before 2.0 is released? I know from Chris that postal codes are no big deal in New Zealand, but they're pretty much required in North America and Europe. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

log of QA meeting
by Pat Eyler 01 Apr '03

01 Apr '03

If you want to read the gory details, please take a look at: http://www.haz.cmsd.bc.ca/cgi-bin/kohalog.pl?date=01Apr03 -pate Pat Eyler Kaitiaki/manager migrant Linux sys admin the Koha project ruby, shell, and perl geek http://www.koha.org http://pate.eylerfamily.org

1 0

1st question from QA Meeting
by Pat Eyler 01 Apr '03

01 Apr '03

Well, it's not really about QA/Testing, but how close are we to having a good set of bulk-import tools? If they're not there yet, I'll open up a problem/enhancement at bugs. thanks, -pate Pat Eyler Kaitiaki/manager migrant Linux sys admin the Koha project ruby, shell, and perl geek http://www.koha.org http://pate.eylerfamily.org

1 0

QA meeting recap
by Pat Eyler 01 Apr '03

01 Apr '03

Wow! that was a great chance to sit down and talk through a lot of stuff. I think we came away with some good places to focus our attention, and some specific tasks to help make the QA/testing effort succeed. Thanks to all who participated. If you didn't, please feel free to join in next week for the two general meetings. -pate Pat Eyler Kaitiaki/manager migrant Linux sys admin the Koha project ruby, shell, and perl geek http://www.koha.org http://pate.eylerfamily.org

1 0

Special QA Meeting today
by Pat Eyler 01 Apr '03

01 Apr '03

Just a quick reminder ... the special QA meeting will be today in about 2 hours (1200 PST, 2000 GMT (or UTC if you prefer)). We're meeting in IRC at irc.katipo.co.nz on #koha. A log will be kept for those of you not able to make it. -pate

1 0

an interesting idea
by Pat Eyler 01 Apr '03

01 Apr '03

(see http://www.perl.com/lpt/a/2002/10/22/phrasebook.html http://use.perl.org/~gnat/journal/11285 http://use.perl.org/~djberg96/journal/11291 for more info) I just ran across a set of articles that triggered some thinking for me. The basic idea is that we could create a phrasebook of (templated) SQL queries external to the normal modules and scripts. Whenever we need to use a specific query we can slurp it out of the phrasebook, fill in the variables, and run it. I think this might win in two ways: 1) it will be easier to maintain/improve the SQL queries if they're not strewn about in the code 2) we can work at translating the queries into other (nonMySQL) dialects of SQL if we ever decide to support them. The same tool *might* also help us maintain translations internal to our scripts (as opposed to things we've already used HTML::Template for). There might be stickiness in a couple of areas too. The biggest one that I see is that we'll have to be very careful not to break the API presented by a query (i.e., what variables it requires, what data it passes back) -- This is an excellent place for unit tests to help us. any other thoughts? -pate Pat Eyler Kaitiaki/manager migrant Linux sys admin the Koha project ruby, shell, and perl geek http://www.koha.org http://pate.eylerfamily.org

3 6

Internal Server Error on 1.90
by Ingrid Lacis 01 Apr '03

01 Apr '03

I don't know if this is a bug or an error on our part. In version 1.90, librarian interface, I do a search (Advanced Search) and get a list of books returned to me. /cgi-bin/koha/search.pl I click on the title and I get: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. The error log says: Tag " " is not a valid tag. at /usr/local/share/perl/5.6.1/MARC/Record.pm line 535 [Fri Mar 28 10:51:48 2003] [error] [client 192.168.0.123] Premature end of script headers: /usr/local/koha-unstable/intranet/cgi-bin/MARCdetail.pl Thanks, Ingrid _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail

2 1