- Koha - lists.katipo.co.nz

[Koha 3.00.02] 'use C4::Circulation' test fails
by Marc Nürnberger 10 Jun '09

10 Jun '09

Dear all, When I try to install the latest 3.0.2 the 'make test' returns: ########################################### t/Circulation_barcodedecode....NOK 1/16 # Failed test 'use C4::Circulation;' # at t/Circulation_barcodedecode.t line 10. # Tried to use 'C4::Circulation'. # Error: DBD driver has not implemented the AutoCommit attribute at /usr/lo cal/lib/perl/5.10.0/DBI.pm line 705. # Compilation failed in require at /home/koha/koha-3.00.02/blib/PERL_MODULE_DIR/ C4/Circulation.pm line 25. # BEGIN failed--compilation aborted at t/Circulation_barcodedecode.t line 10. # Compilation failed in require at (eval 3) line 2. # BEGIN failed--compilation aborted at (eval 3) line 2. Undefined subroutine &C4::Circulation::barcodedecode called at t/Circulation_bar codedecode.t line 31. # Looks like you planned 16 tests but only ran 1. # Looks like you failed 1 test of 1 run. # Looks like your test died just after 1. t/Circulation_barcodedecode....dubious Test returned status 255 (wstat 65280, 0xff00) DIED. FAILED tests 1-16 Failed 16/16 tests, 0.00% okay ########################################### If I try to ignore this, the webinstaller won't start, but complain: ########################################### DBD driver has not implemented the AutoCommit attribute at /usr/local/lib/perl/5.10.0/DBI.pm line 705. Compilation failed in require at /usr/share/koha/lib/C4/Circulation.pm line 25. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Circulation.pm line 25. Compilation failed in require at /usr/share/koha/lib/C4/Overdues.pm line 24. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Overdues.pm line 24. Compilation failed in require at /usr/share/koha/lib/C4/Members.pm line 27. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Members.pm line 27. Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 27. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 27. Compilation failed in require at /usr/share/koha/opac/cgi-bin/opac/opac-main.pl line 22. BEGIN failed--compilation aborted at /usr/share/koha/opac/cgi-bin/opac/opac-main.pl line 22. ########################################### I am using DBD:mysql 4.007 (couldn't install 4.011) on Perl 5.10 on Lenny. Has anyone experienced the same error? Any ideas what I messed up? Best regards, Marc

2 1

Re: [Koha] Setting up a consortium
by Doug Dearden 10 Jun '09

10 Jun '09

Lenora, Check this thread: http://thread.gmane.org/gmane.comp.misc.koha/13706/focus=13729 Best, Doug >>> "Lenora Oftedahl" <OFTL(a)critfc.org> 6/10/2009 8:42:00 AM >>> Ok. On Koha 3.0.1, we're looking at setting up a consortia of far-flung libraries with centralized cataloging (me). Can someone please help me understand Independent Branches (if that's what I need) and how to set up individual OPAC pages for each library so they can have logo, etc. on their search page. Thanx. Lenora StreamNet Regional Librarian Columbia River Inter-Tribal Fish Commission http://www.fishlib.org Lenora A. Oftedahl StreamNet Regional Librarian Columbia River Inter-Tribal Fish Commission http://www.fishlib.org _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Setting up a consortium
by Lenora Oftedahl 10 Jun '09

10 Jun '09

Ok. On Koha 3.0.1, we're looking at setting up a consortia of far-flung libraries with centralized cataloging (me). Can someone please help me understand Independent Branches (if that's what I need) and how to set up individual OPAC pages for each library so they can have logo, etc. on their search page. Thanx. Lenora StreamNet Regional Librarian Columbia River Inter-Tribal Fish Commission http://www.fishlib.org Lenora A. Oftedahl StreamNet Regional Librarian Columbia River Inter-Tribal Fish Commission http://www.fishlib.org

2 1

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 10 Jun '09

10 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