[Gmod-help] FlyBase Chado mapping tables
Dave Clements
clements at nescent.org
Wed Jun 4 09:22:40 EDT 2008
Hi Josh,
It's great to hear that this is going on and thanks for thinking of us.
I have a suggested plan. Please let me know what you think of it.
New Pages:
- "FlyBase Chado" Introductory page that describes what the rest of the
FlyBase chado doc, and use of Chado at flybase.
- "FlyBase Chado - Audit Module" Doc on audit module tables.
- "FlyBase Chado - Companalysis Module" Doc on comp analysis modules
- etc.
New Page Content:
- In the newly generated pages, it would be nice to have separate
sections for each table. This generates HTML anchors which other pages can
then point to.
- Fomat any wiki tables with class="wikitable" to make it look
reasonable. Or, come up with a flybase/chado specific CSS class, send it to
me, and I'll add it to MediaWiki:Common.css.
- For every module include a link to the equivalent generic module page.
For example, on "FlyBase Chado - Audit Module" include a link to "Chado
Audit Module".
- For every table include a link to the equivalent generic table doc.
Let's assume that the section names will retain the same format, e.g.,
"Table: analysis"
- Put a "[[Category:Chado FlyBase]]" tag on each page. We'll make that a
subcategory of both Chado and FlyBase.
Existing Page Content:
- The next time we regenerate the chado module documentation we'll modify
each module page to include a link to the equivalent FlyBase module page.
We'll also modify each table description to include a link to the equivalent
FlyBase table section.
Please let me know what you think.
Again, thanks for doing this,
Dave C
On Tue, Jun 3, 2008 at 3:39 PM, Josh Goodman <jogoodma at indiana.edu> wrote:
>
> Hello again,
>
> FlyBase is currently in the midst of a doc-a-thon this week to get as much
> of our long overdue documentation written as possible. One of the things
> that is being documented is how a field in a FlyBase report corresponds to
> Chado. What we basically have is a simple 2 column table with the field
> name in one column and the SQL used to extract that field in the other.
> What I'm working on is building an automated workflow that will take this
> internal doc and turn it into a GMOD wiki compatible file that can be
> uploaded for public viewing on a regular basis. Which leads me to my
> question, do you have any ideas or preferences for where this information
> should live on the GMOD site?
>
> Cheers,
> Josh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://brie4.cshl.edu/pipermail/gmod-help/attachments/20080604/f6c5d642/attachment.html>
More information about the Gmod-help
mailing list