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

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

Problem creating new marc structure in koha 2.2.6
by Pedro Faria 06 Oct '06

06 Oct '06

Dear all, I noticed some kind of a bug in the new koha 2.2.6. When I tried to make my own marc structure named TEST I got this error (this is just a piece of it...): more before ... [Fri Oct 06 17:28:47 2006] [error] [client 127.0.0.1] DBD::mysql::st execute failed: Duplicate entry 'TEST-686-c' for key 1 at /usr/local/koha/intranet/cgi-bin/admin/marctagstructure.pl line 383., referer: http://localhost:8080/cgi-bin/koha/admin/marctagstructure.pl [Fri Oct 06 17:28:47 2006] [error] [client 127.0.0.1] DBD::mysql::st execute failed: Duplicate entry 'TEST-700-3' for key 1 at /usr/local/koha/intranet/cgi-bin/admin/marctagstructure.pl line 383., referer: http://localhost:8080/cgi-bin/koha/admin/marctagstructure.pl [Fri Oct 06 17:28:47 2006] [error] [client 127.0.0.1] DBD::mysql::st execute failed: Duplicate entry 'TEST-700-4' for key 1 at /usr/local/koha/intranet/cgi-bin/admin/marctagstructure.pl line 383., referer: http://localhost:8080/cgi-bin/koha/admin/marctagstructure.pl ... more after It says 'duplicate entry...' but I have no other structure with the same name (I tryed many just in case...). So I got the new structure but when I go try to add or remove some tags none appears. -- Pedro Faria

1 0

development in module fines from OP
by toumi bruno 06 Oct '06

06 Oct '06

hi i explain (with my best english) all my developement in fines module: new features: the system of fine : -work in day open(work with calendar module). -linked with overdue rules delays . -create a file number to link all accountlines per borrowers,per days . -calcul of fines work with issuingrules. -create new line item price in accounlines. -modify display of pay.tmpl (all lines , and total per days (file number) ). -all data with same notify_id are linked and total was caluled par notify_id. -write off works now with all accounttypes. -Fines.pm is more general . -create new accounttypes (IP=> Item Price ,CH=>charge , RL => Recommended charge , RE => Overdue notice charge); database modification -add two fields in accountlines (notify_id and notify_level) notify_id=>file number,notify_level=>linked with delays -add two table charges,notifys

1 0

New barcode tool configuration
by Pedro Faria 05 Oct '06

05 Oct '06

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? -- Pedro Faria

1 0

Re: [Koha] MySQL 5 fixes - Debian packaging.
by Alex King 30 Sep '06

30 Sep '06

This is going to be a show stopper for getting a Debian package out quickly. MySQL 5 is the standard server in Debian Etch (testing). There isn't even a version of the 4 or 3 server available for it as far as I can tell. So were going to need something that works with 5. I think the current and future versions of Ubuntu are in the same situation. I'd like to know from the developers what led to the patches shown in the bug report, ie what problems they were solving, how serious is this? With just the search queries patched, 2.2.5 appears to work OK (apart from barcodes), although I haven't tested it thoroughly. So we have two possible roads we could go down for a Debian package - either package 2.2.6 and add whatever patches are needed and test test test, or give up on it and package 3.0 What are people's instincts as to what is likely to be the best way to go? I don't want to spend a lot of time packaging 2.2.6 just to find I have to abandon it and switch to 3.0 because 2.2.6 can't be made to work with MySQL 5. On the plus side we can probably gather half a dozen or so testers, and if we know what we're looking for (in terms of where the problems might lie with MySQL 5) we could be effective at flushing out the bugs. Either way it's looking increasingly unlikely we'll get something in for Etch. I'm still planning to get something together soon - probably still 2.2.6 unless the consensus is otherwise. Cheers, Alex PS. My -devel digests have been hidden away by my mailer & I've only just discovered them, so sorry for my lack of responsiveness! After I told people to post there too :-/ PPS. I now think it's even more critical to point out the MySQL dependencies clearly and explicitly on the website. Is it there already, have I missed something? I think more and more Linux distros are/will be shipping with MySQL 5 by default. Mike Dalgity wrote: > I originally replied to Ms. Johnson off list but I'll post here for everyone > else following this topic. I am not a developer but the following is what > I've come across on the subject. > > According to Bug #1089 > http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1089 MySQL 5 will NOT > be supported in Koha 2.x. Apparently MySQL 5 introduces more problems other > than reserved keywords. It's my understanding that the fix isn't as simple > as fixing the keywords and the search problems. The patch that is included > in that bug report makes a LOT of changes, stats modules, aquistions, etc. > And the authour indicates that there are still additional problems the patch > doesn't fix or even introduces. The probable reason that MySQL 5 isn't > supported is that it's a major undertaking to change everything and then > test it. Also the 2.x branch is supposed to be stable so a major change like > this is not recommended. AFAIK you will have to wait for Koha 3.0 to support > MySQL 5 (of course it can be modified to work if you really want it to). If > the developers have changed their plans someone please correct me. > > Mike D. > > > -----Original Message----- > From: koha-bounces(a)lists.katipo.co.nz > [mailto:koha-bounces@lists.katipo.co.nz]On Behalf Of Alex King > Sent: September 29, 2006 5:40 PM > To: BWS Johnson > Cc: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] MySQL 5 fixes > > > It looks like Koha version 2.2.5 was released in January. Normally, the > download for 2.2.5 wouldn't be changed. I would assume the fixes are in > the pipeline for the next version in the series, 2.2.6. > > So when 2.2.6 is released I would expect it will work nicely with MySQL5. > > Perhaps a warning could be put on the download page mentioning the > MySQL5 issue. > > Cheers, > > Alex > > BWS Johnson wrote: > >> Salvete! >> >> Is there a reason that the reserved language switch to make Koha play >> nice with MySQL 5 hasn't been incorporated into the downloads yet? Am >> I missing something? >> >> Cheers, >> Brooke @ Hinsdale MA >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Koha mailing list >> Koha(a)lists.katipo.co.nz >> http://lists.katipo.co.nz/mailman/listinfo/koha >> >> > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > > >

2 1

dev_week / rel_3_0 zebra API
by Paul POULAIN 29 Sep '06

29 Sep '06

I want to summarize what is done on dev_week (& synched to rel_3_0) and check (with Kados) that i'm right : * cataloguing API : - joshua, you have modified recently *Biblio.pm* to change the sub names, to have something using our coding rules. For example, NEWnewbiblio is now NewBiblio. The parameters seems unchanged. - we don't see anything commited in acqui.simple/addbiblio.pl and additem.pl, meaning either you have forgotten to commit them, or that it is still to be done. Pls tell us ;-) - AddBiblio / ModBiblio ... are now the ONLY point of entry to add a biblio. That means the parameter MARC=OFF is definetly gone & abandonned. * Search API : - The search on catalogue can be done with Search.pm, subs BuildQuery & GetRecords. All previous subs (cataloguersearch... are deprecated & can/will be removed from the code) - the search in librarian interface is still search.marc/search.pl, and don't use this new definitive API yet. - the search in OPAC is search (opac-search.pl & opac-zoomsearch.pl are deprecated too & can be dropped). Is there a reason why you called it "search" only (no .pl & no opac-xxx) ? * where can we help ? we are going to merge the code to rel_3_0 and continue cleaning, but should we do this on dev_week BEFORE merging, or on rel_3_0 AFTER merging ? -- 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

3 4