-
Notifications
You must be signed in to change notification settings - Fork 6
Feature 126 add yaml and template based metadata creation #134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
jh-RLI
merged 20 commits into
dev
from
feature-126-add-yaml-and-template-based-metadata-creation
Dec 10, 2025
Merged
Feature 126 add yaml and template based metadata creation #134
jh-RLI
merged 20 commits into
dev
from
feature-126-add-yaml-and-template-based-metadata-creation
Dec 10, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lied to the metadata during run time. This helps to use omi in 3rd party projects e.g. data pipelines
…mp it to yaml and find metadata entries why can be identified as templated fields as they are used frequently across resources
… to specific keys
…meatadata.json file
… metadata fo file
…elated functionality. This ensures empty like newly created metadata JSON passes omis linter
…ted to gitignore as they should not be on github in case users generated them
…sible outputs when generating metadata.json files.
…ic use cases, explain the workflow per use case and provide an usage overview for how tio use omis cli feature
… OEP #135 adapt to new OEP API URL pattern -> to access table/metadata endpoints
- to import (pull) metadata from OEP-Tables into a local OMI-YAML metadata - add oep upload (push) functionality for single resources or all resources available in a OMI YAML metadata workspace
…eract with the open energy platform and possibly other applications
…r multiple tables metadata on the OEP
…etadata especially when required information is missing.
…ieving information form the OEP
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the discussion
Enhancements for #126 requirements. This PR implements more tooling around oemetadata and its integration into other code projects. It also provides cleaning and merging functionality and adds more functionality to the core create and assembler modules.
Type of change (CHANGELOG.md)
Added
Updated
Removed
Workflow checklist
Automation
Closes #126
Closes #136
Closes #135
PR-Assignee
Reviewer