GO-CAM November 22, 2017: Difference between revisions
Jump to navigation
Jump to search
Line 35: | Line 35: | ||
=== export-lego-to-gpad-sparql should collate by MOD === | === export-lego-to-gpad-sparql should collate by MOD === | ||
*[https://github.com/geneontology/go-site/issues/431 github ticket #431 - export-lego-to-gpad-sparql should collate by MOD] | *[https://github.com/geneontology/go-site/issues/431 go-site github ticket #431 - export-lego-to-gpad-sparql should collate by MOD] | ||
= MInutes = | = MInutes = |
Revision as of 11:45, 21 November 2017
Zoom URL
https://stanford.zoom.us/j/679970729
Agenda
Updates/Discussion on 1.0 Release Milestones
Annotation Attribution in GPAD Output Files
- noctua github ticket #458 - Attribution with GO-CAM exports to GOC annotation files
- noctua github ticket #502 - providedBy should be used in GPAD export
- go-site github ticket #453 - All Noctua curators should have "updated" metadata associated in the YAML file (including group and URI)
- Issue summary: we want to make sure that, in the GPAD files, attribution in the 'Assigned By' field is correctly populated with a curator's annotation group
- Is this a good time to clean house wrt older or test models?
- Step 1: Curators need to have entries in the groups field of the users.yaml file
- Some groups still need to review their users.yaml (missing groups and also missing orcids):
- USC
- UniProt (SIB and EBI)
- PomBase
- FlyBase
- SynGO
- Xenbase
- Groups that are okay:
- BHF-UCL
- dictyBase
- MGI
- SGD
- TAIR
- WB
- Zfin
- Some groups still need to review their users.yaml (missing groups and also missing orcids):
- Step 2: Convert any remaining GOC:nn identifiers to orcids
- Step 1: Curators need to have entries in the groups field of the users.yaml file
Display user and group labels from minerva metadata
Allow negation in Noctua and SAE and in GPAD export
export-lego-to-gpad-sparql should collate by MOD
MInutes
- On call: