- Koha - lists.katipo.co.nz

about postgresql and koha
by ricardo mendoza 10 Oct '08

10 Oct '08

hi all, I have a question. What is the reason for that Koha does not have support for postgresql 8.3?

3 3

Observation on Notices/Notice Trigger Tools
by Bradley Peters 10 Oct '08

10 Oct '08

Hello, I just started using Koha (version 3.0) and I was surprised to see the definition of overdue notices and triggers was located under Tools rather than under Administration. I expected them to be in the latter section because the patron category editor (under Administration) has a field that seems to define which patron categories appear in the notice editor. Sincerely, Bradley Peters

1 0

Indicators for MARC fields
by Lenora Oftedahl 10 Oct '08

10 Oct '08

Where can I edit the indicators for MARC fields? I've imported records and am editing them now. I'd like to have the indicators filled in, especially for titles so I can skip initial articles in the title sort. thanx. Lenora -- *************************************** Lenora A. Oftedahl, MLS MEPM StreamNet Regional Librarian Columbia River Inter-Tribal Fish Commission 729 NE Oregon St, Ste 190 Portland, OR 97232 503-736-3581 / ARIEL: 207.173.155.8 503-731-1260 FAX OFTL(a)critfc.org http://www.fishlib.org ************************************* "One by one, the penguins are stealing my sanity" ************************************** "Don't worry about the world coming to an end today. It's already tomorrow in Australia." --(Charles Schultz) ************************************** "The problem with adults is that they are contaminated by experience." --Kumi Naidoo, General Secretary and CEO of CIVICUS **************************************

1 0

LDAP authentication -- getting closer.....
by Scott Owen 10 Oct '08

10 Oct '08

