Revision as of 20:01, 22 July 2021

Attendees

GOC meeting dates: Oct 13-15 (Wed to Friday)

There are some data issues with these annotations
- Use of an obsolete ECO code - https://github.com/geneontology/noctua/issues/726
  - It would be good to at least update the obsolete ECO code in the GO-CAMs
- Use of IMP for CC in possibly a different way than standard annotations - RGD has asked about this
- Uniprot IDs from SYNGO models aren't in NEO - https://github.com/geneontology/noctua/issues/693
- Harmonize SynGO's use of UniProt identifiers and MOD identifiers - https://github.com/geneontology/go-site/issues/1568
- Try contacting SynGO about this before updating any .ttl files in the noctua-models repo?
  - Other places SynGO data resides, e.g. Protein2GO?
Where does all of this stand in our project priority list?
Wait until we've finished up other projects?
Add to the existing project but don't start on the work yet?
Invite Dustin to a call?
More generally, people are asking about importing annotations
- What formats?
- Documentation?

Kimberly and David described tasks - not all tickets are assigned yet; need Jim and probably Sierra

- Jim assigned the tickets with the 'imports' label; this is high priority
- Sierra will be tagged, so she can be trained
We need to schedule Jim's time for this - post RHEA jamboree?

MGI -> waiting for GPAD
WormBase -> waiting for GPAD and round trip before asking Alex changed to the GPAD export he produces
XenBase
SGD (no tickets yet)
ZFIN -> no project; all errors and bugs have been corrected; need to roll out

Tremayne, Laurent-Philippe, Kimberly, David

GPAD project
NEO : fix/refactor to make more robust and add more species/chains(?) (and maybe automate some parts like periodic reloading)
- NEXT: schedule a planning meeting

@@ Line 53: / Line 53: @@
 ===Model Copy===
 * Review requirements
+** https://github.com/geneontology/noctua/issues/606
 * Next steps