| 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.
...
For TermsOfUseAccessRequirement:
For ACTAcessRequirement:
After creating an AccessRequirement, an ACT member will be directed to a page to manage the created AccessRequirement:
For an ACTAccessRequirement, an ACT member will be able to find the DataAccessSubmissions that need to be reviewed:
Requesting Access
From a controlled entity page, a user will see the "Show unmet conditions" button:
...