July 2002 - Koha-devel - lists.koha-community.org

Diffs between rel-1-2 and main branches
by Tonnesen Steve 03 Jul '02

03 Jul '02

This is directed mainly at Paul, but others might find it useful as well. http://www.haz.cmsd.bc.ca:8080/cgi-bin/kohadiff Shows a list of files in rel-1-2 branch that are different from those in the main trunk. This is intended to replace the table on the wiki which is basically impossible to maintain. The kohadiff script will show diffs between files in regular or side-by-side format, and allows arbitrary comments to be attached to specific files. One small bug: doesn't list files that are in the main branch, but missing in rel-1-2. Steve. NB: If you go to www.haz.cmsd.bc.ca:8080 you can even change the volume of the music on my laptop... I'll have to password protect that page. :)

2 1

branch differences script
by Tonnesen Steve 02 Jul '02

02 Jul '02

Chris informed me that my www.haz.cmsd.bc.ca:8080/cgi-bin/kohadiff wasn't working for him. The following address goes to the same machine: http://hazeltonsec-17.cmsd.bc.ca/cgi-bin/kohadiff Steve.

1 0

[Bug 59] New: warn if can't determine apache user
by bugzilla-daemon＠wilbur.katipo.co.nz 02 Jul '02

02 Jul '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=59 Summary: warn if can't determine apache user Product: Koha Version: 1.2.0 Platform: PC Status: NEW Severity: normal Priority: P2 Component: Installation AssignedTo: tonnesen(a)cmsd.bc.ca ReportedBy: tonnesen(a)cmsd.bc.ca QAContact: koha-devel(a)lists.sourceforge.net installer.pl should warn if it can't determine the apache user from httpd.conf, etc. and tell the user what may need to be modified (eg. ownership of /etc/koha.conf in particular, and z3950 scripts). ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

RE: RE: Hello
by Nicholas Rosasco 02 Jul '02

02 Jul '02

For openers: What does Library Pro do for you, exactly? I'm actually not all that familiar (some of the Koha team are however, if it becomes a bigger question) with commercial library software... save as a patron! Koha is a full service catalog and circulation application.... everyone who uses it uses it as a complete solution... [I'm a little confused by the "Does this mean that our Library Pro needs to be Web Based software?" question, and I or the Koha documentation may've miscommunicated what Koha is. Forgive me if you already "get" the above.] What most people who have shifted to Koha from existing library systems have done is exported their catalogs (we can help explain the easy ways to accomplish that) from their existing system(s) into the database that web and circulation systems use to make the usual library things -- finding a book, checking in/renewing, etc -- work. Koha is, from the standpoint of a library patron (I avoid the term user... confusion between the library's staff and the patrons) a web page that provides the usual library catalog services. From a IT person's point of view, Koha is (typically but not exclusively) a server (usually a somewhat souped up PC) with a network connection which runs Linux, the Apache web server software, and the scripts and utilities that are Koha. For the librarian, Koha is either a application (running over telnet) or a web frontend that permits them to check out books. Your Imacs and G4s should have no problem running a reasonably current web browser, and I'm guessing you have some sort of network connectivity for them. As far as support, some of the current Koha-using sites have in-house staff who care for the server (usually doing several other things as well... it isn't a full time function) or have a contract with a local firm to do routine tasks (these aren't too exotic -- I'd wager there is a local ISP or somesuch that can help you -- ask around to see if there is Linux experience nearby.). The standards question is one that can be a little stickier.... is there a bullet-list or somesuch? IE, are there specific standards and protocols [keywords here are "Is full MARC compliance necessary?", "Is SIP/NCIP necessary?"]? It sounds like you guys have MARC at least as a standard -- it is Koha's objective to support MARC as fully as humanly possible :) by the end of this summer. Does any of this help? Sorry for adding more verbiage/work/etc! Nick Rosasco > -----Original Message----- > From: Karen Littlefield [mailto:klittle@mid-del.k12.ok.us] > Sent: Tuesday, July 02, 2002 2:46 PM > To: nsr(a)etome.net > Subject: Re: RE: Hello > > > ** Reply Requested When Convenient ** > > > > Reply requested when convenient > > > Koha is normally run on a dedicated server (most of us use what is in > practice a high performance PC) connected to the internet and the catalog > information is delivered via the web (in other words, whatever > your schools > use for book check out will need a network connection, as will whatever is > used to view the catalog). Does this mean that our Library Pro > needs to be Web Based software? > > Forgive me for the bullet points... > What kind of technology do you currently have? Presently all of > our libraries are using iMac or G4 computers. They are served > from a Novel 5.12 server with the data residing on the server and > the application on the local HDs. > [Koha is normally configured and run on a Unix/Linux machine, but the > catalog and circulation system can be used with anything with a web > browser.] > > What kind of support (staff? contractor?) do you have? We have a > WAN coordinator, a tech support coordinator, both of which take > care of the equipment and repair issues. I do the software > training piece. I am a former librarian and know the Library Pro > software inside and out. > [Koha is intended to be pretty easy to handle, but installation at the > moment is a little complicated at the moment.] I know the guys > would help me with the install. > > What kind of budget do you have for this project? Not much, > that's why free sounded good. I could provide a new server if > needed but anything else is questionable. > [Koha is free, I'm free, but Murphy's law :)] > > Are there are sort of standards (cataloging, circulation) you > must abide by > [you may need to check with your librarians on that]? We have a > district policy for cataloging and ciruculation but I know we > have some who do not follow it to the T. What are the key fields > and issues we must clean up to make this work? > > What sort of record exporting does your catalog support? [If we're lucky, > you may be able to feed all the book records directly from one to the > other...] We can export Marc records as ASCII files or as text > files. We import from vendors all the time. > > Thanks for your help. > > > Karen Littlefield > klittle(a)mid-del.k12.ok.us > Mid Del Schools > Midwest City, OK 73110 > 405-737-4461 x294 >

1 0

[Bug 49] Z39.50 module makes too many connections to the database
by bugzilla-daemon＠wilbur.katipo.co.nz 02 Jul '02

02 Jul '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=49 ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-07-03 04:12 ------- Point taken. I'll remove my changes to this file. Regarding using another user like daemon... the user needs to be able to read the koha.conf file to get the username and password to access the database. Also, at the moment, I'm using "kill -HUP [PID]" to signal the daemon to process the queue of z39.50 queries, which probably requires that the daemon be running as the same user as apache. This could be changed to some other signalling scheme like a named pipe or a socket, though. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

This week
by Pat Eyler 02 Jul '02

02 Jul '02

Hello everybody. Due to some changes in my employment, I'm not going to be nearly as available this week. I still plan on getting my weekly email out, and will be responding to email 2-3 times/day. I hope that Nick, Chris, and Paul can handle some of the additional emails that I would be dealing with, and that the reast of you will enjoy a break from me asking inane questions at unreasonable hours. thanks, -pate

1 0