Projects stand up meeting 2021-06-16: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
Line 21: Line 21:


==Data load frequency in Noctua==
==Data load frequency in Noctua==
Updates are infrequent in Noctua, especially for GO terms it would be very useful for curators to have more frequent data loads.
* Updates are infrequent in Noctua, especially for GO terms it would be very useful for curators to have more frequent data loads.
* This is a long-standing issue and there's been discussion of this in a noctua ticket, as well as in meetings, jamborees, etc.:  https://github.com/geneontology/noctua/issues/710


=Ongoing projects=
=Ongoing projects=

Revision as of 17:08, 15 June 2021

Attendees

  • Present:
  • Regrets:
  • Managers: David, Huaiyu, Kimberly, Pascale, Seth, Suzi, Judy, Paul, Chris

Announcements

GOC meeting dates: Oct 13-15 (Wed to Friday) -> is that our final decision?

Discussion points

User stories / use cases

A user requests annotations for Chlorocebus sabaeus (Vervet - green monkey) in a .gaf (gzip) format (Helpdesk ticket: https://github.com/geneontology/helpdesk/issues/319). This is certainly something GO users expect we can deliver.

  • Issues:
    • We dont have IEAs, and anyway our plan was to fully load annotations from 142 species, and none from other species. Do we have any guidelines for this specific use case? Do we direct users to GOA? Can we set up a special API call to QuickGO?
    • Alternatively, could we generate files (even if only once a year) for many species, without them being in the 'main pipeline', but so that people could get data for their analyses ?
    • This might include Tree Grafter data, as this seems non-trivial to ask users to run this themselves

Release delays

Some delays are caused by upstream sources, and groups cannot always give a new file quickly. Is there a date in the month at which we should decide to go ahead with the release, and use the last correct file for that upstream?


Data load frequency in Noctua

  • Updates are infrequent in Noctua, especially for GO terms it would be very useful for curators to have more frequent data loads.
  • This is a long-standing issue and there's been discussion of this in a noctua ticket, as well as in meetings, jamborees, etc.: https://github.com/geneontology/noctua/issues/710

Ongoing projects

MOD imports

  • Projects are progressing such that we will need a dedicated software developer to help with the GPAD output.
  • MGI
  • WormBase
  • XenBase
  • SGD (no tickets yet)

Pipeline

Priorities

https://docs.google.com/spreadsheets/d/19-i43w0mGQdFYmKXqskVIgrDO-pVTWo1YgjaWa5PI1o/edit#gid=68094648

GOC meeting Action Points

action items

  • Are any of these items high priority?
Retrieved from "https://wiki.geneontology.org/index.php?title=Projects_stand_up_meeting_2021-06-16&oldid=80257"