- Koha - lists.katipo.co.nz

some thoughts about cataloguing and acquisitions [important]
by paul POULAIN 16 Jan '03

16 Jan '03

I want here share some ideas for the 2.0 version of koha, around cataloguing and acquisition. Most ILS, in France at least, separate cataloguing and acquisition. * *cataloguing* is often done through a CDROM (from the BNF for example) : the librarian download from the cd the biblio in MARC format, which is included in it's ILS. The cataloguing refers only to BIBLIO notice, not items and how they arrive in the library. * *acquisition* referers to how "books" arrive in the library (and includes items) In koha, at the moment, there is no distinction between those 2 topics : look at koha main page, there is only a "acquisition" picture, which includes cataloguing and acquisition in fact. I want to begin de debate to see if it's a good idea to distinct acquisition and cataloguing in 2.0. It would mean : * in mainpage => 2 links for cataloguing and acquisition * acquisition => works almost like the normal acquisition system of the old version : search for a supplier, enter a little part of the biblio... * cataloguing => - if marc is selected : works like the acqui.simple in 1.3.3 (see demo.koha-fr.org) - if marc is not selected : works like the 2nd part of the normal acquisition in 1.2 : enter the biblio details. this supposes a new parameter in the systempreferences table. One other idea : it would enable a "suggestion" feature in the opac : readers could suggest books to add, which could be stored in the "acquisition" part of koha, in a "to validate" status. From a developper point of vue, this means : * duplicating biblio table to acqui_biblio table * split normal acquisition in 2 parts * change normal acquisition to write acqui_biblio table and not biblio * create some screens to link the acquisition part and the cataloguing one. some work, but not too much i think (if someone wants to fund it, send me a mail :-) ). Of course, if you create a book in the acquisition part, all what you typed would be auto-copied when entering the cataloguing part :-) So there should not be too much more work for the librarian/cataloguer (but a few, anyway : this would add screens, so, more clics) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Re: [Koha-devel] MySQL and foreign keys (fwd)
by Pat Eyler 16 Jan '03

16 Jan '03

might as well put this here too ... just to satisfy the folks who wondered about Larry's question. -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 ---------- Forwarded message ---------- Date: Wed, 15 Jan 2003 19:27:32 -0500 (EST) From: Pat Eyler <pate(a)eylerfamily.org> To: Larry Currie <lcurrie(a)CalAcademy.Org> Cc: koha-devel(a)lists.sourceforge.net Subject: Re: [Koha-devel] MySQL and foreign keys well, there are a couple of ways to respond. First, MySQL does have foreign keys: http://www.mysql.com/doc/en/ANSI_diff_Foreign_Keys.html (There area also some specific dis-advantages to using foreign key enforcement listed near the bottom of the above document.) Secondly, the question of whether of not MySQL is ACID capable has little to do with its suitiblity for our purposes. MySQL is frequently used by serious websites to do serious business (NASA among them), I think that properly used, MySQL is a completely valid choice for building an ILS. -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 On Wed, 15 Jan 2003, Larry Currie wrote: > Last night I attended a PerlMongers group meeting here in Oakland, CA > and one of the presenters at the meeting asserted that MySQL could not > claim to be a completely relational database because it doesn't let you > define foreign keys. As a result, he feels that MySQL fails the ACID > test (atomicity, consistency, referential integrity, and durability), > and he advised people to avoid using it in Perl applications and instead > use Postgres or some other relational database with more stability. He > cited an example where you might have a one-to-one relationship between > primary key values in two tables and if you deleted a value from one of > the tables, MySQL would leave that value in the other table as dangling > data without warning you to take care of it and as a result really mess > up your database. > > Can anyone on the Koha list comment on this assertion and what the > consequences might be for Koha? > > Larry Currie > > -- > Lawrence W. Currie > User Services Librarian > California Academy of Sciences > Golden Gate Park > San Francisco, CA 94118 > lcurrie(a)calacademy.org > (415) 750-7108 > (415) 750-7106 fax > http://www.calacademy.org/research/library/ > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: A Thawte Code Signing Certificate > is essential in establishing user confidence by providing assurance of > authenticity and code integrity. Download our Free Code Signing guide: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/koha-devel > ------------------------------------------------------- This SF.NET email is sponsored by: A Thawte Code Signing Certificate is essential in establishing user confidence by providing assurance of authenticity and code integrity. Download our Free Code Signing guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel

