[Go] Fwd: GAF changes, addition of new columns
Judith Blake
jblake at informatics.jax.org
Tue May 20 11:31:40 PDT 2008
I feel that we should include this in the newsletter. MGI might not get
into our db, but we can manipulate the GAF file if required and I don't
see a problem with that.
judy
Mike Cherry wrote:
> Decision needed.
>
> There has been no comments from the software group. I feel we could
> include the date(s) for GAF format change in the newsletter that is in
> final edits now.
>
> I'll be traveling until Saturday so I hope someone else can make sure
> this is decided and included in the newsletter.
>
> -Mike
>
>
> Begin forwarded message:
>
>> *From: *Mike Cherry <cherry at stanford.edu <mailto:cherry at stanford.edu>>
>> *Date: *May 19, 2008 8:52:38 AM PDT
>> *To: *software-group Group <software-group at genome.stanford.edu
>> <mailto:software-group at genome.stanford.edu>>
>> *Subject: **GAF changes, addition of new columns*
>>
>> Hi,
>>
>> Everyone asks me when the new columns will become required. What do
>> you all think?
>>
>> I'd suggest September or October. We need to define a date. A GO
>> newsletter will go to press, so to speak, this week. The next
>> newsletter will be in August. That will give two newsletters
>> announcing the change, and having the switch over date be a month or
>> two after the August newsletter.
>>
>> Part of this is when can groups start submitting a GAF with the
>> additional columns, and when would it become manditory? There are
>> two additional columns involved, the long reserved column for
>> properties (column 16) and the newly agreed one for canonical gene
>> name (column 17).
>>
>> Any counter proposals? Concerns? I've heard from Harold that this
>> change will take a few months for the MGI software staff to put into
>> production.
>>
>> -Mike
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Go mailing list
> Go at geneontology.org
> http://fafner.stanford.edu/mailman/listinfo/go
>
More information about the Go
mailing list