... | ... | @@ -2,10 +2,6 @@ |
|
|
|
|
|
**GG-CE** assists in the internal data management of genebank collections. The primary objective is to capture and make use of data across routine genebank operations: acqusition, management and monitoring, and distribution of material in the collection.
|
|
|
|
|
|
1. Inventory management and monitoring
|
|
|
2. Passport and trait data management
|
|
|
3. Management of requests for material and related distribution processes
|
|
|
|
|
|
Only select aspects of the data in GG-CE are shared with external users (e.g. via Genesys).
|
|
|
|
|
|
## Inventory management
|
... | ... | @@ -44,13 +40,47 @@ Accession **passport data** is critical for any collection. The time gap between |
|
|
|
|
|
Curation and updating of passport data continues long after the acquisition itself, as the provider of material makes updated and curated information available (e.g. in [Genesys](https://www.genesys-pgr.org/)). GG-CE enables genebanks to proceed with introduction processes while the data itself may not yet be available.
|
|
|
|
|
|
## Material requests
|
|
|
|
|
|
GG-CE communicates with other systems, such as Genesys, the latter can be used as a public portal to enable users to order gene bank material electronically. GG-CE will take care of recording the requests and publishing to Genesys the updated passport data inventory.
|
|
|
|
|
|
## The application
|
|
|
|
|
|
**GG-CE** is deployed as a web application comprised as two main components: a *server* and a *client*. The server implements the main business logic and takes care of storing the application's data. The client provides the user interface to the user's browsers and communicates with the server to persist state.
|
|
|
|
|
|
The main interface is the GC-Client which is accessed through a web browser. The server does implement a user interface, but it is dedicated to administrative tasks performed by gene bank technicians and managers.
|
|
|
|
|
|
The application user interface is divided into two distinct areas: a left *navigation pane* which contains a hierarchical list of commands and a right detail pane that displays the page corresponding to the selection in the left pane.
|
|
|
The GG-CE-Client user interface is divided into two distinct areas: a left *navigation pane* which contains a hierarchical list of commands and a right detail pane that displays the page corresponding to the selection in the left pane.
|
|
|
|
|
|
![application](../documenting/images/application.png)
|
|
|
|
|
|
The left navigation pane represents the main gene bank areas that the application documents.
|
|
|
|
|
|
*Passport data* deals with accession level data. It is possible to consult the list of all accessions documented in the gene bank, including information regading their backup, core collection and web published status. It is also possible to consult the Multicrop Passport Descriptors (MCPD) associated with each accession. There is an option to display a summary of accessions grouped by a number of characteristics. Finally, one can check in progress, pending and completed actions related to accessions.
|
|
|
|
|
|
*Inventory* deals with the management of packets, cryo tubes or plants in the field, it allows gene bank staff to track where germplasm is currently stored, deployed, for what purpose and to which accession it belongs. This application section provides the key functionality for managing resources in the gene bank. It is possible to have a summary of inventories subdivided by a number of variables. One can consult actions associated with germplasm which are in progress, pending or completed. It is possible to check available amounts and availability status on germplasm, also by scanning barcode labels. Finally, it is possible to create new germplasm records by importing data from spreadsheets or creating new acquisitions.
|
|
|
|
|
|
*Distribution* deals with material requests, either internal to the gene bank or for external requestors. One can see the current list of pending requests, verify request items via barcode scanning, print retrieval lists by scanning the order barcode, or consult material requests recieved via the Genesys website.
|
|
|
|
|
|
*Seed viability* deals with the scheduling and data capture of seed viability checking. It will select gerplasm which is due to be tested, prepare the material order, associate a viability rule and record observations. The actions associated with the testing activities can also be managed by this option. This set of features can be used to ensure the gene bank keeps a sufficient germplasm quantity before germination levels fall below safe rates.
|
|
|
|
|
|
*Taxonomy* deals with the scientific classification of material stored in the gene bank.
|
|
|
|
|
|
*Crops* and *Trait data* deal with the evaluation of material stored in the gene bank.
|
|
|
|
|
|
*Geography* provides a common geographic administrative level information standard which can be used in the other application areas when referencing locations.
|
|
|
|
|
|
*Methods* is an entity that groups together a set of characteristics and contexts under a single definition which can be associated with actions applied to germplasm. It includes reasons for performing actions, plant anatomical part definitions and geographic administrative information and coordinates.
|
|
|
|
|
|
*Cooperators* is an address book and information resource on all staff which contributes to data handled by the application. It is particularly important since all information records in the application come with a time stamp and the reference to the staff that created it.
|
|
|
|
|
|
*Admin tools* collects all functionality needed fo application configuration and ancillary data management. This set of commands is only available to users which have the specific role of application administrators.
|
|
|
|
|
|
The user interface behaves in a consistent way featuring essentially three user interface component classes:
|
|
|
|
|
|
1. *Menus* which are comprised of the left navigation pane, which is always visible and holds first end second level commands, and optional menus above the right detail pane which feature third level commands associated to the current detail page.
|
|
|
2. *Detail pages*, which are displayed in the right pane. These pages are divided into *tables*, which are used to browse information organised in a list and *forms* which are used to capture information provided by users.
|
|
|
|
|
|
Table rows can be selected to create groups. When a list element refers to a specific entity the cell contains a link to that entity, such as an accession number in an inventory list. The list header allows hiding and sorting columns, this selection is stored as a preference associated to the specific user. When relevant, lists feature a plus sign button to enable users to create a new entry.
|
|
|
|
|
|
Forms are implemented as pages, when available as a first level choice, or overlays, when the form references an entry in a table. Some forms feature an expanded area under the control which includes the label and input area which can display documentation regarding the control; this feature is not yet globally implemented, but could be key in providing reference documentation in-app. |