Just as each organization defines its own requirements for a valid metadata standard, it must also be possible to specify the rules and responsibilities for the joint management of enterprise-wide metadata individually. True to the motto: One size never fits all. Whether workflows with very few steps to publication or workflows that are more complex (often those aligned with the general requirements process in the organization) can be easily defined. A workflow can be assigned separately for each model. This makes it possible to take into account the varying workflow requirements of different types of metadata.

People who create metadata definitions are usually experts in a particular field. However, they often cannot be solely responsible for defining the meaning of data and other metadata definitions. Through the dataspot. workflow mechanism, all participants are actively involved in the decision-making process and associated activities are documented. This creates traceability in the specifications, and also a historical understanding of how definitions came about.

For many stakeholders in the data excellence organization metadata management is not their core task. It is therefore particularly important that notifications can be set individually, specifying for which metadata or for which changes notifications are relevant for individual users. Even in projects where metadata is used as the basis for various implementations, active notifications are needed to enable quick and efficient collaboration.