I want to reactivatethis thread, because it describes exactly the feature we need.
We have about 1700 contacts in our organization, splitted into 8 departments with 100-350 contacts each.
In each departement we have 8-20 groups with 10-30 contacts. We also have a mailinglist for each group.
Departements are strictly separated. So it is suitable to have one adressbook for each departement from the authorization point of view.
From the sync point of view, one person needs to have the contacts of one or two groups on his mobile.
We started to split the contacts of one (smaller one) departement into several addressbooks. One for each group. So we have now 12 adressbooks for this department, which can be synced separatly.
But, we identified some issues to go this way.
The same companys must be created redundantly in each addressbook, because the company is related to exactly one addressbook.
When a contact should be moved to another group, there has to be done two actions:
1. Move the contact to the other addressbook and
2. update the mailinglists.
Sometimes users will forget one of these actions and this will result in an inconsistency.
If we would go this way for the whole organization this would result in at least more than 100 addressbooks, what would cause some issues in the management of the access rights.
For us, the proposal described by brainbows would solve all of our issues.
We would have 8 addressbooks and 100 Mailinglists (each with contacts of only one departement).
Each user should choose which mailinglists he wants to sync.
All would be happy