Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • GraceDB Server GraceDB Server
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 107
    • Issues 107
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • IGWN Computing and Software
  • GraceDB
  • GraceDB ServerGraceDB Server
  • Issues
  • #77
Closed
Open
Created Nov 01, 2018 by Leo Pound Singer@leo-singerContributor

Remove "Vetted" param

Our VOEvents contain the following param:

<Param name="Vetted" dataType="int" value="0" ucd="meta.number" unit="">
<Description>
Indicates whether this candidate has undergone basic vetting by humans
</Description>
</Param>

However, this is redundant because we define preliminary alerts as alerts that have not undergone human vetting whereas initial, update, and retraction alerts have been vetted.

I suggest removing this flag. If we want to preserve the human-readable comment, then it can go inside <Why><Description></Description></Why>.

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