| Table of Contents | ||
|---|---|---|
|
...
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.
...
Clicking on "Show unmet conditions" takes user to a page that shows all AccessRequirements applied to the entity:From there, user can Create, Update their DataAccessRequest, and Cancel their submission.. For a TermsOfUse Access Requirement, user will be asked to sign:
For ACT Access Requirement, user will be asked to create a request:
If someone has submitted a request on the user behalf, they will see the status of the request:
If the user has submitted a request and awaiting for an ACT member to review, they can also cancel their submission.
After the submission is approved, a user will be able to update (add/remove user):
After a submission is rejected, a user will be asked to update information to complete the request:
Clicking on "Create Request," a dialog will show the ACT instructions to the user:
...