galaxyproject / galaxyproject/brc-analytics
improve workflow tooling transparency
- Dominant language
- TypeScript
- Stars
- 7
- Forks
- 11
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 16
Description
sry for that maybe poorly named issue.. what im trying to capture here: right now we have names and descriptions of workflows, a link to iwc. thats cool, its a solid start. but if youre a user trying to choose a workflow, or decide if one that sounds right does what you want, it still seems unclear what exactly a workflow does from the brc site alone. it feels particularly true for the new de stepper where weve built out some ui kind of specific to deseq. we need to not just say it does differntial expression for rnaseq, we need to say it uses deseq to do that. (which de stepper is wip and we can work on separately so fine, i get that).. but i think this is a signal that as we build out ui for e2e analyses, and their particular tooling, this sort of general problem of workflow tooling transparency etc will become more critical.
ideally id love to be able to programmatically pick up a list of tools in a workflow, and have a bit of ui in brc that lets ppl search/ filter based on this, and show the list explicitly for any particular workflow.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.