We might want to improve our development periodic_table.yaml recording:
- It's simply too large and monolithic as a single file, and as such maintaining it (and track git history) is quite hard.
- It doesn't carry enough metadata, for example we don't know the "source/reference" of each data entry, also some information/metadata is missing, for example the temperature at which "Electrical resistivity" is measured.
As such I want to propose that we split the recording to one property per file (perhaps core and static properties in one file), for the following benefits:
- Easier to maintain, we could add/modify certain property each time relatively easily, and also the git history would be much easier to read
- It's more similar to how certain data is presented in handbooks, for example the [CRC Handbook of Chemistry and Physics](https://en.wikipedia.org/wiki/CRC_Handbook_of_Chemistry_and_Physics 95th) have "Electrical Resistivity of Pure Metals" table which list the data for each element but at difference temperatures (and therefore we need more detailed metadata)
This is inspired by the following issues:
We might want to improve our development
periodic_table.yamlrecording:As such I want to propose that we split the recording to one property per file (perhaps core and static properties in one file), for the following benefits:
This is inspired by the following issues: