Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • GGCE Server GGCE Server
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GGCE
  • GGCE ServerGGCE Server
  • Issues
  • #46
Closed
Open
Created Jun 16, 2020 by Matija Obreza@mobrezaOwner

Reporting: Safety duplication

(The Original) GG records backup site1 and 2 on Accession level which is not really sufficient for appropriate management of backups.

In GG-CE we wish to record the inventory-level records for material sent for safety backup. This will allow us to report on:

  • Age of the backup
  • Quantity
  • Location

Seed crops

  • % collection held in long-term storage at two locations and also in Svalbard Global Seed Vault (except for tree species).

That's doable with the approach proposed in GG-CE.

Clonal

  • % 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

That's doable with the approach proposed in GG-CE.

Questions for @ncastaneda:

  1. Do we need to take the age of backup into consideration when reporting safety duplication?

We cannot rely only on OrderRequest type BACKUP as that only tells us what was sent for safety duplication.

We need to maintain all safety duplicated material as Inventories in GG (at a backup Site).

If we want to know what happened in a specified period of time (a year), we need to timestamp the appropriate events:

  1. When the material was added to backup site: we can use existing fields in Inventory to determine when it was added.
  2. When it was removed from backup site? Removing material from backup site means flagging the Inventory with some specific flag and inserting an action.

We need to scan additions (by date) and "deletes" (by action) to be able to determine what was replaced, removed and added.

I don't think there is a way to do it without having Inventory level data for material at backup locations. Any thoughts?

Edited Jun 16, 2020 by Matija Obreza
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking