Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beat
  • beat.webbeat.web
  • Issues
  • #181
Closed
Open
Created May 20, 2015 by Philip ABBET@philip.abbetDeveloper9 of 9 tasks completed9/9 tasks

Reports: Model creation + Web API

About the model:

  • A set of hand-picked experiments
  • An author
  • A name
  • A documentation
  • A unique number (see attestations)
  • Must lock (not modifiable() nor deletable()) experiments assigned to it
  • Three possible states: edition, locked, published
  • The content of the report is defined using a JSON array (stored in the database), where each entry might represent either a table (which columns + how to sort the experiments + an optional caption) or a figure (whatever is needed to plot it + an optional caption)

Web API:

  • creation of a report
  • deletion of a report
  • retrieval of a report
  • retrieval of a list of reports
  • locking of a report
  • publication of a locked report
  • addition of experiments in a report
  • removal of experiments from a report
  • update of the content of a report

Each endpoint must be tested.

Assignee
Assign to
Time tracking