This page presents the data development documentation for Battery Conductivity for all sites.
This page was copied from Battery. Needs to be updated
The standard ETL areas and processes are described on LB Data Dev Architecture - General. |

All the schemas are available on google drive for further edition: |
ELN API → <Extraction> → Local JSON File |
| Spreadsheet | Description | Data Status* |
|---|---|---|
| ELN Conductivity Measurement | This is a standard ELN spreadsheet for all sites | |
| ELN Battery Experiment Properties | This is a standard ELN spreadsheet for all sites |
*Data Status: HOT: Data currently being updated at the source. It should be loaded regularly. COLD: No data changes at the source. It should be loaded just once.
The list of the spreadsheets/tables extracted from JSON files coming from ELN can be found in the Data Mapping of the next section.
| Document Name | Link |
|---|---|
| Battery - ELN Data Model | https://app.diagrams.net/#G1sD6OqKnBzSR_SrGvzlhEl7s5F5vUGQqD |
| Battery - ELN Template Documentation |
Lab server → Google Share Drive → <Copy> → Local XML/TXT file |
The instrument files are, most of them, manually added to a Google Drive Shared folder
| Site | Description | Status |
|---|---|---|
| Seoul | ||
| Brussels | ||
| Bollate | ||
| Aubervilliers |
*Data Status: HOT: Data currently being updated at the source. It should be loaded regularly. COLD: No data changes at the source. It should be loaded just once.
No data mapping needed as the data is copied exactly as the source.
Local XML/TXT file → <Load> → Cloud Storage/Staging BigQuery |
The spreadsheet below presents all data transformation between the raw files (extracted files) and a BigQuery delta table. Some files are unstructured and semi-structured. This steps aims to structure the files in the target table format and checking if the column's type (schema) are conformed expected.
The data integration phase for batteries follows the standard approach describe on LB Data Dev Architecture - General.
Staging BigQuery → <Transform> → ODS BigQuery |
The spreadsheet below presents all data transformations between the tables on Staging and ODS. This steps aims to add some calculations and intelligence to the data. Not all tables will need passing through this step.
This spreadsheet shows how to align all cyclers in just one commun table schema:
ODS BigQuery → <Transform> → DW BigQuery → <Expose> → DM_Battery_Electrochemistry BigQuery |
The following data model presents the tables present on DW dataset and the relation between them:


For the DM dataset (DM_Conductivity), we have the views on the top of the tables before. As defined in the convention, there is no need of the abbreviation "conduct". No need either of Talend jobs.
All the jobs are run in sequence under the follow job and project name on TAC/Talend Cloud:
| Project | Job/Flow |
|---|---|
| RnI_ACN_Battery | F010_RnI_ACN_Battery_ELN_IDBS_Orch_Flow |
| RnI_ACN_Battery | F020_RnI_ACN_Battery_ELN_Integration_Orch_Flow |
| RnI_ACN_Battery | F011_RnI_ACN_Battery_Instruments_Orch_Flow |
| RnI_ACN_Battery | F021_RnI_ACN_Battery_Instr_Integration_Orch_Flow |
For scheduling details check the Operational documentation.





