GGCE 2025.0 update

We are happy to announce the 2025.0 release of GGCE.

Please check the complete list of changes at:

This release wraps up the development in 2024. It brings improved BrAPI 2.1 compatibility, enhanced handling of the results of the last seed viability test, integration with https://validator.genesys-pgr.org to validate coordinates, and segregating accessions into distinct collections. There are also many smaller improvements and bug fixes.

Bugfixes and improvements:

Define a fixed URL where the recipient can find more information about the material listed in SMTA
Faster generation of accession data in MCPD format
English translation is automatically created when creating new translated entities
Record medium used in viability test
Filter accessions and inventories by attachment
Ensure OAuth client is registered for the Fieldbook app
Generate up to 100 label copies
Hex encode ~ and ^ for ^FD and ^FV using ^FH\ in ZPL
Support OAuth authentication with SMTP server
Genesys requests display request origin and requestor's preferred language
Uploading data to Genesys with progress dialog and error messages
Progress indicator when assigning DOIs in bulk

Database changes:

Added collection_code to accession (default value is DEFAULT)
Added last_viability, last_viability_date, last_viability_date_code columns to inventory_extra
Added queryTime to kpi_execution_run
Added materiel_id to inventory_viability

Validating coordinates of collecting sites

The Passport data > MCPD section has a new tool to Validate coordinates. It uses https://validator.genesys-pgr.org to validates coordinates against country of origin:

Genebank collections

Genebanks are commonly structured and organized by the crop or type of conservation. In Palmira they have a "Beans collection" and a "Cassava collection" and a "Forages collection", while at IITA they have "Banana collection", "Cowpea collection", etc. These different "collections" require different expertise that may or may not be crop specific. The collection does not affect the crop of the accession is not used in MCPD CROPNAME.

To facilitate the ease of access to data relevant to a specific collection, we added a new required field collectionCode to Accession. It uses a new CommunityCodeValue.ACCESSION_COLLECTION group where you can define your own groups.

Note: BrAPI defines collection as a "specific panel/collection/population this germplasm belongs to".

Last viability results

GGCE stores the initialViability and its date in SeedInventoryExtra and it also maintains a link to the InventoryViability of the last test performed on the inventory. There was high demand for carrying over the results of the last test when inventory is split or withdrawn. GGCE now also maintains the result lastViabilityResult and the date lastViabilityDate of the last test in SeedInventoryExtra. The values are populated when a test is completed.

These values are applied to withdrawn and split inventories: the last known viability and the initial seed viability are copied from the source inventory. We do not make a copy of InventoryViabilty since a test was not actually conducted on those new inventories.

BrAPI

2025.0.0 comes with improved BrAPI 2.1 compatilibity for synchronizing with the FieldBook app for collecting data in the field: both download and upload of trait observations.

Generating SMTA

Easy-SMTA allows for specifying a URL where the recipient can find more information about the material listed in SMTA. In the example below it points to Genesys:

You can configure the value of this URL with the smtaDataUrl in Admin > Application settings.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information