1 0

Introduction
by Bernadette Cassidy 15 Jan '03

15 Jan '03

Kia ora everyone, I've recently joined the list and this is my brief introduction. I am the Library & Learning Coordinator at the Allan Bean Centre for Research and Learning in Rehabilitation at Burwood Hospital, Christchurch, New Zealand. The library is primarily for patients, their families and carers as well as staff and aims to provide good quality information resources for people recovering from serious injury or illness. At present we do not have a library management system or catalogue for our users. I'm looking very closely at Koha as a possible solution but we will need to look at some of the specifications more closely. One of which is having a Linux machine set up - and the minimum specification needed for setup etc. I would be interested to hear from others in a similar situation for advice and suggestions etc. Kind regards, Bernadette Cassidy Allan Bean Centre Coordinator Burwood Academy of Independent Living Burwood Hospital Christchurch Email: bernadettec(a)burwood.org.nz Tel: 03 383 9484 Fax: 03 383 9582

1 0

Re: [Koha] Re: MARC support
by Joshua Brindle 15 Jan '03

15 Jan '03

What is the timeline for the authentication stuff? I've gone through some of the authentication stuff and it seems deeply embedded (ie: not modular) to do this right the authentication should be completely abstracted from the app and allow a simple drop in authentication replacement. If this were the case i'd happilly write the ldap stuff. Are there plans to modularize all this stuff? Thanks.... Joshua Brindle UNIX Administrator Southern Nazarene University >>> paul POULAIN <paul.poulain(a)free.fr> 01/15/03 03:27AM >>> Joshua Brindle a écrit: Wow!, that would be the perfect thing to be in the installation docs :\ In fact, it's the perfect thing to test during the installation process. I'll fix this for 1.9.0 seriously, i didn't even think to check CPAN for the module, i assumed it was part of Koha. Thanks a lot... Also, do you guys think that koha can handle my library? 90000 books, maybe a dozen librarians and a couple thousand patrons? I'd have to make it authenticate to LDAP rather that mysql but that should be trivial... Thanks again Without any problems (if you don't plan to install it on a Pentium 100 server :-) ) About LDAP : others also ask for this. the management team plans to : * release 2.0 with authentification as it is, through mysql tables. * add differents auth methods in the 2.1 or 2.2 version -- Paul POULAINConsultant indépendant en logiciels libresresponsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

Re: MARC support
by Joshua Brindle 15 Jan '03

15 Jan '03

Wow!, that would be the perfect thing to be in the installation docs :\ seriously, i didn't even think to check CPAN for the module, i assumed it was part of Koha. Thanks a lot... Also, do you guys think that koha can handle my library? 90000 books, maybe a dozen librarians and a couple thousand patrons? I'd have to make it authenticate to LDAP rather that mysql but that should be trivial... Thanks again Joshua Brindle UNIX Administrator Southern Nazarene University >>> news-misc(a)ada.dhs.org 01/13/03 09:47PM >>> Hi, In article , Joshua Brindle wrote: >Can't locate MARC/Record.pm in @INC (@INC contains: >/usr/lib/perl5/5.6.1/i686-linux /usr/lib/perl5/5.6.1 >/usr/lib/perl5/site_perl/5.6.1/i686-linux /usr/lib/perl5/site_perl/5.6.1 >/usr/lib/perl5/site_perl .) at >/usr/lib/perl5/site_perl/5.6.1/i686-linux/C4/Biblio.pm line 171. > >this happens in my apache logs and also on the console, i've searched >both 1.3.3 and a cvs checkout from today and neither have that file (or >even a MARC directory). Has this been commited to cvs? Is something >weird going on or am i just screwing something up :) You need to install the MARC::Record package. You should be able to do this by just typing perl -MCPAN -e 'install MARC::Record' -- Ambrose Li http://ada.dhs.org/~acli/cmcc/ http://www.cccgt.org/ DRM is theft - We are the stakeholders _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

2 1

introduction
by Jeroen Baten 15 Jan '03

15 Jan '03

