PEPhub could accommodate pipeline result attributes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
This is a long-term feature request I wanted to record.
In its early state, PEPhub is viewed as a metadata server. In the long term, users could also report pipeline results to the sample table, as we often do when running a pipeline to create an "output" table.
In other words, right now PEPhub is focused on input sample tables, but it could be extended to work as a system also for output tables.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin by reviewing PEPhub's existing web API and database support for input sample tables, then identify how pipeline result attributes and output tables would fit. Done would mean a defined and implemented path for reporting pipeline results alongside the current input metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100