Versions Compared

Key

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

...

According to the governance team’s evaluation of this project, all files should be under a click-wrap data embargo AR (AR.id = 1). In addition, any file with an assayType= genomic and patient country = Germany, should be under a click-wrap that informs the user that the data file cannot leave Germany (AR.Id = 2). According to these rule syn1 should be under AR.ID = 2, while all files should be under AR.ID = 1.

Add MaterializedView to show the join.

Implementation Phases

There are a lot of areas that will need changes/improvements. Therefore, we will break up the implementation work into phases:

...

  • If the caller is an Admin, then GRANT

  • If the caller is a member of the ACT, then GRANT

  • If user is not validated, then DENY

  • If the caller is anonymous, then DENY

  • If the caller is has the “REVIEW” “REVIEW_SUBMISSIONS” permission on the AR, then GRANT

  • All other cases, then DENY

...

  • Creating/updating ACLs on ARs - This would be a new feature that would allow a member of the ACT to create an ACL on an existing AR. Only a member of the ACT would be allowed to create/update these ACLs. The ACT member would grant a non-ACT user permission, to “REVIEW” “REVIEW_SUBMISSIONS” submissions to this by updating this ACL. Note: ACT members will automatically retain the “REVIEW” “REVIEW_SUBMISSIONS” permission for all ARs even if not explicitly listed in the ACL of that AR. Any AR that does not have an ACL will still be fully accessible by members of the ACT.

  • GET /dataAccessSubmission/openSubmissions - This services would need to be changed to list open submission for any user that has been granted the “REVIEW” “REVIEW_SUBMISSIONS” permission. Should an ACT member also see listings for submissions to ARs that have granted non-ACT members “REVIEW”“REVIEW_SUBMISSIONS”?

  • POST /accessRequirement/{requirementId}/submissions - This service would need to be changed similar to the above.

  • PUT /dataAccessSubmission/{submissionId} - This service would need to be changed similar to the above.

  • DELETE /dataAccessSubmission/{submissionId} - This service would need to be changed similar to the above.

...