About

Throughout the Breeding Management System, users can access germplasm details by selecting germplasm GID and/or name.

Open

Germplasm

Basic Details

• Preferred Name (see below for more information on naming)

• GID: BMS instance-specific germplasm identifier. Number assigned new germplasm in acceding order (1,2,3…..1456, 1457)

• UUID: Globally unique identified. Randomly generated alphanumeric sequence unlikely to replicated across BMS instances, genebanks, etc.

• Group ID: Germplasm assigned or descended from a group progenitor will share group ID

• Creation Date

• Location

• Reference

Open

Some germplasm details, like location, date, and reference are editable.

• Select the pencil and paper icon to reveal the editing popup. Confirm edits by selecting Update.

Names

The screenshot below illustrates a germplasm, IB1-1-1, that has a derived name, set by a customized naming convention. Institutes and breeding programs create naming conventions to suit their needs as a part of BMS installation (See your IBP data manager for more information). In the following scenario, the prefix, “IB”, refers to the institute, Integrated Breeding. “IB1” indicates that this is the first IB cross. “IB1-1-1” indicates that the line has been inbreed twice (F₃ generation).

Germplasm names can be edited or added without impacting the pedigree, GID, or UUID.

• Select New to add a germplasm name. In the following example, the breeder wants to give IBP1-1-1 a more human-readable commercial line name, Fabuloso. Selecting Preferred Name insures that “Fabuloso” replaces “IBP1-1-1” in most BMS tabular views.

Notice that while Fabuloso has become the preferred name for this germplasm, the original derived name, IB1-1-1 remains associated with the germplasm details.

Attributes

Attributes are non-heritable qualitative descriptors of germplasm. For example after quantitative characterization in a study or studies, a line may be given a “Rust Resistant” attribute.

• Select New to assign an attribute to the germplasm.

• Create Attribute. Choose variable from drop down list and describe.

The germplasm is now characterized as Rust Resistant.

Note: Germplasm Attributes and Germplasm Passport variables are now part of the Ontology. You can now use the ontology to control scales and properties of the germplasm attributes and passport data.

Pedigree

Progenitors

• Group Source: most recent ancestor created by generative breeding method

• Immediate Source: most recent ancestor

• Breeding Method: method of creation

Pedigree Tree

Select “Include derivative and maintenance lines” and Apply to reveal the full pedigree tree in list format.

• Create a graphical pedigree by selecting “View Pedigree Graph”. Enter the generation depth (level) of interest and choose whether to include derivative and maintenance lines. Use your computers

Click on a given node of the pedigree tree and the germplasm details of such node will open in a separate window (node highlighted in blue).

You can also download the pedigree graph by clicking on the Download button.

Observations

The observations tab allows for review of studies where the germplasm has been grown and/or evaluated. In the case below, Fabuloso has only been grown in a single study, F3 Nursery Winter 18. Search options are available to narrow the search to specific locations and observation levels.

Inventory

The Inventory tab allows for review of lots and transactions. See more in Manage Inventory.

Lists

The Lists tab provides links to germplasm lists in which the germplasm of interest has been included.

Samples

If the germplasm has been sampled for genotyping, the details about the sample are listed.

Audit trace

When looking at your germplasm details, names, descriptors, or pedigree you can now see an audit trace button that will enable you to see a comprehensive report of the change of the corresponding record.

Click on the Audit trace button.
The changes are highlighted in green. The Audit trace table annotates the date, the event type like creation or edition, the user who performed the event, and the timestamp. The timestamp is the one persisted in the server, indicating the timezone used.