Documentation des données
Trouvez ci-dessous une liste de nos tables de données.
Les tables marquées avec un
sont deprecated et ne doivent pas être utilisées pour l'ingestion de données.
Toutes les données importées seront soit directement importées, soit converties dans cette structure. Les données qui ne peuvent pas être directement mappées sur les colonnes existantes sont collectées dans la colonne json personnalisée.
Plus de documentation et d'informations pour les utilisateurs de prospect peuvent être trouvées dans le
Wiki Prospect
| yearly_reports | This tables aggregates the data from the reports table into yearly summaries. It allows for simplification of queries on Grafana. |
|---|---|
| trust_trace | Trust Trace - the results of data validations and checks on subjects from other tables. Populated by data processors. |
| test | This is the description of the table. This table saves test data and is used to test things like import / anonymization / types / views and whatever you can think of. Some column names are reserved id - used internally as id created_at - timestamp when record was inserted updated_at - timestamp when record was updated source_id - the id of the data source import import_id - the id of the exact import process which created / updated the data custom - json column to store all imported data which was given but not mentioned in table structure below visibility - in views - what level of visibility was provided source_name - in views - name of the datasource source_organization_name - in views - name of the organization which provided the data Type is one of the rails db migration types. |
| targets | This tables saves targets data for Ascent reports submitted by PIUs. It allows for tracking and validation of targets set for various metrics. |
| shs_ts | Time Series data of individual Solar Home Systems |
| shs | Represents installations of Solar Home Systems at individual customers |
| reports | This table saves data from Ascent reports submitted by PIUs for both connections and non-connections based metrics. It saves them in the same level of granularity as the submitted report, allowing for validation checks and data ingestion. |
| payments_ts | Payment time series data for SHS Accounts or Meter Accounts |
| paygo_source_snapshots_ts | Time series data containing daily paygo account snapshots as reported directly from CRM data sources (e.g. Paygops, Angaza). |
| paygo_snapshots_ts | Time series data containing daily snapshots of paygo-type accounts (e.g. Paygops, Angaza), containing both internally calculated and CRM-sourced fields. |
| meters_ts | Time Series data of individual meters |
| meters | Represents installations of on-grid or mini-grid meters at a specific customer. |
| meter_events_ts | Time Series data of events processed from meters_ts |
| installations_ts | Time Series data of individual devices |
| installations | All Installations of our devices. This could be an SHS, a grid, a meter, etc. |
| grids_ts | Time Series data of individual grids |
| grids | Static data about electrical grids - minigrids as well as national grids |
| customers | All our Customers |
| agents | All our Agents (Installers/Sales Agents) |
| custom | This tables saves completely custom data as json. For easier export and graphing per source views with customizable structure are automatically created. |