galaxyproject / galaxyproject/foundry
Evaluate Galaxy pattern for Nextflow workflow output index files
Open
agent/research
priority/v2
roadmap/off
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 3
- Avg merge
- 1d 22m
- Merged PRs (30d)
- 63
Description
Source open question from `content/research/nextflow-workflow-io-semantics.md`:
> Do workflow output `index` files deserve a target-side Galaxy pattern for preserving sample metadata beside published datasets?
Context:
- Modern Nextflow workflow outputs can write CSV, JSON, or YAML index files that preserve channel value structure.
- Galaxy translations may need an equivalent metadata sidecar/report pattern for sample labels and published dataset grouping.
- The decision affects output interface design and Galaxy workflow testability notes.
Related: #168, #174.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.