OBO Dashboard

[jamesaoverton]

The is a "catchall" issue for progress on the OBO Dashboard. See a test version here:

http://obo-dashboard-test.ontodev.com/

Some have been discussed so far:

1. Open Principle #1 open - automated validation #1019 [discussed]
2. Common Format Principle #2 common format - automated validation #1018 [discussed]
3. Identifier Space Principle #3 IDs - automated validation #1017 [discussed]
4. Versioning Principle #4 versioning - automated validation #1016 [discussed]
5. Scope Principle #5 scope - automated validation #1015
6. Textual Definitions Principle #6 definitions - automated validation #1010
7. Relations Principle #7 relations - automated validation mechanism #981
8. Documentation Principle #8 documentation - automated validation #1009
9. Documented Plurality of Users Principle #9 users - automated validation #1008
10. Locus of Authority Principle #11 authority - automated validation #1007
11. Naming Conventions Principle #12 naming conventions - automated validation #1006
12. Maintenance Principle #16 maintenance - automated validation #1020

These checks run on Jenkins, where a zip folder containing the results is archived: https://build.obolibrary.io/job/obofoundry/job/OBOFoundry.github.io/job/master/

A full build takes 6 to 7 hours.

Documentation pages have been added for each automated check. They can be accessed from their principle page.

[mellybelly]

I LOVE the new dashboard! Truly fantastic work!

A few questions:
Is there a rule to have all properties in RO?
See SEPIO report: http://obo-dashboard-test.ontodev.com/reports/principles/fp7-sepio.tsv

Also can we update the license so as to include CC BY 4.0 as allowable?

Finally, what do the final two columns mean exactly?

[jamesaoverton]

Thanks @mellybelly.

• For FP7 Relations, our current test is here: http://obofoundry.org/principles/checks/fp_007
  • ERROR if the ontology defines a relation (object property) with the same label as an RO relation; for example:
    • SEPIO defines 'expresses' which is also in RO
    • OBI defines 'supplies' which is also in RO
  • INFO if the ontology defines relations (object properties) not in RO; I think this is fine, but there is some debate; the specific issue is Principle #7 relations - automated validation mechanism #981
• CC BY 4.0 is an accepted license. The warning for SEPIO is for the wrong license predicate. Many projects have been using an non-existent Dublin Core predicate to indicate the license, see We have been using the wrong dublin core URI to indicate license all this time #540
• we're revising the table for clarity, but currently
  • "Report" means the result of robot report and links to that output as a TSV file
  • "Summary" is the worst value of all the previous columns, as a summary of all the checks

[mellybelly]

got it! On it!

[nicolevasilevsky]

I love this, it seems super useful. Great work @beckyjackson and all that were involved.

Minor feature request - could you freeze the top row, so you can still see it when you scroll down?

[wdduncan]

Can we add this to ODK? That way developers can check their ontology locally using a dashboard. I know that can run robot report and output a tsv, but have a visually interface would be a nice enhancement.
Or perhaps just putting in a Docker container would be enough.

[beckyjackson]

@nicolevasilevsky - I think that's a great idea. I'll add that in.

@wdduncan - Right now, the dashboard runs over everything at once, but I'm updating it to run over one ontology at a time so that we can automatically run it as things change (e.g., new release, registry metadata is updated...). I'm adding in functionality to click on each ontology ID and see the dashboard details for just that ontology as well (another HTML page).

[wdduncan]

@beckyjackson Thanks! Let me know if I can help.

[nicolevasilevsky]

When I hover over the definitions cell for Mondo, I see the issues (which is very handy!) and it says see ROBOT report for details - but it's not clear to me how to get to that report.

[jamesaoverton]

@nicolevasilevsky Each ontology has its own page with more details. From the main table, click the name of the ontology in the first column. The details page links to the full ROBOT report, at the bottom.

It probably makes sense for us to add a link in the tooltip you’re describing.

Thanks for the feedback!

[iamkoehler]

I like it a lot. Issues I had:

• Like @nicolevasilevsky , I also struggled to find the actual report.
• I wonder what the sorting of ontologies means? Why not alphabetic? It took me a while to find HPO.
• For HPO, it say robot has 3 errors, but in the report it is only one. Why?

[matentzn]

I wanted to jump to explain how the ordering follows the default OBO foundry website ordering, but I have to agree with you seb, it took me a long time to spot the HP in the list. I also think simple alphabetical order would be good. Also I agree with your second comment. The robot report error count seems misleading. There is really just one!

[iamkoehler]

@matentzn and this one error will also be gone with the next release! hooray!