LIDO Data management system

The LIDO Data Management system provides tools and API to upload, manage and visualize your datasets collected in the LIDO experimental orchards. A general description of the LIDO project can be found in the project's main page. It is composed by the following components:

  • Lido Data Portal: It provides access, links and documentation for all the functionalities of the system.
  • Influx-DB: it is a powerful no-SQL Data Base (DB) that allows organization and management of long time series datasets like observations and measurements:
    • DB: collects all datasets
    • API: it provides web access to write and read data to/from the DB to allowed users only
    • web interface: it provides a web Graphical User Interface (GUI) to create databases, data visualization, upload, management and visualization dashboards.
  • FTP server: it provides a file storage to send data from devices or servers using File Transfer Protocol (FTP). Information and credentials to use FTP server will be provided after the registration of the Organization

The system is available only for registered organizations. Use the Registration page to register your organization and receive the necessary information and credential to use the portal and its functionalities.

Key concepts to work with Lido Data management system and Influx-DB

The core components of the Lido Data management system is based on Influx-DB. It is a no-SQL database to work with long timeseries of data. The few but fundamental concepts that you need to understand to upload and visualize your data are the following Influx elements:

  • Organization: it is the environment where each registered organization can organize their databases (buckets), dashboards, without the risk that other organization could access them.
  • Bucket: all InfluxDB data are stored in a bucket. A bucket combines the concept of a database and a retention period (the duration of time that each data point persists). The retention period by default is infinite, but it can be set to a specific duration (months, days, etc.) to save space and automatically delete non-interesting datasets. A bucket belongs to an organization.
  • Measurement: Measurement names are strings. A measurement acts as a container for tags, fields, and timestamps. Use a measurement name that describes your data. It represents a sort of table to group your data. You can define the measurements according to your needs. Measurements can be a sensor, a location, a station or whatever you want.
  • Token: It is the secret key you can create in the web interface to give read/write permissions to specific buckets (only in your organization) to the users/applications you want. Token are necessary to upload data by the API or to query (read) data through the API. A tipical use case is the data retrieval using a client like python, R or shell scripts or web application like Grafana dashboards.

For a complete overview of the Influx elements we suggest to have a look to the InfluxDB data elements page.