Version 0.22.1

Release Summary - Version 0.22.1

Changes

• Resolved bug causing toolbar tabs to be incorrectly selected in the frontend by @AndreyNenashev (#1588)
• Fixed issue with the search page freezing during loading for tabs with 0 entities in the frontend by @AndreyNenashev (#1587)
• Added necessary permissions to lookup table definitions for create/update/delete actions in the frontend by @AndreyNenashev (#1586)
• Adjusted query examples styles to enhance user experience in the frontend by @AndreyNenashev (#1583)

Contributors

@AndreyNenashev

Version 0.22.0

Release Summary - Version 0.22.0

Features

• MVP for look-ups in [MASTER DATA. REFERENCE DATA] by @AndreyNenashev @Vladysl (#1574)
• Unassign query example from dataset in Feature(fe) by @AndreyNenashev @Vladysl (#1535)
• Splitted Swagger UI into 2 pages for platform-api and ingestion-api by @Vladysl (#1537)

Improvements

• Chore: Fe router refactoring by @AndreyNenashev (#1551)
• Chore(fe): Decompose management page routes by @AndreyNenashev (#1540)
• Integrations: Add ScyllaDB and CKAN logos by @AndreyNenashev (#1539)
• Dependencies(ui): Bump dependencies by @AndreyNenashev (#1538)
• Update Docker Compose for tests in Chore by @AndreyNenashev (#1534)
• All related dataset entities related to the query example presented on getQEbyDatasetId page by @Vladysl (#1533)
• Update ReadMe with information to run as a separate container by @RamanDamayeu (#1516)

Bugfixes

• Resolved issues with date cells, lookup table definition permissions, and boolean cells by @AndreyNenashev (#1578)

Contributors

@AndreyNenashev, @RamanDamayeu, and @Vladysl.

Version 0.21.0

Release Summary - Version 0.21.0

What's Changed

• 1523 - Update odd-integration-manifests version to 0.0.6 by @Vladysl in #1524
• 1519 - Remove length constraint for internal description in dataset_field table by @Vladysl in #1522
• 1525 - Query Examples as part of Data Modeling by @AndreyNenashev in #1525
• 1520 - Fix overwriting internal metadata by the collectors by @Vladysl in #1521

Contributors

• @AndreyNenashev and @Vladysl

Version 0.20.0

Release Summary - Version 0.20.0

What's Changed

• Fix Readme: change reference from master to main branch for odd charts by @RamanDamayeu in #1508
• 1503 - Support new DataEntityType - VECTOR_STORE and new DatasetField… by @Vladysl in #1507
• 1513 - Implementation of unit test for Data Quality Dashboard by @Vladysl in #1514

New Contributors

• @RamanDamayeu made their first contribution in #1508

Version 0.19.0

Release Summary - Version 0.19.0

New Features

• Implemented Data Quality Dashboard with corresponding API (Issue #1484) - @Vladysl
• Added issue template configuration for streamlined reporting (Issue #1494) - @Haarolean

Infrastructure

• Implemented security policy to enhance project security (Issue #1493) - @Haarolean
• Implemented monthly CVE checks workflow for proactive vulnerability management (Issue #1487) - @Haarolean

Contributors

This release was made possible by the contributions of @Haarolean and @Vladysl. Thank you for your valuable contributions!

v0.18.1

Changes

Use odd.platform-base-url property instead of PLATFORM_HOST_URL for email notifications @Vladysl (#1498)

Contributors

@Vladysl

Version 0.18.0

Release Summary - Version 0.18.0

Dependencies

• Upgraded react-query from version 4 to 5 (Issue #1488) - @AndreyNenashev

New Features

• Implemented email alert notifications (Issue #1442) - @Vladysl
• Created Swagger UI for OpenAPI Specifications (Issue #1446) - @Vladysl

Chore

• Proper tags fetching on the main overview page. Prepared useQuery hooks for an upgrade to version 5 (Issue #1486) - @AndreyNenashev
• Resolved serialization console errors and added data source logo into lineage (Issue #1483) - @AndreyNenashev

Version 0.17.0

Release Summary - Version 0.17.0

New Features:

1. Implemented an improvement to the tag search engine, making it easier to find tags when clicking on them. (Contributor: @Vladysl , Issue #1447, #1449)
   Note: Search by tags showing and count only tags that are used under data_entiy only.

Bug Fixes:

1. Fixed a bug related to the correct rendering of terms’ markdown on the dataset structure page. (Contributor: @AndreyNenashev, Issue #1465)

Enhancements:

1. Improved the user interface by making lists scroll more smoothly on the management page. (Contributor: @Leshe4ka, Issue #1448)
2. Replaced the “labels” functionality with “tags” for better usability. (Contributor: @AndreyNenashev, Issue #1440)
   Note: !!!Not Backward compatable!!! The table that is responsible for Labels will be removed. All Labels will be migrated into Tags. Make db backup in case of rollback.
3. Refactored the input component for improved performance and maintainability. (Contributor: @Leshe4ka, Issue #1441)
4. Added a warning message to inform the user before closing modal windows, preventing accidental data loss. (Contributor: @Leshe4ka, Issue #1427)

v0.16.0

Summary

We're excited to announce the following improvements and enhancements in the ODD Platform v0.16:

• Language Translations Added: Our commitment to making ODD Platform globally accessible takes a giant leap forward with the addition of translations in Ukrainian, Spanish, French, Chinese, and Armenian.
• Message Statuses on UI: Enhancements in Data Collaboration allow you to stay updated with real-time message statuses, providing instant feedback on messages sent to Slack.
• Markdown for Business Terms Descriptions: Expanding on the markdown support you're familiar with, Business Terms now allow for richer, more readable descriptions.
• Business Names for Dataset Fields: Building on our existing functionality in Data Entities, you can now add Business Names to Dataset Fields for a more intuitive, clear, and consistent user experience.

Acknowledgments

A huge thank you to our fantastic team of contributors who made this release possible and helped us with translations.

🇪🇸 @jocdiazm, Carolina Chavarria, @alesantiago98, @lapc506, Gustavo Valverde
🇫🇷 @alesantiago98
🇨🇳 Rong Jing
🇺🇦 @FlySpot
🇦🇲 @ArpineKeyan

We Want to Hear From You!

As always, we're eager to hear your feedback. Reach out with your thoughts, and let's make our and your platform even better together!

v0.15.0

The v0.15 release of the platform comes with the following enhancements:

• Data Deprecation: To enhance your interaction with our platform, we've introduced various statuses for data entities: 'General', 'Draft', 'Stable', 'Deprecated', and 'Deleted'. Accessible via both the API and frontend, these statuses provide critical insights into your data entities' condition. Notably, we've incorporated a unique automatic transition mechanism, allowing 'Deprecated' and 'Draft' statuses to change to 'Deleted' after a specific period. Furthermore, for the first time on our platform, we're introducing the ability for users to permanently remove entities, adding an extra layer of control over your data assets. With additional catalog filters and status propagation to entities within a DEG, this feature significantly improves data asset tracking.
• Metadata Stale: We've introduced an intuitive way to identify entities that haven't been updated for an extended period. This feature introduces a distinctive icon in the UI, serving as an alert that the data entity may be stale. This 'staleness' period is entirely configurable, offering flexible controls to align with your unique operational needs. This feature enhances the user interface's clarity, ensuring that you're always aware of the freshness of your data entities.
• Business Terms Linking: In our ongoing effort to streamline and enhance user interaction, we've implemented markdown-based descriptions that enable 'mentions' of Business Terms. This innovation allows for seamless linking of Business Terms within a description text, doing away with the need for button clicking in the UI. Furthermore, the system will automatically detect and parse these 'mentions', displaying a convenient list on the UI. To enhance user understanding, hovering over a mentioned Business Term will trigger a wiki-style info box with relevant details. This feature offers a more intuitive, connected, and context-rich experience in managing your Business Terms.
• Markdown in Dataset Field Descriptions: In keeping with our mission to provide a cohesive user experience, we've extended markdown support to the dataset field descriptions. This feature brings the familiarity and convenience of markdown formatting that our users enjoy in Data Entity descriptions to the dataset fields. Now, your dataset field descriptions can benefit from the enhanced readability and flexibility that markdown formatting offers.

As always, none of this would be possible without the dedicated work of our incredible contributors. A massive thank you to all who contributed to this release, your efforts are greatly appreciated!

As always, we're eager to hear your feedback. Reach out with your thoughts, and let's make our and your platform even better together!