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

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

CVS: koha moremember.pl,1.10,1.11
by Pat Eyler 15 Apr '02

15 Apr '02

Update of /cvsroot/koha/koha In directory usw-pr-cvs1:/tmp/cvs-serv14378 Modified Files: moremember.pl Log Message: moved ethnicity fixups into C4::Koha, eventually to be replaced with a better (non-NZ specific) solution. Index: moremember.pl =================================================================== RCS file: /cvsroot/koha/koha/moremember.pl,v retrieving revision 1.10 retrieving revision 1.11 diff -C2 -r1.10 -r1.11 *** moremember.pl 8 Apr 2002 23:44:43 -0000 1.10 --- moremember.pl 15 Apr 2002 16:17:21 -0000 1.11 *************** *** 1,11 **** #!/usr/bin/perl ! #script to do a borrower enquiery/brin up borrower details etc ! #written 20/12/99 by chris(a)katipo.co.nz ! #Displays all the detailas about a borrower ! #needs html removed and to use the C4::Output more, but its tricky ! #last modified 21/1/2000 by chris(a)katipo.co.nz ! #modifiecd 31/1/2001 by chris(a)katipo.co.nz to not allow items on request ! #to be renewed use strict; use C4::Output; --- 1,14 ---- #!/usr/bin/perl ! # script to do a borrower enquiry/bring up borrower details etc ! # Displays all the details about a borrower ! # written 20/12/99 by chris(a)katipo.co.nz ! # last modified 21/1/2000 by chris(a)katipo.co.nz ! # modified 31/1/2001 by chris(a)katipo.co.nz ! # to not allow items on request to be renewed ! # ! # needs html removed and to use the C4::Output more, but its tricky ! # ! use strict; use C4::Output; *************** *** 22,31 **** - # FIXME - # this hash is never assigned, though it is used (as a placeholder?) - # - my %env; - print $input->header; #start the page and read in includes print startpage(); --- 25,30 ---- print $input->header; + #start the page and read in includes print startpage(); *************** *** 38,69 **** $data->{'dateofbirth'} = slashifyDate($data->{'dateofbirth'}); ! # FIXME ! # turn the ethnicity into a function and make it generalizable ! # check these files to see if one convention or the other makes sense ! # boraccount.pl ! # imemberentry.pl ! # jmemberentry.pl ! # mancredit.pl ! # maninvoice.pl ! # member.pl ! # memberentry.pl ! # moremember.pl ! # moremember.pl ! # pay.pl ! # placerequest.pl ! # readingrec.pl ! # ! if ($data->{'ethnicity'} eq 'maori'){ ! $data->{'ethnicity'} = 'Maori'; ! } ! if ($data->{'ethnicity'}eq 'european'){ ! $data->{'ethnicity'} = 'European/Pakeha'; ! } ! if ($data->{'ethnicity'}eq 'pi'){ ! $data->{'ethnicity'} = 'Pacific Islander'; ! } ! if ($data->{'ethnicity'}eq 'asian'){ ! $data->{'ethnicity'} = 'Asian'; ! } print <<printend --- 37,41 ---- $data->{'dateofbirth'} = slashifyDate($data->{'dateofbirth'}); ! $data->{'ethnicity'} = fixEthnicity($data->{'ethnicity'}); print <<printend

1 0

Upcoming emails from Nicholas
by Chris Cormack 15 Apr '02

15 Apr '02

Hi All This is just a bit of a heads up. Ive asked Nick to help me with coordinating Koha work a bit more. Now we have a few ppl actively working on the code, im finding im loosing track of who is working on what, etc. So I think Nick is going to email around, find out what everyones up to, and build some kinda status report, and make some suggestions in how to move forward. A suggestion he has made already, which I think has merit, is creating a development/stable situation. So we have a stable release cvs tree , and bugfixes and tidy ups get added to that. While we work on new features in the development tree. When new features become stable and tested enuff, we shift them into the stable tree and do a new release. Also I feel we need to be doing more regular releases, so that bugfixes are getting out into the public. Any other suggestions gratefully accepted. Oh, an idea ive just had myself, playing with Roger's wiki to work on the install, I think this is a good way to work on collaborative documentation. Perhaps we could put todo list type things up there, that ppl could add/modify to? Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris(a)katipo.co.nz www.katipo.co.nz

4 5

Method of setting path to koha.conf
by Roger Buck 15 Apr '02

15 Apr '02

Noticed that current CVS version of C4/Database.pm includes a hard-coded path to koha.conf. (I think) that would create a problem if a non default path to koha.conf is specified in Output.pm? Should the method of setting path-to-koha.conf be changed? R.

1 0

CVS: koha/acqui addorder.pl,1.2,1.3
by Gynn Lomax 15 Apr '02

15 Apr '02

Update of /cvsroot/koha/koha/acqui In directory usw-pr-cvs1:/tmp/cvs-serv23750/acqui Modified Files: addorder.pl Log Message: Acquisitions::newbiblioitem updated to be usable for new acqui.simple addorder.pl and updatebibitem.pl modified to use new newbiblioitem Index: addorder.pl =================================================================== RCS file: /cvsroot/koha/koha/acqui/addorder.pl,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -r1.2 -r1.3 *** addorder.pl 10 Apr 2002 05:47:07 -0000 1.2 --- addorder.pl 15 Apr 2002 05:33:33 -0000 1.3 *************** *** 48,55 **** if ($existing eq 'no'){ #if it doesnt create it ! $bibnum=newbiblio({ title => $title, ! author =>$author, ! copyright => $copyright }); ! $bibitemnum=newbiblioitem($bibnum,$itemtype,$isbn); newsubtitle($bibnum); modbiblio($bibnum,$title,$author,$copyright,$series); --- 48,57 ---- if ($existing eq 'no'){ #if it doesnt create it ! $bibnum = &newbiblio({ title => $title, ! author =>$author, ! copyright => $copyright }); ! $bibitemnum = &newbiblioitem({ biblionumber => $bibnum, ! itemtype => $itemtype, ! isben => $isbn }); newsubtitle($bibnum); modbiblio($bibnum,$title,$author,$copyright,$series);

1 0