Trait

A characteristic of a crop that can be measured and observed, which are selected and combined with other traits to produce superior lines. In EBS, these are variables that can be used to record data at entry, plot, plant, and package levels.  

Seed

Refers to the germplasm or plant material being distributed, transferred, tracked, or documented.

Background

The plant embryo that receives the gene construct of another plant or species.

GTL

Gene Construct

The foreign gene that is prepared to be injected/introduced to the crop under study with the aim of producing a gene-edited organism/variety.

GTL

Experiment Creation

A tool used to create experiments in EBS. This is where users can define the details of their study, the germplasms, and the experiment protocols depending on the chosen experiment type.

CoreBreeding

Evaluation Season

The season or cycle at which the experiment is being evaluated.

CoreBreeding, ExperimentCreation, ExperimentManager, HarvestManager

Experiment Steward

A person responsible for the conduct and evaluation of the experiment.

CoreBreeding, ExperimentCreation, ExperimentManager, DataCollection, HarvestManager

Experiment Sub-sub Type

A Sub-sub-type of the experiment, which depends on the objective or context of the experiment sub-sub-type.

CoreBreeding, ExperimentCreation, ExperimentManager

Experiment Sub-type

A Sub-type of the experiment, which depends on the objective of the experiment.

CoreBreeding, ExperimentCreation, ExperimentManager

Occurrence Count

The number of occurrences of an experiment.

CoreBreeding, ExperimentCreation, ExperimentManager

Objective

Purpose of an experiment in the context of its project, stage, type, and sub-type.

CoreBreeding, ExperimentCreation, ExperimentManager

Pipeline

A set of activities that typically proceed in stages used to accomplish a breeding objective. For instance, a pipeline may be developed to deliver a specific product profile.

CoreBreeding, ExperimentCreation

Planting Season

This is a shorthand reference created by users to refer to the year and season of planting or harvest.

CoreBreeding, ExperimentCreation

Project

These are collaborative enterprises that are planned and designed to achieve a set of goals.

CoreBreeding, ExperimentCreation

Entry Class

A class that groups related entries together within the entry list.

CoreBreeding, ExperimentCreation, ExperimentManager

Entry Type

This depends on the purpose assigned to a germplasm in an experiment’s entry list. For example, entry types for a breeding trial experiment can either be “test” or “check”.

CoreBreeding, ExperimentCreation, ExperimentManager, DataCollection

Experiment Name

This can either be user-defined or system-generated. The system-generated  follows this naming convention: Program-Breeding Stage-Year-Evaluation Season-Incrementing Number.

CoreBreeding, ExperimentCreation, ExperimentManager, DataCollection, HarvestManager, InventoryManager

Experiment Type

An experiment type. The EBS supports the following experiment types: breeding trial, observation, cross parent nursery, generation nursery, and intentional crossing nursery.

CoreBreeding, ExperimentCreation, ExperimentManager, DataCollection, HarvestManager, InventorySearch

Breeding Trial

A type of experiment that has a set of germplasm with or without check and a statistical design. These are conducted in a single or multi-location to compare the yields, disease, physiological traits etc. of selected germplasm.

CoreBreeding, ExperimentCreation, ExperimentManager

Observation

An experiment that is commonly used for screening experiments and seed multiplication of fixed materials. The entries and checks may be replicated and planted according to the order specified by the user without using a statistical design.

CoreBreeding, ExperimentCreation, ExperimentManager

Generation Nursery

Experiments are used for advancement and/or selection of segregating populations and for seed increases (multiplications). The germplasm is typically self-pollinated through natural or artificial means.

CoreBreeding, ExperimentCreation, ExperimentManager

Cross Parent Nursery

Parents are planted first without assigning parent roles. Parental combinations for crosses are determined after the initial experiment has been created and may include different types of crosses such as single crosses, double crosses, three-way (top) crosses, back crosses, etc. Delaying the cross planning may allow time to include additional phenotypic or/and genotypic data not available at the time of creating the nursery.

CoreBreeding, ExperimentCreation, ExperimentManager

Intentional Crossing Nursery

Parent roles and crosses to be made are predefined before planting. Different types of crosses such as single crosses, double crosses, three-way (top) crosses, back crosses, reciprocal crosses, etc. can be included in the nurseries.

CoreBreeding, ExperimentCreation, ExperimentManager

Crop

Plants that are the focus of scientific study in an institution. Currently, the EBS supports the following crops: rice, wheat, and maize.

CoreBreeding, ExperimentCreation, ServiceManagement, RequestManager

Program

This refers to an organizational unit creating the experiment. The EBS instance to be used can be configured to only display data coming from a specific program, such as HYBRID for rice and BW for wheat.

REVISED: This refers to an organizational unit creating the experiment and managing the inventory of a germplasm. Programs dictate the visibility of experiments and the generation of new germplasm, seed, and package names.

CoreBreeding, ExperimentCreation, ExperimentManager, DataCollection, HarvestManager, CoreSystem, Printout. ServiceManagement, RequestManager

Experiment Code

A system generated code for each experiment. This only contains the prefix EXP and the record number of that experiment in the system.

CoreBreeding, ExperimentManager, 

Stage

This refers to the stage at which a experiment is currently at.

CoreBreeding, ExperimentCreation, ExperimentManager, DataCollection, HarvestManager

Entry List

A list containing germplasms to be used in an experiment. This can be created in four ways: Input List, Advanced Nursery, Copy Entry List, or Saved List.

CoreBreeding, ExperimentCreation, ExperimentManager,

Experiment Design

These are the design models used in breeding trial experiments. It refers to how the entries will be arranged in the experimental unit, such as a field or greenhouse.

CoreBreeding, ExperimentCreation, ExperimentManager,

Plot Number

This is a unique/chronological number assigned to a plot within an occurrence.

CoreBreeding, ExperimentCreation, ExperimentManager,DataCollection

Entry Number

This is the unique/chronological number assigned to a germplasm within an experiment.

CoreBreeding, ExperimentCreation, ExperimentManager,DataCollection

Block Number

This is the block number assigned to a group of plots planted in a planting area. This can be a result from an statistical design OR manual assignment of the user.

CoreBreeding, ExperimentCreation,

Crop Establishment

This refers to the method of planting a seed onto the soil, such as direct seeding or transplanting.

CoreBreeding, ExperimentCreation,

Seeding rate

This pertains to the amount of seeds in grams per linear meter for direct seeding method.

CoreBreeding, ExperimentCreation,

Replicate

This is a repetition of an entry and its treatment/s to increase the reliability of statistical results. The number of replicates can be identified for each entry, depending on the adopted trial design.

CoreBreeding, ExperimentCreation, ExperimentManager,DataCollection, HarvestManager

Planting Arrangement

This refers to the planting order and layout to be implemented in the field.

Parentage

This specifies the breeding line/cross that produced the germplasm under study. It is also referred to as pedigree.

CoreBreeding, ExperimentCreation, ExperimentManager, DataCollection, HarvestManager, Germplasm, ServiceManagement, GenotypingServiceManager

Parent list

This refers to the beginning germplasm or lines to be crossed for either a Cross Parent Nursery or an Intentional Crossing Nursery experiment. You can add parents in four ways: Input List, Advanced Nursery, Copy Entry List, or Saved List.

CoreBreeding, ExperimentCreation, ExperimentManager, CrossManager

Parent role

This refers to the role to be assigned to a germplasm/line in a Cross Parent Nursery and an Intentional Crossing Nursery experiment. This can either be male, female, or female-and-male.

CoreBreeding, ExperimentCreation, ExperimentManager, CrossManager

Block

This refers to a group of entries planted in one area and subjected to the same treatments and conditions.

CoreBreeding, ExperimentCreation, ExperimentManager,

Sub-block

This is one level below blocks containing a sub-group of plots planted in a planting area.

CoreBreeding, ExperimentCreation, ExperimentManager,

Protocols

A set of instructions for field management or a set of traits that are specified/collected during experiment creation. A user can specify an experiment's planting, trait, management, pollination, and harvest protocols.

CoreBreeding, ExperimentCreation, ExperimentManager,

Planting Type

This describes where a seed was planted. This can either be flat, bed, container, or melgas.

CoreBreeding, ExperimentCreation, ExperimentManager,

Melgas

Spanish; A planting type referring to an irrigated flat basin.

CoreBreeding, ExperimentCreation, ExperimentManager,

Pollination

the transfer of pollen to a stigma, ovule, flower, or plant to allow fertilization.

CoreBreeding, ExperimentCreation, ExperimentManager,

Pollination Protocol

Pollination protocols can only be specified for Intentional Crossing Nursery and Cross Parent Nursery experiments. This is where a user can provide specific instructions relating to the cross activity of their entries.

CoreBreeding, ExperimentCreation, ExperimentManager,

