June 2002 - Koha - lists.katipo.co.nz

Questions about using Koha in our primary school
by georgejenner＠belgacom.net 15 Jul '02

15 Jul '02

Hello there I'm going to start with one long message. I've been through the archives and need to talk to you all. My child's primary school has been split into two campuses, and we've lost the library entirely. And there is no budget for a new library for several years. Open source and freeware look even better when you have no money :-) So some parents have volunteered to make a library. A computer has been donated, and the collection will be started from donated books. The committee have also received good advice from another local school : be very wary of parents offering help with computers. That's me :-) The main question is one you must receive frequently. Does platform independence really include Windows? The computer has been purchased and I assume it came with Win XP (I haven't seen it yet). I don't think I could convince them to use Linux, even if I had a clue about it myself. In any case, I want to test out and demonstrate Koha using my laptop which runs Win ME. I see from the installation notes that it has been installed on NT and Win 2000 with considerable difficulty. Can you tell me how difficult? I have no knowledge of perl or Apache. Does that make it pointless trying without years of study? The next question is about languages. The OPAC at our school would be presented in at least 5 European languages, including Greek. The school has 5 language sections, plus Irish, but all other languages in the European Union would be represented in the book collection. So would a multilingual OPAC be difficult to produce? There would possibly be some benefit to Koha from this, and perhaps this could be our contribution to the cause: translations of key documents into all these languages. Next question. The library will be staffed by volunteer parents with less computer knowledge than even me. There won't be a trained librarian for at least 3 years. Would this present a problem? Is the system sufficiently simple and robust that we can't get into much trouble? Next question. As the collection will be started with donated books, we need to catalog them. There is a shareware proggy that purports to take an ISBN and then search the internet for the book, then places the biblio dat in a database. It's called Readerware. It says it even gets the cover art and includes that. I think that having cover art would be really nifty for a primary school library. So could the OPAC show that. Is this simply a question of having an image in a field of a MySQL database. And is that possible? I'll stop there. If you can give me good news I'll start downloading. I've got a couple of months to get it going as the school year starts in September in Europe. As if things weren't weird enough. Thanks for any help George

2 1

Some question: postgres, italian, ...
by Marco Gaiarin 08 Jul '02

08 Jul '02

I'm looking for a library management software for my organization, so i've found koha. Interesting... ;-))) Some question: 1) there's just a translation in Italian?! Can i contribute this?! 2) i want to use koha with postgres, but i need assurance that work with potgres. I've had experience with other software written for mysql that in theory work with pgsql but in practice all sources have to be rewritten. ;( 3) In any case need to be rewritten the schema. Please, don't distribute the schema in mysql dump format, is not portable and are full of (nonstandard) SQL instruction. Someone have just rewritten the schema for postgres?! Basically have to be rewritten the KEY instances (to CREATE INDEX) and the auto_increment (to serial). Again: PG support real referential integrity (FOREIGN KEY). There's somewhere a E/R schema that explain referential integrity, or can i add referential integrity (if someone exlain me the schema?!). 4) I'm new to library related problem, but seems that the MARC format is a standard in this field. Someone know if this also rule for european country?! Before starting a big google session, if someone have some pointers... Thanks. -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia'' http://www.sv.lnf.it/ Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN) gaio(at)sv.lnf.it tel +39-0434-842711 fax +39-0434-842797 Supporta il disegno di legge sul software libero! http://www.softwarelibero.it/news/news020417_01.shtml

6 12

Feature Request : Database Tables
by Tom Albrecht 02 Jul '02

02 Jul '02

Hi, I'm not sure if this is the correct address for feature requests, but here goes. If I'm wrong, please let me know where I should send it. I've been testing Koha for our church library, and it looks like exactly what we need. However, I've noticed a database shortcoming that if addressed would make things a lot easier for me. The database tables Biblio and Bibliosubject are linked with the common field biblionumber, with a one-to-many relationship, allowing multiple subjects for a particular title. This is wonderful, but the list of available subject strings are not stored anywhere, and are entered manually. My thought is that there should be another table, say "subjects" that would contain two fields, a unique subject ID number, and a subject string. Then, replace the string "subject" in bibliosubject with the id number. This has multiple advantages... 1) It allows a universal subject name change to be easily implemented. For example, currently, if I want to change all instances of "FEMINIST THEOLOGY" with "FEMINIST DOCTRINE", I'd have to search and replace through every "bibliosubject" record. With the change, I would only need to change one "subject" record. 2) It allows for an exclusive list of subjects. I would hate to accidently misspell "Religien", and create a whole new field. If the "subject" table were exhaustive, only fields from that table would be allowed to be use. Please let me know your thoughts! Tom Albrecht III

