- Koha - lists.katipo.co.nz

character encoding & bulkmarcimport.pl
by Jason Ronallo 09 Jun '07

09 Jun '07

Hi, I'm wondering if the script bulkmarcimport.pl is simply checking for the value of leader byte 9 if your framework is set to MARC21/USMARC records and then trusting that value. If it's blank it assumes MARC-8 encoding and converts it to UTF-8 using MARC::Charset; if ldr9 is 'a' then it assumes UTF-8 and leaves it as is. Is there something else going on here? Is this a relatively safe approach with MARC21/USMARC records as a whole? Should bulkmarcimport.pl only be used on records that are known to be only MARC-8 and/or UTF-8? I'm wondering if there aren't other non-standard character encodings for MARC21 records out there. For instance, the Wellcome library [1] says it provides records in MARC21 and then says they are in ISO-8859-1 (Latin1) character set. I can imagine there are others out there. I don't know if Latin1 would be a problem, but it seems that other character encodings might be if MARC-8 is assumed to be the character encoding when it isn't. Does the built in Z39.50 search, do character set conversion to UTF-8 as well? Thanks for any help you can provide understanding how Koha handles character encodings. --Jason [1] http://library.wellcome.ac.uk/node58.html#P24_1668

2 1

Automatic Email sending with Koha
by Cyril Lafont 08 Jun '07

08 Jun '07

Hi everybody, I have a problem with my Koha server (2.2.8) on a Linux Debian. The server doesn't want to send automatic emails to the borrower. It's strange because the server can send email with the command line. The postfix configuration is OK. Have you any idea? Thanks Regards -- LAFONT Cyril Communauté d'agglomération dracenoise Computer departement manager

2 1

upgrading to Koha 2.0
by Robert Polidoro 08 Jun '07

08 Jun '07

Hi, I've got an ancient version of koha(1.2.3) and I am having trouble upgrading this to koha 2.0 or finding any information on how to do this. Is upgrading from 1.2.3 to 2.0 similar to upgrading 2.0 to 2.2.* as in making the symlinks, etc, as described in these steps: (http://www.kohadocs.org/Updating_Koha.html#d0e285) ??? I cant find much documentation and what I've tried so far doesn't seem to work. This will be running on debian system with MySql 5.0 and apache 2 Any information on getting from 1.2.3 to 2.0 would be much appreciated, thanks in advance Rob This Message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender and not necessarily the views of the Judicial Commission of NSW.

2 1

koha version available with PostgreSQL database
by Amit Gupta 08 Jun '07

08 Jun '07

Hi, I am Amit Gupta from New Delhi using koha-2.2.9 on CentOS operating system with MySQL database. I want to know is there any koha version is available with PostgreSQL database. Thanks & Regard Amit Gupta Software Trainee Engineer +91-9891559754 IndServe Infotech Pvt. Ltd. Malviya Nagar New Delhi-110017 India

2 1

please unsubscribe me from the list
by Bernadette Cassidy 08 Jun '07

08 Jun '07

please unsubscribe me from the list. Bernadette Cassidy Information and Design Team Manager Allan Bean Centre Library Private Bag 4708 Christchurch

3 2

Reserves problem
by Jethro Carr 08 Jun '07

08 Jun '07

hi all, I have a problem with a Koha 2.2.8 - when I log into the opac-user.pl page, I get an internal server error. When I looked into the error log, I found the following: HTML::Template->output() : fatal error in loop output : HTML::Template::param() : attempt to set parameter 'reserves' with an array ref - parameter is not a TMPL_LOOP! at /usr/lib/perl5/site_perl/ 5.8.8/HTML/Template.pm line 3069, referer: http://xxxxx:8000/cgi-bin/ koha/opac-user.pl [Wed May 30 22:35:44 2007] [error] [client XXX.XXX.XXX.XXX] at /usr/ local/koha/opac/cgi-bin/opac-user.pl line 160, referer: http://xxxxx: 8000/cgi-bin/koha/opac-user.pl [Wed May 30 22:35:44 2007] [error] [client XXX.XXX.XXX.XXX] Premature end of script headers: opac-user.pl, referer: http://xxxxx:8000/cgi- bin/koha/opac-user.pl When I looked into the /usr/local/koha/opac/opac-user.pl file, I found I can prevent the errors if I comment out line 123. This then allows me to logon, but not view any reserves for the user. 123 #$template->param(RESERVES => $reserves); Anyone come across this problem, or have any suggestions for me? It appears to be a software bug in Koha, but if that was the case, I would have expected other people to have found it as well.... Koha is installed on a CentOS/RHEL 5 server. thanks, -- Jethro Carr

5 15

Versions of Koha and the current users
by Srinivas 07 Jun '07

07 Jun '07

Dear Sir, I join this group today,I want to know all versions of Koha since from begining with releasing date and approximate no of users (if  there is any list available it would be better)can anybody suggest me where will i get this information.with worm regards,srinivas

2 1

News of koha 3.0 and poll [important]
by MJ Ray 07 Jun '07

