Skip to content

Recode sensor statuses to include good/bad as a separate flag #10

Description

@monica-pwd

Right now, many features of the sensor hub hinge on whether a sensor is in good order or not. When we added a second good order status, many individual areas of code needed to change, Moreover, several features are hardcoded to the status name rather than using a key.

To resolve both issues,

  • the sensors.tbl_status_lookup table should be amended to include field that indicates whether a sensor is good for deployment or not
  • the downstream data structures that include the sensor statuses should include both the ID key for the status and the good order key
  • features in the app should be modified to use either of those keys as appropriate

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions