dataspot. Release 4.0

Ticketing

Place metadata concerns where colleagues from the Data Excellence organization need them.

Whether communicating change requests, conducting governance discussions, or obtaining status approvals. From now on, tickets and comments can be entered directly at the asset in dataspot.

A practical side effect of this is that the contents of the issues and comments recorded are also automatically documented for posterity and decision-making processes are supported.

To ensure that everyone is always up to date with their metadata, the new notification function also ensures that responsible persons are informed as soon as a new metadata request is created for the assets for which they are responsible.

This new main feature of Release 4.0 is therefore also 100% dedicated to the topic of collaboration and optimally supports the processes of joint metadata management.

Here's how it works:

Discussion tickets allow users to enter their own comments on the asset and exchange ideas with each other.
Business requirements (change requests, enhancements, etc.) are displayed as issue tickets directly on the asset and the requirements management process is triggered.
Comments for DQ measurements recorded in dataspot. can be stored (e.g. to document findings from plausibility checks)
In dataspot. notifications are sent to responsible persons as soon as someone creates issues or comments on "their" assets.

Why do I need ticketing in metadata management?

Issue Management

Requirements for data, processes, projects and also applications can be recorded directly at the affected assets via the various types of dataspot. tickets such as change requests, improvements, errors, tasks. This means that both data and application requests can be recorded quickly and processed efficiently by those responsible using the workflow - as well as tasks relating to projects and processes.

Active data governance

Emails, chats over various channels or separate ticketing applications do not create sufficient consistency and continuity for data governance. With direct visibility of tickets on the respective metadata in dataspot., stakeholders can be directed directly to the assets that are waiting to be processed. The convenient notification feature provides timely notification that tasks are pending, or that changes have been made.

To Do Lists

Tickets are the perfect tool for controlling activities around data, projects and any other metadata tasks. Processing lists for tickets and releases create a good overview making it easy to complete all tasks in a timely manner. With the direct link to the affected assets in dataspot. editing them is extremely efficiently, while conversely the affected tickets are also directly visible at the asset.

Another highlight of dataspot. 4.0

Our new release also includes the parameterizable workflow, which allows status definitions and status transitions to be customized for all metadata assets and workflows to be assigned to individual models in dataspot.

What's new in dataspot. 3.2

Our Release 3.2 features still deserve attention. Thanks to the cross-tenant use of metadata, actual collaboration across multiple organizations (organizational units) is possible.

Our JdbcMetadataConnector enables easy synching with metadata from databases.