v1.0.0 - Major release - Rewrite OMI

We’re excited to introduce Version 1 of the Open Metadata Integration (OMI) tool for the OEP and OEMetaData specification, marking a significant milestone with a comprehensive rewrite. The previous implementation faced limitations in feature support and maintainability, leading us to re-engineer the tool from the ground up.

Key Enhancements and New Features:

• Full JSON Schema Compliance: The OMI tool now fully supports JSON schema specifications, providing robust validation for OEMetaData from version 1.5.2 up to the latest version 2.0. This update enables precise schema validation and ensures that your OEMetaData documents align with the latest standards.

• Improved Error Messaging and Warnings: Validation now includes clear error messages and warnings that facilitate the creation and maintenance of OEMetaData JSON documents. These messages offer guidance on issues that may arise, simplifying troubleshooting and enhancing data integrity.

• Enhanced Data Resource Validation: OMI introduces a new validation feature to ensure that metadata resource descriptions accurately represent the data in your tables on the oeplatform. This validation functionality is integral to the OEP website, making error messages available through the OEP API and UI components, offering real-time feedback during metadata submission and validation workflows. (Some features will be live following the completion of additional implementations.)

• Version Compatibility Conversion: To support users with legacy metadata, the OMI tool includes a conversion feature to help migrate metadata to the latest OEMetaData specification seamlessly, ensuring ongoing compatibility and adherence to the latest standards.

• Data Inspection Functionality: Using the Frictionless Data Package framework, the new inspection feature collects and compiles essential data attributes into the correct metadata resource format. This enables an efficient description of your data within the OEMetaData, streamlining the metadata generation process and ensuring structured, accurate metadata descriptions.

see full Changelog
Main developers: @jh-RLI @henhuy

v0.2.1

• The order of the metadata fields has been improved to better align them with the Oemetadata specification and to make the download functionality of the OEP website more robust. Not all keys are still in the correct order.

see full Changelog

v0.2.0 - Keep none/null fields

• It is noweEasier to specify whether nones are retained after compiling the oemetada.json. Python None / json nulls are now retained in the json by default.

see full Changelog

0.1.2 Patch - Datetimeparser

• Fix bug when Parsing datetimeformats

see full Changelog

0.1.1 Patch - Parser bugfixes and validation Improvements

see full Changelog

0.1.0 - Minor release - Add jsonschema validation to omi parser

See full Changelog

v0.0.9 - Bugfix

Fixes a bug that is raised when omi is used with metadata that includes the minimum ammount of keys e.g. {"id":"id"}.

See full Changelog.

v0.0.8-alpha1

This is the alpha release for v0.0.8 of omi. This release is published as alpha to test the new automated release pipeline (publish pypi package on github release). The stable release will follow once the pipeline is tested.

See full Changelog.

v0.0.8 - Metadata conversion and Bug fixes

Version 0.0.8 introduces automated workflows for code testing and release management. The main new feature is the metadata version conversion for oemetadata version 1.4 to 1.5 . Also alot of minor bugs have been fixed.

See full Changelog.

v0.0.7

• add support for oemetadata v1.5.1

See the full changelog.