Hi, I come back because there's something which is not absolutly clear in my mind with interaction between ldap and koha. Can we make a massive import of borrowers from ldap or the method is 1) making an export in csv of the ldap and use import tool 2) using ldap when we want update some informations about the borrower? Best regards samuel Le 15/11/2012 19:08, MJ Ray a écrit :

...

I've the following message when i search a member

Can't use an undefined value as a HASH reference at /usr/share/koha/intranet/cgi-bin/members/member.pl line 139, <DATA> line 577.

What does it mean? How can i solve it? I think to a problem on my database but i'm not sure. I don't know what version you are using, but member.pl line 139 for me is %{$categories_dislay{$$borrower{categorycode}}}, so I think you maybe have a borrower without a categorycode - as with

Samuel Desseaux <samuel.desseaux@ecp.fr> the problem I saw yesterday, that shouldn't happen, so I doubt it can be repaired from in Koha. So I'd connect to mysql and find and fix the borrowers table.

Hope that helps,

Le 16/11/2012 14:30, MJ Ray a écrit :

...

I come back because there's something which is not absolutly clear in my mind with interaction between ldap and koha.

Can we make a massive import of borrowers from ldap or the method is

1) making an export in csv of the ldap and use import tool

2) using ldap when we want update some informations about the borrower? You can do either - and more besides. I think basically method 2 is

Samuel Desseaux asked: preferred, but your LDAP may be strange and so something like 1 will work better. Could some librarians describe their working LDAP patron setups, please?

Thanks,

Hi, To complete my message, here is my configuration <useldapserver>1</useldapserver> <ldapserver id="ldapserver" listenref="ldapserver"> <hostname>**********</hostname> <base>ou=people,dc=ecp,dc=fr</base> <user>cn=syncrepl,ou=applications,dc=ecp,dc=fr</user> <pass>*****</pass> <replicate>1</replicate> <update>1</update> <auth_by_bind>1</auth_by_bind> <principal_name>uid=%s,ou=people,dc=ecp,dc=fr</principal_name> <mapping> <firstname is="givenname"></firstname> <surname is="sn"></surname> <address is="">Ecole Centrale Paris</address> <city is="">Chatenay-Malabry</city> <zipcode is="">92290</zipcode> <branchcode is="">ECAM</branchcode> <userid is="uid"></userid> <password is="userpassword"></password> <cardnumber is="ecpbadgenumber"></cardnumber> <email is="mail"></email> <categorycode is="supannetudiplome">employee</categorycode> <phone is="telephonenumber">903-566-7654</phone> <dateenrolled is="">2012-09-01</dateenrolled> <dateexpiry is="">2013-09-01</dateexpiry> </mapping> </ldapserver> and our ldap with an example in attached file. What it gives now 1) when i connect to the first time, it doesn't add the borrower. I need to create it manually and after, with ldap, it makes an update 2) when i use the ldap, i would like to use the login (supannAliasLogin) instead of the uid. In this case, is principal name necessary? Why? Because, in the configuration, the login is (example) '2012desseauxs'. But, we would like 'desseauxs' 3) Something strange: when i use cas (which is linked to the ldap), i can use normally my login "desseauxs", the connection is ok but the personal informations aren't so complete as i use instead "2012desseauxs". With others colleagues, we are working on this problem but we don't find great solutions for the moment. I 'll certainly make a csv export of the ldap and i' ll see next year how can i make it better. Many thanks samuel