Data Mesh Manager

What's new

The release notes of the Data Mesh Manager

2024-12-18

  • Layout changed to use full width of available screen

2024-10-30

  • Renamed DataUsageAgreement to Access. In API and event, both names can be used. Consider migrating to the new name access.

2024-09-24

  • 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.

2024-09-04

  • Use the ID (instead of internal UUIDs) for URLs in the web.

2024-09-03

  • Support for Bitol Open Data Contract Standard (ODCS). Contact support to enable this feature for your organization.

2024-07-10

  • Access Request: Add rejection reason

2024-07-09

  • New Logo

2024-06-16

  • Data Governance AI: Added a new feature that uses AI to check data contracts for compliance with data governance policies.

2024-05-13

  • 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.

2024-02-28

  • We're currently working on making all relevant events available through the /api/events endpoint.

2024-01-23

  • 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.

2024-01-18

  • 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.

2024-01-09

  • 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