Design Objectives

General Requirements and Design Principles for Success

The following are identified as broad, general requirements that supplement the collected use cases and permissions matrix developed during our analysis phase.

1. Permissions are extensible to locally customized features, in addition to existing Hyrax functionality

2. Permissions should apply comprehensively and retroactively (beyond current Hyrax behavior)

   1. There are some use cases for this retroactive assignment to be optional

3. Expand workflow capabilities beyond the current 1:1 constraint with Admin Sets so that workflows can be applied to additional actions (delete, etc)

   1. Ability to perform Deletion actions must be configurable (vs. current Hyrax ability)  

4. Expand workflow capabilities beyond just works, so higher level actions can also be configurable (flag collections for deletion)
   

   1. Ability to perform Deletion actions must be configurable (vs. current Hyrax ability)  

5. Provide pre-configured application Roles

   1. abilities can be locally customized

   2.  ability to create local, custom Roles

6. Provide ability to manage permissions via GUI

7. Enable assignment and management of permissions to members of (works within) Collections vs. current Admin Set permissions management structure

8. Support for integration with institutional directory-based groups (e.g. Directory Services/AD)

9. Support for simple IP range based access  

10. Separate intellectual "ownership" concept from asset management permissions

    1. Intellectual ownership, stewardship, and provenance information is handled via metadata, not application logic

       1. original depositor

       2. person on whose behalf the work was depositor

       3. creator of original content
       4. primary contact (department or user responsible for questions and information)
       5. "My" information, for reporting & analytics context

    2. Asset management means ability to create, modify, view, delete entities

       1. manager

       2. editor

    3. Hyrax currently includes a "transfer ownership" option.

       1. What is being transferred and why?

11. Ability to broadly differentiate staff activities from end-user/public activities (e.g. “administrative view” of repository entities and metadata)