2 1

Re: [Koha-devel] 1.2.1 RC6
by Pat Eyler 29 Jun '02

29 Jun '02

RC tarballs can also be found at http://pate.eylerfamily.org/Koha/ Please feel free to grab it and test it (and let us know what you find). Please, remember that these are release candidates only -- using them may cause all of your hair to fall out (unless you're already bald, in which case it will all grow back in but will be purple.) thanks, -pate On 29 Jun 2002, Chris Cormack wrote: > Hi all > > A new and even shinier release candidate is out. > Included in RC6 are some fixes for some bugs that crept into RC5 as well > as extending the installer script to set up basic authentication for the > intranet. > > http://developer.koha.org/koha-1.2.1RC6.tar.gz > > Please download and put it through its paces. > Bugs can be reported at bugs.koha.org > > Chris >

1 0

Koha success stories sought
by Pat Eyler 28 Jun '02

28 Jun '02

Hello, I'd like to write an article about Koha for the linuxgazette (or see someone else write one if they'd rather). Key to doing so would be to gather one or more success stories about using it, writing an introductory text, and creating a list of resources (links) for people to follow up with. Any stories contributed might also make nice articles for www.perl.com in their success stories. If anyone is interested in contributing stories (or writing the article), please drop me a line. thanks, -pate

2 1

Bug?
by Tom Albrecht 28 Jun '02

28 Jun '02

Hi all... I'm new to the list, and I've been searching through the archives for information on the following bug, and didn't see anything, so I decided to post it. Please don't flame me. In many of the perl files, the following code exists... print mktablerow(5,$toggle,$results->[$i]{'printername'},$results->[$i]{'printqueue'},$results->[$i]{'printtype'}, mklink("$script_name?op=add_form&searchfield=".$results->[$i]{'printername'},'Edit'), mklink("$script_name?op=delete_confirm&searchfield=".$results->[$i]{'printername'},'Delete','')); Now, when I ran these perl functions "out of the box" I was gettig 500 server errors... digging through the apache logs, I see the following. Too many arguments for C4::Output::mklink at /home/httpd/cgi-bin/koha/admin/printers.pl line 227, near "'')" Execution of /home/httpd/cgi-bin/koha/admin/printers.pl aborted due to compilation errors. [Thu Jun 27 23:44:22 2002] [error] [client 66.92.231.155] Premature end of script headers: /home/httpd/cgi-bin/koha/admin/printers.pl Odd, I think to myself, so I look at the two calls to "mklink" and I see that they do, in fact, have a different number of parameters. Now, since the final parameter in the "delete" call is blank, I tried deleting the last parameter, and it works (well, at least it displays). Is this a legitimate bug, or did I totally screw something up? Tom Albrecht III West Chester, PA United States of America

2 1

From the Kaitiaki
by pate＠bigfun.whirlycott.com 28 Jun '02

28 Jun '02

28 June, 2002 To the Koha community; Namaskar, This week's note is a short one. Not because we haven't done much, but because we're all getting pretty busy. I'm currently talking to a couple of organizations about getting some more visibility for Koha. I don't want to tip my hand just yet, but I'm hopeful that we'll see Koha beginning to make appearances in the bigger Open Source world 'Real Soon Now'. We're also starting to see some more feedback from other library centric Open Source projects. It looks like the idea of some inter-project cooperation is gaining ground. One interesting area that came up was in helping one another in securing financing (sponsorship, hired work, or grants all come to mind) -- this will be an important area for Koha moving forward. Free Software doesn't come without a price tag, the price is just hidden better than with other software. Much of Koha is developed by volunteers in their 'spare' time. If there were funding available for given tasks, it would give the developers more time to work on Koha (because they'd need to spend less time making a living). If you're interested in helping this way, please take a look at <http://koha.org/installation/support.html> for some potential vendors. 1.2 We're still hard at work on 1.2.1. In fact, Steve Tonnesen has produced three Release Candidates this week alone. He's also made the job easier by automating this process, so expect to see Release Candidates for every future release -- it's another way we're trying to improve our process. Other big features for 1.2.1 include: * a much improved installer (it only requires 1 ip address, and creates a branch and a printer during install now) * more work on the Z39.50 programs * sample data that can be installed to test a new koha system Many thanks to Paul and Steve who've both jumped in and are making the 1.2 series really shine. Translations The first question people seem to ask when volunteering to do translations of Koha is, "Where do I start?". Since we're still on the verge of having the application readily translatable, this question deserves a thoughtful answer. There are a number of things that could be translated and provide value to the project. These newsletters, if translated, could help advertise Koha to people who don't currently know about it. The Manual could be translated to help users and developers who don't understand english. I think one of the best documents to translate would be the INSTALL document. If we could get this done in multiple languages, it would be much easier to get Koha into the hands of the people who will help us make it suitible for international use. IRC Meeting Due to some scheduling conflicts, this weeks irc meeting was postponed. We're going to shoot for 7/11 (7/4 is a big holiday in the US, so that won't work either). The proposed agenda is currently: * CVS * 1.2 schedule * 1.4 plans * thoughts on templating * translations * documentation housekeeping * community (Koha, and the larger OSS4lib, and the larger library * new koha website Community The Koha community is continuing to grow. More libraries are trying Koha out, and many of them are sticking with it. We've added more people to the developers list, several of whom are concentration on testing new Koha releases. Another exciting advance is the new <www.koha.org> website. Rachel and her team at Katipo have done a wonderful job. I'd like to hear back from people who are currently using or investigating Koha. If you've got stories, requests, or suggestions, please feel free to drop me a line at: kaitiaki(a)koha.org Dhanyabad, -pate Pat Eyler Kaitiaki of the Koha Project ps. This weeks language is Bengal. Hopefully my usage isn't too far off. Thanks Md. Aftabuddin, for helping out.

1 0

upgrade script
by Tonnesen Steve 27 Jun '02

27 Jun '02

I managed to put together an upgrade script today that will be going out with the 1.2.1 release. The upgrade script (koha.upgrade) will make backups of your koha data, and all of the koha scripts and html files before installing the new files and making any necessary changes to the database. The upgrade script also indicates changes that may need to be made to the Apache configuration. I suspect there aren't a whole pile of production Koha systems out there yet, apart from Katipo's clients and my schools. If you _are_ using Koha in a production environment, I'd really appreciate hearing from you before the 1.2.1 release goes out. Steve.

1 0

Koha install problem summary, final I hope
by Md. Aftabuddin 25 Jun '02

25 Jun '02

On Sat, 22 Jun 2002, Pete Dubler wrote: > Below is a summary list of the problems I am experiencing with my new > fresh install of Koha 1.2.1 on my new server running RH 7.1 > > Each problem is started with "***" subtopics of that problem start with > "###" > > I will be using my koha system to do two things: > 1-Track all of the science resources on my charter K-12 school campus. > Teachers will be able to search for items using keywords and then check > them out to themselves for use in their classrooms. I would like to be > able for them to know who has an item check out so they can go get it > directly from that person. > > 2-Bring up our new library for the whole school on koha, using the same > server. > > I need to be "on-the-air" by July 5 as we move all our inventory into > our new building and receive new big shipments the week of July 8. > > The good news is that I have all of the networking stuff worked out and > have koha (lib) and opac (lookup) running across my home network. Now > if I can just get all of this volunteer work done for the school without > burning down my house, from all of the computers in my home office, and > starting the next wildfire in Colorado... > > Thanks for any and all help you can provide. Special thanks to Chris, > CJ, Md, and Pat for their help to date. > > Pete Dubler > for Ridgeview Classical Schools > Fort Collins, Colorado > > *** Acquisitions: I still can't get the "simple" acquisitions version to > load. But, I can force myself into it by using a link like: > http://lib/cgi-bin/koha/acqui.simple/addbooks.pl > (lib is the name of this virtual server underwhich koha is running). I > have tried using mysql with the command: > > update systempreferences set value='simple' where > variable='acquisitions'; > quit; The command is insert into systempreferences values('acquisitions','simple'); quit; > > with no success. (stopped mysqld, restarted httpd, started mysqld, > flushed netscape caches). I have webmin and first set the > systempreferences table to be modifiable in everyway by root. Advice? > > > *** Addbooks: When I go to add a book (using the armstrong method > outlined above), I understand that there are three screens that one has > to complete . I complete the first 'Section One: Copyright Information' > and press 'add new bibliography', then it brings up the second 'Section > Two: Publication Information for Test Book by Tommy Tester', which I > complete and press 'add new bibliography'. It then returns me to a > blank first screen, 'Section One: Copyright Information'. What's with > that? > Solution is below, after circulation. > *** Circulation: Comes up without the "Choose a branch" and "Choose a > printer" pulldowns. So per earlier advice, I tried to add a branch and > printer to my database. Below is what happened. > you have to enter atleast one record for printer and branches table insert into printers values('xxx','yyy','zzz'); insert into branches (branchcode,branchname, issuing ) values('abc','name of the branch','1'); ====note===replace 'abc' and 'name of the branch' with suitable words you ====prefer. replacement of 'abc' can be maximum of four charecters. ====memorise the the replaced word with 'abc'.It will be required for the ====three page book insertion. for addbooks : modify the file addbools.pl find the word SWTE and change with the word you memorised above in Circulation reply. In three places you have to change. > ### Parameters:Library Branches: I cannot add a new branch > successfully. When I try by filling out the form and pressing "OK", I > just get a blank page. I do not know what goes in the "Issuing" field, > so I have once left it blank and another time just put 'ok' in it. > Advice? > where do you get the above page ? > Things I know: > * Koha is my database and according to mysqlshow and webadmin, it > is there. > * mysqld is running. > * (I also know other things, in case you were wondering, but they > are not relevant to this situation ;^) > > ### Parameters: Printers: I was able to add a printer named "LaserJet" > on the lpt queue of the type local. > > *** Adding Members: I am unable to add members because I do not know > the valid range for library card numbers. Anyone able to provide me a > pointer here? (eg man page to refer to) > add another record in the systempreferences table insert into systempreferences values('autoMemberNum','1'); > *** Adding Members: How hard would it be to modify this screen to > reduce the number of fields since I really only need names and card > numbers? This would mean telling the database that the other 'required > fields' are not required. > Md. Aftabuddin

1 0

Re: [Koha] importing MARC records
by Alan Millar 25 Jun '02

25 Jun '02

> From: micheas <micheas(a)micheas.dyns.net> > FreeBSD does not have an equivalent of linux's 'su -c' Equivalent? You're right the FreeBSD "su" command does not have the same option to run an arbitrary command as an argument, but there are other ways to solve the problem. Worst case, the z3950-daemon-shell can be SUID with the appropriate file owner. Not the ideal solution, but it is functionally equivalent. I think this falls in the "keep looking" category. > Are any of the environment names set by the shell script passed to > the perl script that runs the daemon by name (ie do I have to keep > your variable names?) No, you don't have to keep them. Do they need to be changed? If they aren't descriptive or explanatory enough, let's change them in the current script also. > Is there any reason to not have apache call the script? (ie does > anything have to be done as root?) Yes, there is a reason not to. For one, the Linux "su -c" does need to be root. Also, the script should be run once, not everytime someone makes a search request. I don't think Apache was designed to be an arbitrary launcher, so it would probably be a lot *more* work to shoe-horn it into Apache. And the search daemon isn't really Apache related. I have some command-line text-mode add-ons for Koha, which may show up in the release later, which use the Z39.50 search facilities. They don't have anything to do with Apache, and neither does the search daemon. <rant> Only bad applications are "purely" web-based. Good applications have a major amount of web facing to them, but also have parts that are abstracted from it so they are useful in other ways also, such as batch automation. "I don't *want* to click [Submit] 483 times..." </rant> > Does it make sense to try changing the perl script instead of > rewriting the shell scripts for each os? No. The shell scripts should handle each OS's various quirks, precisely so the Perl script *doesn't* have to change for each OS. If you look closely, after all the comments and overhead are stripped out, the two Z39.50 scripts do only two lines of actual work: The -launch script uses "su" to change the user ID, and the -shell script sets PERL5LIB before running the daemon. That's the only actual work done in the scripts. Everything else in there now is either comments or fluff. Anything else needed for another OS should be encapsulated in the script likewise. So a "rewrite" of the scripts should be two or three lines of code. > Telnet terminals -- HERE BE DRAGONS -- these maybe problematic under > FreeBSD. Actually, this is non-issue. The name "Telnet terminals" is misleading. It really just means "text mode". There is absolutely nothing special about Telnet. It's a handy name because people know that when you use telnet, you get a text-mode session. You can use SSH and the program will be exactly the same. Thanks for your work in identifying issues. - Alan ---- Alan Millar --==> am12(a)bolis.com <==--

2 2