[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Common LDAP fields used in input for ldif2ldbm?
LDAP newbie here... I am writing a script to parse my current contacts
database to create the input file for ldif2ldbm. So far the basics work
fine, I can create a simple data file (with name and email pairs), run
it thru ldif2ldbm and successfully browse my contacts from my LDAP
client.
Now I am moving on and attempting to add some other fields, namely
address information. I noticed when I export contacts from Netscape it
creates a file that [appears to be] ldif compatible. However some of
the fields have Netscape-specific names (e.g. xmozilladn) that I assume
clients like Outlook ignore. (?)
Is there a "standard" list of fields that all LDAP-compatible clients
[should be able to] recognize? I was using for example the keyword
"locality" to define city but when I browse my contacts the city field
is blank. Therefore I assume the keyword "locality" is incorrect.
I am under the assumption here that you can add any kay/value pairs you
want to the input data file, unless the client specifically queries on
that field it gets ignored, right?
Thanks... CDR
--
Clark Ritchie
clark@ritchie.com
warn if ($^O ne "linux");