Suggested format for use cases is user story: As a < type of user >, I want to < specific goal >, so that < the reason >
Other possible formats:
- application activity: list of specific activities which require individual permission
- i.e. edit metadata (without editing other object attributes)
- access grid format: list specific application tasks in rows, and user roles in columns. Check the intersection of roles and tasks
Coordinated Use Case Spreadsheet
| Organization | Use Cases
|
|---|---|
| UNC | https://docs.google.com/document/d/1gAu5HNLBEKnLtwVY_FKTzy5FbD4TWCV8vwOoWpU6fmk/edit |
| Emory | Draft user profiles for Repository Management (local effort to inform roles/permissions needed; Deposit-related profiles forthcoming) |
| Emory | Permissions Matrix template (in progress through March): entities, verbs, roles |
| Emory | Additional user stories (in progress through March) - some stories may change as we learn the Hyrax permissions model |
| Emory | Internal Project Glossary of Terms (Repository Management oriented) |
| Indiana University | https://wiki.dlib.indiana.edu/display/VarVideo/Collection+Member+Roles |
| Indiana University | https://docs.google.com/spreadsheets/d/1_LEZI6IcxTNlhpWsQRvRz2s5SyJV443e2ny0pYg5gFY/edit?usp=sharing Our QA Analyst, Karthikeya Dulla, created the list of user stories and Chris Colvard (Deactivated) identified what was in hyrax, partially in hyrax, or not in hyrax. There were more comments on the original document that I have removed because they are not relevant to this discussion. There may be a way to work around some of the gaps we identified. |
| Notre Dame | https://docs.google.com/document/d/1abPOEdmvEKQNfKIGgcInOA67cy-TXh-QAKrlYd3CDGE/edit |
| Emory | Sample diagram showing use cases for needing admin set permissions assignments separated from the "one workflow per admin set" limit https://docs.google.com/presentation/d/1ulTA7BUO5jNBo1UXJmFPkbK8STvnMs6JJIlXaVrMIaY/edit#slide=id.p |