QCQA next call

From GO Wiki
Revision as of 01:51, 25 September 2018 by Pascale (talk | contribs)
Jump to navigation Jump to search

http://wiki.geneontology.org/index.php/QCQA_call_2018-08-21

New error reports

http://snapshot.geneontology.org/reports/gorule-report.html Discuss - feedback and priorities

github tickets

Ontology tracker

How to blacklist papers

This would include retracted papers and predatory journals https://github.com/geneontology/go-annotation/issues/2029

New QC check?

Reported from the previous meeting

  • Should Taxon checks be a hard check:

https://github.com/geneontology/go-site/issues/660 https://github.com/geneontology/go-site/issues/758

  • Unmaintained annotation sets:

https://github.com/geneontology/go-annotation/issues/1724#issuecomment-390136730

TIGR, JCVI, PAMGO ISS annotations: Michelle: The ISS annotations from at least TIGR (and should be also JCVI and PAMGO) were all manual. They were either matches to HMMs or based on pairwise alignments. We used IEA for any annotations that were automatic from our pipeline and not reviewed. I assume JCVI continued that process after I left - at least until they stopped using their pipeline and shifted completely to using the NCBI PGAP tool (prokaryotic genome annotation pipeline). I think we (and hopefully PAMGO) were pretty good about using the GO_REFs to indicate whether it was HMM or pairwise. The problem with replacing our HMM annotations with InterPro2GO mappings is that we made much more specific annotations based on HMMs than what the InterPro mappings often do. I'd hate to lose those but I understand your desire to keep the annotations current.

  • GO-CAM QC plan
    • including SynGO, > 90 % of the production models