Projects stand up meeting 2021-06-16: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
Line 23: | Line 23: | ||
=Ongoing projects= | =Ongoing projects= | ||
MOD imports | MOD imports | ||
* | * [https://github.com/orgs/geneontology/projects/58 MGI] | ||
* | * [https://github.com/orgs/geneontology/projects/59 WormBase] | ||
* | * [https://github.com/orgs/geneontology/projects/60 XenBase] | ||
* | * [https://github.com/orgs/geneontology/projects/61 SGD] (no tickets yet) | ||
Improve downloads | |||
* [https://github.com/orgs/geneontology/projects/57 Improve downloads] | |||
==Priorities== | ==Priorities== |
Revision as of 02:41, 10 June 2021
Attendees
- Present:
- Regrets:
- Managers: David, Huaiyu, Kimberly, Pascale, Seth, Suzi, Judy, Paul, Chris
Announcements
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?
Ongoing projects
MOD imports
Improve downloads
Priorities
GOC meeting Action Points
- Are any of these items high priority?