Study details stand alone page and/or tab for "Prerelease" and "Private" studies

[SheenaTomko]

Jay loaded the study characteristics and everything from the ClinEpiPresenter that's needed for the all studies table and study details page for the "Prerelease" studies: India ICEMR DAMaN Quasi-experimental Stepped-wedge, LAKANA Cluster Randomized Trial, Namibia rfMDA RAVC Cluster Randomized Trial, and PERCH Case Control.

We would like a user to be able to click on the name of this study and be re-directed to the study details tab for it. However, at the moment, the user first gets a pop-up like the one below, and if they click the link, they get a page with an error message.

Error message:

As a reminder, "Prerelease" studies are studies with data that we plan to load (and in some cases have already loaded), where we want the study card and study page to be publicly accessible before the data is released.

Proposal:

1. Have all links for a "Prerelease" study re-direct to the "View study details" tab
2. Grey out all other tabs (Browse and Subset, Visualize, etc.) and make them unclickable or remove them completely
3. Remove the entity diagram
4. Remove the "New Analysis", "My analyses", and "Make Analysis Public" links
5. If someone is logged into a ClinEpi account that has access to the study, and there is real data loaded, they should be able to see the EDA appear as normal for that study (this can be done for a later release if needed)

[bobular]

DF: Simplest path could be a standalone study record page (instead of as first tab in EDA)

[danicahelb]

Discussed in 1/28/2022 EDA meeting:

Stand-alone study pages are needed for both prerelease and private studies. Currently, users cannot access the study page (the link in the popup currently takes you to “Page not found”; we need this link to take the user to a stand-alone study page)

• We need a new attribute in the presenter so that the client code can discover that there is no data. This attribute will only be filled out for studies with no data (or for studies where Jay has loaded dummy data)

- Note: studies that are pre-release on the live site are private on the QA site so that providers for various studies cannot access data from other studies before it is released

For private studies:

• Data is always loaded
• The stand-alone study page should have a banner with a link for providers/users to login or submit a request
• Users must have an approved access request to see even aggregate data
• We will manually give study providers access to their private studies. When logged in, providers should be able to access all EDA tabs (view study page, browse & subset, visualize, notes, and download)

For prerelease studies where data is available on the live site:

• The stand-alone study page should have a banner indicating that data is not yet available and that users can contact the original study team directly for the data before it is made available on ClinEpiDB Verbiage currently used on WDK site for Namibia is fine: This study has not yet been released. For more information, please email Michelle Hsiang at michelle.hsiang@utsouthwestern.edu.
• We will manually give study providers access to their private studies. When logged in, providers should be able to access all EDA tabs (view study page, browse & subset, visualize, notes, and download). Note: the banner will not contain a link for providers to login. Most providers are going to be looking at unreleased data through the qa site anway
• Users cannot request access to study data through ClinEpiDB

For prerelease studies where data is NOT yet available on the live site:

• Pre-release studies with no data should just have access to the stand-alone study page
• The stand-alone study page should have a banner indicating that data is not yet available and that users can contact the original study team directly for the data before it is made available on ClinEpiDB Verbiage currently used on WDK site for Namibia is fine: This study has not yet been released. For more information, please email Michelle Hsiang at michelle.hsiang@utsouthwestern.edu.
• Users cannot request access to study data through ClinEpiDB
• Providers will only be able to see the stand-alone study page and will not be able to access all EDA tabs (because data has not yet been loaded)

[dmfalke]

Note: I did not add the banner to the page for private studies. We hadn't done this in the past, so I thought I would ask. It shouldn't be too hard to add.

[nkittur-uga]

So...this one is almost there. When I try to access a private/prerelease study, I get this error pop-up, however when I chose the error pop-up, the study page is there and looks great.

[dmfalke]

Ah, strange. That wasn’t happening on my development site. I’ll take a look!

On Wed, Feb 16, 2022 at 9:34 AM nkittur-uga @.***> wrote:

So...this one is almost there. When I try to access a private/prerelease study, I get this error pop-up, however when I chose the error pop-up, the study page is there and looks great. [image: Screen Shot 2022-02-16 at 9 32 40 AM] https://user-images.githubusercontent.com/67710160/154286484-50f92384-76dd-4802-b251-44234c16c2f5.png

— Reply to this email directly, view it on GitHub https://github.com/VEuPathDB/web-eda/issues/809#issuecomment-1041555317, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACZEU7D3NWZYOENHLSZ5NTU3OYYVANCNFSM5MWNPZPA . You are receiving this because you modified the open/close state.Message ID: @.***>

[dmfalke]

I am not able to reproduce. In what browser is this happening?

[nkittur-uga]

Chrome.

[nkittur-uga]

All studies denoted "Private" need a button on the study page to request access to the data.

Clicking on this button will prompt users to log in, and if their accounts have been added as study team members, then they can access the data for QA. This feature isn’t essential for b56, but should be prioritized right after all essential functionality for b56 is done, because study teams will be looking at their private studies for QA.

[dmfalke]

Chrome.

I'm still unable to reproduce this. Is this happening consistently for you?

[nkittur-uga]

Yes, unfortunately still happening for all private and prerelease studies.

[dmfalke]

I'm going to need some more details about this error. Maybe we can chat on slack later.

[dmfalke]

All studies denoted "Private" need a button on the study page to request access to the data.

Clicking on this button will prompt users to log in, and if their accounts have been added as study team members, then they can access the data for QA. This feature isn’t essential for b56, but should be prioritized right after all essential functionality for b56 is done, because study teams will be looking at their private studies for QA.

Ah, yes, this makes sense. Since we are redirecting to the standalone page, the typical popup is not seen. I will work on this.

[nkittur-uga]

Banner is seen as expected.