...
IRB-approved versions of all of the 'data access documents' :
Summary:
- Data layer access in Synapse requires one or more approval steps.
- In Synapse granting data access is synonymous with providing the URL to the stored data.
(This URL may have an embedded access token.)
- Currently (i.e. as of Jan. 2012), the backend has a representation of EULAs and of Agreements (i.e. that a particular user agrees to a EULA)
- The work flow logic for creating the agreement is embedded in the Web client, so other clients would have to maintain duplicate logic. Specifically, the web client has the following logic:
1) When a user tries to download a layer, the Web client checks whether the parent dataset has an associate EULA;
2) If there is an EULA, the web client checks whether there is an Agreement, owned by the User and referencing the dataset and EULA;
3) If there is a EULA but no Agreement, the web client prompts the User to sign the EULA, creates the Agreement, then allows the download.
- There is no provision in our permissions scheme for an "IRB ACT role" which can grant or revoke 'download permission' to a user.
...
Tier 3: (Tier 1) + (Tier 2) + User access must be requested/approved through an institutional review board (IRBAccess and Compliance Team (ACT).
Design
Security Model
- In the entity schema we allow a field to have a (some?) permission(s) which a user need to have before the field can be accessed.- We add a 'Download' permission to the location field of the Layer entity. To control download ability on a Layer, we control whether a user has the "Download' permission.We add a 'Download' permission, as distinct from 'Read' permission to entity access control lists.
- In order for a user to get the location field(s) of an entity, they must have Download permission.
Workflow Model
Design Assumptions
...