- Koha - lists.katipo.co.nz

koha
by vivek kumar 10 Jun '09

10 Jun '09

hello I have upload a Patron image but show the error Error in tempdir() using XXXXXXXXXX: Parent directory (.) is not writable at /usr/share/koha/intranet/cgi-bin/tools/picture-upload.pl line 76 i have change the permission but show the same error how to slove plz help me vivek kumar

1 0

Import Matching rules: Tags 001 / 999$d
by Marc Nürnberger 10 Jun '09

10 Jun '09

Dear all, I cannot figure out, how to set up a working matching rule for tag 001 Control Number or tag 999$d Biblioitem Number. Please find my rules below - any suggestions how to correct the rules would be appreciated. Trying on Koha 3.01.00.032, Best regards, Marc ####################################### Configuration for Control Number 001: Matching rule code: CNUMBER Description: 001 Match threshold: 1000 Match points Add matchpoint Remove this matchpoint 1. Search index: Control-number 2. Score: 1000 1. Tag: 001 2. Subfields: [blank] 3. Offset: 0 4. Length: 0 ###################################### Configuration for Biblioitem Number 999$d: Matching rule code: BIBLIO Description: 999$d Match threshold: 1000 Match points Add matchpoint Remove this matchpoint 1. Search index: biblioitemnumber 2. Score: 1000 1. Tag: 999 2. Subfields: d 3. Offset: 0 4. Length: 0

3 3

Koha authentication against existing LDAP directory
by Ben Finney 09 Jun '09

09 Jun '09

Howdy all, I am trying to get a Koha server to authenticate against an existing LDAP directory. I've followed what appear to be the appropriate documentation, but haven't succeeded in authenticating. Proving that LDAP authentication and query is working: ===== $ user_uid=percy $ ldapsearch -LLL -x -D uid=${user_uid},ou=People,dc=lan -W "(uid=${user_uid})" Enter LDAP Password: dn: uid=percy,ou=People,dc=lan cn: Percy uid: percy uidNumber: 1006 loginShell: /bin/sh homeDirectory: /home/percy gidNumber: 100 userPassword:: [blabla password hash] objectClass: posixAccount objectClass: shadowAccount objectClass: person objectClass: inetOrgPerson shadowLastChange: 14355 gecos: Percy sn: Percy ===== The ‘/etc/koha/koha-conf.xml’ contains, in part: ===== … <ldapserver id="ldapserver" listenref="ldapserver"> <hostname>example.lan</hostname> <base>dc=lan</base> <replicate>1</replicate> <update>1</update> <mapping> <surname is="sn" ></surname> <branchcode is="branch" >MAIN</branchcode> <userid is="uid" ></userid> <password is="userpassword" ></password> <categorycode is="employeetype" >PT</categorycode> </mapping> </ldapserver> ===== There's also a suggestion in the docs of two other elements, ‘user’ and ‘pass’. But shouldn't the LDAP connection be made as the user who's trying to authenticate, with the password they used? I hope I don't need to record some administrative user's authentication information in a configuration file. How can I get authentication working with Koha like with other LDAP clients? -- \ “I used to be a proofreader for a skywriting company.” —Steven | `\ Wright | _o__) | Ben Finney

5 21

Multiple LDAPs
by Walls, Ian 09 Jun '09

09 Jun '09

Koha folks, My library serves multiple institutions, and we have valid library patrons coming to us who are authenticated against different LDAP servers. I remember seeing somewhere, briefly, in some Koha documentation, something about support for multiple LDAPs, but when I try to find it again, or any kind of example on how to set it up, I turn up nothing. We'd want the system to behave something like this: 1. Check first LDAP; if patron authenticates, end. Else: 2. Check second LDAP; if patron authenticates, end. Else: 3. Either check a third LDAP, or just use the internal Koha login authentication (can one mix and match LDAP auth and Koha DB auth?). 4. Ultimately reject if not in any of the above sources Does the existing code support this, or would a modification need to be made? If it already does, how can I go about setting it up? If it doesn't, where in the code should I look to make the enhancement? Any assistance is greatly appreciated. Thanks! Ian Walls Systems Integration Librarian NYU Health Sciences Libraries (212) 263-8687 </PRE> <html> <body> ------------------------------------------------------------<br /> This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is proprietary, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this email in error please notify the sender by return email and delete the original message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email.<br /> ================================= </body> </html> <PRE>

