The Synapse Web Client provides a mechanism for end users to create and review access restrictions on entities.
The following design fulfills SWC-52, SWC-121, SWC-157, SWC-159, SWC-160.
The entity page for a data object having no access restrictions appears as follows:
The flag button is only enabled if the user is logged in.
Pressing the "Flag" button triggers this dialog:
Clicking "Contact ACT" 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 has admin access (more specifically 'change-permission' access) to the entity, then the data icon button is enabled.
Clicking the data icon triggers this dialog:
I
Clicking "Contact ACT" will open a JIRA issue (in a dedicated "Synapse ACT" 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 clicking the data icon.
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 works as described above.
Clicking the data icon button, if the user has not fulfilled the terms of use, displays a dialog as described here:
If the user has already fulfilled the terms of use, the dialog will appear as:
