Current Work Flow

Dataset A has ACT Restriction. User B wants to download dataset A, he/she needs to email the ACT to request access to data set A. Via emails, an ACT member would ask the user to complete some forms. The forms are different for each dataset. Each request may request n number of users to access the data.

After the user meets all requirements given by the ACT (via emails), an ACT member would go to the dataset and manually enter the user(s) to give the user(s) access to the dataset.

A script is run (Brian Bot in mPower?) that gathers public information from the spreadsheet and publishes to a wiki: Principal Investigator, Institution, Date, and Intended Data Use Statement

Example form:

Link to instructions: https://www.synapse.org/#!Synapse:syn2954404

Disadvantages:

• Manually entering the detailed information (in a spreadsheet) about the request for access (including approval status) is a burden for the ACT.

• User's handwriting is hard to read.

Proposed Work Flow

The ACT setup the necessary form for dataset A.

User B goes to dataset A to submit his/her request, and fill out the form electronically. A notification email then sent to the ACT. 

An ACT member could approve the request using a one-click link provide in the email or go to view the user request and their submitted form before approving their request.  Approval may grant access to one user, or to many (ACT will decide based on request).

On approval, public information will be available about the request (the public can see the following standard fields):  Principal Investigator, Institution, Date, and Intended Data Use Statement

ACT member could query requests (find requests that need to be processed, find requests that have been approved and see when they were approved, etc). 

ACT member could export set of files (associated with the dataset requests) as zip file, to be sent to data contributor.