QCQA next call: Difference between revisions
mNo edit summary |
|||
| Line 39: | Line 39: | ||
**Can we come up with a proposal for the Montreal meeting? | **Can we come up with a proposal for the Montreal meeting? | ||
**http://wiki.geneontology.org/index.php/2018_Montreal_GOC_Meeting_Agenda#Handling_redundant_information | **http://wiki.geneontology.org/index.php/2018_Montreal_GOC_Meeting_Agenda#Handling_redundant_information | ||
** see https://github.com/geneontology/amigo/issues/43 and https://github.com/geneontology/amigo/issues/440 | |||
* GO-CAM QC plan | * GO-CAM QC plan | ||
Revision as of 10:57, 2 October 2018
http://wiki.geneontology.org/index.php/QCQA_call_2018-08-21
New error reports
http://snapshot.geneontology.org/reports/gorule-report.html https://github.com/geneontology/go-site/issues/709
- 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?
- Check for genes annotated to an MF as well as BP 'regulation of that same MF'?
- Would that ever make sense?
- See https://www.uniprot.org/uniprot/Q7Z7L7 as an example
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.
- SPKW hierarchy - at odds with transitivity as found in GO ontology?
- https://github.com/geneontology/go-annotation/issues/2036
- emailed Chris, Seth about help with querying the GO database for non-redundant SPKW-based annotations (2018-08-16)
- Annotation redundancy - non-experimental annotations
- Can we come up with a proposal for the Montreal meeting?
- http://wiki.geneontology.org/index.php/2018_Montreal_GOC_Meeting_Agenda#Handling_redundant_information
- see https://github.com/geneontology/amigo/issues/43 and https://github.com/geneontology/amigo/issues/440
- GO-CAM QC plan
- including SynGO, > 90 % of the production models