Planting Protocol

These protocols define how the plots will be prepared for planting. Users can specify the crop establishment, planting type, and plot type. Common plot types (e.g. Transplanted 1 Row x 25 Hills) have predefined plot values used to compute the plot area. However, users can still define their own plot type and values.

CoreBreeding, ExperimentCreation, ExperimentManager,

Trait Protocol

These refer to data collected (e.g. phenotypic, agronomic) by users. These can be specified individually or a trait protocol set can be defined by the user and used repeatedly in experiments. Additional instructions for the collection of each trait may also be provided.

CoreBreeding, ExperimentCreation, ExperimentManager,

Management Protocol

Management attributes refer to the data and tasks performed to manage the field. An attribute may refer to the same task/item, such as fertilizer, but records different aspects of it (e.g. type, date of application, amount). These can be specified individually or a management protocol set can be defined by the user and used repeatedly in experiments. Additional instructions for the collection of each attribute may also be provided.

CoreBreeding, ExperimentCreation, ExperimentManager,

Harvest Protocol

A harvest protocol can be set ahead of time if the method of harvest is already known. During the harvest itself, users have the option to use the predefined harvest protocols or to replace them.

CoreBreeding, ExperimentCreation, ExperimentManager,

Harvest Method

This refers to the method of collecting mature crop from the field. The harvest method can be defined at the plot or cross level. The method depends on the crop to be collected. For example, the individual ear harvest method is available for maize crops.

CoreBreeding, ExperimentCreation, ExperimentManager, DataCollection

Crosses

These pertain to the pair of male and female parents to be crossed in Intentional Crossing Nursery and Cross Parent Nursery experiments. The Self-cross option for a parent is also available.

CoreBreeding, ExperimentCreation, CrossManager

Entry role

A germplasm is assigned a role depending on its purpose in a certain experiment type. The entry role for cross experiments will only consist of male, female, or female-and-male roles, while the rest of the experiment types may assign the role of entry, check, or test to a germplasm.

CoreBreeding, ExperimentCreation, ExperimentManager,

Test

These are the entries being observed in a breeding trial experiment. These serve as cases, as opposed to controls, based on the objective of the experiment.

CoreBreeding, ExperimentCreation, ExperimentManager,

Check

Checks are plots that serve as controls and are placed at regular intervals during planting arrangement. These serve as baseline indicators in an experiment. Only those germplasms with the entry role check can be assigned in check groups and as start or end checks.

CoreBreeding, ExperimentCreation, ExperimentManager,

Check Group

These are three or more checks grouped together and positioned in-between plots.

CoreBreeding, ExperimentCreation, ExperimentManager,

Experiment Manager

A tool used to manage the experiments that have been created. This supports updating features of an experiment before it is committed for planting.

CoreBreeding

Entry Class

Class that groups related entries together within the entry list

CoreBreeding, ExperimentManager,

Experiment Name

This can either be user-defined or system-generated (Program-Breeding Stage-Year-Evaluation Season-Incrementing Number)

CoreBreeding, ExperimentManager,

Experiment Type

An experiment type. The EBS supports the following experiment types: breeding trial, cross parent nursery, generation nursery, and intentional crossing nursery.

CoreBreeding, ExperimentManager, Data Collection

Occurrence Name

This can either be user-defined or system-generated (Experiment Name-Incrementing Number)

CoreBreeding, ExperimentManager, Data Collection, HarvestManager

Cross Name

Refers to the name of a new variety from the interbreeding of 2 germplasm lines. Its syntax is Female parent cross name | Male parent cross name.

CoreBreeding, ExperimentManager,

Status

This column displays the progress of a transaction in terms of a tool's workflow.

CoreBreeding, ExperimentManager,

Design

This column shows the statistical design used for an experiment.

CoreBreeding, ExperimentManager,

Entry Count

The number of germplasm/lines selected as entries in an experiment.

CoreBreeding, ExperimentManager,DataCollection

Plot Count

The number of plots in an occurrence.

CoreBreeding, ExperimentManager,DataCollection

Location Steward

A person or farm manager responsible for an experiment location.

CoreBreeding, ExperimentManager,DataCollection

Ecosystem

A variable that pertains to the environmental conditions in which a crop is subjected to. A user can select whether an ecosystem is upland, rainfed lowland, irrigated, or flood-prone.

CoreBreeding, ExperimentManager,

Market Segment

This is a variable that guides the design of product concepts and breeding objectives. This is the target end-user of the crop variety being developed.

