Sorry for double postings, but I would like to get some feedback from people on both lists.
Currently we are distinguishing five user profiles that inherit properties from the profile below (a profile defines what services a user has access to).
These are:
1 - Administrator (all functions)
2 - User administrator (can do everything an editor can do and can add new users to the groups he/she is a member of)
3 - Editor (can create, edit and delete metadata, do XML imports AND set privileges on records)
4 - Registered user (can access data visible to selected groups only)
5 - Guest user
For the workflow, you may want to have the privileges settings handled by another person than the editor. For this, it could be useful to have another profile between User administrator and editor, e.g. "reviewer" that has the permission to set these privileges.
Although this can fairly easily be customized by each administrator itself by modifying the user-profiles.xml file, we may want to use a set of profiles valid for most installations.
So please indicate where you would prefer privileges should be handled, at the Editor profile or at a new Reviewer profile?
Thanks,
Jeroen
Jeroen Ticheler wrote:
Sorry for double postings, but I would like to get some feedback from people on both lists.
Currently we are distinguishing five user profiles that inherit properties from the profile below (a profile defines what services a user has access to).
These are:
1 - Administrator (all functions)
2 - User administrator (can do everything an editor can do and can add new users to the groups he/she is a member of)
3 - Editor (can create, edit and delete metadata, do XML imports AND set privileges on records)
4 - Registered user (can access data visible to selected groups only)
5 - Guest user
For the workflow, you may want to have the privileges settings handled by another person than the editor. For this, it could be useful to have another profile between User administrator and editor, e.g. "reviewer" that has the permission to set these privileges.
Although this can fairly easily be customized by each administrator itself by modifying the user-profiles.xml file, we may want to use a set of profiles valid for most installations.
So please indicate where you would prefer privileges should be handled, at the Editor profile or at a new Reviewer profile?
I think an application is more useful if it has more possibilities to configure it. I'm sure that exists a guy working for the company X who needs this new user profile. I'm thinking an scenario with a lot of possible metadata editors, which produced data must be checked by an admin istrator before their publication.
Regards
--
Jorge Piera Llodra
Equipo de desarrollo gvSIG
Conselleria de Infraestructuras y Transporte
Generalitat Valenciana
Valencia - Spain
http://www.gvsig.gva.es