On viability testing
The common procedure for Viability testing in GG-CE is as follows:
- Someone (or something) flags the inventories that need to be tested for viability and adds them to the Pending viability test list
- Someone decides which of the inventories on the Pending list will go into testing now and requests retrieval of seeds.
- Retrieved seeds are packed and appropriately labeled.
- The viability team receives the seeds and executes the testing protocol, eventually producing the latest viability results for the tested inventories.
This text describes the tools in GG-CE in support of the procedure.
Flagging inventories for viability testing
When the user has decided that an inventory should be tested for viability (in the near future) they schedule an inventory action
Viability test for the inventory. A scheduled inventory action is one that is in the database, but does not yet have a
One can schedule inventory actions from the Inventory list page by first selecting the inventories, then clicking the Schedule inventory action button:
In the dialog you select Viability test for action type and confirm. If you now check the Pending inventory actions list, you'll notice the freshly added records:
Until this inventory action is started and becomes in progress (because it has a
startedDate), GG-CE considers the inventory is Scheduled for viability testing.
Deciding what to test (this month)
The Pending viability test list will grow way beyond what can be tested in a month or two. It may have thousands of inventories waiting for viability testing.
In the Viability section you will find the Prepare order function. It lists inventories with pending viability tests:
Select the ones that should go for testing (now) and click "Prepare order":
In the dialog, select the
Cooperator that will receive the seeds for testing:
After hitting "Create Order", the system will:
- Create the
OrderRequestfor selected inventories with the quantities defined in the
InventoryViabilityRule(e.g. 2 x 40 seed = 80 SD)
nullvalue for end viability result
- Mark the pending inventory action
Viability testas started, removing these inventories from the list Pending viability test
Seed retrieval / Order processing
The seed retrieval follows its own process and eventually the seed packets are delivered to the Viability team to do the testing.
Viability team receives the seed packets. They scan the inventory barcode which will immediately display the
InventoryViability record prepared earlier.
The Print labels button prints labels for each replicate.
The replicates are prepared for testing based on
grin-global-ui#256 (closed) has details.
The viability test labels printed for each replicate are unique to the replicate. By scanning the barcode, the previous observations are loaded and can be edited. A new observation can be registered.
A button to Finish testing is available.
The details are in grin-global-ui#257 (closed)
Finish viability testing
The results may require Retesting and since this is more of an exception than a rule, we will discuss that separately.