MoMaVis - Supplemental Material

Data Base Schema

Using the tables VIS_CULTIVAR and VIS_POPULATION various mapping populations could be stored. All possible populations are connected over the foreign key POPULATION_ID into the mapping table VIS_MAPPING_DATA. When this value is 0, then MoMaVis interpretes this population as a consensus map.

Using entries in the column MARKER_ID of the table VIS_MAPPING_DATA connections to internal marker identifiers could be modelled and stored.

The column MARKER_TYPE codes the type of a marker. In the existing data set the following code is used:

MARKER_TYPE	our marker type
1	RFLP
2	SSR
3	SNP
0	Public Domain Marker

Within the jnlp-File this definition could be rearranged, by editing the follwing line:

--markertypes=0,Public,0x808080;1,RFLP,0x0000FF;2,SSR,0x00FF00;3,SNP,0xFF0000

The columns CHROMOSOMEN_LOCATION and MAP_POSITION store the actual mapping information.

Database Dumps

• MySQL^TM SQL-DDL dump including an example dataset
  After importing the MySQL^TM dump a database with 3 tables and defined primary foreign key connestions is created. Furhtermore the following mapping data from GrainGenes is distributed over the 3 tables:
  • POPULATION_ID = 4: GrainGenes: Barley, IxF
  • POPULATION_ID = 5: GrainGenes: Barley, SxM basemap
  • POPULATION_ID = 6: GrainGenes: Barley, OWB, 2004

• Oracle^TM SQL-DDL dump without data
  After importing the Oracle^TM dump an empty schema with 3 tables and defined primary foreign key connestions is created.

Author: Uwe Scholz
Document: index.html, v 1.00 2005/09/23 12:00:58