-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update data accessibility info in Study details & Download tabs, specifying that access requests are pending #1150
Update data accessibility info in Study details & Download tabs, specifying that access requests are pending #1150
Comments
fyi: #1143 (comment) |
in fut (steve, dave and i) on Jan 5 2023, we propose the following: the backend part in (3) and (4) is in VEuPathDB/service-dataset-access#55 |
In addition to the above Danica notices:
|
Just to clarify (1): Update the verbiage as follows: Data Accessibility: Protected Data Accessibility: Controlled Data Accessibility: Public Data Accesibility: Prerelease |
Would the current plan mean this ticket is obsolete? |
It appears the backend is ready to support this. |
@danicahelb i think the answer is no.. not obsolete |
related to VEuPathDB/EbrcWebsiteCommon#127 |
Blocked by VEuPathDB/service-dataset-access#57 |
Hi Danica, do we want the Prelease verbiage to mention ClineEpi specifically? I thought that was something we were avoiding due to code being used in multiple sites |
good catch @chowington! you can say |
Not yet done actually---waiting for a review on #1592 |
Hey @chowington, the updates are appearing on the
Also, pre-release studies does not show what we intended (maybe because changes have not been made to study details page:
Also, sorry I messed up in writing this ticket. For controlled studies, the verbiage should be:
|
Fixed by #1676 |
@danicahelb, this should now be ready for qa again |
looks perfect, thanks @chowington |
Related to: #1172 and VEuPathDB/EbrcWebsiteCommon#143
Discussed in 5/20/2022 EDA UX meeting. We will add responsive messaging on the download and study details tabs, immediately below the tabs (above all download buttons and links).
We are currently differentiating (1) users who were not logged in / did not have access from (2) users who had access.
In this ticket, we want to differentiate a third group: (3) users who submitted a request FOR A PROTECTED STUDY but the request is still pending.
For users whose access requests are pending (relevant to protected studies only):
Notes:
- For public studies, anyone can download the data so we don't need verbiage pending requests.
- For controlled studies, access requests are approved immediately upon submission and do not need verbiage for pending requests.
The text was updated successfully, but these errors were encountered: