GG-CE 2021.8 update
I’m happy to announce the availability of the v2021.8 release of GG-CE.
2021.8 adds improved support for Viability Testing, including label printing for test replications and calculation of the final test results. Request management is moved to a new "section" and it provides a Retrieval list function with an option to print the items requested for retrieval from storage.
Please check the complete list of changes at:
- Announcement #93 (closed)
- Web https://gitlab.croptrust.org/grin-global/grin-global-ui/-/releases/v2021.8
- API https://gitlab.croptrust.org/grin-global/grin-global-server/-/releases/v2021.8
- The data type of all
descriptioncolumns in _lang tables are converted from
nvarcharin 797fa28 to allow for UTF-8 text. This change does not affect operations of GG-CE.
- There are no other changes to the database model between v2021.7 and v2021.8 release
- Recording viability observations and final test results.
- Printing labels on Android to printers connected via Bluetooth Classic or Bluetooth LE.
- Retrieval list guides technicians in preparing inventories for distribution.
- Added configurable password policy.
- Mapping to MCPD is highly customizable by using the "MCPD" language.
- Administrators can browse and filter Audit Log records generated by GG-CE Server.
Improvements and bug fixes:
- Managing attachment details is enabled for Crops and Crop Traits.
- Request management moved to a new "section" of GG-CE Web.
This release includes improved support for Viability Testing. We added support for printing labels for each replicate. GG-CE provides a default label template, but it is customizable in Admin > App Settings screen. The label uniquely identifies each test replication and allows technician to make multiple observations during the test.
Step 1: Begin testing
(No change since
2021.7) The technician begins the testing process by scans the inventory barcode on the received packet (inventory.barcode) and is able to print labels for test replicates as per inventory viability rule. They prepare and label each replicate and begin the test.
Steps 2-5: Record counts
Multiple counts are made during the test. The technician scans the barcode of the replicate and is presented with a screen with previously recorded observations. Tapping "Add observation" opens the screen to add a new "count". The screen is significantly updated since the previous release.
- "Tested count" may be updated to reflect that less than required number of seed are in this test replication.
- Current observations are entered into "Normal count" and other count fields (see under "Advanced").
- All counts are aggregated and used to calculate the Remaining seed in the test. When this number is
0, there are no more seed to evaluate.
When inputting the subsequent counts, the technician inputs the current counts for that observation.
The previous count + the current count represent the sum total that contributes towards Remaining seed to be evaluated next time:
Step 6: After the observations are complete and there are no more seed to evaluate, the technician may tap the Finish test button:
GG-CE Server will calculate the results of the viability test across replications and present the calculation results to the user for confirmation:
- The results are not yet saved to the database. The technician may update the fields.
- The screen shows which data contributes to summarized values.
Percent viable represents the test results and is calculated across replicates and across different evaluated categories:
Summarized results for replications shows final data for each replication and allows the user to return and update individual observations, and then recalculate test results:
Last step: hitting the Save button stores the results of the viability test in the database.
Requests: Retrieval list
The Retrieval list provides technicians with a special display of requested source inventories: location, quantity on hand, inventory and accession data.
Step 1: Scan the barcode of the
Step 2: Browse (or Print) the source inventories. By hitting the X button, user is returned to the barcode scanning screen:
We will focus on managing withdrawal and printing package labels for
2021.9. That release also aims to improve support for managing request data in preparation for withdrawal and distribution.
GG-CE Server records changes to the data. Audit logs include who, when, and what change was made to the data or deleted from the database.
The new tool enables Administrators to explore audit logs, and identify and react to any unwanted changes in the system: