This page provides a demo for a variety of topics I am working on:

1) Implementation of a "GMODviews" based on Drupal Views, that provides an alternative web based interface to the GMODweb interface that Brian O'Connor and others created earlier. My impression is that the GMODweb approach can be useful for model organims with relatively limited data available. However, my own work is on Drosophila (fruit fly) genes, and there is information available for that model organism that I do not think it can be realistically represented with a GMODweb interface. I therefore have been using the Drupal content management system to provide a robust and scalable system for my own work. The tools developed for fly genes should also be useful for other model organisms.

2) As part of this overall work, I have been working of the implementation of a Unified Gene Page format for Fly genes, since there is so much data for every gene in Flybase, that a limited subset must usually be presented in the user interface. This involves making judgement calls about just what information will be needed / desired for any user, or for any particular model organism. So far, it has not been possible to come to an agreement about that. Here are two different example "Unified Gene Page" formats that I have found useful in my own work on analyzing "DNA transcription codes" for fly neural genes, and which illustrate some of the issues involved in trying to generate a truly "unified gene page" format that will be useful for most or all users, and for most/all model organisms.

i: Flybase "Synopsis" gene page (circa 2004; unfortunately, this simple, but useful one page format is no longer available at Flybase.

ii: gClusters web portal for analysis of DNA transcription codes for fly neural development. This includes another example of a "unified gene page" format that I have found more useful my own work, and which many/most other fly biologists would likely find useful. It contains a more comprehensive mining of essentially all of the gene interaction data, gene expression data, and mutant phenotype data for each gene, rather than the partial data shown in the above "Synopsis" page. gClusters was developed on the Frontier CMS platform, which is no longer viable, and gClusters will eventually be ported completely to Drupal.

3) Flygenes UGP. This shows a very rough, preliminary view of a Unified Gene Page - based on the gClusters example I showed earlier - displayed as a very simple type of Drupal view. This interface and UGP format will be further developed later.

4) Flygenes Web Service. I also have been working on the development of a web services system in Drupal for fly gene data, where specific subsets of data can be selected by the user. This uses a Flygenes Services Module that I wrote, which is fully extensible. This will eventually will have a REST interface in addition to a simple Drupal Views interface for fly genes.