This page presents the data development documentation for Electrochemistry for all sites
The data ingestion phase for batteries follows the standard approach describe on LB Data Dev Architecture - General.
The list of the spreadsheets 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 |
The instrument files are, most of them, manually added to a Google Driver's folder or a folder in lab servers.
The spreadsheet Where to find instrument files? has the full list of instrument folders and location:
No data mapping needed as the data is copied exactly as the source.
The jobs F010 and F011 are responsables for orchestrating the Data Ingestion:
The data preparation phase for batteries follows the standard approach describe on LB Data Dev Architecture - General.
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 jobs F020 and F021 are responsables for orchestrating the Data Preparation:
The data integration phase for batteries follows the standard approach describe on LB Data Dev Architecture - General.
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.
The job F030 is responsable for orchestrating the Data Integration:
Data Presentation or DW/DM
The data presentation phase for batteries follows the standard approach describe on LB Data Dev Architecture - General.
No data mapping available, as there are no transformations for now. This must be created if there are requirements for that.
No need of jobs as there are no steps to load DW/DM. A priori, all data is presented as views.
The data model presents the tables/views presented on DW/DM dataset and the relation between them.
{Add model}
All the jobs are run in sequence under the follow job and project name on TAC/Talend Cloud:
| Project | Job/Flow |
|---|---|
| RnI_ACN_Battery | F000_RnI_ACN_Battery_Orch_Flow |
For scheduling details check the Operational documentation.
Most files are organized based on its "Workflow name", "Method name". For exemple:
| Workflow name | Method name | Instrument name |
| Conductivity | Conductivity | Biologic SP-150 |
| Electrochemical tests | Conductivity | Biologic VMP 300 |
| Raw materials | Lithium Metal Compatibility | Biologic VMP 300 |
| Raw materials | Tortuosity factor | Biologic VMP 300 |
| Mechanosynthesis | Calcination / Drying | Rotative Oven |
| Dry Process | Coating | Coating line |
| Wet process | Mechanical test | Mark-10 90° Peel Test Fixture Model G1109 |
All instruments folders structure and tables name use the same logic depending on the file or table format. For exemple:
Abbreviations specifically for Battery, they are used in the Talend jobs or tables names:
| Name | Abbreviation | Note |
|---|---|---|
Instrument | Instr | |
Raw Materials | RawMat | |
Conductivity | Conduct | |
Mechanosynthesis | Mechano | |
Critical Current Density | Crit_Curr_Density | |
Lithium Metal Compatibility | Lith_Met_Comp | |
Tortuosity factor | Tortuosity | |
Dry Process | Dry | |
Wet process | Wet |