Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Genesys Backend Genesys Backend
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 28
    • Issues 28
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Genesys PGRGenesys PGR
  • Genesys BackendGenesys Backend
  • Issues
  • #26
Closed
Open
Issue created May 14, 2017 by Matija Obreza@mobrezaOwner

Sample data generation

Genesys uses FirstRunListener to generate content on startup:

  1. Updates Country data
  2. Update FAO WIEWS data
  3. Update Geo Regions

The CreateContentListener and CreateAdminListener generate initial content and the first Administrator user.

To make testing more friendly, update FirstRunListener to also generate:

  1. Add one OAuth client
  2. Two Crops: sweetpotato and sorhgum
  3. Accession data

Generating accession data

Skip this part

Most appropriate approach would be to include 2-3 text files containing accession JSON in the project. These files would be parsed and passed to BatchRESTServiceImpl#upsertAccessionData method. Perhaps we encode the instCode in the file name:

  • PER001.json
  • IND002.json
Edited Oct 06, 2017 by Matija Obreza
Assignee
Assign to
Time tracking