3 2

Re: [Koha] Multiple LDAPs
by Joe Atzberger 09 Jun '09

09 Jun '09

The Net::LDAP module does support multiple targets, but nobody has implemented this in Koha, to my knowledge. Your main consideration should be namespace collision. Before attempting what you describe you have to guarantee that the usernames would never overlap between various LDAP targets. This seems unlikely to have been designed in, since it would have been easier to consolidate the servers than to coordinate separate ones in parallel. Your best bet is to construct an LDAP proxy server with the behavior you want, and then use Koha with the proxy as the sole target. --joe via cell On Jun 9, 2009 1:56 PM, "Walls, Ian" <Ian.Walls(a)med.nyu.edu> wrote: Koha folks, My library serves multiple institutions, and we have valid library patrons coming to us who are authenticated against different LDAP servers. I remember seeing somewhere, briefly, in some Koha documentation, something about support for multiple LDAPs, but when I try to find it again, or any kind of example on how to set it up, I turn up nothing. We’d want the system to behave something like this: 1. Check first LDAP; if patron authenticates, end. Else: 2. Check second LDAP; if patron authenticates, end. Else: 3. Either check a third LDAP, or just use the internal Koha login authentication (can one mix and match LDAP auth and Koha DB auth?). 4. Ultimately reject if not in any of the above sources Does the existing code support this, or would a modification need to be made? If it already does, how can I go about setting it up? If it doesn’t, where in the code should I look to make the enhancement? Any assistance is greatly appreciated. Thanks! Ian Walls Systems Integration Librarian NYU Health Sciences Libraries (212) 263-8687 ------------------------------------------------------------ This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is proprietary, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this email in error please notify the sender by return email and delete the original message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email. ================================= _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Re: [Koha] Reference books & books for loan
by Kathy Rippel 09 Jun '09

09 Jun '09

