|
|
The main goal of a genebank is to conserve germplasm and to do so it is important to ensure samples are kept alive, so germination testing is a fundamental task.
|
|
|
|
|
|
The seed viability functions provided by GRIN-Global CE help tracking, recording and scheduling actions associated with operations performed during the viability testing workflows.
|
|
|
|
|
|
Typically, the sequence of steps in viability testing is as follows:
|
|
|
|
|
|
1. Schedule an inventory action for the viability test.
|
|
|
2. Prepare an order, associated with the scheduled viability test, for receiving the material to be tested.
|
|
|
3. Once the material has arrived, subdivide each sample into replicates.
|
|
|
4. Observe and record the germinability of each replicate.
|
|
|
5. Finish the test and calculate the seed viability.
|
|
|
|
|
|
The first thing that must be done is to schedule an inventory action to for a germination test, this is done in the *Inventory* section of the application.
|
|
|
|
|
|
![viability-schedule](images/viability-schedule.png)
|
|
|
|
|
|
You select the inventory item and press the **Schedule inventory action**.
|
|
|
|
|
|
![viability-schedule-save](images/viability-schedule-save.png)
|
|
|
|
|
|
# Prepare order
|
|
|
|
|
|
![viability-order](images/viability-order.png)
|
|
|
|
|
|
The **Prepare order** option will display the list of inventories whose viability has been scheduled to be tested. This is determined by the **Viability test** inventory action created above, whose *Not before date* is prior to the current date and the action has not yet started.
|
|
|
|
|
|
To prepare a viability test order you select one or more scheduled inventories in the list and press the **Prepare order** button.
|
|
|
|
|
|
![viability-order-prepare](images/viability-order-prepare.png)
|
|
|
|
|
|
The form allows you to add the **Inventory Viability Rule**, which is a categorical value indicating what workflow the viability testing should follow. **Maintenance Site** can be used to select the site where the germplasm must be shipped. Finally, select the **Cooperator** to whom the germplasm must be shipped to.
|
|
|
|
|
|
Below the input fields there is the list of the inventory items that should be tested, therefore ordered.
|
|
|
|
|
|
By pressing **CREATE ORDER** a *Germination* request for material is created and entered in the *Requests* section of the application.
|
|
|
|
|
|
![viability-order-done](images/viability-order-done.png)
|
|
|
|
|
|
# Begin testing
|
|
|
|
|
|
Once the material order has been evaded, you will receive the germplasm to be tested, at this point you can start preparing the sample replicates to be processed.
|
|
|
|
|
|
![viability-begin-testing](images/viability-begin-testing.png)
|
|
|
|
|
|
You scan or type the inventory item’s barcode and you will get the following screen.
|
|
|
|
|
|
![viability-begin-testing-details](images/viability-begin-testing-details.png)
|
|
|
|
|
|
This screen can also be reached if you press a link in the *Inventory* column in the *Viability records* screen**.**
|
|
|
|
|
|
The screen displays the viability status of a tested inventory item. The upper part displays information on the inventory, the accession from which it is derived and the details of the replicates and seed count to be used during tests.
|
|
|
|
|
|
The lower list contains the individual viability test observations; note that in the current example the inventory item has not yet been tested, so the list is obviously empty.
|
|
|
|
|
|
The middle part of the screen has three buttons: **REMOVE**, which will remove the current inventory item from the test, **FINISH TEST**, which will calculate all the cumulative statistics of the test and **GENERATE LABELS**, which will generate the labels to be applied to the replicates.
|
|
|
|
|
|
If we follow the order of events up to this point, we have just received the germplasm to be tested, so we will press the **GENERATE LABELS** button to tag the replicate samples and print the physical labels to be applied to the sample containers.
|
|
|
|
|
|
A confirmation alert is displayed.
|
|
|
|
|
|
![viability-labels-ready](images/viability-labels-ready.png)
|
|
|
|
|
|
The application will generate a text, in the [Zebra Programming Language (ZPL)](http://wiki/Zebra_Programming_Language) that can be fed to the label printer.
|
|
|
|
|
|
![viability-labels](images/viability-labels.png)
|
|
|
|
|
|
The application will generate one label per replicate, in this case for 2 replicates. Once the label printer is fet the above text, it will produce the following labels.
|
|
|
|
|
|
![viability-labels-1](images/viability-labels-1.png)
|
|
|
|
|
|
![viability-labels-2](images/viability-labels-2.png)
|
|
|
|
|
|
The barcodes of the viability replicates can be found in the first line of each label: *Viability 19#1* and *Viability 19#2*: which correspond to the barcodes **19.1** and **19.2**.
|
|
|
|
|
|
![viability-inventory-item-id](images/viability-inventory-item-id.png)
|
|
|
|
|
|
The barcodes correspond to the viability inventory ID, 19, and the replicate number, 1 and 2. These two codes represent the viability replicate barcodes that can be scanned, or typed in the application, to record viability observations.
|
|
|
|
|
|
The label template can be set in the *Admin tools* - *Application settings* section of the application, under the name *INVENTORYVIABILITY_REPLICATE*. To test your templates you can use the [Labelary site page](http://labelary.com/viewer.html).
|
|
|
|
|
|
# **Record new observation**
|
|
|
|
|
|
At this point we have subdivided the received germplasm into the required number of replicates, we have prepared the samples for germination and, when it is time to test the samples, we are ready to record observations.
|
|
|
|
|
|
![viability-observations-scan](images/viability-observations-scan.png)
|
|
|
|
|
|
You scan the replicate label or insert its barcode into the above field.
|
|
|
|
|
|
![viability-observations-scanned](images/viability-observations-scanned.png)
|
|
|
|
|
|
The screen shows the inventory item’s quantity on hand, its type and the viability rule for testing. The **VIEW TEST** button will return you to the details view of the **Viability records** option. The **ADD OBSERVATION** will allow you to record the test observation details.
|
|
|
|
|
|
![viability-observations-add](images/viability-observations-add.png)
|
|
|
|
|
|
The form will display the **Replication Number**, the **Counting Cooperator**, the **Count Number** and the **Count Date**.
|
|
|
|
|
|
The **Tested Count** and the **Remaining Seeds** will be automatically updated as you add the observation counts.
|
|
|
|
|
|
The **Normal Count** and **Abnormal Count** represent the cumulative number of samples that respectively displayed normal and abnormal germination.
|
|
|
|
|
|
If you need to be more specific in the status of the tested samples you can disclose the *Advanced* pane, here you can add observations for **Unknown**, **Dead**, **Empty**, **Infested**, **Hard**, **Dormant**, **Estimated Dormant**, **Treated Dormant**, **Confirmed Dormant**, **TZ Positive** and **Tz Negative** counts.
|
|
|
|
|
|
The **Note** field can be used to add more details.
|
|
|
|
|
|
When you press the **Save** button, the observation is recorded.
|
|
|
|
|
|
![viability-observations-added](images/viability-observations-added.png)
|
|
|
|
|
|
At this point you can view the data for all the replicates by pressing the **VIEW TEST** button, or add other observations for the same replicate by pressing the **ADD OBSERVATION** button.
|
|
|
|
|
|
# **Viability records**
|
|
|
|
|
|
The list of all viability tests can be consulted with this option.
|
|
|
|
|
|
![viability-records](images/viability-records.png)
|
|
|
|
|
|
By selecting a row you can edit the record, while by clicking on the links in the *Inventory* column you can see the details of that test. Once testing has been completed you can use this page to access the details of the test.
|
|
|
|
|
|
![viability-finish](images/viability-finish.png)
|
|
|
|
|
|
This is the same screen in which we printed the labels, now we have finished testing the samples and we are ready to close the test by pressing the **FINISH TEST** button.
|
|
|
|
|
|
![viability-observations-result](images/viability-observations-result.png)
|
|
|
|
|
|
This will perform all necessary calculations and return a form with all calculation details. By pressing the **SAVE** button you close the viability testing and set a viability percentage value for the inventory item tested.
|
|
|
|
|
|
![viability-observations-done](images/viability-observations-done.png)
|
|
|
|
|
|
# Viability actions
|
|
|
|
|
|
![viability-actions](images/viability-actions.png)
|
|
|
|
|
|
This option can be used to consult viability actions which are in progress, pending, completed and scheduled, press the corresponding tab button to access the list.
|
|
|
|
|
|
# **Viability rules**
|
|
|
|
|
|
Viability rules contain the necessary information to define how samples should be tested for viability.
|
|
|
|
|
|
![viability-rules](images/viability-rules.png)
|
|
|
|
|
|
By pressing the ➕ button you can create a new rule.
|
|
|
|
|
|
![viability-rules-add](images/viability-rules-add.png)
|
|
|
|
|
|
An inventory rule has a unique **Name**, a **Category**, the **Number of Replicates** and the number of **Seeds per Replicate**. These two latter values are used to automatically keep track of the tested samples.
|
|
|
|
|
|
Other information are the **Requirements** for the testing, **Count Regime Days**, **Substrate**, **Lighting**, **Moisture**, **Prechill** and **Temperature Range**.
|
|
|
|
|
|
The section starting with *Requirements* should contain all that is needed to define the viability protocol. All the fields are full text, so the form doesn’t expect numeric or coded data: one should take advantage of these free fields to describe as much as possible the various aspects and steps, intervals and environmental conditions needed to correctly implement the testing protocol.
|
|
|
|
|
|
![viability-rules-edit](images/viability-rules-edit.png)
|
|
|
|
|
|
By selecting a row in the list you can delete a viability rule, or view its details for adding additional information. |
|
|
\ No newline at end of file |