On Thu, 2007-06-14 at 12:02 +0300, [EMAIL PROTECTED] wrote: > > The best practice is probably not to create branches for business > units and put people under them. Better is to use an attribute for > each person: fooComBusinessUnit, or something similar which you can > use to filter against. With this technique, you can easily make mass > organizational changes without any pain.
Again Mike showed professional know-how in this area. I'd certainly start formal consult your company but our project is still not in the level of importance to managers to accept using external consult: but the project need external consult experts like you. I don't very much get your idea actually. Use an attribute for each person? Do you mean using a special attribute on business branch entry, value of which is a DN referring to a person in ou=people? Actually because we are not sure of the final best structure we used both: people are put under business branch entry and also there is an attribute in branch entry with multiple values of DN referring to these people. Or do you mean adding an attribute to each person entry which is a DN referring to the business branch this person is working for? -- Zhang Weiwu Real Softservice http://www.realss.com +86 592 2091112 --- You are currently subscribed to ldap@umich.edu as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
