New Roles in GOCDB
The GOCDB role mechanism will be updated to better address the needs of our user community. We will update the name of some roles, add new roles and make changes to the actions each role grants the user. These changes will affect both the front end portal and information made available through our programmatic interface. The original request for these improvements was made by Vera Hansper and has been followed up by Peter Sologna. Thanks to both for their contributions so far.
- Agree on new roles + authorizations
- Agree on changes to the PI
- Users of queries that will change
- Cyril - Central and Regional Ops Portal
- Emir - Nagios
- Deploy new roles
- Deploy code
- Switch old roles over to new
Changes to Roles
|Old Role Name||New Role Name||Type of Role|
|Site Administrator||Site Administrator||C|
|Security Officer *||Site Security Officer||C'|
|Regional Operations Staff||Regional Staff (ROD)||D|
|Regional Manager||NGI Operations Manager||D'|
\* This role name is duplicated at a site, NGI and project level. The new roles will explicitly define which level the roles operate at.
The following spreadsheet further explains the new role types and changes to the old roles. (C' and D' have been added, others have had their permissions changed). Media:FinerGrainedGOCDB_rolesVeraProposal2.xls
When we change the name of roles and add new roles this will be reflected through our PI. We will need to contact other PI users (including operational tools) to ensure they're Ok with the changes we'll make.
The following methods are affected by these changes: