General Requirements and Design Principles
The following are identified as broad, general requirements that supplement the collected use cases and permissions matrix developed during our analysis phase.
Extensible to locally customized features, in addition to existing Hyrax functionality
Permissions should apply comprehensively and retroactively (beyond current Hyrax behavior)
Expand workflow capabilities beyond the current 1:1 constraint with Admin Sets and deposit functions, so that workflows can be applied to additional actions (delete, etc.)
Ability to perform Deletion actions must be configurable (vs. current Hyrax ability)
Provide pre-set application Roles whose abilities can be locally customized, plus the ability to create local, custom Roles
Provide increased ability to manage permissions via GUI
Enable assignment and management of permissions to members of (works within) Collections vs. current Admin Set permissions management structure
Support for integration with institutional directory-based groups (e.g. Directory Services/AD)
Support for simple IP range based access
Separate intellectual "ownership" concept from asset management permissions (ability to create, modify, view, delete entities), such that intellectual ownership, stewardship, and provenance information is handled via metadata, not application logic
Ability to broadly differentiate staff activities from end-user/public activities
Design Principles
The following are proposed objectives for design to take into consideration.
https://docs.google.com/document/d/1OdacxmL2FfAKgbY6Z5eM4fCaXXB2AqhSJMqJaJynkD4/edit#