INCATools / INCATools/ontology-development-kit

Encourage documentation of QC pipeline by providing a blueprint

Open
#304 0 comments 0 reactions 0 assignees View on GitHub
documentation
Dominant language
Dockerfile
Stars
375
Forks
69
Avg merge
3d 5h
Merged PRs (30d)
7

Description

Maybe we can add a section in the README-editors.md, or create a [seperate doc ala HPO](https://github.com/obophenotype/human-phenotype-ontology/blob/master/src/ontology/QC.md). In any case it would be good if QC is clearly explained somewhere (on a by ontology basis, thinking of configurable ROBOT report levels and so on).

Contributor guide

Open the contributing guide

Research direction

Start by reading README-editors.md and the linked HPO QC.md example. Document how QC works on a per-ontology basis, including configurable ROBOT report levels. Done means the QC process and configuration options are clearly explained in an appropriate project document.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.