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

[danicahelb]

@SheenaTomko can you please flesh out this ticket?

[danicahelb]

Info from @aurreco-uga

b63: work on vdi

• vdi (veupathdb dataset installer) is the new UD/DIY infrastructure
• vdi uses minio like other services use minio (compute service, mblast)
• vdi will be used for user studies and also for curated genomics data loading
• This will allow us to generate the unidb, one database serving all genomic websites.

b64: vdi, feature in vdi

[aurreco-uga]

2 features:

1- 'released' UDs: 2 types

• by users: show in menus/tables in its own section
• by us: QO requires "released" UDs with public access by us (internal?); should show in menus and tables as curated. or maybe they ll show in a new way: different UDs at time points, under one study?

anyone can share analyses on released studies (generate url, access url, make a copy, reshare).

2- for 'non released' UDs, offer owner option to allow sharing analyses, or not (default).

Possible plan for 1 in current system, PLAN:

• eda access service: --- based on database UD status ("released" == shared table "all") make it available in response for the current user, using new property "isReleased: true"
• client/UI : use the new property: --- add new section in menu and all studies page with the “released" UDs. --- UD workspace: owner, share column “released” (no need to show these in UD workspace for recipients.)

LIMITATIONS:

• we release a user study by manually updating the installed UD in appDB (where do we keep track?)
• no access control: all are "public" (no owner ability to modify UD or access control)
• no UD updates (edit name, or modify content)
• unclear if UDs will be migrated to vdi