Open dustine32 opened 3 years ago
Thanks @dustine32 !
Can we clearly specify which GO release was used?
Also - I dont think we load the xx-isoform.gaf.gz and xx-RNA.gaf.gz files in PAINT.
Thanks, Pascale
@pgaudet We do pull the GO release's release-date.json
, which I use to grab the date to construct the http://release.geneontology.org/2021-05-01/ URL. Should I add a line to the top like GO release date: 2021-05-01
?
I am not exactly sure what the final Readme will look like, but to be sure it'd be good to have the date very visible, so I'd say to add the date at the top, yes.
Thanks, Pascale
Le jeu. 3 juin 2021 à 8:12 PM, dustine32 @.***> a écrit :
@pgaudet https://github.com/pgaudet We do pull the GO release's release-date.json, which I use to grab the date to construct the http://release.geneontology.org/2021-05-01/ URL. Should I add a line to the top like GO release date: 2021-05-01?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pantherdb/fullgo_paint_update/issues/53#issuecomment-854077292, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABEPWUFMV6U2J7LCDB3K7HTTQ7A2XANCNFSM457SWFZQ .
There is currently a simple README file generated at time of GO release download. Ex:
We should add to this file, clarifying some things:
release-date.json
to construct the release.geneontology.org/YYYY-MM-DD/ URL*.gaf.gz
,go.obo
,go-gaf.owl
A rough draft example for the 2021-06-01 IBA release: