Hi Andreas,
On 2010-11-25 16:17 UTC Andreas Dick wrote:
Features I implemented allredy:
- more fields like address, phone nubers, notes, and the flexibility to
add more in the config file.
Sounds great.
- the "name" field is redundant, it is just "surname lastname", thus it
must not be shown and editable.
Please think of other languages and scripts, where it's not that simple. A large amount of people write their family names first, and then their given name(s), not separated by commas or spaces (for example Chinese - see http://en.wikipedia.org/wiki/Chinese_names). So it's not that simple. Maybe output of the name should be determined by an additional field, that's linked to a format string*, or something. Or there must be a separate 'displayName', but that requires entering the name(s) twice. Or there should just be one 'Name' field, which can be set in any way one wants, but where it's up to the person reading it, to figure out what's the family name, and what's the given name - maybe that's even the most sane thing to do ;)
*) for example like this: A field 'Name format' could have values such as
- 'Western (Given Middle Family)' => printf('%s %s %s', givenName, middleNames, familyName)
- 'Western (Family, Given Middle)' => printf('%s, %s %s', familyName, givenName, middleNames)
- 'Western (Family, Given)' (just omitting middle name(s)) => printf('%s, %s', familyName, givenName)
- 'CJK' => printf('%s%s', familyName, givenName)
- ... and probably many more ...
The input fields for givenName, middleNames and familyName should probably be arranged depending on the chosen Name format, so the person can write the name in the way she is used to write names. A default 'Name format' must be configurable (after all, there are lots of people who don't have names of people from around the world in their address books).
Features I have planed to implement soon:
- group management: read groups out of the LDAP, create and remove
groups. (I still looking for a "standard- like" LDAP implementation of address groups, I tried allready to use the "o:" attribute, but I think it is better to use seperate LDAP subdirectories for each group)
I don't know how this is usually done, but I don't think 'o' (Organization) is suitable. Maybe 'ou' (Organizational Unit)? Or maybe use 'groupOfNames' with many 'member' values?
It's probably best to stick to an established Schema (inetOrgPerson etc.), so for example Mozilla Thunderbird finds the LDAP directory useful as well (although that would be limiting, since Mozilla's LDAP support is a bit of a joke).
Patrick.