Releases: pseinfo/database-schema
Release list
vers. 0.7.1
Utilize @pseinfo/hp-statements for typing GHS hazard and precautionary statements.
Full Changelog: v0.7.0...v0.7.1
vers. 0.7.0
This major update marks another significant milestone on the journey toward Database Schema 1.0. While the core layout of the database remains largely consistent, substantial "under-the-hood" improvements have been implemented to enhance precision and reliability.
What's Changed
- Enhanced scope and depth of physical and chemical properties
- Overhauled Blob/Media system to be more strict, ensuring reliable asset mapping and data integrity
- Improved handling of IAEA nuclear data
- Numerous structural improvements and bug fixes
Strategic Pivot
With this release the JSON Schema will be removed. Since the database will be fully written in TypeScript, there is no need for a separate JSON Schema. This change makes it easier and allowes to dive deep into more complex types.
Roadmap
The following objectives are planned for upcoming releases:
- Moving physical quantity / unit system to a standalone package (#20)
- Implementing specialized packages for fluent database factory functions (#22)
- Implementing structures for spectral and material composition analysis (#21)
Full Changelog: v0.6.6...v0.7.0
vers. 0.6.6
This patch addresses media storage and data integrity. Various scientifiy properties were corrected, the unit system improved.
What's Changed
- Implemented blobs (#15) as raw data storage
- Reworked database stats and meta data
- Fixed physical quantities / units
- Centralized attribution data (for blobs and media)
- Added
contextfield toValuetypes - Enrich value types with a physical quantity unit field only when applicable
- Fixed properties within multiple collections
Full Changelog: v0.6.5...v0.6.6
vers. 0.6.5
Patching Factory types to enforce structural improvements. Additionally, introducing the EntityType enum.
Full Changelog: v0.6.4...v0.6.5
vers. 0.6.4
This patch introduces new factory types intended to simplify and standardize the database structure.
What's Changed
- Introduced
Factorytypes for all entities (Element,Compound,Mineral,Mixture,Nuclide), references, and physical quantities to enforce strict repository file structure. - Revised
StatsCollectionto capture even more accurate statistics. - Standardized identifier naming conventions across the entire schema (e.g.,
CompoundId,MineralId,NuclideId).
Full Changelog: v0.6.3...v0.6.4
vers. 0.6.3
Patching units and nuclide entity:
- Fix SI dimensions
- Add basic Planck units
- Pass through element symbols for nuclides
- Fix JSDoc comments
Full Changelog: v0.6.2...v0.6.3
vers. 0.6.2
This update introduces revamped entity types to facilitate a file-based, automated enrichment process. It enables the definition of individual entities (like Elements, Compounds, etc.) directly in clean data files (for instance, data/element/h.ts) without the need for manual metadata input, all while guaranteeing that the final JSON database can be automatically enhanced with versioning and commit details.
Full Changelog: v0.6.1...v0.6.2
vers. 0.6.1
Minor patch addressing missing enum export.
Full Changelog: v0.6.0...v0.6.1
vers. 0.6.0
This update includes a major overhaul of the entire database structure. All enums were moved to their separate directory and now have their own entry point. Additionally, data structures were revised, properties optimized, collections expanded, and entities enhanced. A new entity for mixtures has been added, along with database statistics.
What's Changed
Full Changelog: v0.5.3...v0.6.0
vers. 0.5.3
Quick fix for path resolving and change naming of exported entity types.
Full Changelog: v0.5.2...v0.5.3