Requirement #769
(Requirement) Authorization should support critical roles, such as curators and system administrators
0%
Description
While the principals contributing data should be able to specify access, they frequently struggle with the software systems intended to do so, and at times make mistakes. The system should support certain roles with elevated privielges for groups of objects to allow, e.g, a system administrator or data curator to change objects for which they are not otherwise granted access. For example, all objects that are associated with a particular field station might be managed by the information manager at that field station, and the person filling that role through time might change. Individual principals should be able to determine who has access to objects, both through explicit grants of access and through indirect roles that may be only implicitly defined.
Fit Criteria
- Its possible for access by some roles to be assigned implicitly through certain membership criteria (e.g., a data object is part of an LTER site)