GG-CE 2022.2 update
I’m happy to announce the availability of the 2022.2
release of GG-CE!
Please check the complete list of changes at:
- Announcement #137 (closed)
- Web https://gitlab.croptrust.org/grin-global/grin-global-ui/-/releases/v2022.2
- API https://gitlab.croptrust.org/grin-global/grin-global-server/-/releases/v2022.2
2022.2
improves the admin tools available for managing Code Values and allows for generating records for future inventories when distributing material for regeneration. It introduces Virtual Dataviews and Lookups for the Curator Tool. A few bugs are also squashed in this release.
New features:
- Added support for removing and replacing
CodeValues
- Added function to generate new inventories from order request items
- Virtual Dataviews and Lookups
- CodeValue statistics API
Improvements and bug fixes:
- Arabic, French and Spanish translations updated
- A more intuitive autocompleter when looking up species
- Added missing
@CodeValueField
annotations to the model - Refuse deletion of used code values
- Replace and remove a code value with another code
- Fixed incorrect role check when accessing API with OAuth Client authentication
- Use Lax HTTP ATiC cookie setting when not on https://
- MCPD: Accession availability is based on current inventory data
Database changes:
- Added
withdrawn_inventory_id
column toorder_request_item
(as foreign key toinventory
table) to hold the optional reference to the withdrawn inventory.
Tracking withdrawn material
Distribution of germplasm generally does not require the genebank to maintain the same level of detail for the sample as for the material in the collection (meaning that we do not register a new Inventory
record because we don't expect to monitor it in the future). Samples sent for viability or health testing may be tracked using the order_request_item_id
since the test results will be applied back to the source inventory.
Select cases however require the genebank to manage the information about the withdrawn material. Samples sent for safety duplication should be handled as if they are just in a different room: you want to know the quantity, location, dates, etc. about everything that is backed up. Similarly, material sent for regeneration will (hopefully) come back to the genebank and the database should be ready to receive the fresh material when it arrives.
GGCE now allows you to generate Inventory
records for distributed OrderRequestItems
and links each new record with its source inventory and populates the necessary fields. Split and Canceled order request items are ignored.
After triggering "Generate withdrawn inventories" the resulting list shows newly generated inventories:
These "inherit" the data from their corresponding source inventory, but do not have the quantity or location specified.
Managing Code Values
GGCE now protects code values from being removed from the database if they are currently in use. At the same time, it allows for removing unused codes and for merging two codes with the same meaning into one code. It is also able to detect any codes that are used in the database, but are missing definitions as Code Values (and translations).
This release adds new tools for GGCE Admins to manage code value definitions:
Virtual Dataviews and Lookups
MSSQL database engine is primarily used for full compatibility with the Dataviews included with GG. We are making progress towards removing the dependency on MSSQL for GGCE server and the important first step is to avoid using sql_dataview
and related tables.
GGCE introduces virtual dataviews and lookups that are generated from the object model and do not require manual updating of the sys_*
data with the GG Admin Tool. Virtual dataviews and lookups still allow for using the Curator & Search Tools with GGCE for bulk data manipulation.