To build on Ian's answer.... Many of our libraries use an item-type of "ref" and also one like "book". You can set up your circulation rules for each so that the program knows whether or not to circulate the item. If you want patrons to know at a glance which are "Reference", then put something in the call number (or Shelving Location) like R, Ref, Reference, etc. Kathy At 08:30 AM 6/12/2009, Walls, Ian wrote: >Content-Class: urn:content-classes:message >Content-Type: multipart/alternative; > boundary="----_=_NextPart_001_01C9EB61.E76EEA40" > >Youll need to assign your non-circulating books >to one Item Type, and your circulating books to >another (you could use more Item Types if you >need to make more distinctions for statistical >purposes). If you do not want to burden your >patrons with this distinction in the OPAC, you >can then define a CCODE (in Authorized Values) >for Books, assign both circulating and >non-circulating books to that CCODE, and switch >the AdvancedSearchTypes system preference (in >the Searching tab) from itemtypes to ccode. > >This is assuming you arent already using CCODE for something else > >Hope this helps, > > >Ian Walls >Systems Integration Librarian >NYU Health Sciences Libraries >(212) 263-8687 > > > >From: koha-bounces(a)lists.katipo.co.nz >[mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Ondrej Mlecka >Sent: Friday, June 12, 2009 3:49 AM >To: koha(a)lists.katipo.co.nz >Subject: [Koha] Reference books & books for loan > >In our library, there's a big part of books >which a patron can read inside of the library >but which are not available for loan. There's >another part of the library which contains books >for loan. I would like to ask how is it possible >to distinguish these categories in Koha. > >If I simply check the "Not for loan" field for >items which are for referene only, the OPAC >search summary displays "No copies available" >(but they are available, but not for loan). > >I could also define that for ex. that books are >not for loan (in the "Item types and >circulation" settings). But in this case I can't >distinguish books which are for loan. > >Would anyone know how to resolve this difficulty? > >Thanks > >Ondrej Mleca >Casa Balthasar >Roma > > >------------------------------------------------------------ >This email message, including any attachments, >is for the sole use of the intended recipient(s) >and may contain information that is proprietary, >confidential, and exempt from disclosure under >applicable law. Any unauthorized review, use, >disclosure, or distribution is prohibited. If >you have received this email in error please >notify the sender by return email and delete the >original message. Please note, the recipient >should check this email and any attachments for >the presence of viruses. The organization >accepts no liability for any damage caused by >any virus transmitted by this email. >================================= > >_______________________________________________ >Koha mailing list >Koha(a)lists.katipo.co.nz >http://lists.katipo.co.nz/mailman/listinfo/koha Kathleen D. Rippel Dept. Head/Consultant--Resource Sharing and Access ; Pathfinder Central (Manager) Central Kansas Library System 1409 Williams Great Bend, KS 67530 (620-792-4865) phone (800-362-2642) toll-free, KS (620-792-5495) fax kdr(a)ckls.org ******************************************************************************************** I'm currently reading: Unmasked, by C. J. Barry. I'm currently listening to: Eclipse, by Stephenie Meyer.

1 0

Re: [Koha] Koha Digest, Vol 44, Issue 16
by Katharine Dixon 09 Jun '09

09 Jun '09

Karen received a letter showing her her password. She was never assigned to me to train her on City Accounts etc. No, she cannot "automatically forward her City mail to her Yahoo account. Access is the same at all three Libraries. Any staff computer in the back room will allow her access. At JS we have the luxury of extra cubicles, at the branches, I assume they have worked out how to use the computers of the staff members that are not working that day. We have to determine if she still has her letter, if not, we will have to ask for another to be sent, it may take an hour, it may take a week, I never know. Katharine -----Original Message----- From: koha-bounces(a)lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of koha-request(a)lists.katipo.co.nz Sent: Saturday, June 06, 2009 5:00 PM To: koha(a)lists.katipo.co.nz Subject: Koha Digest, Vol 44, Issue 16 Send Koha mailing list submissions to koha(a)lists.katipo.co.nz To subscribe or unsubscribe via the World Wide Web, visit http://lists.katipo.co.nz/mailman/listinfo/koha or, via email, send a message with subject or body 'help' to koha-request(a)lists.katipo.co.nz You can reach the person managing the list at koha-owner(a)lists.katipo.co.nz When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..." Today's Topics: 1. Re: Serials Management (thandu venkat narayana) 2. Import Matching rules: Tags 001 / 999$d (Marc N?rnberger) 3. Overdue notices (Owen Leonard) 4. kloha (mike re-v) ---------------------------------------------------------------------- Message: 1 Date: Sat, 6 Jun 2009 13:42:47 +0530 (IST) From: thandu venkat narayana <thandu_venkat(a)yahoo.com> Subject: Re: [Koha] Serials Management To: koha(a)lists.katipo.co.nz Message-ID: <164319.86946.qm(a)web94904.mail.in2.yahoo.com> Content-Type: text/plain; charset="iso-8859-1" Dear All, ? How to maintain serials in Koha 2.2.9 windowsxp platform? I created supplier and biblio, but at the time of searching supplier in serials subscription no results are appearing. Please give your valuable information for this. ? Regards Venkata Narayana T Bollywood news, movie reviews, film trailers and more! Go to http://in.movies.yahoo.com/

1 0

Problems installing HTTP::OAI from CPAN for Koha 3.0.2
by Ricardo Dias Marques 09 Jun '09