Hi all, I seem to be making some headway getting the LDAP authentication working betwixt Koha and Netware/NDS/LDAP. A quick glance at the two login attempts below , shows that a username (in my case "test") without the full NDS context will not authenticate and will generate a failed user/password combination. However, using a NDS fully qualified distinguished name (in my case cn=test,ou=students,o=SCHOOL) seems to generate a successful login ? (Sending operation result 0:"":"" to connection 0xa7684b60) But then dies later on ......(Duplicate entry 'cn=test,ou=stude') A quick peek at the borrowers in the Koha MySQL data base (CSV export) 338 71582 FA ZA PINE AVENUE ALMA 339 71583 BR AU PINE AVENUE ALMA 340 44863 ED ZA PINE AVENUE ALMA 341 cn=41337,ou=stud 342 cn=test,ou=stude 343 71584 test test 123 happy lane alma Shows that my test users (test and 41337) are being added to the borrowers ???? (FA ZA etc...are truncated user lastnames, firstnames...I truncated them for this post) And that my LDAP attrib mapping in NDS are correct (the firstname, lastname address and city are all correct for my "test" user...but they are under a user named 71584.....I have no idea where this username came from....but I'm guessing it was automagically added (after the two real studend ID number of 71582 and 71583)) So...I'm guessing that some playing with the LDAP section of the Auth.pm file may allow me to use just a used ID (41337) rather than the fully qualified distinguished name ??? Any Ideas on that ?? Any ideas on the Duplicate entry error ?? (or might this go away as soon as the logins are working properly ???) ******************************** Logging in as "test" --Intranet Error Log -- New cleartext connection 0xa7684b60 from 10.1.1.192:3081, monitor = 0x259, index = 1 DoBind on connection 0xa7684b60 Bind name:test, version:3, authentication:simple Illegal ndsname "test" in ldap2uNDSDN, err = 34 (0x22) ldap2uNDSDN ldapDN = "test" - error 34 (0x22) Failed to convert LDAP DN "test" in nds_back_bind, err = 34 (0x22) Sending operation result 34:"":"" to connection 0xa7684b60 Operation 0x1:0x60 on connection 0xa7684b60 completed in 0 seconds Monitor 0x259 found connection 0xa7684b60 socket closed, err = -5871, 0 of 0 bytes read Monitor 0x259 initiating close for connection 0xa7684b60 Server closing connection 0xa7684b60, socket error = -5871 --DStrace Error Log-- [Wed Oct 08 10:01:47 2008] [error] [client 127.0.0.1] LDAP Auth failed server not responding or wrong user password combination at c:/usr/koha229/intranet/modules/C4/Auth.pm line 528., referer: http://127.0.0.1:8000/cgi-bin/koha/mainpage.pl ******************************************************* Logging in as cn=test,ou=students,o=SCHOOL --Intranet Error Log -- New cleartext connection 0xa7684b60 from 10.1.1.192:3088, monitor = 0x259, index = 1 DoBind on connection 0xa7684b60 Bind name:cn=test,ou=students,o=SCHOOL, version:3, authentication:simple Sending operation result 0:"":"" to connection 0xa7684b60 Operation 0x1:0x60 on connection 0xa7684b60 completed in 0 seconds DoSearch on connection 0xa7684b60 Search request: base: "OU=STUDENTS,O=SCHOOL" scope:2 dereference:2 sizelimit:0 timelimit:0 attrsonly:0 filter: "(cn=cn=test,ou=students,o=SCHOOL)" no attributes Empty attribute list implies all user attributes Sending operation result 0:"":"" to connection 0xa7684b60 Operation 0x2:0x63 on connection 0xa7684b60 completed in 0 seconds Monitor 0x259 found connection 0xa7684b60 socket closed, err = -5871, 0 of 0 bytes read Monitor 0x259 initiating close for connection 0xa7684b60 Server closing connection 0xa7684b60, socket error = -5871 Connection 0xa7684b60 closed --DStrace Error Log-- [Wed Oct 08 10:14:01 2008] [error] [client 127.0.0.1] DBD::mysql::st execute failed: Duplicate entry 'cn=test,ou=stude' for key 1 at c:/usr/koha229/intranet/modules/C4/Members.pm line 155., referer: http://127.0.0.1:8000/cgi-bin/koha/mainpage.pl ************************************************

3 3

Viewing logs
by Winter, James 09 Oct '08

09 Oct '08

This should be a quick one, and you'll have to excuse my ignorance. Koha is my first exposure to Perl. Where are the logs, and how do I view them? James Winter Arcadia University <http://www.arcadia.edu/> Systems Manager 215.517.2588 winterj(a)arcadia.edu <mailto:winterj@arcadia.edu>

2 2

Koha 3.0 and LDAP
by Winter, James 09 Oct '08

09 Oct '08

In trying to get LDAP authentication working with Koha 3.0, I'm coming across the following error when loading the OPAC page: No "ldapserver" in server hash from KOHA_CONF: /etc/koha/koha-conf.xml at /usr/share/perl/5.8/CGI/Carp.pm line 314, <DATA> line 275. Is this indicating that the LDAP connection is failing, or that my koha-conf.xml isn't configured correctly? This is my LDAP config section: <ldapserver id="ldapserver" listenref="ldapserver"> <hostname>abc</hostname> <base>dc=abc,dc=domain,dc=com</base> <replicate>1</replicate>  <update>1</update>  <mapping>  <firstname is="givenname" ></firstname> <surname is="sn" ></surname> <address is="postaladdress" ></address> <city is="l" >Athens, OH</city> <zipcode is="postalcode" ></zipcode> <branchcode is="branch" >MAIN</branchcode> <userid is="uid" ></userid> <password is="userpassword" ></password> <email is="mail" ></email> <categorycode is="employeetype" >PT</categorycode> <phone is="telephonenumber"></phone> </mapping> </ldapserver> Thanks for any insight into this. James Winter Arcadia University <http://www.arcadia.edu/> Systems Manager 215.517.2588 winterj(a)arcadia.edu <mailto:winterj@arcadia.edu>

2 2

Re: [Koha] Holds Waiting to Be Pulled
by Kathy Rippel 09 Oct '08

09 Oct '08

I don't have an answer; but we agree with you wholeheartedly. This and the fact that holds show up as "Available" in the OPAC unless checked out are two of the serious issues about holds that need to be addressed. Kathy At 05:38 PM 10/8/2008, Fooled One wrote: >Koha version <http://3.01.00.002>3.01.00.002 >Debian Etch >Perl version 5.008008 >MySQL version 5.0.32 >Apache version 2.2.3 > >The "Holds Awaiting Pickup" and "Holds to Pull" circulation reports >do not show a list of items that are placed by patrons from home >that are already available in the library. The "Holds Awaiting >Pickup" report does seem to show a list of items if they have been >on hold while the item was checked out to another patron and that >patron just check it back in. > >The lack of "Holds to Pull" reporting is an important issue because >librarians need to know what items need to be pulled off the shelf >when a patron places a hold - even if the item is already available. > >I have my preferences set to: > >AllowOnShelfHolds: ON > >emailLibrarianWhenHoldsPlaced: ON (though this does not work either) > >Any thoughts on how to fix this this? Is there a job that needs to >be running? Am I just missing something? >_______________________________________________ >Koha mailing list >Koha(a)lists.katipo.co.nz >http://lists.katipo.co.nz/mailman/listinfo/koha Kathleen D. Rippel 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

1 0

Holds Waiting to Be Pulled
by Fooled One 09 Oct '08

09 Oct '08

Koha version 3.01.00.002 Debian Etch Perl version 5.008008 MySQL version 5.0.32 Apache version 2.2.3 The "Holds Awaiting Pickup" and "Holds to Pull" circulation reports do not show a list of items that are placed by patrons from home that are already available in the library. The "Holds Awaiting Pickup" report does seem to show a list of items if they have been on hold while the item was checked out to another patron and that patron just check it back in. The lack of "Holds to Pull" reporting is an important issue because librarians need to know what items need to be pulled off the shelf when a patron places a hold - even if the item is already available. I have my preferences set to: AllowOnShelfHolds: ON emailLibrarianWhenHoldsPlaced: ON (though this does not work either) Any thoughts on how to fix this this? Is there a job that needs to be running? Am I just missing something?

1 0

error in opac-sendbasket.pl
by Basu Talikoti 08 Oct '08

08 Oct '08

hi all we are using centos operating system and koha 3, when you send list of book through email saved in basket, it give the following error kindly help in resolving the problem. Koha error The following fatal error has occurred: Wide character in subroutine entry at /usr/share/koha/opac/cgi-bin/opac/opac-sendbasket.pl line 132. Apache Server version: Apache/2.2.3 Server built: Jan 15 2008 20:33:30 Koha 3.00.00.107 Koha DB 3.0000107 MySQL mysql Ver 14.12 Distrib 5.0.45, for redhat-linux-gnu (i686) using readline 5.0 OS Linux dplcat.com2.6.18-92.el5PAE #1 SMP Tue Jun 10 19:22:41 EDT 2008 i686 i686 i386 GNU/Linux Perl 5.008008 with regard basu

2 1

UTF-8 again
by "Thommy M. Malmström" 08 Oct '08

08 Oct '08

I'm about to get crazy on this character set mix. I have Koha 3 on Ubuntu 8.04 MySQL 5 Apache 2.2 Perl 5.8 Firefox 3 Stright out of the box installation. I've followed the instructions on http://wiki.koha.org/doku.php?id=ubuntu_gutsy to install and it went in with some minor hickups. When I use Z39.50 to search for an item it shows up with a black rhomb with a white question mark in it if the character is outside ASCII. Like ö becomes � If I save the record it shows up with the same rhomb/q-mark for those characters. Then I went to http://wiki.koha.org/doku.php?id=encodingscratchpad but none of the hints there made any difference. So, is there anyone who have made this combination to play with non ASCII characters. And if so, can you list what you have done outside of the vanilla installation?

2 2