We’re excited to introduce the latest version of oeplatform, bringing significant upgrades, improved API functionalities, and refinements to the metadata management experience. This release marks a major technical advancement, migrating the platform from Django 3.2 to Django 5.1, ensuring better performance, security, and long-term maintainability.
Key Updates in This Release
🚀 Core Improvements & API Enhancements
- Django Upgrade: The entire platform has been migrated from Django 3.2 to Django 5.1, improving performance, security, and framework stability. (#1884)
- More Informative API Responses: API interactions now provide clearer, more helpful responses, making debugging and integration easier.(#1912)
- Refactored Header/Footer Templates: Enhances maintainability and consistency across the platform. [(#1914)]
🔍 New Features & Expanded Metadata Handling
- Bulk Dataset Management for Scenario Bundles: A new API endpoint enables efficient bulk addition of datasets to a scenario’s input/output. This supports datasets listed on OEP as well as external datasets registered on databus.openenergyplatform.org. The API includes detailed error messages for enhanced usability. [(#1894)]
- Enhanced Metadata Builder UX:
🗄️ Ontology & Data Management Enhancements
- SPARQL Query Improvements: The OEKG SPARQL endpoint now uses HTTP POST, aligning with expected usage patterns and improving query performance. [(#1913)]
- Deprecation of Legacy Features: The outdated references module (which handled BibTeX files) has been removed, streamlining the codebase. [(#1913)]
📖 Documentation Updates
- Expanded Documentation for Scenario Bundle Management: A detailed guide has been added to explain the new dataset management API for scenario bundles. [(#1894)]
👉 Explore the full changelog and let us know your thoughts!