BDS Ontology output validation

[hkir-dev]

BDS ontology started to become complex and some pieces of the ontology is optional due to species specific data availability differences (such as allen descriptions and dataset info does not exist for the most of the species except mouse). This optional processing makes system run without failure even some necessary data are missing (mouse allen descriptions etc.). To assure quality of the generated ontology, a post validation logic is required.

Some of the validations are:

• Allen descriptions exists (for mouse)
• Taxonomy metadata exists (for all species)
• Taxonomy has Allen details (mouse only)
• Allen dataset metadata exists (only mouse)
• Allen ontology is generated and it has color information (for mouse, human, marmoset but hot for MTG)
• Class manual curations exists in the ontology (All)
• Homologous to relations exists (except MTG)
• Different entities don't have the same label

[dosumis]

Define minimal requirement for taxonomy => pass/fail criterion.
Add some stricter criteria that are configured on a per-taxonomy basis.
For everything else generate warning logs?

@hkir-dev & @shawntanzk to write draft spec/implementation.