With this release, the release identifier is adjusted. dataspot. switches to calendar identifiers for releases. From now on, releases will be labeled with a year and then sequential numbering.
Basic functions
| Functionality | Description |
|---|
| Extension of link options for components | Previously, only attributes, metrics, dimensions, and DQIs could be linked in dataset components. With an extension, it is now also possible to link entire data or business objects, other datasets, and data types. This allows datasets to be used even better for mapping complex data provisions. |
| CustomProperties for measurements | CustomProperties can now also be defined for measurements in DQIs. This makes it easy to add additional required information to measurements. |
| Derivation for dimensions | Dimensions can now also be linked in the derivation. Previously, dimensions could only be linked via a transformation. |
Import/Export & Reports
| Functionality | Description |
|---|
| dataspot. Connector | dataspot. Connector is the new, unified platform for connecting metadata from different sources, e.g. databases, storage (e.g. parquet files from AWS S3) or Databricks Unity Catalog. |
| JdbcMetadataConnector | JdbcMetadataConnector is replaced by dataspot. Connector. JdbcMetadataConnector is delivered and supported in release 2025.1 but will no longer be delivered in release 2026.1. Existing integrations must be migrated to dataspot. Connector. |
| AgentID for Connectors | With the new Agent ID a connector can mark the assets created or changes by him. In a next run, only elements with this agent id will be checked for deletion or inactivation. |
| Import format V3.0 | The new import format v3.0 support the dataspot. connector framework. With this new version hierarchical inactivation of assets is possible. The default version of import and export is still version 2. |
| Service User and Access Keys for Interfaces | It is now possible to define service users with access keys for interfaces. These service users cannot log into the dataspot. frontend but are used to call dataspot. interfaces. To access these interfaces, an access key is assigned to the service user. This allows technical interface integrations to import metadata into dataspot. without requiring a user in the identity management system. |
Usability
| Functionality | Description |
|---|
| Expansion of automatic aspect ratio adjustment during editing | Due to the change of the UI toolkit, the automatic aspect ratio adjustment during the editing of elements has been removed. Even with a narrow display, all necessary fields can now be displayed correctly. |
| Adjustment of upload & download labels | The buttons for uploading and downloading data in dataspot. were previously labeled Import & Export. To better align the representation and labeling, the buttons have been changed to Download and Upload. |
| Naming of components | Previously, a specific name always had to be given for components of datasets. With this release, the designation of a component is now automatically filled with the identifier of the linked element if no name is specified. |
| Ordinal number for processes | Processes can now be assigned an ordinal number to display processes in a specific order. |
| Display of loading processes in the frontend | Loading indicators are now displayed in more places in dataspot. to make loading processes more transparent. |
| Thousand separators in deletion processes | Thousand separators are now also displayed in deletion processes. |
| Syntax-Highlighting in Markdown | Code snippets are now displayed with the use of syntax highlighting, to make the code more easy to read. |
Configuration
| Functionality | Description |
|---|
| Profiles for annotations | Annotations (YAML configuration) can now be structured and managed even more easily using profiles. Previously, all annotations were managed together in one editor. Now, specific annotations can be managed in individual profiles. |
| Model-specific annotations | Specific, individually configured profiles can also be applied only to selected models. This allows individual configurations for the special use of a model type to be applied only to the specific model. This function enables the different configuration of the same model type. |
| Display of applied annotations | The profiles applied to a model can now be displayed as a whole. This makes it easy to see which configuration is applied to each model. |
| Configuration of plurals when renaming assets | The plural of new identifiers for elements previously had to be determined with the declension class. The plural formation has now been simplified by dataspot. From release 2025.1, the desired plural can now simply be specified directly in the annotation. |
| Overwrite protection and versioning of annotations | The annotations or profiles in dataspot. are now also versioned. This allows historical annotations to be read and reactivated. |
