Open jaredroach opened 1 month ago
I can't really remember why we don't have this anymore
We removed the download feature due to the constant changes to the format of results, which would require a rework every time something changes in trapi. We intended to add that back in once the format of results stabilizes at some point in the future (from when we removed the feature).
If there's desire to add that feature back in presently we can do so, likely after the treats refactor changes have fully propagated.
perhaps we can revisit in Hammerhead planning
Or don't let the perfect stand in the way of excellent. Being able to download a list (in any format, e.g., return-delimited) of merely the names of the hits would be extremely useful. 98% of the value is in this list. All the extra annotation is nice to explore but adds only 2% to the value of the download, as exploration can be done manually through the interface.
@dnsmith124, I am glad @jaredroach brought up this issue.
I had noticed that download feature had disappeared inexplicably and apparently without wide consensus from the consortium (or at least it wasn't reported as an agreed decision.)
Yet, aren't the upcoming SME sessions in the September Relay conducted in the Translator UI, where the download feature will come in useful, however flawed or minimal?
@codewarrior2000 @jaredroach I appreciate the additional context here, we will revisit adding the download feature back in the future.
@dnsmith124 is this on the roadmap for Hammerhead as the tag implies?
I couldn't find a button to download the results to a csv or EXCEL file. If I can't do that, then the whole Translator UI is a dead end in terms of a bioinformatics workflow.
Note: Issue created in pursuit of this task for teams Expander Agent & Multiomics Provider, as mentioned 7/19/24 in the TAQA meeting notes https://docs.google.com/document/d/1eWwa-sC5xxghu7SNPsXEmUvis52njpT6-2YNzjIr-vA/edit: In addition to those universal priorities, we are asking each team/priority owner to take ownership of their work throughout the release process. That includes: Manually testing in TEST https://ui.test.transltr.io/.and creating issues as needed in the Feedback Repo