Add review process
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 21
- Forks
- 11
- Avg merge
- 12h 5m
- Merged PRs (30d)
- 24
Description
The user can override the pass/fail decision that the pipeline made for each sample/region, as well as for an entire sample or region. Display a check mark or X for manual pass or fail.
The user can also mark the run as reviewed. Confirm if any samples were overridden or if the run has already been reviewed.
Log who reviewed the run and when, along with which samples were overridden.
Create another issue for reviewing after a new version of the pipeline has rerun a run that you reviewed. Should highlight differences with the previous run by showing question marks.
- Display an info box when you click on a sample region. The box displays the sample name, the region name, the raw counts, mapped counts, minimum coverage, minimum coverage position.
- Add pass / fail radio buttons to the info box that show a cross or check mark.
- Use short cut keys: (c)heck, (x)cross, and (z)blank. Codes 67, 88, and 90.
- Save to the database when a sample is reviewed.
- Add buttons to accept pipeline decisions on a whole row or column.
- Add a review button at the bottom, along with a display of who reviewed and when.
- Confirm with the user if any samples were overridden.
- Show history of pipeline runs and reviews for a sample below the info box.
- Create issue for reviewing after a new version of the pipeline has run.
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
Start by reviewing the existing sample-region info box and the checked items in this issue, then map each unchecked item to the current pipeline, sample, and run data handling. The work is done when review decisions, reviewer metadata, override confirmation, history, and whole-row or column actions are implemented, with the requested follow-up issue created for reruns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- bioinformatics, databases, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100