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

aqbooksellers.pl missing?
by Roger Buck 18 Apr '02

18 Apr '02

There's a link to /cgi-bin/koha/admin/aqbooksellers.pl from /admin/index.html but the aqbooksellers script does not exist in CVS.... yet... ever... never? :) R.

2 2

CVS: koha/C4 Koha.pm,1.2,1.3
by Pat Eyler 17 Apr '02

17 Apr '02

Update of /cvsroot/koha/koha/C4 In directory usw-pr-cvs1:/tmp/cvs-serv16606 Modified Files: Koha.pm Log Message: starting to move ethnicity stuff out of programs and into modules Index: Koha.pm =================================================================== RCS file: /cvsroot/koha/koha/C4/Koha.pm,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -r1.2 -r1.3 *** Koha.pm 15 Apr 2002 16:15:38 -0000 1.2 --- Koha.pm 17 Apr 2002 21:35:53 -0000 1.3 *************** *** 10,17 **** @ISA = qw(Exporter); @EXPORT = qw(&slashifyDate ! &fixEthnicity); use vars qw(); sub slashifyDate { --- 10,19 ---- @ISA = qw(Exporter); @EXPORT = qw(&slashifyDate ! &fixEthnicity ! $DEBUG); use vars qw(); + my $DEBUG = 0; sub slashifyDate {

1 0

CVS: koha installer.pl,NONE,1.1
by Chris Cormack 17 Apr '02

17 Apr '02

Update of /cvsroot/koha/koha In directory usw-pr-cvs1:/tmp/cvs-serv24982 Added Files: installer.pl Log Message: Submitting on behalf of Nicholas First cut (not functional yet) of an installer script --- NEW FILE --- #!perl print "**********************************\n"; print "* Welcome to the Koha Installer *\n"; print "**********************************\n"; print "\n\n\n"; print "This installer will prompt you with a series of questions.\n"; print "It assumes you (or your system administrator) has installed: \n"; print " * Apache (http://www.apache.org) \n"; print " * Perl (http://www.perl.org) \n \n"; print "and one of the following database applications:"; print " * MySql (http://www.mysql.org) \n\n"; print "on some type of Unix or Unix-like operating system \n"; print "\n\n"; print "Is Apache, Perl, and a database from the list above installed on this system?\n"; print "\n"; $answer = chomp $_; if ($answer eq "Y") { print "Great! \n"; }; if ($answer eq "N") { print "You will need to setup database space for your application. \n"; print "The installer currently does not support an automated setup with this database.\n"; print "Please be sure to read the documentation."; }; print "I need to unpack the Koha TarFile -- where is it? "; $answer = chomp $_; system("tar -x $answer"); #unpack fill out #test for Perl and Apache? print "Are you using MySql?[Y/N]: "; $answer = chomp $_; if ($answer eq "Y") { system("mysqladmin -uroot -ppassword create $KohaDBNAME "); system("mysql -u$root -p$password "); #need to get to mysql prompt HOW DO I DO THIS? system("grant all privileges on Koha.* to koha@localhost identified by 'kohapassword'; "); }; if ($answer eq "N") { print "You will need to setup database space for your application. \n"; print "The installer currently does not support an automated setup with this database.\n"; }; print "\n"; system ("perl updatedatabase -I /pathtoC4 "); #KOHA conf print "You will need to add the following to the Koha configuration file\n"; print "database=Koha\n"; print "hostname=localhost\n"; print "user=Koha\n"; print "pass=$password\n"; print "includes=/usr/local/www/koha/htdocs/includes\n"; #SETUP opac # <VirtualHost opac.your.site> # ServerAdmin webmaster(a)your.site # DocumentRoot /usr/local/www/opac/htdocs # ServerName opac.your.site # ErrorLog logs/opac-error_log # TransferLog logs/opac-access_log # </VirtualHost> ###RESTART APACHE system('/etc/rc.d/init.d/httpd restart');

1 0

Re: Koha Work
by paul POULAIN 17 Apr '02

17 Apr '02

Nicholas Rosasco wrote: >Paul -- > >You've been fairly active on the Koha list, and I'm doing a kind of survey >as Chris and I are getting concerned about the problems that have popped up >in re releasing a next version. > >What features do you consider highest priority for Koha? > From a FUNCTIONALITY point of vue : MARC, MARC, and MARC. and, also, MARC ;-) I consider very important thesaurus too. It's, IMHO something really missing and that causes errors in datas that user enter. From a technical point of vue : I think what should be decided soon is what tool we should use to separate presentation code and perl code. We spoke a little about perl template module, then we spoke about XML-XSLT. I think MARC is a HUGE thing. So, we can't decide to use XML-XSLT immediatly. That would be 2 BIG projects at the same time, and we have not enough strength. Should we decide to use perl-template for a moment ? Maybe. It's easier to use, and I know how they work. It's not the case for XML-XSLT... >What features are you currently working on? > None. In a week or 2, I'll be back on koha. I will work on MARC compliance, and on thesaurus. If we decide to wait for XML-XSLT AFTER the MARC release, I will translate koha in french with the tool presently working... >How extensive are they? What is your target for getting them done? > I want the MARC version ready to install in french for september. >What background (if any) do you have with the library specific (MARC, >Z39.50) items currently under consideration? > Don't understand the question... >The draft version short term plan is for a real/soon/now release, which will >become the "stable" and be turned over to a couple, with a new version being >"opened" as the devel in CVS -- this will start with the stuff Katipo is >working on for a number of clients, become a stable(probably 1.2.0), then >the MARC changes will start to go in with 1.3.0. Any comments, suggestions? > I agree for a really short term stable version. The current one is really out of date. I can give a help if you want for the sample DB (in May, I repeat again) what will be on the katipo stuff ? Is it necessary to build a 1.2 AND a 1.3 version ? I thought the MARC import/export was well advanced, and we could assume a progressive translation from the non-MARC DB/soft to the MARC DB/soft ? >The way documenting -- both support, and code -- is handled is due for an >overhaul as well -- any thoughts? > Not sure to understand well this sentence... >Sorry if this sounds like an inquisition, but Chris and I are trying to get >a handle on the who/what/where, etc. > No, what I think is that we must be more aware about who/what/where... So, I'm happy to answer ;-) Last thing, it should be important for me to have a uptodate view of who is really working on koha. And who is who too. I'm quite new on this project, so I don't understand everybody history and experience. (who is from katipo, who is not, who already use koha in a library,...) >Thanks > De rien (in french :-) ) -- Paul

1 0

CVS: koha/acqui.simple bulkmarcimport.pl,1.1,1.2
by Steve Tonnesen 16 Apr '02

16 Apr '02

Update of /cvsroot/koha/koha/acqui.simple In directory usw-pr-cvs1:/tmp/cvs-serv20381 Modified Files: bulkmarcimport.pl Log Message: Fixed typo Index: bulkmarcimport.pl =================================================================== RCS file: /cvsroot/koha/koha/acqui.simple/bulkmarcimport.pl,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -r1.1 -r1.2 *** bulkmarcimport.pl 16 Apr 2002 17:37:19 -0000 1.1 --- bulkmarcimport.pl 16 Apr 2002 18:00:39 -0000 1.2 *************** *** 12,18 **** ! $filename=$ARGV[0]; ! unless ($filename) { print "USAGE: ./bulkmarcimport.pl filename\n"; exit; --- 12,18 ---- ! $file=$ARGV[0]; ! unless ($file) { print "USAGE: ./bulkmarcimport.pl filename\n"; exit;

1 0

CVS: koha/acqui.simple bulkmarcimport.pl,1.2,1.3
by Steve Tonnesen 16 Apr '02

16 Apr '02

Update of /cvsroot/koha/koha/acqui.simple In directory usw-pr-cvs1:/tmp/cvs-serv26816 Modified Files: bulkmarcimport.pl Log Message: Added some comments detailing how MARC fields are mapped to Koha data Index: bulkmarcimport.pl =================================================================== RCS file: /cvsroot/koha/koha/acqui.simple/bulkmarcimport.pl,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -r1.2 -r1.3 *** bulkmarcimport.pl 16 Apr 2002 18:00:39 -0000 1.2 --- bulkmarcimport.pl 16 Apr 2002 19:49:15 -0000 1.3 *************** *** 99,108 **** close F; $splitchar=chr(29); RECORD: foreach $record (split(/$splitchar/, $data)) { - my $marctext="<table border=0 cellspacing=0>\n"; - $marctext.="<tr><th colspan=3 bgcolor=black><font color=white>MARC RECORD</font></th></tr>\n"; $leader=substr($record,0,24); - $marctext.="<tr><td>Leader:</td><td colspan=2>$leader</td></tr>\n"; print "\n\n---------------------------------------------------------------------------\n"; print "Leader: $leader\n"; --- 99,110 ---- close F; $splitchar=chr(29); + + + # Cycle through all of the records in the file + + RECORD: foreach $record (split(/$splitchar/, $data)) { $leader=substr($record,0,24); print "\n\n---------------------------------------------------------------------------\n"; print "Leader: $leader\n"; *************** *** 116,121 **** foreach $field (split(/$splitchar2/, $record)) { my %field; - ($color eq $lc1) ? ($color=$lc2) : ($color=$lc1); unless ($directory) { $directory=$field; my $itemcounter=1; --- 118,123 ---- foreach $field (split(/$splitchar2/, $record)) { my %field; unless ($directory) { + # Parse the MARC directory and store the cotents in the %tag hash $directory=$field; my $itemcounter=1; *************** *** 135,139 **** $tagcounter++; $field{'tag'}=$tag; - $marctext.="<tr><td bgcolor=$color valign=top>$tagtext{$tag}</td><td bgcolor=$color valign=top>$tag</td>"; printf "%4s %-40s ",$tag, $tagtext{$tag}; $splitchar3=chr(31); --- 137,140 ---- *************** *** 143,159 **** my $firstline=1; if ($#subfields==0) { - $marctext.="<td bgcolor=$color valign=top>$indicator</td></tr>"; print "$indicator\n"; } else { print "\n"; my %subfields; - $marctext.="<td bgcolor=$color valign=top><table border=0 cellspacing=0>\n"; - my $color2=$color; for ($i=1; $i<=$#subfields; $i++) { - ($color2 eq $lc1) ? ($color2=$lc2) : ($color2=$lc1); my $text=$subfields[$i]; my $subfieldcode=substr($text,0,1); my $subfield=substr($text,1); - $marctext.="<tr><td colour=$color2><table border=0 cellpadding=0 cellspacing=0><tr><td>$subfieldcode </td></tr></table></td><td colour=$color2>$subfield</td></tr>\n"; print " $subfieldcode $subfield\n"; if ($subfields{$subfieldcode}) { --- 144,155 ---- *************** *** 170,174 **** } } - $marctext.="</table></td></tr>\n"; $field{'subfields'}=\%subfields; } --- 166,169 ---- *************** *** 187,191 **** push (@record, \%field); } - $marctext.="</table>\n"; $rec=\@record; $counter++; --- 182,185 ---- *************** *** 193,197 **** my $marc=$record; foreach $field (sort {$a->{'tag'} cmp $b->{'tag'}} @$rec) { ! #print $field->{'tag'}." ".$field->{'subfields'}->{'a'}."\n"; if ($field->{'tag'} eq '010') { $lccn=$field->{'subfields'}->{'a'}; --- 187,191 ---- my $marc=$record; foreach $field (sort {$a->{'tag'} cmp $b->{'tag'}} @$rec) { ! # LCCN is stored in field 010 a if ($field->{'tag'} eq '010') { $lccn=$field->{'subfields'}->{'a'}; *************** *** 201,204 **** --- 195,199 ---- ($lccn) = (split(/\s+/, $lccn))[0]; } + # LCCN is stored in field 015 a if ($field->{'tag'} eq '015') { $lccn=$field->{'subfields'}->{'a'}; *************** *** 207,210 **** --- 202,206 ---- ($lccn) = (split(/\s+/, $lccn))[0]; } + # ISBN is stored in field 020 a if ($field->{'tag'} eq '020') { $isbn=$field->{'subfields'}->{'a'}; *************** *** 212,215 **** --- 208,212 ---- ($isbn) = (split(/\s+/, $isbn))[0]; } + # ISSN is stored in field 022 a if ($field->{'tag'} eq '022') { $issn=$field->{'subfields'}->{'a'}; *************** *** 217,232 **** ($issn) = (split(/\s+/, $issn))[0]; } if ($field->{'tag'} eq '082') { $dewey=$field->{'subfields'}->{'a'}; - print "DEWEY: $dewey\n"; $dewey=~s/\///g; if (@$dewey) { $dewey=$$dewey[0]; } - #$dewey=~s/\///g; } if ($field->{'tag'} eq '100') { $author=$field->{'subfields'}->{'a'}; } if ($field->{'tag'} eq '245') { $title=$field->{'subfields'}->{'a'}; --- 214,234 ---- ($issn) = (split(/\s+/, $issn))[0]; } + # Dewey number stored in field 082 a + # If there is more than one dewey number (more than one 'a' + # subfield) I just take the first one if ($field->{'tag'} eq '082') { $dewey=$field->{'subfields'}->{'a'}; $dewey=~s/\///g; if (@$dewey) { $dewey=$$dewey[0]; } } + # Author is stored in field 100 a if ($field->{'tag'} eq '100') { $author=$field->{'subfields'}->{'a'}; } + # Title is stored in field 245 a + # Subtitle in field 245 b + # Illustrator in field 245 c if ($field->{'tag'} eq '245') { $title=$field->{'subfields'}->{'a'}; *************** *** 239,242 **** --- 241,249 ---- } } + # Publisher Info in field 260 + # a = place + # b = publisher + # c = publication date + # (also store as copyright date if date starts with a 'c' as in c1995) if ($field->{'tag'} eq '260') { $place=$field->{'subfields'}->{'a'}; *************** *** 263,266 **** --- 270,276 ---- } } + # Physical Dimensions in field 300 + # a = pages + # c = size if ($field->{'tag'} eq '300') { $pages=$field->{'subfields'}->{'a'}; *************** *** 270,273 **** --- 280,284 ---- $size=~s/\s*:$//g; } + # Vol/No in field 362 a if ($field->{'tag'} eq '362') { if ($field->{'subfields'}->{'a'}=~/(\d+).*(\d+)/) { *************** *** 276,279 **** --- 287,292 ---- } } + # Series Title in field 440 a + # Vol/No in field 440 v if ($field->{'tag'} eq '440') { $seriestitle=$field->{'subfields'}->{'a'}; *************** *** 283,290 **** } } if ($field->{'tag'} eq '852') { $barcode=$field->{'subfields'}->{'p'}; push (@barcodes, $barcode); - print "BARCODE: $barcode\n"; my $q_barcode=$dbh->quote($barcode); my $deweyfield=$field->{'subfields'}->{'h'}; --- 296,309 ---- } } + # BARCODES!!! + # 852 p stores barcodes + # 852 h stores dewey field + # 852 9 stores replacement price + # I check for an itemtype identifier in 852h as well... pb or pbk means PBK + # also if $dewey is > 0, then I assign JNF, otherwise JF. + # Note that my libraries are school libraries, so I assume Junior. if ($field->{'tag'} eq '852') { $barcode=$field->{'subfields'}->{'p'}; push (@barcodes, $barcode); my $q_barcode=$dbh->quote($barcode); my $deweyfield=$field->{'subfields'}->{'h'}; *************** *** 300,305 **** $replacementprice=$field->{'subfields'}->{'9'}; - #print "BC: $barcode, $title, $author\n"; } if ($field->{'tag'} eq '700') { my $name=$field->{'subfields'}->{'a'}; --- 319,325 ---- $replacementprice=$field->{'subfields'}->{'9'}; } + # 700 a stores additional authors / illustrator info + # 700 c will contain 'ill' if it's an illustrator if ($field->{'tag'} eq '700') { my $name=$field->{'subfields'}->{'a'}; *************** *** 310,316 **** --- 330,343 ---- } } + # I concatenate all 5XX a entries as notes if ($field->{'tag'} =~/^5/) { $note.="$field->{'subfields'}->{'a'}\n"; } + # 6XX entries are subject entries + # Not sure why I'm skipping 691 tags + # 691 a contains the subject. + # I take subfield a, and append entries from subfield x (general + # subdivision) y (Chronological subdivision) and z (geographic + # subdivision) if ($field->{'tag'} =~/6\d\d/) { (next) if ($field->{'tag'} eq '691');

1 0

[CVS help] how to transmit a modification in a file
by paul POULAIN 16 Apr '02

16 Apr '02

I've just modified index.html, and created 2 (dirty) pictures for the link to /admin/ dir. cvs add for the 2 gif files is done, but how to update index.html ? Newbie at CVS... "cvs import" I think, but what's the syntax ? -- Paul

4 3

Re: Koha Work
by Roger Buck 15 Apr '02

15 Apr '02

Hi Nicholas, I am posting a copy of this to devel list - hope that's OK. Please speak up if you think it's too much "noise" to post this kind of stuff to list. Nicholas Rosasco wrote: [--snip--] > I'm doing a kind of survey > as Chris and I are getting concerned about the problems that have popped up > in re releasing a next version. > > What features do you consider highest priority for Koha? 1. User access via Internet for reservations etc. I think security/privacy issues would become more important! 2. Make installation more friendly, flexible and generic. Koha installation should allow for "public", "member" and "intranet" services without requiring multiple virtual servers. File paths should be configurable though single config file. 3. Better documentation - user and administration manuals required. Bottom line: More documentation and reference information required at every level. 4. Better Internationalisation / Integration (standards) As well as Library specific stuff, I'd like to see support for the most common LDAP schemas for storing user information... but more realistically in short term, at least make sure that whatever is done now for storage in SQL can be easily migrated to LDAP in future ;^) > What features are you currently working on? 1, 2 and 3 above. > How extensive are they? Hmmm... still in information gathering and a proof of concept mode... but being very actively pursued on a daily basis. > What is your target for getting them done? Currently have several test systems operating - We will be going live in three to four weeks (max), no matter how complete/incomplete the changes may be at that time. > What background (if any) do you have with the library specific (MARC, > Z39.50) items currently under consideration? None. > The draft version short term plan is for a real/soon/now release, which will > become the "stable" and be turned over to a couple, with a new version being > "opened" as the devel in CVS -- this will start with the stuff Katipo is > working on for a number of clients, become a stable(probably 1.2.0), then > the MARC changes will start to go in with 1.3.0. Any comments, suggestions? > The way documenting -- both support, and code -- is handled is due for an > overhaul as well -- any thoughts? Yes - I think the next release should be upgrade release only - with no surprises for existing uers. Proposal for new CVS provides an opprtunity to re-organise - especially to support more flexible installation options... and hopefuly more participants. I will see if I can formalise something more specific about that and post suggestions to the list (in next few days). > > Sorry if this sounds like an inquisition, but Chris and I are trying to get > a handle on the who/what/where, etc. You're most welcome :-) R.

2 1

RE: [Koha] A basic question
by Nicholas Rosasco 15 Apr '02

15 Apr '02

" It's a BIG problem in open-source : every modification can be done. but some modifications causes my version to be no more upgrabale with the "standard" one, so any evolutions in the "standard" version must be checked and corrected to fit my own modifications. That's why I think we must have only 1 version, even if it causes some dis-agreements (not sure of this word in english ?) In the long time, it REALLY BETTER. " I concur with Paul -- and I note that a good number of the items earlier (barcode sizes, etc) can actually be handled through modularization, tc. -- allowing us to maintain the "one version" of koha, while allowing the flexibility people seem to want. This is one of the things the emails I intend to get out to you all individually will address, at least in part. Nick pulling his notes & thoughts together.

1 0

CVS: koha/C4 Koha.pm,1.1,1.2
by Pat Eyler 15 Apr '02

15 Apr '02

Update of /cvsroot/koha/koha/C4 In directory usw-pr-cvs1:/tmp/cvs-serv13719 Modified Files: Koha.pm Log Message: moved ethnicity fixing out of moremember.pl into a function, eventually to replace with a more configurable version (non-NZ specific) Index: Koha.pm =================================================================== RCS file: /cvsroot/koha/koha/C4/Koha.pm,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -r1.1 -r1.2 *** Koha.pm 8 Apr 2002 23:44:43 -0000 1.1 --- Koha.pm 15 Apr 2002 16:15:38 -0000 1.2 *************** *** 9,13 **** @ISA = qw(Exporter); ! @EXPORT = qw(&slashifyDate); use vars qw(); --- 9,14 ---- @ISA = qw(Exporter); ! @EXPORT = qw(&slashifyDate ! &fixEthnicity); use vars qw(); *************** *** 21,24 **** --- 22,40 ---- } + sub fixEthnicity($) { # a temporary fix ethnicity, it should really be handled + # in Search.pm or the DB ... + + my $ethnicity = shift; + if ($ethnicity eq 'maori') { + $ethnicity = 'Maori'; + } elsif ($ethnicity eq 'european') { + $ethnicity = 'European/Pakeha'; + } elsif ($ethnicity eq 'pi') { + $ethnicity = 'Pacific Islander' + } elsif ($ehtnicity eq 'asian') { + $ethnicity = 'Asian'; + } + return $ethnicity; + }

1 0