v21 Import Germplasm Template

Column

Description

Column

Description

ENTRY_NO (mandatory)

Sequential enumerator for the entries

LNAME, DRVNM (at least one name is mandatory)

These are the columns to specify the line name and/or derivative name. You can add other name-types by adding new columns to the file and naming the column heading using the available name-types in the “Other codes” tab, table “NAMES

i.e:

VABBR ABBREVIATED VARIETY NAME
AABBR ALTERNATIVE ABBREVIATION
AACCNO ALTERNATIVE ACCESSION NAME
ACVNM ALTERNATIVE CULTIVAR NAME
ADVNM ALTERNATIVE DERIVATIVE NAME

PREFERRED NAME

Enter the name-type column heading that you want to be the preferred name for each new germplasm entry. Ex. LNAME, DRVNM (or other name-types in the column header). If you leave it blank you can define an order of priority for the naming after importing

ENTRY_CODE

Custom code to identify the entry. Local to the list. If left blank the system will assign automatically

LOCATION_ABBR

LOCATION_ABBR is the abbreviation of the location where the germplasm was produced. You can lookup the breeding codes in the “Other codes” tab, table “LOCATIONS” but this is not a complete list and you can look up others in the BMS Manage Locations page.

If left blank you can search for the locations after import for the records without it.

REFERENCE

Text which will be added as a reference new germplasm.

CREATION_DATE

Date the germplasm was created, collected or received according to your convention. Format YYYYMMDD

If left blank you can define a creation date after import for the records without it.

BREEDING_METHOD

fill the column with the code of the breeding method finally used to produce the entry.

You can lookup the breeding codes in the “Other codes” tab, table “BREEDING METHODS

ie.

AGB1 Accession into genebank
AGB2 Accession into historical genebank
ALP Allo-polyploid

PROGENITOR1, PROGENITOR2

These fields be used to capture pedigree information for the line or the cross you’re importing. They need to be filled with GIDs of the progenitors - this is to say that the progenitors must already exist in the BMS (You must import the parents first).

If the entry is a cross (an F1 like entries 3 and 4 in the example) then PROGENITOR1 should contain the GID of the female parent and PROGENITOR2 the GID of the male parent if they are known and 0 if it is unknown

 If the entry is a derived line (not F1) then PROGENITOR2 should contain the GID of the immediate source of the entry, in this case PROGENITOR1 should be set to 0.

However if the immediate source is not known, but the cross from which the entry was derived, is known then PROGEITOR2 should be 0 and PROGENITOR1 should be set to the cross from which the entry was derived.

NOTES_AA_Text

You can add attributes for the entries being imported by adding columns with headings obtained from the Passport or Attributes tabs of the Template, similarly to what you can do with names.

If the attribute you want is not there you must add it first through the ontology manager.

A column for NOTES_AA_Text is added by default.

STORAGE LOCATION ABBR

If you are creating seed inventory for the imported entries you can define the location of storage

You can lookup the breeding codes in the “Other codes” tab, table “STORAGE LOCATION ABBR”.

New ones must be entered through the Location Manager.

UNITS

If you are creating seed inventory for the imported entries you can define the storage units for each entry from the list.

You can lookup the breeding codes in the “Other codes” tab, table “UNITS”.

AMOUNT

If you are creating seed inventory for the imported entries you can define the amount of seed going into storage for new or existing entries. If some inventory entries are blank BMS will ask if you want those left blank of filled with set values at the time of importing.

STOCK ID

Is a short unique, human readable ID for the seed inventory lot. It is better to let the BMS assign these codes since they must be unique.

PUI

In this field you can specify any persistent, unique identifier assigned to the accession so it can be unambiguously referenced at the global level (i.e DOI’s)