Currently we have a table to set units in the database. We havent yet implemented a model for sensors. For these two entities it would be nice to have more specifications. For example for units, a list of predefined units available, and maybe an example of list of sensors.
In the case of sensors, we might probably need a table to specify types of sensors, and another table to actually enter sensors. The second one might not be strictly necessesary because we have readings, and a reading could be simply tagged with a unit and maybe a type of sensor.
Hi Jose, here is the list of sensors we have. My thoughts aligns with yours. Maybe we can discuss further next Tuesday to see what specifications we need.
Currently we have a table to set units in the database. We havent yet implemented a model for sensors. For these two entities it would be nice to have more specifications. For example for units, a list of predefined units available, and maybe an example of list of sensors.
In the case of sensors, we might probably need a table to specify types of sensors, and another table to actually enter sensors. The second one might not be strictly necessesary because we have readings, and a reading could be simply tagged with a unit and maybe a type of sensor.
It would be great to have your view on this.