07 Jun '07

This is a translation of the email of Wed, 21 Mar 2007 11:25:44 +0100 from paul POULAIN to koha-Infos. The original is at http://ob.paulpoulain.com/pipermail/infos/Week-of-Mon-20070319/002112.html if you want to spot my mistranslations. *I would like to hear global-list views on the 1 / 2 / 3 survey below.* So, the message from paul POULAIN: Hello, As usual, I'm going to give you some news of Koha 3.0. *The second part of this email is extremely important for the users among you.* Progress ======== * Joshua (the release manage for v3.0) and his company LibLibe have started tests on this version. He's found some bugs, as expected, but finds that it's in an encouraging shape. The installer has been developed by Henri-Damien as his construction job: once the sysadmin installation is done, the initial configuration (language, MARC type, catalogue tables, ...) are set through a web interface. It's very practical and more than that, it can be extended easily. We can therefore give "public library" example settings, a "society trust" example, that can be installed in a few clicks. The hosting platform for koha development (savannah.gnu.org) had a very large problem at the start of the month. In summary, multiple disks broke simultaneously. It required three days to bring the platform back up. But more annoying, it's lost two days of work in the meantime. Everyone has had to commit their work of those two days anew (this concerned LibLime more than anyone in fact, but was within 36hours of causing me problems...) In short, a good week of loss, lots of energy and stress. Continuing work (and the survey) =============== Joshua (and it's his role as release manager) would like to improve three things before releasing the version: 1- fix the bugs. No-one can dispute the necessity of that. 2- Finish the code cleanup. Antoine, who worked for me for four months on this, didn't finish 100% of the work. That won't change anything much for the user, but, in the long term, it's important: it makes for a more stable software, easier to develop and perhaps also more attractive for other contributors. And then 90% of the work is already done, with 10% to do. 3- Revise all the templates to make something very polished. He proposes to use YUI (Yahoo User Interface), some components "freed" by Yahoo that we can therefore integrate. Graphically, that will give something like http://kados.org/stuff/yui_borrowers.png and http://kados.org/stuff/moremember.png - pretty, isn't it? There is a problem in doing all that: the time that it takes. Joshua doesn't know enough to estimate that for the moment and me neither. But I'm certain that it won't take days or weeks, but months. Now, some among you are waiting for Koha 3.0 with barely-contained impatience. As I've always promised to put the users first, I ask your opinion: 1- Argh! We must release Koha 3.0 as soon as possible. The code clean-up concerns you developers alone, so do it afterwards. And the improvement of user interface can wait too. But I need 3.0's features now! 2- Damn! Bad news. But good, we're working with 2.2 well enough and we can wait 3 months more. But not more than 3 months, even so. 3- Pah! I'm very happy with Koha 2.2. Koha 3.0 can take another 6 months to arrive and I won't be unhappy. You can just reply 1 / 2 / 3, but you can also say more. It's essential that you reply, as many as possible, so I will know in which direction the francophone community points and so communicate it to Joshua (who reads us otherwise, even we must translate because he doesn't speak French ;-) ). I say that the argument "there's bug XXX in Koha 2.2, so I want koha 3.0" isn't good - if there's a bug in 2.2, we'll fix it in 2.2.x! PS: to reassure Pascale Nalon, who's done the translation to VF: this shouldn't impact the translation, or very marginally. Translatedly, -- MJ Ray - see/vidu http://mjr.towers.org.uk/email.html Webmaster/web developer, statistician, sysadmin, online shop maker, developer of koha, debian, gobo, gnustep, various mail and web s/w. Workers co-op @ Weston-super-Mare, Somerset http://www.ttllp.co.uk/

8 7

problem in getting the page at client side.
by rajeesh U 07 Jun '07

07 Jun '07

hi this mail is regarding a problem in getting the page at the client side. from server (where i installed koha) i am getting all the pages correctly. But from any other machine i was unable to connect to koha. this koha is installed on a linux machine.please give me the steps to configure barcode generator. thanks and regards rajeesh. --------------------------------- Get the free Yahoo! toolbar and rest assured with the added security of spyware protection.

1 0

OPAC username and password
by Rick Welykochy 07 Jun '07

07 Jun '07

Hello to all list members, The Intranet area of the Koha website has username + password protection for authentication and authorisation. Is the same available for the OPAC, thereby rendering the P in OPAC to "Private" instead of "Public"? I would think that this would be a common and widespread requirement for the OPAC. For example, a private collection has been put online at a dedicated remote hosting service but the content should not be publicly accessible. One option of course is to use htpasswd and a config section in Apache to restrict access to the OPAC. But this would entail maintaining two access lists: one in a text file for htpasswd and another in the Koha database. We require one single authentication and authorisation scheme, not several. Can password access for the OPAC simply be "turned on"? If not, would I have to copy the existing password/cookie functionality as found in the intranet scripts into the OPAC scripts? cheers rickw -- _________________________________ Rick Welykochy || Praxis Services If we don't succeed, we run the risk of failure. -- Bill Clinton, President

2 2