[EMAIL PROTECTED] wrote:
Assuming a flat tree is preferable, is it better to
have everyone combined into ou=people,dc=companyname,dc=com and have a
separate object classes for employees, contractors, business partners,
etc.?
You don't need separate objectclasses. You can use the same object class
but use another attribute like businesscategory to filter on for the
types of people you're interested in.
Would a separate objectclass be appropriate if different attributes were
needed for contractors? For example, contractors would have a "supervisor"
at our site and a supervisor at their company. Similarly they may have a
email addresses, phone numbers, physical addresses at our company and
email/phone/address information from their company too.
Sure, but you may want to use a common structural objectclass like
inetorgperson for all people and add additional attributes through
auxiliary objectclasses for your particular types of people. That way,
one somebody could wear multiple hats.
Jon Roberts
www.mentata.com
---
You are currently subscribed to [email protected] as: [EMAIL PROTECTED]
To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the
SUBJECT of the message.
