v29 Manage Germplasm
- Corina Habito
Related video
- 1 Related video
- 2 Introduction
- 3 Filter germplasm
- 4 Create new list
- 5 Add to an existing list
- 6 Import germplasm
- 7 Edit germplasm
- 8 Delete germplasm
- 9 Merge Germplasm
- 9.1 Glossary
- 10 Export data and labels
- 11 Group and ungroup germplasm
- 11.1 Inbred Lines
- 11.2 Group
- 11.3 Options
- 11.4 Ungroup
- 12 Apply code names to germplasm
- 13 Hybrid Line Development
- 14 Create inventory lots
Introduction
The Germplasm Manager allows you to:
Filter germplasm by a variety of parameters
Create a new germplasm list
Add germplasm to an existing list
Import germplasm or germplasm updates
Group and ungroup germplasm
Apply code names to germplasm
Create inventory lots for germplasm
Filter germplasm
Filter germplasm by a variety of search filters.
Example: Germplasm List Filter
Choose the Germplasm List filter then click the plus icon.
Click on the Germplasm List filter (teal button) to browse through the lists. Germplasm List: All in the following example.
Choose the list of interest. Click Ok.
The selected entries are now available for various actions.
View germplasm details, by clicking on the GID or germplasm name hyperlink.
Add and remove columns in the Germplasm Manager
You can add and remove columns of selected entries using the Columns button.
To add columns:
Click on the Columns button
Select LOCATION
Click on APPLY BUTTON.
The Column with LOCATION details will appear in the table and be populated with corresponding values.
To remove columns:
Click on the COLUMNS button
Uncheck the columns that should not appear in the table. In this case, we unselect the column with CROSS.
Click on the APPLY button.
The column (s) selected are not displayed anymore.
Attributes
Attributes are descriptors of germplasm. For example, a line can be deemed “drought tolerant” after characterization in a multi-location study. See below for more on editing attributes.
Attributes can be edited via Import germplasm updates.
Pedigree
The BMS database keeps a record of pedigree connections throughout the process of crossing and nursery advancement.
Expand Pedigree Tree and select View Pedigree Graph. The default view shows only generative steps in the pedigree.
22IB1F is the result of backcrossing. The recurrent parent, CML578:201704, is female.
Tick the option Include derivative and maintenance lines to view steps, like seed increase. Similarly, tick the breeding method option to display the methods used.
- The recurrent female parent, CML578:201704, is derived by seed increase from CML578.
Inventory Information
Reveal details about inventory lots, storage locations, and availability. See more
Click on a germplasm name and open the inventory tab. The view lots, has details associated with the lot including seed stock ID, Seed storage location, available amount, and the date when the lot(s) were created.
Lot transaction details including withdrawals and deposits are in the View transactions tab.
Create new list
Using filters, select the germplasm of interest. Select "Create New List" from the Actions menu.
Select or create a folder to house the new list. Name the germplasm list and Save. The germplasm list will then be available from the germplasm list filter and the Germplasm Lists module of the BMS.
Add to an existing list
Using filters, select germplasm of interest. Select "Add to an existing list" from the Actions menu.
Specify the list to which the selected germplasm will be added.
Import germplasm
The Germplasm Import template is very versatile for supplying a lot of information about the new imported germplasm. It is also useful for assembling germplasm, whether new or existing in the database into lists and can be used to add inventory for new or existing entries. However, information will not be changed if the Germplasm exists in the BMS. You must use the Germplasm Editing features of the Germplasm Details forms or the Germplasm Update template from the Germplasm Manager Actions menu to change or add information about existing germplasm.
Step-by-step instructions for germplasm import
1. From the Actions menu, select Import Germplasm
2. Download the template file
3. Fill the template file
See v29 Import Germplasm Template for descriptions of the columns in the Import Germplasm template file.
The Germplasm Import Template has four Sheets:
Observation sheet: The sheet to be filled with germplasm details. It has several columns describing the characteristics of the germplasm record.
Passport sheet: The sheet containing germplasm passport variables to fill out the observation sheet.
Attributes Sheet: The sheet containing germplasm attribute variables needed to fill out the observation sheet.
Other codes sheet: The Sheet with metadata information such as: breeding methods, name types, storage locations used to fill out the observation sheet.
A filled germplasm import template with basic details will look as follows:
Tip: It is important to fill the MANDATORY columns: ENTRY_NO, any column with entry name e.g. LNAME or DRVNM, BREEDING METHOD, and LOCATION_ABBRV (abbreviation) before importing the germplasm. Also, you can use this template to import the Inventory to BMS.
4. Import the germplasm to BMS
Once the template is completed, select IMPORT GERMPLASM from the ACTIONS Menu of the MANAGE GERMPLASM as described above. Browse and click on open to pick the template.
The template will be attached then click NEXT to import the germplasm.
The next page will display the mandatory basic details. If the information of the mandatory basic details is incomplete, there will be an option to select Breeding methods or Germplasm locations details that apply to all entries in the import file.
The Next page displays inventory information. If there is no inventory details in the import file, the page will be inactive.
Import file with NO Inventory
Import file WITH inventory
A preview page of the germplasm you intend to import follows next:
Pull down the show matches pick list to review the entries in the import file to find whether they are new records, have existing matches, or, in some cases, match multiple GID matches in the database.
A review window of a germplasm name with multiple matches of GIDs
If there are multiple matches the user must select the most appropriate one and click NEXT to continue with the import process. Select the appropriate option and click SAVE. In this case we select the first option (GID 121248) as it seems to be the first germplasm name entered into BMS.
Option 1: Use the same match for all remaining occurrences: Used when there are repeated germplasm names in the import file (e.g CML 202 in the above example is repeated 3 times) and If “Use same match” is ticked for the first occurrence of the germplasm name found, the user will not be prompted again for the succeeding occurrences of the same germplasm name in the import file.
Option 2: Ignore matches and add a new entry: the found matches will be ignored and a new GID will be assigned to the entry.
Option 3: Ignore remaining matches and add new entries: All entries in the import file will be added as new entries.
GID Creation options
The BMS assigns numeric identifiers, called GIDs* to every new germplasm imported to the database. See more about germplasm Germplam and Geneology in BMS. New germplasm names are assigned a GID number and when the import file has already existing germplasm in the BMS, they are mapped to GIDs of similar germplasm name matches in the database to allow continuity of data relationships. Users with permissions have an option to ‘force BMS create new records’ by ignoring the germplasm name matches identified. The user permission(s) are usually defined when user accounts are created.
When all the entries have been processed BMS will show you a summary of found and new records. This is a second chance to catch any typos (if there should be no new records) and you can cancel to return to the Review window.
Save the imported germplasm in right folder with a name
Edit germplasm
Update a single GID: Germplasm details
Clicking on blue hyperlink text containing a GID or germplasm name anywhere in the BMS reveals the germplasm details.
The pencil button is visible and enabled for a user with Edit Germplasm permission. Germplasm basic details, names, descriptors (e.g. passport information, attributes), pedigree, and files can be modified.
The trash can button is visible and enabled for a user with Delete Germplasm permission.
The bullet points button is visible and enabled for a user with View Change History permission.
Update a batch of GIDs: Import germplasm updates
There are two ways to update Germplasm Records in BMS if you have the correct privilege to do so (e.g. Crop Admin ). The first way is to use the edit features on the Germplasm Details forms – one GID at a time as described in the previous section. A second way is to use the Germplasm Update template from the Germplasm Manager to update a batch of GIDs in a single pass. We will demonstrate the second way here.
Click on Import germplasm updates from the Actions menu of Germplasm Manager.
You can download a Germplasm Update template by clicking on the “here” link:
Now suppose I want to add accession numbers and make them the preferred name for germplasm IBP-3 C2 TLYD-68 with GID 45780 and germplasm IBP-3 C2 TLYD-54 with GID 45781. (If you are trying this in a classroom setting, pick some different GIDs for your own exercise by looking in the Germplasm Filter list).
First I have to define the germplasm I want to change by entering their GIDs in column A of the template. I can also look up their unique identifiers on the Germplasm Details page and enter them in column B (instead of GID or as well as GID if I want). Then I look up in the Codes sheet the code for Name Type Accession number – ACCNO and I replace the heading in column J (DRVNM) with this code (ACCNO). Since I want the accession number to be the new preferred name, I add the same code in column F of the template.
I can also change the germplasm location by entering a location abbreviation in column G. (I can look up location abbreviations in the Codes sheet or in the Location Manager of the BMS).
I can change the germplasm date by adding a valid date (YYYYMMDD) in column H, I can add a germplasm reference by adding a reference text in column I.
Finally, I can add any attributes I want. For example I can add some notes in column K and I can add columns after that with attribute codes from the Passport or Attributes sheets of the template. For example I can add a column header STATUS_ACC_AP_text (accession status ) to column L and fill it with AV for available.
Your completed template appears as above.
I could also change the pedigree of the germplasm using columns C,D, E as will be described below in the Pedigree editing section.
Once the template is complete, select Import germplasm updates from the Actions menu of the Germplasm Manager and browse to the file, and click Import. The updates will be applied and can be viewed in the germplasm details form: by Clicking on blue hyperlink text containing a GID or germplasm name.
Pedigree Editing
There are two ways to edit the pedigree of Germplasm Records in BMS if you have the correct privilege to do so (e.g. Crop Admin). The first way is to use the edit features on the Germplasm Details forms – one GID at a time. A second way is to use the Germplasm Update template from the Germplasm Manager to update a batch of GIDs in a single pass. We will demonstrate the second way below.
Let us consider our example on Importing New Germplasm described in a previous section where we imported new entries CGMLine1 and CGMLine2.
CGMLine1 has GID 8016348 and CGMLine2 GID 8016349.
Suppose we later discover that CGMLine1 is a purification from NERICA 4 (GID 765439) and that CGMLine2 is an unknown derivative line from the cross IR 1234 (GID 1903) made at IRRI in 19950101.
Suppose also that we discover that the unknown cross IR 56279 (GID 68722) is a three-way cross between NERICA 4 (GID 765439) and the F1 IR 1234 (GID 1903) and that we would like to make the alternative name CP 135, which is a cultivar name, the preferred name.
Click on Import germplasm updates from the Actions menu of Germplasm Manager and download a template.
See v29 Import germplasm updates template for instructions on how to fill the template.
Column Effect
A. GID – Fill the GID column with the GIDs of the germplasm for which you wish to change the pedigree information.
B. GUID – you can enter the Germplasm unique identifiers in the GUID column instead of the GIDs or as well as the GIDs if you like.
C. BREEDING METHOD – look up in the Codes sheet the codes for the breeding methods you want for the germplasm: DPR for Purification, UDM for unknown derivative method, and C3W for three-way cross. If you don’t want to change the method for a line leave the cell blank.
D. PROGENITOR1 – If the subject germplasm is derivative (like an inbred line) and you want to connect it to a known immediate source set PROGENITOR1=0 and PROGENITOR2 to the GID of the known source. If the subject germplasm is derivative from a known cross, but you don’t know the immediate source, set PROGENITOR1 to the GID of the known cross and PROGENITOR2=0.
E. PROGENITOR2 – If the subject germplasm is generative (like a cross) set PROGENITOR1 to the GID of the female parent and PROGENITOR2 to the GID of the male parent.
F. PREFERRED NAME – If you want to change the preferred name of the subject germplasm to one of a different type, look up the code for the type in the Codes sheet and enter it in the PREFERRED NAME column. The name could exist for the germplasm already or it could be added in a column of the template having the name type code as column heading.
G. LOCATION ABBR – If you want to change the germplasm location for the subject germplasm, look up the abbreviation in the Codes sheet or in the Location Manager of the BMS and enter it in the LOCATION ABBR column.
H. CREATION DATE – If you want to change the creation date of the subject germplasm, enter a valid date (YYYYMMDD) in the CREATION DATE column.
I. REFERENCE – If you want to add or change the reference relating to the subject germplasm enter the text of the reference in the REFERENCE column.
J. DRVNM – If you want to a add new names for the subject germplasm, enter the names in column(s) headed by the name type code for the type of name you want. Derivative name (DRVNM) has been added as a column for example, but you can look up for other name types in the Codes sheet and add columns for those name types as well as DRVNM or instead of DRVNM.
K. NOTES_AA_text – If you want to add attributes for the subject germplasm, enter the values in column(s) headed by the attribute code(s) which you can look up on the Passport or Attributes sheets of the template. The attribute NOTE_AA_text has been added to the template as an example.
Before Updates
After Updates
Before Updates
After Updates
Before Updates
After Updates
Delete germplasm
Germplasm created in the system erroneously can be deleted. Once deleted, the designation and GID will not appear in germplasm searches. The GID is not available for reuse after deletion.
The system will prevent deletion of germplasm:
if the germplasm has inventory
if the germplasm exists in multiple lists
if the germplasm is associated with a nursery or trial
if the germplasm is fixed
if the germplasm has descendants
Confirm deletion.
Merge Germplasm
Glossary
Target germplasm: The germplasm that the user has decided to keep from the merge selection
Non-selected germplasm: The germplasm or set of germplasms that the user has decided to remove from the merge selection
For reference: this germplasm was imported for creating the merge case explained here.
Basic validations
The system validates that the non-selected germplasm is not marked as fixed, doesn’t have any progeny, and doesn’t belong to a locked list.
Merge Germplasm requires specific permission in Manage Germplasm and at least 2 germplasm selected for triggering the action.
Select the germplasms to be merged.
Actions > Select the Merge germplasm option
Select the target germplasm
Select the option(s) for transferring data from the deleted germplasm to the target germplasm:
Notice the non-selected germplasm has inventory lots.
Confirm
You can manage the non-selected germplasm inventory lots in the Inventory lots window, or omit the germplasm from the merge action.
You have two options:
Apply an option to all non-selected germplasm
2. Tick individually the action desired for each non-selected germplasm
In the example, we are going to associate two lots of the first and the third non-selected germplasm (GID 387007 & 387009 )to target germplasm and close the lot for the second one (GID 387008)
Confirm
IMPORTANT NOTES:
Studies: If the non-selected germplasm has been used in studies, then the system replaces it with the target germplasm in the corresponding studies
Lists: If one or more of the non-selected germplasm have been used in a list, the system replaces the non-selected germplasm for the one that has been selected in all the corresponding lists
A Review of the merge action is displayed.
This review informs you of the following:
number of germplasm to be deleted
number of lists that will be modified
Number of studies, number of plots where the germplasm will be replaced
Lot(s) migrated, and lot(s) will be closed
Germplasm data (e.g. passport, attributes, name-types, passport and attributes files) will be transferred to the target germplasm.
Confirm
A successful message that germplasms have been merged is displayed.
At the first glance, you’ll notice the GIDs 387007, 387008 and 387009 are no longer displayed. The new names have been added for the target germplasm, and the number of lots increased from 1 to 3.
Review the germplasm details for checking the data transferring.
Export data and labels
This feature can be used to export germplasm list or Labels from BMS. You can export data and labels based on the current label printing features in Manage Germplasm.
Select the germplasm of your interest- You can use a filter, the checkbox, or the current page.
From the Actions menu select Export data and labels
You will be presented with options to select the Output format (Formatted PDF Label Sheets, Excel, CSV)
And an option to select an existing configuration pre-set, if exists.
Also, you can select: i) GID, ii) Preferred Name), iii) GroupID, or iv) Creation Date for sorting the data to be exported.
Available Fields
The fields available for export come from Germplasm Details, Pedigree, Names and germplasm Attributes sections.
Export Option - PDF Label
Select the PDF output format and Preferred Name in Sort label by option.
Specify the label stock parameters: Size of label sheet and the number of rows per page
Drag and drop the selected fields to either the left or right sections of the label. You will see two sections where to allocate the available fields.
When the PDF format is selected, you are also presented with options to include barcodes in the export.
Click ‘Yes’ to use automatically generated Unique barcodes.
Exported PDF Labels with GUID as the Unique Barcode:
NOTE: the GUID is the barcode field if you select Yes to "automatically generate barcodes"
If you do not want to use automatically generated unique barcodes then select 'No'
Select the First, Second and Third barcode fields to combine these values as your barcode
You can save the fields specified in a pre-set to be used in the future.
In Save settings, add a pre-set name.
Save Preset, a success message is displayed: SUCCESS - Successfully saved pre-set. The pre-set is now available for selection when checking the "Load saved settings" option.
Export. The file exported should have germplasm-labels_ [USERNAME] _ [yyyymmdd]_[hhmmss] as its file name, truncating the file name if it is needed.
Predefined template
Export option - CSV
Use this option to export the fields or data in Excel to be used in your own label designs. See How to generate labels using BMS and MailMerge in Word - IBP Support Knowledge Base - Confluence (atlassian.net)
Group and ungroup germplasm
In the BMS, a 'group' is a set of germplasm with a shared ancestry. Grouping is useful when working with inbred lines in hybrid breeding or varieties of a self-pollinating species. In a typical hybrid breeding program when a line is considered homozygous (fixed), either by inbreeding or doubled haploid formation, it is set as the founder of a new group and given a code name. Grouping and coding can also be useful to track families and to indicate when germplasm has passed through a breeding phase, such as disease resistance selections.
A group is created by selecting a germplasm that is to be the founder of a new group and using the 'Group' action in the List view of the Germplasm Management module. This creates a group identity -- a Group ID. When Germplasm with a group identity is propagated using breeding methods that refine or preserve genetic variation (derivative or maintenance methods) the resulting descendants will inherit the group identity.
Inbred Lines
Group ID can be used to identify a fixed inbred line and all descendants. A line that has reached fixation is expected to give rise to genetically identical offspring through maintenance breeding methods. When an inbred line is deemed "fixed" it can be grouped, so that all descendants, even those with different breeding histories and GIDs, can be retrieved by searching Group ID. At any point in the breeding process, descendants can be re-grouped or un-grouped. For example, inbred lines resulting from pedigree breeding will not be 100% homozygous. Offspring with off-type phenotypes can be regrouped to distinguish from non-segregating lines.
Scenario: A breeder considers some F4 lines sufficiently inbred (fixed) and wants to group them.
GERBB020-1-RB-1 is an F4, which has homozygosity estimated at ~87.5%. This estimate can be presumed higher for traits of interest if the selection was applied during line development. A breeder might consider F4 lines as fixed and want to keep track of descendants.
Group
To create a group, one or more germplasm records are selected in Germplasm Search in the Manage Germplasm module and the Group action is selected from the Actions menu. For each germplasm record, the BMS will create a new group with that germplasm record as the founder of the group. Note that if you select multiple germplasm records, they will not belong to the same group unless they are related by descent.
From Germplasm Search, select lines to group. Click on Actions, then Group.
20 F4s are selected for grouping.
Options
Preserve existing group
Preserve existing group will preserve the existing Group ID. In other words, if the germplasm is already a part of a germplasm group, that group ID will be preserved.
Include descendants
Include descendants in the grouping to ensure that all descendants from these lines can be tracked for inbred line development. This is useful in cases where the line has already been advanced. For example, a line may have been advanced to the F6, but the breeder considers the F5 to have been sufficiently homozygous and homogeneous to be considered the founder of an inbred lineage. The breeder would then open a list containing the F5, select the individual for grouping, and check 'Include descendants'. The F5 and any F6s derived from that F5 would then belong to the same group.
To assign a new Group Id to selected germplasm and their offspring, do not select 'Preserve existing group' and select 'Include descendants'.
The descendants by maintenance and derivative breeding methods will inherit the same GroupID as these selected F4s. Preserve existing group is not relevant in this example, because these lines are ungrouped.
Review the grouping results and select OK.
All entries received a new Group ID that will be inherited by the descendants.
The germplasm is now updated with a new Group ID.
Notice that the founder of a group's GID matches the Group ID. Subsequent advancement of the founder and its descendants will share this same Group ID, but will receive unique GIDs.
This table shows a list of seed increases from the previously grouped F4s. Notice that the newly created germplasm receives new GIDs, but shares the Group IDs of their progenitors (see F4 list in the example above).
Selection of individual germplasm reveals that this germplasm is a grouped line, Group ID.
Ungroup
If grouped germplasm is found to be "off-type" or segregating it can be ungrouped and removed from the shared lineage designation (Group ID).
Highlight germplasm and select ungroup from the Coding and Grouping Options of the Action menu.
Confirm
The selected line is now ungrouped - there is no longer a group ID associated with this entry. Ungrouping only affects the selected line. Ungrouping does not retroactively apply to descendants.
Apply code names to germplasm
Codes are customizable names that can be assigned to grouped lines at different stages of line development, such as inbred line fixation and hybrid formation. Coded names become the preferred name for the lines, and are inherited as the preferred names of descendants in the same group. There are three levels of codes which can be assigned at different stages of development and each level supersedes the other as the preferred name for the group as it is assigned to any member of the group.
From Manage Germplasm list view, assign codes to selected grouped lines from the Actions menu.
Coding Level
The BMS allows breeding programs to automatically name 3 different coding levels. For example, a program may want to update the name of germplasm after it successfully passes through a specific phase in the breeding process. Examples of breeding milestones that may be associated with code levels include: 'fixation' of inbred lines, successes after disease selection, creation of hybrids, line release.
Automatic name generation
Institutes can set automatic naming conventions through database customization. Please see your BMS database administrator for more information on your institution's coded naming conventions.
To use your institution's coded naming conventions, select 'Automatic naming generation' and Apply Codes.
Specify Codes Manually
Users are able to customize coded names via UI options.
Select 'Specify Codes Manually'. Enter the naming details and Apply Codes.
In this example, the 20 selected F4s are going to be renamed with the inbred line prefix "IL", a 3 digit sequence number, and a suffix "-18" to indicate the year of fixation.
Review the code results and select OK. Notice that the specified prefix has been concatenated with a sequence number to produce the code names.
Notice that the coded name is applied to all members of the group. In the first entry or example, GID 379138 & 366641 share the same group ID, so both are assigned IL022-18 as their preferred name. Also notice that the final entry shows that 379142 and 366645 have previously been coded, so the new name will not apply. The new name will not apply to GID 366646 because it is not part of a germplasm group.
Hybrid Line Development
When grouped lines are used to create hybrids using hybrid breeding methods, the BMS will automatically group hybrid duplicates. So, all crosses between lines having the same male and female parental groups form a single group of hybrids.
Group ID can be used to define inbred and hybrid lines. This example illustrates that crossing inbred lines with groupIDs of 15404 &15405, using a hybrid method will always result in a hybrid line with group ID 15619.
The BMS has several default hybrid breeding methods for producing candidate or more advanced hybrids. The method IDs of these hybrid crossing methods are customizable in the file C:\BMS4\infrastructure\tomcat\webapps\Fieldbook\WEB-INF\classes\crossing.properties. Contact your BMS Administrator to customize or add more hybrid methods.
Default Hybrid Breeding Methods
ID | Code | Name | Description |
321 | VHY | Hybrid formation | Forming a hybrid cultivar |
416 | TNL | Narrow based tester, line | Test (Top) cross between a known plant and a narrow based (1 or few plants) population. For practical reasons the tester population or line is used as the male which can be stored pollen. |
417 | TNP | Narrow based tester, pop | Test (Top) cross between a known population and a narrow based tester population. For practical reasons the tester population or line is used as the male which can be stored pollen. |
418 | TBL | Broad based tester, line | Test (Top) cross between a known plant and a broad based (many plants) tester. For practical reasons the tester population is used as the male which can be stored pollen. |
419 | TBP | Broad based tester, pop | Test (Top) between a known population and a broad based tester. For practical reasons the tester population is used as the male which can be stored pollen. |
426 | TCR | Test cross | Crosses made for generating hybrids for early generation testing. The females can be lines in any generation of inbreeding or DH lines, and the male is usually a fixed inbred line, or a F1 single cross between two fixed inbred lines. |
Cross Fixed Lines with Hybrid Methods
From Manage Studies: Cross fixed lines with a hybrid method. Generally, you will want to select 'Apply grouping to new crosses only" to ensure the hybrids inherit the same GroupID as those made previously. Continue.
Finish and save the cross list.
The resulting hybrids will receive a Group ID matching the parental groupings. Subsequent crossing of any member of the parental groupings, will result in hybrids with identical Group IDs. Hybrid grouping can also be coded (see above).
The parents of cross 1 have different GIDs, but the same GroupID. The parents of cross 1 are fixed F4 lines. The parents of cross 2 are grouped as the same fixed lines, except these are the result of an F4 seed increase. The hybrids have distinct breeding histories, but are grouped identically because they are considered genetically identical.
Create inventory lots
Create inventory lots allows you to generate lots one at a time through the user interface (see v26 Manage Inventory - IBP Support Knowledge Base - Confluence (atlassian.net) for batch functionality). This function also provides the option to specify an initial deposit amount in Manage Germplasm. This action requires that germplasm already exists in the system with GIDs. (See related topics: Import Germplasm, Crossing, Selections)
Select the desired germplasm using a filter or using the checkbox. From the Actions menu, select Create inventory lots option.
Fill in the required details. Stock ID prefix cannot end in a number. For the deposits, tick Initial deposit if the value is known. Otherwise, it is optional and the initial value can be recorded later on. Confirm transactions on saving can be unselected if there is another person responsible for checking or packing. Save.
If the lot creation is successful, you will receive a confirmation message and the germplasm is now updated with a lot.
