Users can make custom columns in some of the templates and those custom columns should be specified in the property_bims. Templates that can have custom columns include contact_bims, cross_bims, sowing_bims, site_bims, accession_bims, progeny_bims, marker_bims, haplotype_block_bims, phenotype_bims, genotype_snp_wide_form_bims, haplotype_block_bims, and marker_bims.
Below are descriptions for each of the columns in property_bims. Columns with * are required. Type is a validated column.
- *name: name of the property
- *type: type of the property. Valid data entries are contact, cross, sowing, site, accession, progeny, marker, haplotype_block, phenotype, snp, and haplotype_block.
- alias: alias for the property
- Definition: definition of the custom property
Different types of columns
In each template, the required columns have * as a prefix as shown above. Other columns can be used to enter data or left empty. Columns that are not specified in the templates will be ignored when loading data. Users can, however, make custom columns in some of the templates which should be specified in the property_bims and have ## as a prefix of the column name as shown above. In phenotype_bims, trait descriptor names are entered as column headings, and they need to have # as a prefix as shown above. The trait descriptor names need to match an entry in the descriptor_name column in the descriptor_bims if they have not been loaded to BIMS already. In the genotype_snp_wide_form_bims, marker names are entered as column headings, and they need to have $ as a prefix. The marker names need to match marker_name in the marker_bims if they have not been loaded to BIMS already. For some columns, only one of the specified terms can be entered as valid data. For example, valid entries for the type column in contact_bims are person, company, database, institution, lab, and organization. Those columns and their valid entries will be described in each data template section