Management FRG - Permissions Analysis and Matrix
Prepared By: DLP Repository Management Functional Requirements Group (FRG)
Date: March 2018
Status: Final DraftApproved
...
Table of Contents maxLevel 1
...
While creating a work breakdown structure and analyzing tasks, the group made the determination to consolidate multiple permissions-related deliverables into one effort, since they were closely interrelated. As a preliminary step, the team conducting a three-part brainstorming session to identify repository entities, types of people/roles participating in long-term management of repository assets, and verbs/activities. This information was further refined to produce the Management User Profiles and also helped inform the matrix in Appendix C.
...
The functional requirements noted inform levels of visibility that the system can enable; actual assignment of visibility to material is subject to Emory Libraries policy and procedure. Hyrax documentation indicates “Visibility only controls who can view or download your work – it does not control edit access.” When view permissions are assigned for an object or file, those same settings apply to download options.
Standard Hyrax Software Levels of Visibility:
Public:Public makes the work available to the general public. Metadata is available to be crawled by search engines for discovery.
Institution: restricts access to works and work metadata to users with login privileges. Users will need to be logged into the repository to access the work. (Note: Institution does not mean the Emory campus network:it means that any authenticated/internal repository system users can view it, relative to other settings assigned at the Admin Set or Collection level.)
Embargo:lets you restrict access to Private or Institution until a specified date, when it will be opened to the public or your institution
Lease:permits access to the work to the public or Institution until a specified date, when it will be restricted to Private or your institution
Private (Note: this status is not fully documented, but appears to mean only visible to the work owner or Administrator only)
Emory Visibility Customizations Requested
IP-range restriction for Reading Room access
IP-range restriction to restrict visibility to Emory campus network users only (Emory network/VPN connection required to view)
Custom embargo duration lengths
ETDs: 6 months, 1 year, 2 years, 6 years
Emory FIRST to OpenEmory embargo durations: 6 months, 12 months, 18 months, 24 months, 36 months, 48 months, Indefinite.
Ensure open-ended date ranges (Hyrax default) are also available for Libraries’ Admin Sets/Collections
Custom embargo for sub-object levels: (e.g. ETDs)
Embargo content files
Embargo content files and Table of Contents
Embargo content files, Table of Contents, and Abstract
...
The matrix entries were based on known DLP requirements produced by other FRGs as well as available permissions-related documentation in the Hyrax Developer Knowledge Base, primarily the Manager’s Guide for version 2.x.