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 37
    • Issues 37
    • 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
  • #64
Closed
Open
Created Jul 01, 2020 by Grace Capilit@gcapilit

Acquisition: Checking for Duplicates

After documenting incoming materials to the Genebank, we want to check whether we already have a copy of these newly received materials in the Genebank, either as registered seeds (accession) or unregistered samples (from another incoming batch with TemporaryID only)

This function will search the database for similar entries by name (cultivar name, DonorID, CollNo, etc) using algorithms for

  • exact match
  • edistance
  • soundex

Checking for duplicates can be done

  1. by batch where the user can either specify/choose the BatchID of the incoming materials to be compared or upload list from a file or
  2. by entry where a name is entered in the search box
Edited Jul 29, 2020 by Grace Capilit
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking