Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Use Cases for this Workflow can be found here.

Current Work Flow

ACT has been using an R script to create Access Requirement on a set of entities (data set). On some data set, there will be multiple Access Requirements: ACTAccessRequirement, and SelfSignAccessRequirement.

Dataset A has ACTAccessRequirement. User B wants to download dataset A, s/he 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. A form includes the information that Sage and data contributors requires. It is an agreement between Sage and data contributors, so it will not change after it's established for a data set. When there is updated on the data set, we have the data in a different project/ folder and have a new set of Access Requirements on that data.

...

Since the request information is kept in a spreadsheet, a script is run that gathers public information from this spreadsheet and publishes to a wiki: Principal Investigator, Institution, Date, and Intended Data Use Statement.

Example form:

View file
nameROS.MAP_DataUseCertificate_July24.2015.pdf
height250

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.
  • Since requests are submitted via email, there is no ways to prevent requests coming in with missing information.
  • Keeping track of which request is about to expire and emailing reminding users about their expired request takes a lot of time.

Proposed Work Flow

Setting up the Access Requirement:

The ACT member will navigate to a page specifically for Access Requirements and Access Requests. (They can enter the URL directly or clicking on a link from the entity page.)

...

(Please see the process of creating a form below.)
Once a form has been created, the table of requests will be shown on the page, and there will be a button for viewing the form as a requestor would see it.

The form creation process is as follows:

Every form contains an instruction given by the ACT, and the following fields:

...

The ACT can preview the form before creating it.

Creating a request:

User B goes to any entity A with an ACTAccessRequirement associated with it, and clicks on "show unmet conditions" to get to the data access request form (if one has been set up.  If not, the process will be the same as it is currently for requesting access).  If they are not logged in, then they will be met with this view:

...

____________________________________________________________________________________________________________________________________

Hi:

The Synapse Access and Compliance Team has approved your application for use of the MayoGWAS data distributed through Synapse.

To use this data you must adhere to the Terms of Use as described in the MayoGWAS DUC: https://www.synapse.org/#!Synapse:syn2910256

The MayoGWAS data can be accessed through the following Synapse project:https://www.synapse.org/#!Synapse:syn3219045

Please note that the first time you download a datafile you will also be asked to agree to acknowledge the AMP-AD Partnership in publications derived from any of the AMP-AD data. This approval must be performed through the website.

For a review of the AMP-AD Data Terms of Use, please see here: https://www.synapse.org/#!Synapse:syn2580853/wiki/78604.

Please note, this email is sent from an unmonitored account. Send any questions to act@sagebase.org.

Sincerely,
The Synapse Access and Compliance Team

____________________________________________________________________________________________________________________________________

...

____________________________________________________________________________________________________________________________________

Hi:

The Synapse Access and Compliance Team has rejected your application for use of the MayoGWAS data distributed through Synapse, because you did not sign the DUC.

To submit another request, please visit the MayoGWAS dataset at: https://www.synapse.org/#!Synapse:syn2910256.

Please note, this email is sent from an unmonitored account. Send any questions to act@sagebase.org.

Sincerely,
The Synapse Access and Compliance Team

____________________________________________________________________________________________________________________________________

...