Hello, I recently joined the list and this is my small introduction: I run a small company focused on Linux and Open Source software. I evaluate OSS programs regularly and now find it's time to start supporting Koha in the Netherlands. I have started the translation proces (1.3.3.) but have some questions left: -where do I sent the translations to? -Can you include me on your page with world-wide support organisations? -is it not easier to just make a language file to be included in all programs. This also makes to software better maintainable. (If this has been said a zilion times I am sorry). kind regards, -- Jeroen Baten | EMAIL : JBATEN(a)I2RS.NL ____ _ __ | web : www.i2rs.nl | )|_)(_ | tel : +31 (0)30 221 00 11 _|_/_| \__) | fax : +31 (0)30 220 31 91 Kometenlaan 26, 3721 JT, Bilthoven, the Netherlands

2 1

Re: Antw: Re: [Koha] Problem with Koha-1.3.3
by paul POULAIN 15 Jan '03

15 Jan '03

It seems this mail contains nothing. What did you mean ? Arnold Graeub a écrit: >Verkehrs-Club der Schweiz VCS >Arnold Gräub >Leiter EDV/Informatik >Tel. 062 956 56 45 >mailto:arnold.graeub@verkehrsclub.ch >Internet: www.verkehrsclub.ch > > > >>>>paul POULAIN <paul.poulain(a)free.fr> 09.01.03 15:30:02 >>> >>>> >>>> >Arnold Graeub a écrit: > > > >>Hi, >>I have installed the new Version Koha-1.3.3. The script mainpage.pl requires Template.pm, so I downloaded HTML::Template from CPAN. When running mainpage.pl, the following error messge occurs, koha-error.log: >> >>HTML::Template->new() : Cannot open included file /default/en/intranet-main.tmpl : file not found. at /usr/lib/perl5/site_perl/5.8.0/HTML/Template.pm line 1580 >> HTML::Template::_init_template('HTML::Template=HASH(0x81c4434)') called at /usr/lib/perl5/site_perl/5.8.0/HTML/Template.pm line 1177 >> HTML::Template::_init('HTML::Template=HASH(0x81c4434)') called at /usr/lib/perl5/site_perl/5.8.0/HTML/Template.pm line 1071 >> HTML::Template::new('HTML::Template','filename','/default/en/intranet-main.tmpl','die_on_bad_params',0,'global_vars',1,'path','ARRAY(0x857a180)',...) called at /usr/lib/perl5/site_perl/C4/Output.pm line 92 >> C4::Output::gettemplate('intranet-main.tmpl','intranet') called at /usr/lib/perl5/site_perl/C4/Auth.pm line 105 >> C4::Auth::get_template_and_user('HASH(0x857a85c)') called at /usr/local/httpd/koha/intranet/cgi-bin/mainpage.pl line 11 >>[Thu Jan 9 09:53:55 2003] [error] [client 194.191.145.126] Premature end of script headers: /usr/local/httpd/koha/intranet/cgi-bin/mainpage.pl >> >>Where is the path to /default/en/intranet-main.tmpl defined ? >> >Strange indeed... >It means the path_to_template has not been set. > >did you install koha from scratch or upgrade from a previous 1.3.x version ? >It means that the path_to_template is not defined. >To define it go to /etc/koha.conf and look at the line : >intrahtdocs=/home/httpd/html/intra_133/htdocs/intranet-tmpl >(that's mine). >where "/home/httpd/htlm/intra_133" is the root directory you've entered >at 1st stage of installer. > >Let us know if this helps. > > > -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

MARC support
by Joshua Brindle 14 Jan '03

14 Jan '03

ok, i've read some list archives about marc support and it seems that it should be here, however when i try to import or export marc records i get this error Can't locate MARC/Record.pm in @INC (@INC contains: /usr/lib/perl5/5.6.1/i686-linux /usr/lib/perl5/5.6.1 /usr/lib/perl5/site_perl/5.6.1/i686-linux /usr/lib/perl5/site_perl/5.6.1 /usr/lib/perl5/site_perl .) at /usr/lib/perl5/site_perl/5.6.1/i686-linux/C4/Biblio.pm line 171. this happens in my apache logs and also on the console, i've searched both 1.3.3 and a cvs checkout from today and neither have that file (or even a MARC directory). Has this been commited to cvs? Is something weird going on or am i just screwing something up :) I need to be able to import MARC very badly, I work at a university and we have about 90000 records. I've had some other problems, but have been able to work around them, just thought i'd mention them incase they are unknown by default Output.pm didn't know where intranet-tmpl was (and was failing due to no template file), so i put intrahtdocs=/home/httpd/koha/htdocs/intranet-tmpl in the koha.conf, this wasn't mentioned anywhere in the documentation. i also don't see why intranet and opac should be on different vhosts, i'd rather have them on the same vhost and just use permissions to determine who can access what. We also use novell, and we'd like to use LDAP to authenticate users, and also fetch patron information, ie: first, last name, card number, etc. How hard is this? I've looked at C4/Auth.pm and it seems like the place to do it, but it doesn't seem modular enough to just drop in another without disturbing other things, is this something that has been done, or someone knows how to do? If i have to write the stuff myself (which isn't a big deal) i'll certainly send it upstream.. Thanks for all your help.............. Joshua Brindle UNIX Administrator Southern Nazarene University

3 2

Popularity?
by Daniel Guermeur 12 Jan '03

12 Jan '03

Hello, I would like to know if Koha is a system that is widely adopted in schools. Is there some information about the current users? Thanks. Daniel

1 0

Antw: Re: [Koha] Problem with Koha-1.3.3
by Arnold Graeub 09 Jan '03

09 Jan '03

Verkehrs-Club der Schweiz VCS Arnold Gräub Leiter EDV/Informatik Tel. 062 956 56 45 mailto:arnold.graeub@verkehrsclub.ch Internet: www.verkehrsclub.ch >>> paul POULAIN <paul.poulain(a)free.fr> 09.01.03 15:30:02 >>> Arnold Graeub a écrit: >Hi, >I have installed the new Version Koha-1.3.3. The script mainpage.pl requires Template.pm, so I downloaded HTML::Template from CPAN. When running mainpage.pl, the following error messge occurs, koha-error.log: > >HTML::Template->new() : Cannot open included file /default/en/intranet-main.tmpl : file not found. at /usr/lib/perl5/site_perl/5.8.0/HTML/Template.pm line 1580 > HTML::Template::_init_template('HTML::Template=HASH(0x81c4434)') called at /usr/lib/perl5/site_perl/5.8.0/HTML/Template.pm line 1177 > HTML::Template::_init('HTML::Template=HASH(0x81c4434)') called at /usr/lib/perl5/site_perl/5.8.0/HTML/Template.pm line 1071 > HTML::Template::new('HTML::Template','filename','/default/en/intranet-main.tmpl','die_on_bad_params',0,'global_vars',1,'path','ARRAY(0x857a180)',...) called at /usr/lib/perl5/site_perl/C4/Output.pm line 92 > C4::Output::gettemplate('intranet-main.tmpl','intranet') called at /usr/lib/perl5/site_perl/C4/Auth.pm line 105 > C4::Auth::get_template_and_user('HASH(0x857a85c)') called at /usr/local/httpd/koha/intranet/cgi-bin/mainpage.pl line 11 >[Thu Jan 9 09:53:55 2003] [error] [client 194.191.145.126] Premature end of script headers: /usr/local/httpd/koha/intranet/cgi-bin/mainpage.pl > >Where is the path to /default/en/intranet-main.tmpl defined ? > > Strange indeed... It means the path_to_template has not been set. did you install koha from scratch or upgrade from a previous 1.3.x version ? It means that the path_to_template is not defined. To define it go to /etc/koha.conf and look at the line : intrahtdocs=/home/httpd/html/intra_133/htdocs/intranet-tmpl (that's mine). where "/home/httpd/htlm/intra_133" is the root directory you've entered at 1st stage of installer. Let us know if this helps. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org) Bonsoir Paul, Merci beaucoup de ton assistance! The path intrahtdocs was not set. The next problem is the following, koha-error.log: DBD::mysql::st execute failed: Unknown column 'userid' in 'where clause' at /usr/lib/perl5/site_perl/C4/Auth.pm line 387. DBD::mysql::st fetchrow failed: fetch() without execute() at /usr/lib/perl5/site_perl/C4/Auth.pm line 389. On line 386 in Auth.pm string "my $sth=$dbh->prepare("select borrowernumber from borrowers where userid=?");" In the mysql-tables there is no column "userid" but "usercode". Is this the problem? Merci d'avance Arnold

1 0