Feature requests for Dashboard on Stage: Clarify "download", "task"

[krobasky]

Upload/Download is confusing because we "upload" from our computer to ImmCellfie, but we "download" data from immunespace into immcellfie, and we also "download" data from ImmCellfie. Task/output" is also confusing because we use it to mean

On the "Data Source" -> "Immunespace" screen (see below):

• [x] Replace 'Download ID' with 'Dataset ID'
• [x] Replace 'CellFIE tasks' with 'CellFIE runs'
• [x] Replace 'Load new....' with 'Retrieve new...' on the screen & popup On the "Data Source" -> "Data upload" screen (see below):
• [x] Suggestion: Replace "Data upload" with "My computer" (or similar) On the "CellFIE" -> "Select CellFIE Task" panel (see below):
• [x] Replace "Select CellFIE Task" with "Select CellFIE Run"
• [ ] Replace "uploaded data" with "retrieved data"
• [ ] Replace "task_id:" with "run_id" On the "CellFIE" -> "CellFIE Output Visualizations" panel (see below):
• [ ] Replace "CellFIE Output Visualizations" with "CellFIE Run Output Visualizations"
• [x] Replace "Task started" with "Run started" On the top navigation bar (see below):
• [ ] Suggestion: Replace 'Input data' with 'Loaded Dataset' On 'Downloads' page (see below):
• [ ] Suggestion: Replace 'CellFIE output' with 'CellFIE Run output'
• [ ] Suggestion: Remove 'Phenotype data' and 'Expression data'? - I'm not sure we have license to repackage serve the data we retrieve from immunespace.

[davidborland]

I've implemented some of these. We can discuss the others.

Regarding the data download: if we are not going to enable downloading the phenotype and expression data (note that these are still available via the API if users really want it...), should we just remove the Download Data page and move the download CellFIE output button to the CellFIE output panel?

[krobasky]

@LauraCapps let's add this to the agenda for discussion with Immunespace guys: "can we allow users to download the data they import and transform from Immunespace"

@davidborland ... "import" is a good word, if you want to use that instead of "retrieve" - I see you've already made the changes to "retrieve", so its your call if you want to change it again. Either seems good to me.

David, one more:

• [ ] Suggest replace "No CellFIE output" with "No CellFIE run output"

[davidborland]

I like import. Will go with that for now. I'm less inclined to CellFIE run output in the various places, as it is more verbose, and I think CellFIE output works on its own. We can discuss though.

[krobasky]

I agree with you, but "CellFIE output" doesn't seem quite right, it doesn't indicate that each run has its own output, and it doesn't generalize well to other tools like PCA. How about "CellFIE resultset"? Then you might also have "PCA resultset", and you might somehow indicate the run_id that resultset is tied to, in case you want to check the parameters and dataset you used or something.

[davidborland]

• [ ] Remove "Data source"
• [x] Rename to CellFIE Run Results, perhaps with subtitle explaining in more detail
• [x] Move Download to Results page
• [x] Dataset selection
• [x] Rename "import" to "retrieve"

[krobasky]

Glossary of terms from this ticket disucssion:

• data source: upload file, Immunespace, example data, etc.
• dataset: set of data used for input to a tool run where the tool can be cellfie or something else. There's multiple datasets per
• datasource, and multiple runs per dataset
• run: formerly, 'task', is the job associated with a tool, a dataset, a distinct set of parameters, and ultimatelly, a redis job. There'
• can be multiple instances of the same run parameters, one per redis job
• resultset: one resultset per run, used for visualizations

• We need to capture this in a google to allow it to evolve and drive any necessary changes to the API

[krobasky]

@davidborland I captured the above in the txscience co-work team meetings, we can add/modify it from there

https://docs.google.com/document/d/1UBQmzMnQvjfAD_nl9SKDimW0bcSOFv2BV1ncP4XWWH0/edit

[davidborland]

Implemented