Please do work for this task in a branch called issue-107.
The goal of API End Points is to enable external services to both read and write to our database in accordance with our data model.
For example, it should be possible for a member of the Lava Lab to read from our database in order to build a visualization of OPQ data.
Similarly, it should also be possible for the Smart Campus Energy Lab to develop an external service that writes location-based solar data to our database as Annotations (or perhaps some other as-yet undefined data model entity).
This task might consist primarily of documentation of the procedures necessary for reading and writing, and for obtaining access to the database. I don't know if it involves development of code.
Please do work for this task in a branch called issue-107.
The goal of API End Points is to enable external services to both read and write to our database in accordance with our data model.
For example, it should be possible for a member of the Lava Lab to read from our database in order to build a visualization of OPQ data.
Similarly, it should also be possible for the Smart Campus Energy Lab to develop an external service that writes location-based solar data to our database as Annotations (or perhaps some other as-yet undefined data model entity).
This task might consist primarily of documentation of the procedures necessary for reading and writing, and for obtaining access to the database. I don't know if it involves development of code.