Annotation Conf. Call 2019-07-09: Difference between revisions
Jump to navigation
Jump to search
Line 19: | Line 19: | ||
== GO-CAMs and Annotation Extensions == | == GO-CAMs and Annotation Extensions == | ||
* After USC hackathon in June, we formed a small working group to | * After USC hackathon in June, we formed a small working group to fully articulate the GO-CAM model specifications | ||
* This will allow uniform QC across workbenches, projects (e.g. Reactome and MOD imports) | * This will allow uniform QC across workbenches, projects (e.g. Reactome and MOD imports) | ||
* Will also allow us to move forward with harmonizing AE relations used in GO-CAM and conventional annotation | * Will also allow us to move forward with harmonizing AE relations used in GO-CAM and conventional annotation |
Revision as of 09:32, 9 July 2019
Agenda
github submission for InterPro2GO mappings
- Tagging InterPro in issues
- Lorna has requested that we tag InterPro curators so they can be alerted to issues relevant to them (can find relevant gitHub handles on the group-contacts.yaml file: https://github.com/geneontology/go-site/blob/master/metadata/group-contacts.csv)
- Please also add the InterPro mapping label (always good practice to add labels)
Protein oligomerization terms in GO
- Follow up to 2019-06-11 annotation conference call to review recommendations and actions
- Gitter question from Petra
QC Reports
Pipeline Reports
Matrix QC checks
- How is this work going for people?
- Questions, comments?
GO-CAMs and Annotation Extensions
- After USC hackathon in June, we formed a small working group to fully articulate the GO-CAM model specifications
- This will allow uniform QC across workbenches, projects (e.g. Reactome and MOD imports)
- Will also allow us to move forward with harmonizing AE relations used in GO-CAM and conventional annotation
Minutes
- Present: