Skip to content

GGCE 2024.5 update

We are happy to announce the 2024.5 release of GGCE.

Please check the complete list of changes at:

This release adds Collecting missions and the map of Collecting sites! It also comes with improvements to workflows: steps can be triggered conditionally and can be configured to start with a delay.

Bugfixes and improvements:

  • Selecting species and genus now includes full names
  • Only Administrators can update the inventory barcode manually
  • Actions for which users don't have permissions are hidden
  • Updated UI for managing schedules based on user feedback
  • Show history of changes to accession's taxon
  • Fixed a bug in tables where row selection was not possible after scrolling it out of view
  • Label templates are generated on the server instead of client
  • Use {{#RFIDBARCODE}}{{{inventory.barcode}}}{{/RFIDBARCODE}} in ZPL template to prepare UUID for printing RFID tags
  • Apply preservationMethod and regenerationMethod to withdrawn inventories
  • Fixed a bug that prevented users from cleanly logging out

Database changes:

  • Added exploration_id to accession
  • Added delay to workflow_step
  • Added condition to workflow_transition
  • Added notNull constraint to sort_order in sys_dataview_param

Collecting missions

The Collecting missions in the Passport data section allow you to record information about explorations organized by your institute, with details about target species, funding and the period of collecting.

image

Passport data of the material collected during the mission is linked directly to the exploration and an accession can belong to only one exploration.

Map of collecting sites

We also added Collecting sites to the Passport data section: this displays the localities of where the material was collected (from accession source records) on a map! You can focus on the accessions of interest by applying filters.

image

Clicking on the map will fetch the list of accessions associated with that location:

image

Workflows

Delaying the next action

After a workflow step is completed, the next action in the workflow can be scheduled with a delay. Delays are specified as periods of time in the format PxYyMzD where P prefix is mandatory and the other parts are optional, but must appear in the correct order: Y > M > D.

image

Example period Description
P1D Delay for 1 day from completion of the previous action
P1M Delay for 1 month from completion of the previous action
P1Y Delay for one year
P6M7D Delay for 6 months and 7 days

Conditional steps

Workflow steps can be triggered conditionally: when an action is completed, the condition (if defined) is evaluated and the target action step will be scheduled only when the condition expression evaluates to true.

image

Context Example condition Description
Accession action accession.mlsStatus == null Schedule target step only if accession's MLS Status is not set
Inventory action inventory.quantityOnHand < 100 && inventory.quantityOnHandUnitCode == "SD" Schedule target step only if inventory quantity is less than 100 seed
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information