CoreBreeding, ExperimentManager,

Geospatial Coordinates

This refers to an exact planting location containing the degrees of latitude and longitude. This is defined at the site level.

CoreBreeding, ExperimentManager,

Planting Area

This is one way of mapping an occurrence to a location that consists of X and Y values for each plot. In the mapping file, the planting array is indicated by the “PA X” and “PA Y” acronyms.

CoreBreeding, ExperimentManager,

Trait List File

This is a file generated from EBS related to data collection. This contains the traits to be collected for an occurrence. This has a filename extension of .trt, which is read by the Field Book application.

CoreBreeding, ExperimentManager, DataCollection

Location File

This is a file generated from EBS related to data collection. This file contains all the occurrences in a location whose data will be collected. Thus, it serves as the storage of all data collected in the field using the Field Book application. This has a filename extension of .csv and is uploaded to EBS after data collection.

CoreBreeding, ExperimentManager,

Occurrence List File

This is a file generated from EBS related to data collection. This file contains the selected occurrence whose data will be collected. Thus, it serves as the storage of all data collected in the field using the Field Book application. This has a filename extension of .csv and is uploaded to EBS after data collection.

CoreBreeding, ExperimentManager, DataCollection

Entry Code

These are unique codes created by users for entries of an entire experiment or occurrence. Entry codes may be generated to encrypt a germplasm. This may also involve defining prefixes, suffixes, and leading zeroes.

CoreBreeding, ExperimentManager,

Plot Code

These are unique alphanumeric codes created by users for plots of an entire experiment or occurrence. This may involve defining prefixes, suffixes, and leading zeroes. This code also informs the package labels and codes upon harvest. The plot codes are displayed in field tags.

CoreBreeding, ExperimentManager, DataCollection

Collaborator

A person or program outside EBS that is granted access to occurrence/s of an experiment. The access can either be read or write, as defined by the experiment owner.

CoreBreeding, ExperimentManager,

Planting Instructions Manager

A tool used to manage the seed sources needed for an experiment.

CoreBreeding, PlantingInstructionsManager

Packing Job

A request to prepare the seeds needed for occurrence/s of experiment/s in preparation for planting.

CoreBreeding, PlantingInstructionsManager

Job Code

A system-generated code for each packing job, indicated by a prefix, leading zeroes, and a sequence number.

CoreBreeding, PlantingInstructionsManager

Envelope

A physical container for seeds used for experiments.

CoreBreeding, PlantingInstructionsManager

Unit

The measure of quantity used to describe an envelope. The supported units of measurement are plants, panicles, seeds, grams, and kilograms.

CoreBreeding, PlantingInstructionsManager, ServiceManagement, GenotypingServiceManager

Filler

A germplasm that is selected to replace an entry. Fillers are planted in place of an entry as a placeholder in an otherwise empty area.

CoreBreeding, PlantingInstructionsManager

Cross Manager

A tool used to manage crosses and create cross lists. The parent/s are sourced from the enrtries of an experiment.

CoreBreeding

Generation

The succession of progenies resulting from crosses, where the first filial generation is indicated by F1, and so on.

CoreBreeding, CrossManager, Germplasm, HarvestManager, ListManager

F1

The abbreviation for the first filial generation resulting from a cross.

CoreBreeding, CrossManager, Germplasm

Parent Type

A parent is assigned a type depending on its purpose in a cross.

CoreBreeding, CrossManager

Cross Count

The number of crosses created in a cross list.

CoreBreeding, CrossManager

Cross Name

A system-generated name for each cross, indicated by the female and male parent’s germplasm name separated by a pipe symbol. A cross name is generated only after harvesting the materials of a successful cross.

CoreBreeding, CrossManager

Cross List Name

A user-defined name to identify a cross list made.

CoreBreeding, CrossManager

Cross Method

This refers to the crossing procedure assigned for parent germplasm/s. Cross methods can either be selfing or non-selfing crosses.

CoreBreeding, CrossManager, HarvestManager

Trait Introgression

A cross method that aims to develop an elite material by introducing a desired trait.

CoreBreeding, CrossManager, HarvestManager

Backcross

A cross method wherein a high yielding crop variety (A) is crossed with another variety carrying a desired trait (B). The resulting progeny (C), the improved variety, is then crossed back to one of its parents (either A or B) to build the desired traits in the succeeding progeny lines.

CoreBreeding, CrossManager, HarvestManager