Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • nomad-FAIR nomad-FAIR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 218
    • Issues 218
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 30
    • Merge requests 30
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nomad-labnomad-lab
  • nomad-FAIRnomad-FAIR
  • Issues
  • #1181
Closed
Open
Issue created Nov 17, 2022 by Markus Scheidgen@mscheidgOwner

Bundle format and functionality

An upload "bundle" is a data artifact that contains everything necessary to interpret the data of a single upload.

I needs to contain:

  • raw files (optionally)
  • archive (optionally based on a required)
  • all upload and entry metadata
  • all related DOI records
  • all necessary schema
  • a directory of all external references
  • hashes/checksums, etc. ideally following some long-term archive standard

We should use these "bundles":

  • to internally store immutable/published uploads
  • transfer uploads from installation to installation
  • import/export functionality
Edited Nov 18, 2022 by Markus Scheidgen
Assignee
Assign to
Time tracking