v21 Import germplasm updates template

This functionality enables you to apply multiple updates to a group of germplasm in batch, via a GID or a GUID. Only add values for the columns that you want to modify for each germplasm record and the process will take care of the updates.

Column

Description

Column

Description

GID (mandatory, if GUID not specified)

Identifier of the germplasm record to be modified (i.e: 1034)

GUID (mandatory, if GID not specified)

Universally unique identifier of the germplasm record to be modified (ie PXLCGjg124)

BREEDING_METHOD

Used to change the breeding method of the germplasm

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

You can modify the progenitors of the germplasm records, provided that they don’t have progeny. If germplasm has progeny records you need to proceed with the edition manually, via the germplasm details interface)

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 necessary).

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.

PREFERRED NAME

You can modify the preferred name of the germplasm by entering the name-type column heading (see “Other codes” tab, table “NAMES”) that you want.

LOCATION_ABBR

Change the location associated to the germplasm by looking-up the breeding codes in the “Other codes” tab, table “LOCATIONS” (remember, this is not a complete list and you can look up others in the BMS Manage Locations page)

REFERENCE

Change the text which will be added as a reference new germplasm.

CREATION_DATE

Change the 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.

DRVNM

You can add new names to existing germplasm records, or change the names of the existing ones.

You can add 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

NOTES_AA_text

You can add attributes or modify the values for the existing ones 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.