What is the current best practice for groups?
I have always been against using nested groups in organizations, and if so, only nest one level.
I am working with a Domino environment which is used solely for Lotus Notes/Domino mail.
They have several nested groups, sometimes going 5 levels deep. These are more distributions lists than access groups (ACL) groups.
Does anybody have thoughts, ideas, or best practices regarding groups, nesting, and Domino mail environments?
What performaance issues are we dealing with? Have improvements been made with R6?
Thanks.
Subject: Nested Groups, what is best practice
The Lotus CTO once stated: “Best practises are yesterdays technology”. There is instrinct nothing wrong with nested groups. The main concern is to keep track of them .Notes limits the amount of data per field to about 40k nett of data, so you have to resort to nesting if you have a large organisation (SingTel?). A good practise is to use a delimited notation, where the dot has been quite popular. You also might want to prefix your groups to separate them from users. So your groups could look like this:
#singtel.sales.broadband as main group and #singtel.sales.broadband.1 – 10 for all the members.
It is rather an organisational problem than a technical (besides the 40k limitation).
Hth
stw
P.S.: Greetings to a fellow Singaporean (well I’m half) – look me up, let’s have coffee.