Current Work Flow
...
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
**TODO: Incorporate the Access Requirement creation/linking into the process.
The ACT setup the necessary form for dataset A. This will look similar to setting the schema for a table in Synapse, with certain fields included by default.
...
The ACT member can also add a custom new field to the form.
***In addition, the form creator may specify that accessors must be verified/certified users*** Either with a checkbox option, or a VerifiedUserList...
Each form includes a brief instruction given by the ACT.
...
Upon clicking Request Access, the user will be shown a form to fill out, and upon submitting the form, an email will be set to notify the ACT.
***TODO: The person filling out the form should be added automatically to the list of accessors.
The requestor can add multiple users for the access request by clicking "Add Accessor"
...
The requestor will be able to add accessors, remove accessors, change the research statement, or (optionally) upload files
Depending on what the requestor chooses, they will be shown a screen with those options for updating. Here is what choosing all three will look like:
Now the requestor can update the research statement:
The requestor can remove an accessor:
The requestor can add a different accessor:
edit all submitted fields:
On clicking Update, if anything is not filled in, the user will be shown an error message instructing them to fill in any fields they left blank.
To view all requests made on the dataset, an ACT member can navigate to the dataset and select "View Requests" from the tools menu. This will open a table:
After a request has been approved, the requestor may find that they want to update it. Submitting an update to the request will increment the version, and any accessors added will be missing the approval checkmark:
A requestor may also want to update the research statement:
Finally, the requestor may need to remove an accessor as well as adding a new one. The removed accessor would no longer appear in the list of accessors. In this way, we keep track of the list of all people with access to the dataset in the newest version of the request to allow for easy auditing.
Features of the table view:
Users that have been certified and verified (?) will have a symbol next to their synapse id (in this case a trophy) as an indicator. Users who have previously been approved for access to the dataset will have a check mark next to their name.
If the requestor updates their request, the fields they change will be highlighted for the ACT to more easily see. The version of the request will be incremented.
The ACT member can query the table to only show requests that are pending, or only ones that were approved or rejected. The latter requests will have their approve/reject buttons disabled.
...
____________________________________________________________________________________________________________________________________
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
____________________________________________________________________________________________________________________________________
...