VDI User datasets - allow users to release their own datasets (mockups UI)

[danicahelb]

Finalize UI and verbiage to allow users to release their own datasets

[danicahelb]

For more details see 4/21 user dataset notes: https://veupathdb.atlassian.net/wiki/spaces/WG/pages/251658241/2023-04-21+DIY+meeting+notes

We will have 3 “classes” of studies:

1. Curated studies - integrated by VEuPath team with harmonized ontology

   • no change needed

2. Community studies - user datasets with Protected, Controlled, or Public restrictions

   • Will be fully visible to anyone who comes to the website & will function the same as curated studies

3. My studies - user datasets with Private restrictions

   • Will be invisible to anyone who is NOT an owner
   • Owners can view & download
   • Analyses can be shared amongst owners

For both Community studies and My studies:

The person who originally uploaded the dataset is the Owner-Manager.

• Owner-managers can assign additional owner-managers
• Owner-managers can edit data and metadata, delete the study or change access restrictions
• Only Owner-Managers can grant access to others by adding them as owners

Owners are people who the Owner-Manager manually added via the access dashboard

• Owners can view the data but they cannot edit it, delete it, share it with others, or change access restrictions
• Being an Owner is the only way to view a Private user dataset (ie, My studies) on the website
• Owners can download the data from Community studies or My studies without submitting an access request.

Non-owners are those who have never been assigned Owner status via the access dashboard

• Non-owners never see private user datasets (ie, My studies)
• Non-owners can see Community study data in aggregate and can explore with EDA tools (B&S, visualize)
• Non-owners must submit a data access request to download Controlled or Protected Community studies
• Non-owners can download Public Community studies without submitting an access request

Frontend UX work needed:

• 3 labeled headers dividing studies into My studies, Community Studies, or Curated Studies classes for the Studies dropdown in the header
• 3 separate tables with these headers on the study summaries page
• UI to allow owner-managers (ie, the person uploading a study) to determine the appropriate access level for their user dataset
• UI to allow owner-managers to use the dataset access dashboard to field requests to download data if Controlled or Protected restrictions are selected
• Manually add additional owners or owner-managers (ie, VEuPathDB accounts)
• Messaging for analyses shared with non-owners of “My studies” (ie, those who do not have access to that user dataset) --> redirect to a page instructing them to ask an owner-manager to give them owner permissions

TBD - verbiage for My studies:

• Owner vs Collaborator vs Viewer
• Owner-manager vs Owner

[aurreco-uga]

slack May 8 2024 danica cristina this is the easy phase 0 version of this, with no study access levels, no curation.

1. enable public user studies -UI: checkbox to make it public or not -steve: ----database control table: flag, ----vdi service: update flag in database (is public on/off) ----model: new attribute ispublic for UDs.. -eda permissions endpoint to read the new flag.? -UI: header menu, all datasets page: list 3 sections: curated, community and my studies -UI: user datasets table: new column ispublic

2 MAYBE: add data dictionary file

• client: you need 2 files upload: data and data dictionary (tab o rcsv file with column definitions)
• update vdi service/isasimple plugin: 2 files, validation..