Data Mesh Manager

What's new

The release notes of the Data Mesh Manager

Upcoming

We will be updating and simplifying the navigation structure. The new navigation structure will have three main tabs simplifying the user journey for the main user groups with clear entry points:

  1. Marketplace: This is the entry-point for data consumers discovering data products for their business case and requesting access
  2. Studio: The place for data product owners and developers to add, edit, and monitor data products
  3. Governance: For stewards, managers, and platform team to set up cross-cutting policies and get insights on the platform

The new navigation structure is already available in the demo and will be rolled out to all customers in the next weeks.

1.6.0

  • Source Systems are deprecated. They will be removed in a future release. Please use data products with type Application instead.
  • Improved ODCS Excel Import/Export
  • Fixes in ODCS Web UI Editor
  • Improved logging for errors and API calls
  • Add "connect data product" as a workflow

1.5.16

  • Minor bugfixes and improvements

1.5.15

  • Minor bugfixes and improvements

1.5.14

  • Data Contract Excel Export and Import have better documentation
  • Tags List Pagination
  • Fixed a bug where the "Edit" button was not displayed for data products in the data product details page.

1.5.13

  • Deletion of used managed tags via API is no longer possible

1.5.12

1.5.11

  • Reworked user navigation

1.5.10

  • In the data products map, neighboring data products are now shown when using filters.

1.5.9

  • The default view of data contracts is now a table, analog to other resources such as data products.
  • Business Definitions can now be used with ODCS, including the Web UI.
  • Add users to teams is now easier with suggestions.
  • The list of business definitions was hugely improved.
  • Teams and domains can now have icons.

1.5.8

  • Sync data contracts with GitHub.
  • Assign tags to assets.

1.5.7

  • Excel Import/Export for ODCS
  • ODCS enabled by default. Supported data contract formats can be configured through environment variable APPLICATION_DATACONTRACT_SPECIFICATIONS.

1.5.6

  • Enforce managed tags (Option in organization settings).

1.5.0

1.4.0

  • Add UI editor for Open Data Contract Standard (ODCS)

1.3 and older

  • Layout changed to use full width of available screen
  • Renamed DataUsageAgreement to Access. In API and event, both names can be used. Consider migrating to the new name access.
  • New top navigation structure: It is now simpler to manage definions, teams, source systems and other settings.
  • Domain/team hierarchy: You can now create a domain hierarchy to structure your domains and teams. You can create a team of type "Domain" and define a parent relationship.
  • Use the ID (instead of internal UUIDs) for URLs in the web.
  • Support for Bitol Open Data Contract Standard (ODCS). Contact support to enable this feature for your organization.
  • Access Request: Add rejection reason
  • New Logo
  • Data Governance AI: Added a new feature that uses AI to check data contracts for compliance with data governance policies.
  • Create data products and data contracts as YAML
  • Data Contract Editor now supports more format fields
  • Simplified policies, Markdown editor, support for a computational policies and customization policies.
  • We're currently working on making all relevant events available through the /api/events endpoint.
  • Added description to the Team model in the API. It's a free text field that can be used to describe the team. You can also see and edit it in the UI.
  • Added the option to set a profile picture for a user in their 'My Profile' section. You can set a URL, and it will be shown in the top right corner of the application.
  • Changed the SourceSystem model in the API: renamed the field teamId to owner. It was called owner everywhere, except here. So the API is more uniform now.
  • Changed the DataUsageAgreement model in the API: moved the field info.id to top-level id. It was top-level everywhere, except here. So the API is more uniform now.
  • Changed the DataUsageAgreement model in the API: made the field info.purpose a required field. It was required in the UI, but not in the API. So the API is more aligned with the UI now.
  • Changed the Team model in the API: made the field type a required field. It was required in the UI, but not in the API. So the API is more aligned with the UI now.
  • Added the Definitions. It is a new central concept of the Data Mesh Manager, that helps in defining business concepts and reusable fields so data contracts can reference them.
  • Added the info.active field in the DataUsageAgreement model in the API. It's read-only, but you can now observe whether a data usage agreement is active or not by accessing a data usage agreement via the API.
  • Added the server section to output ports for detailed connection settings and specific location to the data set.
  • Deprecated the location field in the output port