Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
GRIN-Global CE Server
GRIN-Global CE Server
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • GRIN-Global CE
  • GRIN-Global CE ServerGRIN-Global CE Server
  • Issues
  • #42

Closed
Open
Opened Jun 09, 2020 by Nora Castaneda-Alvarez@ncastanedaReporter

Genebank reporting

We want to enable partners to report on several genebank management aspects, using information recorded in GG. Partners should be able to report on:

  • Availability of selected crop collections - accession level.
  • Security (safety duplication) - accession level.
  • Data availability - accession level.
  • Distribution - accession level.

Some considerations to look upon are:

  1. Availability is estimated on four variables:
  • health - conducted at inventory level.
  • viability - conducted at inventory level.
  • quantity sufficiency - conducted at inventory level.
  • legal status - defined at accession level.
  1. Distribution: we also ask genebanks to report on:
  • type of recipient
  • country of recipient
  • distinguish between internal vs. external recipients (same institution or not)
  • exclude material sent to safety duplication
  • type of germplasm (SAMPSTAT)
  • distribution of subsets
  • purpose of the requestor
  1. Storage: we ask genebanks about the storage of inventory/accessions.

  2. Security: we ask genebanks to report on the places where they have sent material for safety duplication.

How to summarize inventory level to report at accession level?

  1. We also want to know how many viability tests are conducting per year.
  2. We want to know the number of accessions/inventory (?) regenerated and characterized per year.
  3. We want to know the number of requests received annually.
  4. We want to know the total number of accessions and number of unique accessions distributed annually.

Here is the table of indicators and targets applicable to Seeds for Resilience (indicators 1,2,3,5,11 are potentially estimated through GG):

Indicator Target at year 5
1 Availability: % collection which is clean of pathogens of quarantine risk, viable, and in sufficient quantity to be immediately available for international distribution from medium-term storage (or local distribution for some tree species). 90% accessions available
2 Security: For seed crops: % collection held in long-term storage at two locations and also in Svalbard Global Seed Vault (except for tree species). For clonal crops: % of the collection held in long-term storage or cryopreservation at two locations; % of the collection held in slow growth conditions in vitro at two locations 90% seed accessions safety duplicated 50% clonal accessions in cryo-preservation; Intermediate target 90% accessions duplicated in in vitro
3 Data availability Passport: PDCI >6 Characterization: 100% accessions with characterization data
5 Distribution: % of annual requests for seed samples from users successfully serviced 80% relevant requests serviced annually
11 Number of user requests for seed samples 100
Edited Jun 10, 2020 by Nora Castaneda-Alvarez
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: grin-global/grin-global-server#42