...
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
Example form:
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. User B is and clicks on "show unmet conditions" to get to the data access request form. If they are not logged in, then they will be met with this view:
Once they log in, then they will have the option to "Request Access":
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.
User B can see the status of request on the dataset with the ability to cancel own request.
An ACT member could go to the dataset link provided in the email. From the dataset view, the ACT member could query for the user request, and use a one click approval button, or They will see a queryable table of access requests for the given dataset (since each will have it's own schema).
After querying for only requests that are awaiting approval/rejection:
Now the ACT member can view the user request and their submitted form before approving their request. request with a one click approval button. Approval may grant access to one user, or to many (ACT will decide based on request).
The data contributor wants to know who has access to their data. Sage has been given report about approved requests including the following information: Principal Investigator, Institution, Date, and Intended Data Use Statement. Verify with Brian Bot (Unlicensed).
...