09 Jun '09

Hi everyone! So, I see that Koha 3.0.2 has been released some days ago (on 4-Jun-2009). Congratulations to everyone involved! :) Today (08-Jun-2009), I tried to update an install of Koha 3.0.1 to Koha 3.0.2 (running on SLES 11 - "SUSE Linux Enterprise Server" 11). SLES 11 uses Perl 5.10 Here's the snipped output of my upgrade attempt: ---------------------------------------- myhost:~/koha-3.00.02 # perl Makefile.PL --prev-install-log /usr/share/koha/misc/koha-install-log [snipped most output... ] If installing on a Win32 platform, be sure to use: 'dmake -x MAXLINELENGTH=300000' Checking if your kit is complete... Looks good [Mon Jun 8 16:19:37 2009] Makefile.PL: Warning: prerequisite HTTP::OAI 3.2 not found. [Mon Jun 8 16:19:37 2009] Makefile.PL: Warning: prerequisite JSON 2.07 not found. [Mon Jun 8 16:19:41 2009] Makefile.PL: Warning: prerequisite XML::SAX::Writer 0.44 not found. Writing Makefile for koha myhost:~/koha-3.00.02 # ---------------------------------------- OK. So it seems that I need to install the HTTP::OAI Perl module. No problem, I'll install it from CPAN: ---------------------------------------- myhost:~/koha-3.00.02 # cpan cpan shell -- CPAN exploration and modules installation (v1.9304) ReadLine support enabled cpan[1]> install HTTP::OAI CPAN: Storable loaded ok (v2.18) Going to read /root/.cpan/Metadata Database was generated on Tue, 12 May 2009 10:27:03 GMT CPAN: LWP::UserAgent loaded ok (v5.816) CPAN: Time::HiRes loaded ok (v1.9711) Fetching with LWP: http://cpan.perl.pt/authors/01mailrc.txt.gz CPAN: YAML loaded ok (v0.68) Going to read /root/.cpan/sources/authors/01mailrc.txt.gz Going to read 60 yaml files from /root/.cpan/build/ ............................................................................DONE Restored the state of 60 (in 1.4212 secs) ............................................................................DONE Fetching with LWP: http://cpan.perl.pt/modules/02packages.details.txt.gz Going to read /root/.cpan/sources/modules/02packages.details.txt.gz Database was generated on Mon, 08 Jun 2009 11:26:58 GMT ............................................................................DONE Fetching with LWP: http://cpan.perl.pt/modules/03modlist.data.gz Going to read /root/.cpan/sources/modules/03modlist.data.gz ............................................................................DONE Going to write /root/.cpan/Metadata Running install for module 'HTTP::OAI' Running make for T/TI/TIMBRODY/HTTP-OAI-3.21.tar.gz Fetching with LWP: http://cpan.perl.pt/authors/id/T/TI/TIMBRODY/HTTP-OAI-3.21.tar.gz CPAN: Digest::SHA loaded ok (v5.47) Fetching with LWP: http://cpan.perl.pt/authors/id/T/TI/TIMBRODY/CHECKSUMS Checksum for /root/.cpan/sources/authors/id/T/TI/TIMBRODY/HTTP-OAI-3.21.tar.gz ok Scanning cache /root/.cpan/build for sizes ............................................................................DONE HTTP-OAI-3.21/ HTTP-OAI-3.21/CHANGES HTTP-OAI-3.21/Makefile.PL HTTP-OAI-3.21/t/ [snipped most output...] Manifying blib/man3/HTTP::OAI::ListSets.3pm Manifying blib/man3/HTTP::OAI::Repository.3pm Manifying blib/man3/HTTP::OAI::MetadataFormat.3pm TIMBRODY/HTTP-OAI-3.21.tar.gz /usr/bin/make -- OK Running make test PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/00static.t ............. 1/20 Use of uninitialized value in string eq at t/00static.t line 16. # Failed test 3 in t/00static.t at line 16 # t/00static.t line 16 is: ok($repo->Identify->version eq '2.0s'); # Failed test 4 in t/00static.t at line 22 # t/00static.t line 22 is: ok($id->is_success); # Failed test 5 in t/00static.t at line 23 # t/00static.t line 23 is: ok($id->repositoryName && $id->repositoryName eq 'Demo repository'); # Failed test 6 in t/00static.t at line 27 # t/00static.t line 27 is: ok($lmdf->is_success); # Failed test 7 in t/00static.t at line 28 # t/00static.t line 28 is: ok(my $mdf = $lmdf->next); # Failed test 8 in t/00static.t at line 29 # t/00static.t line 29 is: ok($mdf && $mdf->metadataPrefix && $mdf->metadataPrefix eq 'oai_dc'); # Failed test 9 in t/00static.t at line 33 # t/00static.t line 33 is: ok($lr->is_success); # Failed test 10 in t/00static.t at line 35 # t/00static.t line 35 is: ok($rec && $rec->identifier && $rec->identifier eq 'oai:arXiv:cs/0112017'); # Failed test 11 in t/00static.t at line 39 # t/00static.t line 39 is: ok($li->is_success); # Failed test 12 in t/00static.t at line 41 # t/00static.t line 41 is: ok(@recs && $recs[-1]->identifier eq 'oai:perseus:Perseus:text:1999.02.0084'); # Failed test 13 in t/00static.t at line 45 # t/00static.t line 45 is: ok($ls->is_success); # Failed test 14 in t/00static.t at line 47 # t/00static.t line 47 is: ok(@errs && $errs[-1]->code eq 'noSetHierarchy'); # Failed test 15 in t/00static.t at line 51 # t/00static.t line 51 is: ok($gr->is_success); # Failed test 16 in t/00static.t at line 53 # t/00static.t line 53 is: ok($rec && $rec->identifier eq 'oai:perseus:Perseus:text:1999.02.0084'); # Failed test 18 in t/00static.t at line 59 # t/00static.t line 59 is: ok(@errs && $errs[0]->code eq 'idDoesNotExist'); # Failed test 20 in t/00static.t at line 64 # t/00static.t line 64 is: ok(@errs && $errs[0]->code eq 'cannotDisseminateFormat'); t/00static.t ............. Failed 16/20 subtests t/01parse.t .............. 1/4 # Failed test at t/01parse.t line 18. Can't call method "metadata" on an undefined value at t/01parse.t line 19. # Looks like you planned 4 tests but ran 2. # Looks like you failed 1 test of 2 run. # Looks like your test exited with 9 just after 2. t/01parse.t .............. Dubious, test returned 9 (wstat 2304, 0x900) Failed 3/4 subtests t/02token.t .............. ok t/50mets.t ............... 1/3 Can't call method "metadata" on an undefined value at t/50mets.t line 20. # Looks like you planned 3 tests but ran 1. # Looks like your test exited with 9 just after 1. t/50mets.t ............... Dubious, test returned 9 (wstat 2304, 0x900) Failed 2/3 subtests t/80network.t ............ ok t/error.t ................ ok t/getrecord.t ............ 1/8 Can't call method "metadata" on an undefined value at t/getrecord.t line 72. # Looks like you planned 8 tests but ran 6. # Looks like your test exited with 2 just after 6. t/getrecord.t ............ Dubious, test returned 2 (wstat 512, 0x200) Failed 2/8 subtests t/identify.t ............. 1/8 # Test 7 got: <UNDEF> (t/identify.t at line 32) # Expected: "mailto:tdb01r@ecs.soton.ac.uk" # t/identify.t line 32 is: ok($r->adminEmail,'mailto:tdb01r@ecs.soton.ac.uk'); t/identify.t ............. Failed 1/8 subtests t/listidentifiers.t ...... ok t/listmetadataformats.t .. ok Test Summary Report ------------------- t/00static.t (Wstat: 0 Tests: 20 Failed: 16) Failed tests: 3-16, 18, 20 t/01parse.t (Wstat: 2304 Tests: 2 Failed: 1) Failed test: 2 Non-zero exit status: 9 Parse errors: Bad plan. You planned 4 tests but ran 2. t/50mets.t (Wstat: 2304 Tests: 1 Failed: 0) Non-zero exit status: 9 Parse errors: Bad plan. You planned 3 tests but ran 1. t/getrecord.t (Wstat: 512 Tests: 6 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 8 tests but ran 6. t/identify.t (Wstat: 0 Tests: 8 Failed: 1) Failed test: 7 Files=10, Tests=54, 6 wallclock secs ( 0.04 usr 0.11 sys + 3.09 cusr 0.62 csys = 3.86 CPU) Result: FAIL Failed 5/10 test programs. 18/54 subtests failed. make: *** [test_dynamic] Error 255 TIMBRODY/HTTP-OAI-3.21.tar.gz /usr/bin/make test -- NOT OK //hint// to see the cpan-testers results for installing this module, try: reports TIMBRODY/HTTP-OAI-3.21.tar.gz Running make install make test had returned bad status, won't install without force Failed during this command: TIMBRODY/HTTP-OAI-3.21.tar.gz : make_test NO cpan[2]> quit Lockfile removed. ---------------------------------------- Oops... so it seems I'm having some problems installing the HTTP::OAI Perl module from CPAN, because it fails several installation tests. Are other people having the same problem? Did you have to "force install" HTTP::OAI ? Thanks in advance! :) Cheers, Ricardo Dias Marques lists AT ricmarques DOT net Installation Guide for Installing Koha 3 on openSUSE 11 http://wiki.koha.org/doku.php?id=opensuse_11.0

