...
The following design fulfills SWC-52, SWC-121, SWC-157, SWC-159, SWC-160.
Adding Data to Synapse through the Web Client
Clicking "Tools > Upload File..." (or other mechanisms to trigger setting entity content / annotations?) opens a modified version of the current file upload dialog, reminding users of their obligations to restrict data:
The "guidelines" hyperlink takes the user to the detailed rules for restricting data. Clicking "Upload Restricted" results in (1) uploading the data, (2) launching the same dialog as when clicking the "About" hyperlink below.
The entity page for a data object having no access restrictions appears as follows:
The flag button is only enabled if If the user is logged in.Pressing , pressing the "Flag" button triggers this dialog:
Clicking "Contact ACT" the hyperlink will open a JIRA issue (in a dedicated, publicly readable "Synapse Flagged Data" JIRA project) prompting the user to give additional info, e.g. the user's email address, the object's Synapse ID and the reason for flagging the data.
If the user is not logged in, they are prompted to do so, then to return to the dialog.
A user may also click the "About..." hyperlink, which pops up another dialog. The dialog which appears depends on whether the user has admin access (more specifically 'change-permission' access) to the entity. If the user has administrative access, then the data icon button is enabled.Clicking the data icon triggers this dialogdialog appears as:
I
Clicking "Contact ACT" will open a JIRA issue (in a dedicated "Synapse ACT" Jira project) prompting the user to give additional info about the nature of the dataset, for use by the ACT in setting access restrictions. Also, download access is prevented (this restriction being removable by the ACT).
Clicking "Tools > Upload File..." opens a modified version of the current file upload dialog, reminding users of their obligations to restrict data:
The hyperlink takes the user to the detailed rules for restricting data.
Clicking "Upload Restriction" results in (1) uploading the data, (2) launching the same dialog as when pressing "Access".
If the user does NOT have administrative access to the data, the the following dialog appears:
The entity page for a data object having access restrictions appears as follows:
...
The flag button is only enabled if the user is logged in.The "Flag" button , and works as described above.
Clicking the data icon buttonAbout hyperlink, if the user has not fulfilled the terms of use, displays a dialog as described here:
:
(This example is for a "tier 2" restriction. The dialog for a "tier 3" restriction is slightly different. The details are described here: Data Restriction and Access Management)
If the user has already fulfilled the terms of use, the dialog will appear as:
