[Kolab-devel] Problems after importing addresses

[Stephan Buys]

Hi Andreas,

The cn field is used to store "Firstname Surname" and the mail field is used 
for the email address. The Admin interface parses the cn field when creating
the user lists.

Regards,
Stephan

On Tuesday 17 May 2005 22:17, Andreas Gungl wrote:
> Hi,
> 
> my company wants me to import a lot of addresses into our Kolab server. I get 
> the data in LDIF format. I have to adjust the format. After some fighting 
> with problematic data constellations I'm facing the following problem:
> 
> I have to insert data as:
>  dn: cn=email,cn=external,dc=...
>  cn: email
>  sn: lastname
>  firstname: firstname
> 
> (The attribute name may be wronghere, I don't remember correctly.)
> 
> AFAIU the cn is set to "firstname lastname" when I add addresses via the admin 
> interface. But I can't use the names, as I get duplicates for persons with 
> the same name in different companies.
> Anyway, the cn should not matter. However, after importing the data I get very 
> strange results in the admin interface when looking at the data. Somehow the 
> cn is used to build the displayed name. This might be due to the fact, that 
> the firstname was added later in th development.
> 
> I think the admin interface needs to be fixed, but I haven't found the time to 
> look into the code to make really sure that my assumption is correct. I won't 
> be able to do so until the beginning of the next week either, so I thought to 
> better drop you a quick note about the issue.
> 
> Regards,
> Andreas
> 
> PS. After having read the discussion about the OpenLDAP performance, I wonder 
> if it is a great deal to import about 20.000 addresses. I mean memory wise, 
> the import is slow, but I can run it in the background. Does anyone have 
> experiences with such volumes?
> 

-- 
Stephan  Buys
Code Fusion cc.
Tel: +27 11 673 0411
Mobile: +27 83 294 1876
Email: s.buys at codefusion.co.za

E-mail Solutions, Kolab Specialists.
http://www.codefusion.co.za