2 2

General project IRC meeting - 1 July 2009
by Galen Charlton 09 Jun '09

09 Jun '09

Hi, The next general meeting of the Koha project will be held on the #koha IRC channel at 19:00 UTC+0. The following standing agenda items will be discussed: 1. Koha 3.2 update 2. Koha 3.0.x update 3. Actions from the previous IRC meeting To suggest additional agenda items, please go to the wiki page for this meeting located at <http://wiki.koha.org/doku.php?id=meetingnotes09jul01>. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 0

Record matching rule for Koha biblio 999c?
by Nelson Fredsell -CCE 09 Jun '09

09 Jun '09

On batch edits of records and items, I'm using Koha Tools and MarcEdit. On record matching rules for re-import, we cannot make use of ISBN or ISSN as neither have been used in legacy catalogue. We've been advised to use Koha biblio number as the unique identifier. Might anyone be able to share settings for a record matching rule on the Koha biblio number, 999c? I looked in the manual, but it didn't seem to provide enough info for me to actually set up this rule. (http://koha.org/documentation/manual/3.0/administration/catalog-administrat ion/record-matching-rules ) For testing, I'm exporting a single biblio *.mrc, making edits w/ MarcEdit *.mrk, re-compiling to *.mrc, then staging w/ Koha Tools. Koha then gives me a no_match on the record, so I suspect that I've used incorrect settings. Using the ISBN rule as an example, I set up the following: -------------------------------------------- Matching rule code: KBiblio Desc: 999$c Match threshold: 1000 Match points - Search index: KBiblio (Do I need an actual Koha index, or just make something up?) Score: 1000 Tag: 999 Subfields: c Offset: 0 Length: 0 Normalization rule: KBiblio (Do I need an actual Koha rule, or just make something up?) If I need actual Koha search index and/or normalization rule, pls cite URL in manual. Match checks - N/A ---------------------------------------- Thanks for any feedback, Nelson Implementing a union catalogue in Cape Town, South Africa

2 1