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

record.abs and melm declaration order.
by Henri-Damien LAURENT 31 Oct '06

31 Oct '06

Hi it seems that data indexed in record.abs depends on the order of declaration. Take for instance : melm 600 Subject-heading melm 600$a main-subject and melm 600$a main-subject melm 600 Subject-heading On the one hand, you will NOT be able to query for main-subject But on the other hand, declaring 600$a BEFORE tag 600, you will get data from 600$a when querying on main-subject. I have not read this on documentation. And this seems quite useful to know. Moreover, if you declare melm 600$a main-subject melm 600$a other-identifier the second declaration will be ignored. Hopes that helps. -- Henri-Damien LAURENT

2 1

CGI.pm
by Wojciech Zatorski 28 Oct '06

28 Oct '06

Hello Koha-devel, I have found bugs/feature in module CGI.pm. script: /cgi-bin/koha/acqui.simple/additem.pl Alert about exists of itemcallnumber and options have doubled/tripled selected options! <select name="field_value" tabindex="1" size="1" style="font-family: Courier;"> <option selected="selected" value=""></option> <option value="G">Biblioteka Filologii Germańskiej</option> <option value="P">Biblioteka Filologii Polskiej i Słowiańskiej</option> <option value="CIDE">Biblioteka Główna - CIDE</option> <option value="ODSK">Biblioteka Główna Oddz. ds Komputeryzacji</option> <option value="ZS">Biblioteka Główna Zbiory Specjalne</option> <option value="H">Biblioteka Humanistyczna</option> <option selected="selected" value="WF">Biblioteka Instytutu Wychowania Fizycznego</option> <option value="A">Biblioteka Języków Obcych</option> <option value="PD">Biblioteka Pedagogiki i Psychologii</option> <option value="N">Biblioteka Wydz. Matematyczno-Fizycznego</option> <option value="BL">Biblioteka Wydz. Nauk Przyrodniczych</option> <option value="SA">Biblioteka Wydz. Prawa i Administracji</option> <option value="THEO">Biblioteka Wydz. Teologicznego</option> <option value="E">Czytelnia Biblioteki Ekonomicznej</option> <option value="Z">Czytelnia Biblioteki Głównej</option> <option value="T">Czytelnia Biblioteki Wydz.Zarządzania i Ekonomiki Usług</option> <option value="GRO">Gromadzenie i Uzupełnianie Zbiorów</option> <option value="INF">Oddział Informacji Naukowej BG </option> <option selected="selected" value="OPR">Opracowanie Zbiorów</option> <option value="TM">Wypożyczalnia Bibl.Wydz.Zarządzania i Ekonomiki Usług</option> <option value="S">Wypożyczalnia Biblioteki Ekonomicznej</option> <option value="W">Wypożyczalnia Biblioteki Głównej </option> <option value="WM">Wypożyczalnia Biblioteki Głównej Podręczniki</option> </select> sub previous_or_default { my($self,$name,$defaults,$override) = @_; my(%selected); ############################bug? if (!$override && ($self->{'.fieldnames'}->{$name} || defined($self->param($name)) ) ) { grep($selected{$_}++,$self->param($name)); #############################bug? } elsif (defined($defaults) && ref($defaults) && (ref($defaults) eq 'ARRAY')) { grep($selected{$_}++,@{$defaults}); } else { $selected{$defaults}++ if defined($defaults); } return %selected; } END_OF_FUNC -- <wojciech(a)zatorski.net> tel. +48 509-855-239; GG: 1500861; Skype: zatorski http://www.Zatorski.Net -- Omnia mea mecum porto.

1 0

Koha translation Problem
by Pedro Faria 27 Oct '06

27 Oct '06

Dear all, I am using koha 2.2.6 and I am trying to translate it to portuguese. The OPAC interface is already translated, but now when executing tmpl_process3.pl like it is said in http://www.kohadocs.org/usersguide/apb.html (and worked for opac) I get: ... ... Making directory ../../../../templates_devel/intranet/pt/catalogue...Creating ../../../../templates_devel/intranet/pt/catalogue/detail.tmpl... Creating ../../../../templates_devel/intranet/pt/catalogue/subject.tmpl... Creating ../../../../templates_devel/intranet/pt/catalogue/searchresults.tmpl... Creating ../../../../templates_devel/intranet/pt/catalogue/detail- opac.tmpl... <b>Copyright:</b> : Completely confused parametrizing Any Help? -- Pedro Faria

1 0

New Search (rel_3_0) in question
by Henri-Damien LAURENT 18 Oct '06

18 Oct '06

Hi, I am trying to get things together for rel_3_0 with synching dev on devweek. It appears that the page search.pl (the advanced search) makes heavy use of hardcoded elements which perfectly fit USMARC but are useless for UNIMARC. Moreover, it relies on coded fields which are supposed to be mandatory, but most of the time, our custommers will overlook them and not fill them in. So this raises some problems to us. First, Up 'till now, itemtypes for instance were user defined. But with using such search, there would be some kind of "itemtypes" (see Material-type or Litterature-Code or target-Audience) that would be prompted by the system and users should change a little their way to use the software, if I don't mind. Second, lists should be marcflavour dependant or at least should be processed in the Template and not in the code. What could be proposed is to get all these things into Templates through a loop that would parse some authorised_values. For instance, Material-Type would be in category MTTY and would contain : d = large print e = newspaper format f = Braille or Moon script g = microprint h = hand-written i = multimedia (e.g. an item in regular print with a microfiche supplement) j = mini-print r = regular print z = other form of textual material for unimarc... and for usmarc # - None of the following a - Microfilm b - Microfiche c - Microopaque d - Large print f - Braille r - Regular print reproduction Eye-readable print. s - Electronic | - No attempt to code (But I found ta, tb, fk in our code stored in 07/0-1) A diffculty would be that where USMARC uses only one field (007), UNIMARC uses multiple ones 110, for serials, 126 for sound recordings, 115 for motion pictures, 130 for Microforms, each one having its own list of material type. What I am trying to say here is that it seems to me that - I have on the long-term to study both norms to try and make things together BUT - that our customers surely donot need such a tough norm abidance but they require that looking for a user-defined itemtype they can find it. This I will try and code. NEVERTHELESS, along with it and preparing the long-term developement, we think it may be useful to propose strict abidance to norms. But this should be done carefully and not with too much hardcoded lists but should be either in templates or in database so that users could invoke this or that part of base and it fills templates with right values. And we should settle which categories would be searchable and which should be in database. THEREFORE, I try and share some thoughts about that.

1 0

Koha 2.2.6 is available...
by Paul POULAIN 17 Oct '06

17 Oct '06

We worked hard, but, finally, it's here !!! Koha 2.2.6 has been released & is available at : http://download.savannah.nongnu.org/releases/koha/koha-2.2.6.tar.gz IMPORTANT : a package (not announced) was at this address, named "koha-2.2.6" was here since some days (2 weeks ?) this packages contained some bugs that were discovered just before announcing the release. So, if you had downloaded & installed this "2.2.6", you MUST reinstall, as it's not the same version. Here are the release notes : RELEASE NOTES ============= Koha is the first Open-Source Integrated Library System. Koha is a full-featured open-source ILS. Developed initially in New Zealand by Katipo Communications Ltd and first deployed in January of 2000 for Horowhenua Library Trust, it is currently maintained by a team of software providers and library technology staff from around the globe. Koha 2.2.6 is more than 250,000 lines of code (see : http://bureau.paulpoulain.com/cvslog/) , contributed by about 50 different developers (46, +translators). The 2.2.6 version of Koha is a mature product, with a lot of nice features. More than 100 libraries are registered as users on wiki.koha.org, and we are sure that at least 300 libraries use the software. There are 2 projects derived from Koha. ======== WARNINGS ======== * The librarian interface is tested only with Mozilla/Firefox. Should work (partially) with IE. OPAC should work fine with any browser. * In this release, french, english &ukrainian are up to date. Other language po files are provided in the package. If you update/complete one of them, please send it to paul @ koha-fr.org, it will be included in a 2.2.6b release ! * NEW PACKAGES REQUIRED : - Class::Accessor (0.25) - XML::SAX (0.14) - MARC::File::XML (0.83), - MARC::Charset (0.95), - LWP::Simple - XML::Simple - GD::Barcode - Data::Random - ZOOM They will be checked during upgrade process. * during install, you may get some warnings during package dependency checkings. Something like : "Too late to run INIT block at /usr/local/lib/perl/5.8.4/ZOOM.pm line 37." or "Subroutine PDF::API2::Resource::Font::Postscript::O_RDONLY redefined at /usr/share/perl/5.8/Exporter.pm line 65." You can ignore them. KNOWN BUGS ********** Critical/blocking : * mySQL5.0 : Koha is NOT compatible with mySQL 5.0 We plan to add 5.0 compatibility in Koha 3. If you want to give a try to 2.2.6 with mySQL5, you can have a look at http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1089, but it's untested & unofficial. * child card craziness, see http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1117 for details * Update child looses guarantor and address., see http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1065 for details * don't use spaces in currencies codes. Use USD, not US DOLLAR, for example. spaces breaks acquisition module. see bugs.koha.org for more information. Please report any problem in bugs.koha.org Apple users : it seems there is an annoying bug in Firefox, that you can have in librarian biblio search: only the first MARC field list is available and the others can't be opened. The problem is described and fixed at http://www.macfixit.com/article.php?story=20051226091140372 ======= CHANGES ======= Changes 2.2.5 => 2.2.6 ********************** DB CHANGES ********** DB structure : dewey field has been moved to a char(30) DB content : many many new systempreferences Koha opac stylesheets : none, but the opac css stylesheet has been redesigned even if it contains no new classes. ******** BUGFIXES ******** === ACQUISITION === * Acquisition has been deeply investigated & tested. should work fine. (there was complex problems depending on prices rebates, VAT charging,...) === CATALOGUE === * Major bugfixes in encoding handling for MARC21 : there was bugs using the MARC21 indicators for character encoding. They should have been fixed for now, and koha 2.2.6 handles MARC21 with unicode correctly. === CATALOGUING === * result page display was incorrect when searching a biblio before adding a new one. * no more saving of an empty field in the DB * Fix for splitting up fixed fields containing | in them causing incorrect storage of fixed fields in Koha DB. * An item that is on loan can't be deleted anymore. === CIRCULATION === * minor bugfix : Adding 0 before days and months in order to make date comparison work. === MEMBERS === * fixed a but to be able to modify an Institution. === PARAMETERS === * adding page facility in book funds. ************ IMPROVEMENTS ************ Almost nothing has changed in the DB & this version has been heavily tested, so the stability should be good. But you are warned that some/few bugs may occur. Please READ the release notes. Everything is compatible with previous versions, so, if you just install Koha, you should have the same behaviour as previously, but you will miss many interesting features! === ACQUISITION === * added a (crontab) script : check_suggestion.pl, that send a mail to the librarian when a suggestion is pending. * *MAJOR IMPROVEMENT* : - online help has been added - the order.pl page doesn't show baskets closed for more than 6 months anymore. - when recieving an order, you now see the list of existing parcels. The parcel code used to be the "Supplier invoice information". Now when you go to the reciept page, you see all previous recieves, and can create a new parcel, exactly as before. This does not require any change in Koha internals, but we hope it's clearer than before. - when recieving an order in a parcel, you now see all orders still waiting for a receipt. Thus, you can enter isbn/title as previously, or directly click on a title in the list. We worked hard on those new acquisition screens, and hope that you'll find it easier to use than before. === AUTHORITIES === * if the library doesn't define a summary for an authority, a standard/default one will be built automatically. * if the librarian set * as subfield, all subfields will be shown, without any separator, but respecting the order. Previously, you had to define every subfield, causing problems in case of reordered subfields. === CIRCULATION === * added a (crontab) script : overduenoticesSelect.pl, that can be used as replacement for the overduenotice script. This one has many more parameters, including a filter on branches and an external letter (to avoid the need to modify the script on each release) * merged today & previous issues list during issuing. Added a button to renew issues & return issues in 1 click === CATALOGUE === * highly improved MARC21 default framework * new systempref "sortbynonfiling". If you catalogue with complete MARC (including indicators), you can set this pref to Yes. It will remove non filing chars and order "The King Henry IV" to letter "K". This systempref is USELESS for UNIMARC (as UNIMARC doesn't manage non-filing chars in an indicator, unlike MARC21) === CATALOGUING === * added a (crontab) script : delete_authority.pl, that deletes all entries of an authority in a biblio. * *MAJOR IMPROVEMENT* in MARC editing : - duplicating a field (+ on the tag) will show a number of creation to do. Thus, you can quickly create 6 subjects lines (for example) - duplicating a subfield is no longer done with a pipe (|), but by clicking on the + facing the subfield - the "hidden" property of the framework now has 19 possible values. Look in the online help to see them. The immediate interesting value is -1, which means the subfield is minimized on the MARC editor and you must click on it to expand it. Rarely used fields/subfields are easier to manage. - a advancedMARCeditor systempref has been added. If set, tag/subfield values are not shown, except when putting the mouse on the tag/subfield. This systempref is only for "MARC addicts"! * MARC21 : many plugins have been added (by LibLime). It seems you now have as many plugins for fixed length fields in MARC21 as in UNIMARC! Note that plugins help you filling a tag/subfield in the MARC editor. === MEMBERS === * patron images management. A new systempreference has been added (patronimages, in borrowers section). If set (to an image extension, like jpg or gif), the image will be shown on patron detail or circulation page. The images must be stored in KOHADIR/htdocs/intranet-tmpl/patronimages/ . The image must be named <borrowernumber>.<patronimagessystempref> (1.jpg for example, for borrower #1) === OPAC === Many preferences have been added to OPAC. Read them carefully, as you will be able to modify highly the look and behaviour of your OPAC! * new default stylesheet for css (purple on white). A new stylesheet (contributed by liblime.com) has been added to show everybody the changes in OPAC. If you want to stay with the old one (dark/light green), just reach Koha >> Parameters >> Systempreferences >> OPAC >> opacstylesheet > modify > /opac-tmpl/default/opac_old.css * Amazon content : if the new AmazonContent systempref is set AND an AmazonDevKey/AmazoneDevTag (available on www.amazon.com) is entered in systempreferences AND XML::Simple package is installed, OPAC will show amazon cover pages when available. Note that this feature may not be legal everywhere. For example, it seems it may not be legal in France (you must ask each editor for permission) * new systempref : opaccredit. If something (including html) is stored there, the footer of OPAC pages will contain what is there (instead of the "Library powered by Koha..." that is on css default templates) * new systempref : opacnav. In this preference, you can put any html that will be added to your menu. For example, to add a button to reach the koha website : <a class="menu" href="http://www.koha.org" title="Koha world website">Koha</a> * new systempref : opacbookbag : if set to 0, the basket/book bag features will be hidden in OPAC (even for logged in users). * authorities heading search : a new menu has been added so the user can search in authorities (same behaviour as in intranet) * new systempref : opaclanguagesdisplay. If set to "yes" (default value), the list of available language is shown. Otherwise, there is no list, koha will stay in default language only. * new systempref : opacreadinghistory. If set to "yes" (default value), the reading history will be available on OPAC (for logged in users). If set to "no", the reading history never appears. * Recent Acquisition : added a new page to filter recent acquisitions on a given branch. * if you use npl templates, you can have an alternate stylesheet (to set it, go to librarian interface >> Parameters > Systempreferences > OPAC > opacstylesheet > modify > /opac-tmpl/npl/en/includes/opac.liblime.css) * when there is more than 1 item at a given location (branch/callnumber/location), the list shows the number of items, not 1 line for each (same) value. === REPORTS === * Inventory : you can now scan in a text file, on an unconnected laptop, with every book in your library. Then, just upload the file in Koha. It will "mark as seen" all books. Once you've scanned everything in your library, just query for all books not seen since the beginning of the inventory, and you'll get "lost" books. === SERIALS === * MAJOR IMPROVEMENT : Adding item creation on the fly when receiving serial : if you activate systempref > Catalogue > serialsadditems, you'll have a form to create an item on the fly at the end of the serial receipt form. The item contains the callnumber, the branch, the barcode and the location (where applicable). Go to the catalogue after setting a serial to "arrived", and you should see the item created. If you let serialsadditems to OFF, behaviour is unchanged from previous releases. * the last 5 arrived serials are shown when receiving serials. === SYSTEM PREFERENCES === === ALL == * Unimarc datas in english are provided * Unimarc datas in ukrainian are provided -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

2 1

Re: [Koha] ldap in 2.2.6RC2
by MJ Ray 15 Oct '06

15 Oct '06

Mourik Jan I am resending your message to the koha-devel list, so that hopefully a developer can test and commit the improved LDAP authenticator to the next versions. I may be offline for some of next week and hesitate to commit something I won't have enought time to test and support. Thank you for chasing up this useful upgrade. Forwarded message: > From koha-bounces(a)lists.katipo.co.nz Fri Sep 15 15:17:17 2006 > Date: Fri, 15 Sep 2006 12:31:06 +0200 > From: mourik jan heupink <heupink(a)merit.unu.edu> > To: Koha(a)lists.katipo.co.nz > Cc: paul.poulain(a)free.fr > Subject: [Koha] ldap in 2.2.6RC2 > List-Id: Discussion list for the Koha Library system <koha.lists.katipo.co.nz> > > dear list, > > There has been some discussion on koha(a)lists.katipo.co.nz about the ldap > authentication bit of koha. (mostly in december 2005) The outcome of > that discussion was (as far as I understood it) that the actual checking > of the password should be done by trying to connect (authenticate) to > the ldap server with a specific username/password and see if ldap > accepts the connection. > > What koha does: It tries to receive the password field from the ldap > server, and compares that to the password the user has typed, to check > if they are the same. > > There are some problems with this approach: > - most (if not all..?) ldap servers will be configured NOT to provide a > user's password to an anonymous connection. Meaning koha would have to > logon with a rootdn (or use acl's) to be able to 'read' the users password. > - if the ldap server uses a a way to encrypt the password, comparing the > (encrypted) password with the plain text (or otherwise encrypted) > plassword two values will not give the desired result. > > Anyway, a solution was provided on this list. To my surprise I noticed > that in the new koha 2.2.6RC2 the old method was still in place. > > Is there anything I missed? Are there reasons NOT to use the trying to > connect (authenticate) to the ldap server with a specific > username/password approach? Does it break other things? > > The Auth.pm provided by KL Nasveschuk is quoted below, and works here. > > Kind regards, > Mourik Jan > > ################################################## > ### LOCAL > ### Change the code below to match your own LDAP server. > ################################################## > > # LDAP connection parameters > > # LDAP server > my $ldapserver = 'ldap.server.com'; > > # Base DN for users > my $name = "ou=users,dc=server,dc=com"; > > # Bind uses the users full DN, if uid doesn't work try "cn" > my $binddn = "uid=$userid,$name"; > > my $db = Net::LDAP->new( $ldapserver ); > > # do bind > my $res =$db->bind( > dn =>$binddn, > password =>$password); > > # check connexion, anything other code than LDAP_SUCCESS (0) > # is a problem > if($res->code != 0 ) { > # auth refused > warn "LDAP Auth failed server not responding or wrong user > password combination"; > return 0; > # search user > }else { > > my $userdnsearch = $db->search(base => "$name", > filter =>"(cn=$userid)", > ); > my $userldapentry=$userdnsearch -> shift_entry; > > # build LDAP hash > my %memberhash; > my $x =$userldapentry->{asn}{attributes}; > my $key; > foreach my $k ( @$x) { > foreach my $k2 (keys %$k) { > if ($k2 eq 'type') { > $key = $$k{$k2}; > } else { > my $a = @$k{$k2}; > foreach my $k3 (@$a) { > $memberhash{$key} .= $k3." "; > } > } > } > } > # > # BUILD %borrower to CREATE or MODIFY BORROWER > # change $memberhash{'xxx'} to fit your ldap structure. > # check twice that mandatory fields are correctly filled > # > my %borrower; > $borrower{cardnumber} = $userid; > $borrower{firstname} = $memberhash{givenName}; # MANDATORY FIELD > $borrower{surname} = $memberhash{sn}; # MANDATORY FIELD > $borrower{initials} = > substr($borrower{firstname},0,1).substr($borrower{surname},0,1)." "; # > MANDATORY FIELD > $borrower{streetaddress} = $memberhash{postalAddress}." "; # > MANDATORY FIELD > $borrower{city} = $memberhash{l}." "; # MANDATORY FIELD > $borrower{phone} = $memberhash{telephoneNumber}." "; # MANDATORY > FIELD > $borrower{branchcode} = "MERIT"; # MANDATORY FIELD > $borrower{emailaddress} = $memberhash{mail}; > $borrower{categorycode} = $memberhash{employeeType}; > > ################################################## > ### /LOCAL > ### No change needed after this line (unless there's a bug ;-) ) > ################################################## > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > Thanks, -- MJ Ray - see http://mjr.towers.org.uk/email.html North End, Lynn, Norfolk, England Work: http://www.ttllp.co.uk/ IRC/Jabber/SIP: on request

2 1

dumpdict => something to investigate...
by Paul POULAIN 13 Oct '06

13 Oct '06

I'm copying a mail from Eric Lease Morgan, about a dictionnary coming from zebra. Sounds like an idea to investigate later... Eric Lease Morgan a écrit : > > By exploiting zebraidx's dumpdict option I have been able to create an > Aspell dictionary and accompanying lookup script paving the way for a > Did You Mean? (alternative spelling) service against my zebra indexes. > It is not perfect but a decent start. > > First is zebra2aspell.pl: > > #!/usr/bin/perl > > # zebra2aspell.pl - create an Aspell dictionary from a zebra index > > # Eric Lease Morgan <emorgan(a)nd.edu> > # October 5, 2006 > > # require > use strict; > > # define the zebraidx and aspell binaries > my $ZEBRAIDX = '/usr/local/bin/zebraidx dumpdict'; > my $ASPELL = '/usr/local/bin/aspell --lang=en create master > /home/emorgan/idzebra-2.0.2/examples/marc21/aspell.dict'; > > # initialize input and output words > my @words; > > # get the list of words from the index > open INPUT, "$ZEBRAIDX |"; > while ( <INPUT> ) { > > chop; # get rid of trailing return > next if ( ! /^\d\d:\s/ ); # only look for word lines, not debugging > s/^\d\d:\s+\d+\s//; # remove "leader" > s/\s-\d.*$//; # remove "trailer" > next if ( / / ); # no words containing spaces; why do > they exist? > next if ( /\W/ ); # no non-word characters > next if ( /\d/); # no words containing digits > next if ( ! $_ ); # has content > push @words, $_; > > } > close INPUT; > > # remove duplicates; from perl cookbook pg. 102 > my %seen = (); > my @words = grep { ! $seen{$_} ++ } @words; > > # build a list aspell can use > my $words; > foreach ( @words ) { $words .= $_ . "\n" } > > # create a dictionary > open OUTPUT, "| $ASPELL"; > print OUTPUT $words; > close OUTPUT; > > # done > exit; > > > Next is lookup.pl. Usage: ./lookup.pl foobar > > #!/usr/bin/perl > > # lookup.pl - look up a word in a aspell dictionary > # and return alternative spellings > > # Eric Lease Morgan <emorgan(a)nd.edu> > # October 5, 2006 > > > # require > use Text::Aspell; > use strict; > > # define > use constant DICTIONARY => './aspell.dict'; > > # get the query > my $query = $ARGV[0]; > > # branch accordingly > if ( ! $query ) { print "Usage: $0 word\n" } > else { > > # initalize dictionary > my $dictionary = Text::Aspell->new; > $dictionary->set_option( 'master', DICTIONARY ); > > # get suggestions > my @suggestions = $dictionary->suggest( $query ); > > # display the suggestions > print "Alternative spellings for $query:\n"; > foreach ( @suggestions ) { print $_, "\n" } > > } > > # done > exit; > > > --Eric "It Feels Good To Hack Again" Morgan > University Libraries of Notre Dame > > > > > _______________________________________________ > Zebralist mailing list > Zebralist(a)lists.indexdata.dk > http://lists.indexdata.dk/cgi-bin/mailman/listinfo/zebralist > > -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

1 0

LIANZA Conference
by Russel Garlick 12 Oct '06

12 Oct '06

Hi everyone, Chris and I have just got back from the LIANZA (Library and Information Association of New Zealand Aotearoa Conference. Katipo had a stand there once again. We decided to ditch the orange fur this time, and got some logos cut out of polystyrene. There are some photos in the Katipo Gallery. http://katipo.co.nz/gallery/lianza2006 I did a talk on Open Source, which went pretty well. We got quite a few people coming up to the stand afterwards to have a chat. I went to a couple of the sessions and it was good to see Open Source being talked about by other speakers. We had a demo of 2.4 up and going, and received lots of positive feedback. Well done to Joshua and everyone else who has contributed to getting it up and going. Cheers -- Russel Garlick Operations Manager Katipo Communications Ph: +64 4 934 1285 Fax: +64 4 934 1286 Mob: +64 27 537 1377 Skype: russelgarlick Web http://www.katipo.co.nz

1 0

Debian Packaging
by alex＠king.net.nz 10 Oct '06

10 Oct '06

I'm interested in having a Koha package available in Debian. I'm also interested in helping to make it happen, although I don't have the skills to do it all myself. After a call on the koha list there are a couple of others willing to help with this. I'd like to invite comments from Koha developers. Is it a good idea to go down this track? Would people like to see Koha in Debian? My original plan was to do a basic package of 2.2.5 with some mysql5 fixes, that would suit my own needs, and try to get it into Etch. However, others have suggested (Actually it was M J Ray http://lists.katipo.co.nz/pipermail/koha/2006/010508.html) modifying the code more extensivly to "look a lot more like the typical perl modules+scripts packages that you find on CPAN". If we're going to go down that path it would probably make sense to pull cvs and perhaps work more closely with the developers feeding back patches if this is seen as a good thing. Following on from that, I guess this is the sort of thing that would happen in a development branch (3) more than a stable branch (2.2?) This is all getting beyond what I really want to do myself - which is to get together a package quickly. I don't have the perl skills to do any extensive work myself. However I am willing to put energy in and assist going down whatever path is appropriate if there are a few people interested and a clear path mapped out. Is this an approprate forum to discuss Debian packaging issues or should we break off into our own list ASAP? Looking forward to your feedback... Alex

8 11

re: New barcode tool configuration
by Mason James 10 Oct '06

10 Oct '06

hiya Pedro, sorry for the late reply. i have been doing some work on spine and barcode label printing for koha recently, that might have the functionality that you are after. the new commits allow users to create 'label templates' where you can define a bunch of size dimensions for. page height and width label height and width number of label rows and columns per page outer page margins between label row and colums gaps spine label font sizes im not too sure if my _very_ recent commits have made it into 2.2.6 but they are available via cvs in the 'devweek' branch here -> http://cvs.savannah.nongnu.org/viewcvs/koha/barcodes/?root=koha&only_with_t… http://cvs.savannah.nongnu.org/viewcvs/koha/C4/Labels.pm?root=koha&only_wit… http://cvs.savannah.nongnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/npl/en/… and possibly this one http://cvs.savannah.nongnu.org/viewcvs/koha/koha-tmpl/intranet-tmpl/npl/en/… the new commits have a new re-designed structure for the label* tables so use the 'create_labels_conf_table.sql' file to update the label* tables like this $ mysql -ukohaadmin -pxxxx koha < ./create_labels_conf_table.sql shout out on #koha if you need some help :) cheers, Mason. > > I am using the new 2.2.6 Koha release and I choose it mostly because > it's new barcode generation tool. Imagine I want to configure the size > (image dimensions in pdf) of the barcode generated and the dimensions > of the red boxes (to fit some specific kind of sicky labes sheet), how > can I do it? Should I go through Perl? > -- Mason James Katipo Communications www.katipo.co.nz +64 4 934 1285

1 0