-
Notifications
You must be signed in to change notification settings - Fork 19
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
Integrate with databus.openenergyplatform.org as backend service #1906
base: develop
Are you sure you want to change the base?
Conversation
- make it more modular - prepare htmx based partial template loading
Is openergy.databus.org correct? Or do you reference https://databus.openenergyplatform.org/ ? |
Yes sorry there was a energy.databus some time ago and im always confusing it now :D https://databus.openenergyplatform.org/ is the correct one. |
i enhanced the description above a bit. |
Not the best idea to add all these additionall issues here ... but this PR will implement the initial databus integration it will not stay open until it is fully integrated. |
Summary of the discussion
The Databus instance for the OEP (https://databus.openenergyplatform.org/) has been operational for some time, though currently, it is primarily known and utilized by related projects and their maintainers. With updates like the recent release of OEMetadata v2.0, and with regard to enhanding the search and adding features like dataset collections, we are actively working to integrate the Databus with the Open Energy Platform (OEP), bringing together these two core services. Additionally, another service is added MOSS (https://moss.openenergyplatform.org/) but it is currently empty. This service aims at consuming additional (to the databus) metadata. Once integrated, it will store the OEMetadata. Through this integration, OEMetadata will be added as a MOSS metadata layer extension on the Databus, making data descriptions richer and more standardized.
The Databus itself will not store any actual data but will act as a metadata registry, creating and managing metadata records for data distributions (which can be tables on the OEP or external distributions with available link).
This PR introduces functionality to register datasets hosted on the OEP directly with the Databus. Moving forward, the Databus will become an integral component of the OEP’s backend, handling advanced data organization and metadata management. This includes features such as creating collections across multiple tables, managing data groups, and harmonizing topics with Databus groups. By offloading data management and search functionalities to the Databus, the OEP core software can focus on its primary objectives, with Databus providing a robust foundation for metadata handling and discoverability.
This ongoing development will progress gradually, with step-by-step migrations, ensuring a seamless transition of data management tasks to the Databus backend and enhancing the overall user experience on the OEP.
Type of change (CHANGELOG.md)
Features
Workflow checklist
Automation
Closes #1348
Additional
Closes #1822
Closes #1666
Closes #1883
Closes #1882
PR-Assignee
Reviewer