Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • satnogs-network satnogs-network
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 192
    • Issues 192
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • librespacefoundationlibrespacefoundation
  • SatNOGSSatNOGS
  • satnogs-networksatnogs-network
  • Issues
  • #868
Closed
Open
Issue created Nov 04, 2022 by Dan White@etihwnad

Include observation creator information via the API

The web view displays the creator username of a particular observation with the label "Observer", which is stored in the field author. While stored as author it is commonly also called observer.

This information is not available at the /api/observations API endpoint.

Related user information is available as waterfall_status_user and the deprecated vetted_user fields returned by the API already.

Including who created the observation is useful for e.g., giving credit to someone for scheduling an "interesting" observation, or extracting via the API various statistics about the implied scheduling priorities of users. The information is already public via the web view, but an analyst wanting to make use of that information must currently scrape the HTML.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking