Compositdb home page

Home
Information about Compositdb
News

Databases
Lettuce
Sunflower
Lettuce cultivar
SunGen

Colleagues
Data entry forms, mailing list archives and information for colleagues

Germplasm
Lettuce and sunflower germplasm collection centers

Tools
Locally developed tools

Links
Useful URLs

Conferences & Meetings
Information on upcoming and past events

Submit Data
Submit data and contact Compositdb

General Marker Data
(dbstandardgeneral.xls: 24KB, last modified: 3 May 2001)

Please use this Excel spreadsheet to submit genetic map data, locus records (for each marker), and related information such as polymorphism, probe data, primer and DNA sequences of mapped loci.

Completed forms should be submitted via e-mail to Steve Edberg at sbedberg@ucdavis.edu. If you need additional information or help please write to the above address.

Brief descriptions of fields used in the spreadsheet for general marker data:

It is important that the data is entered exactly as requested and the spreadsheets are not modified. This is necessary to ensure that the data can be parsed from the Excel spreadsheet into the ACEDB format prior to being uploaded into the database. A separate spreadsheet should be submitted for each segregating population. All loci segregating in a cross should be listed. All relevant cells should be filled even when redundant. Cells not relevant to a particular marker should be left empty.

Please note that spreadsheet columns are numbered. Information relevant to each numbered column is given below.

Cross: Parent information: please use the order female x male. This is interpreted as A x B in the database (eg. Calmar x Kordaat)
Cross_abbreviation: For each population, use the brief name or acronym you like to tag the data with (eg. C_x_K).
Locus name: Locus or marker name
(1) Marker type: The options for marker type are: AFLP, RAPD, RFLP, Microsatellite, STS, gene.
(2), (3), (4), (5) Primer sequence: Primer name, one space, then the primer sequence used for AFLP, RAPD or microsatellite markers. eg. AFLP marker R11/H20_SAMPL3/S01 has four primers. 'R11 AGACTGCGTACCAATTCA' would be one. Leave unused cells (i.e. when fewer than 4 primers) empty.
(6) Vector Enzyme: Refers to the enzyme required to release RFLP probe from the vector.
(7) Data Source-marker: Individual(s) responsible for development of the marker/probe. This is how the name will appear on the Colleagues page. Please use the format: family name, first name.
(8) Data Source-cross: Individual(s) responsible for the development of the cross. This is how the name will appear on the Colleagues page.
(9) Map Dist: Cumulative genetic distance from the start of the linkage group; distance in cM.
(10), (11) Alleles (Polymorphism): Size of the fragment(s) visualized on the gel (in kb). eg. in Calmar x Kordaat, parent A is Calmar, parent B is Kordaat. Where there is a dominant marker, the null allele should be indicated as 'null'. eg. Parent B contains 'null', indicating that there is no band present in Kordaat. Where information is absent (eg: when the size of band hasn't been recorded), the lack of data should be indicated by 'nd'. eg. Parent A contains 'nd' indicating that data is missing for Calmar.
(12) Enzyme: Enzyme required to visualise polymorphism.
(13) Reference: Reference to the publication where this marker was first described and subsequent references in which this particular marker was used.

Remarks cells:

Locus: Indicates any pertinent information about the locus, eg: repeat unit (microsatellites).
Probe: Indicates pertinent information about the probe, eg: origin.
Sequence: eg: single or double pass sequencing, quality of sequence, etc.
Polymorphism: indicates any enzyme required to release polymorphism, cosegregation of bands, etc.

Images:

Please use this form to submit images of gels, autoradiographs etc. Images should be formatted as .gif or .jpg.

Segregation data:

Please use this form to submit segregation data.

Colleague:

If you are involved in research of Compositae species, we would like to include you in the database.

Comments:

Any suggestions or comments about Compositdb or to modify the standard data submission forms would be appreciated.
go to top of page