Difference between revisions of "GMOD Components"

From GMOD
Jump to: navigation, search
m
m
Line 6: Line 6:
 
[[Image:roadmap25.jpg]]
 
[[Image:roadmap25.jpg]]
  
−
[http://www.gmod.org/?q=node/99 Key to diagram]
+
 
 +
'''Symbols used in this UML diagram'''
 +
* boxes
 +
** tabbed white boxes are packages -- logical groups of related components
 +
** boxes marked with ''<<interface>>'' are abstract interfaces required by GMOD-Web. All other labeled boxes are concrete components of the GMOD system.
 +
* connectors
 +
** solid arrows indicate a relationship between components that currently exists.
 +
** dashed arrows indicate a relationship between components that does NOT currently exist.
 +
** dashed arrows with a solid white head indicate an interface/realization relationship between a GMOD-Web required interface and a component that provides that interface. e.g. gbrowse implements the "genomeVis" interface.
 +
* coloration
 +
** white: components or interfaces that currently exist and integrated into the GMOD system.
 +
** green: components or interfaces that currently exist and are integrated into the GMOD system.
 +
** pink: components or interfaces that currently exist, but the feasibility of integrating their functionality into the GMOD system is unknown.
 +
** red: components that do not currently exist, but may need to be implemented.
 +
** orange: a common set of templates to provide a consistent look and feel for all GMOD systems. The "common gene page" concept is in this group.
 +
** cyan: components that are specific to each MOD, and are not deployable as part of a GMOD system.
  
 
GMOD components fulfilling the requirements of an interface are linked to the interface, as well as to the Chado schema modules if they are known to interact with Chado. The requirements of an interface, as well as the components that implement a given interface are described in the documents linked at the end of this document.
 
GMOD components fulfilling the requirements of an interface are linked to the interface, as well as to the Chado schema modules if they are known to interact with Chado. The requirements of an interface, as well as the components that implement a given interface are described in the documents linked at the end of this document.
−
 
−
----
 
−
 
  
  
Line 29: Line 41:
 
* [[Workflow Management]]
 
* [[Workflow Management]]
  
−
 
−
 
−
[http://www.gmod.org/files/roadmap.png roadmap.png]
 
−
| 45.53 KB
 
−
|- class="light"
 
−
|
 
−
[http://www.gmod.org/files/roadmap25.jpg roadmap25.jpg]
 
−
| 14.09 KB
 
−
|- class="dark"
 
−
|
 
−
[http://www.gmod.org/files/GMOD_components_roadmap.zuml GMOD_components_roadmap.zuml]
 
−
| 28.25 KB
 
−
 
−
 
−
 
−
 
−
I think he said something to the effect that the front page looked too crowded. Most new posts will be noted on the front page: blog posts will go in their block, comments will go in their block. What will not go in is new 'book' pages, though it will still go into an RSS feed. We could make a block with the site's RSS feed, which would show recent posts on the side, without having to show content. If someone wanted to highlight a new book page, they can blog about it too. (That is very unlikely to happen in real life, though, I expect.)
 
−
 
−
Moving things off the front page seems to have messed with the RSS feed, so that solution won't work. Here's what I did instead: I added a module called 'front_page' that lets you configure a custom front page, and then created a node that has just sticky nodes in it, and now requests from outside drupal for www.gmod.org will get redirected to that node. This is the 'clean' homepage. But any clicks on links from inside drupal to www.gmod.org will go to the default homepage with recent nodes. This is the 'working' homepage. I also reset blog entries and book nodes to display on the front page by default.
 
−
 
−
Hey, where did the UML diagram go? I really liked having the mini-version on the frontpage, it's a good way to see what GMOD currently is and what is being or needs to be developed. If the diagram needs to be resized, recolored, cropped, etc let me know.
 
−
 
−
It was huge. I think you had it set at 600 pixels, so I put it after the break. It is a great picture, but if you shrink it more, it becomes completely non-informative but if you make it bigger it is much to big to have on a front page. I would say even at 600 pixels it was too distorted to be informative (I couldn't read any of the text).
 
  
 
[[Category:To Do]]
 
[[Category:To Do]]

Revision as of 02:58, 14 February 2007

GMOD is a loose federation of software applications (components) aimed at providing functionality that is needed by all model organism databases.

This diagram represents a model organism database (MOD) and its typical components. The "top ten" types of functionality are represented in the top row of the diagram as a set of interfaces. The "Vis" prefix on the end of each interface is an abbreviation of "Visualization", and should be interpreted literally -- an alignment visualization interface should not merely allow users to passively view pre-existing alignments, but should also to user interaction to create and visualize alignments of their own.


Roadmap25.jpg


Symbols used in this UML diagram

  • boxes
    • tabbed white boxes are packages -- logical groups of related components
    • boxes marked with <<interface>> are abstract interfaces required by GMOD-Web. All other labeled boxes are concrete components of the GMOD system.
  • connectors
    • solid arrows indicate a relationship between components that currently exists.
    • dashed arrows indicate a relationship between components that does NOT currently exist.
    • dashed arrows with a solid white head indicate an interface/realization relationship between a GMOD-Web required interface and a component that provides that interface. e.g. gbrowse implements the "genomeVis" interface.
  • coloration
    • white: components or interfaces that currently exist and integrated into the GMOD system.
    • green: components or interfaces that currently exist and are integrated into the GMOD system.
    • pink: components or interfaces that currently exist, but the feasibility of integrating their functionality into the GMOD system is unknown.
    • red: components that do not currently exist, but may need to be implemented.
    • orange: a common set of templates to provide a consistent look and feel for all GMOD systems. The "common gene page" concept is in this group.
    • cyan: components that are specific to each MOD, and are not deployable as part of a GMOD system.

GMOD components fulfilling the requirements of an interface are linked to the interface, as well as to the Chado schema modules if they are known to interact with Chado. The requirements of an interface, as well as the components that implement a given interface are described in the documents linked at the end of this document.


Retrieved from "http://gmod.org/mediawiki/index.php?title=GMOD_Components&oldid=791"