Learn & Share

Hi everyone, Welcome back to our best practice series on MDM. In this post, we're diving deep into the features that make MDM - so buckle up 🚘 MDM’s primary feature is its model-driven architecture. It's a domain-agnostic MDM that empowers developers to craft domain-specific MDM models. Let's break down its high-level features by type. Model-Driven Architecture MDM's domain-agnostic approach is complemented by vertical models (metadata templates) designed to be domain-specific. These models are not cast in stone; they are customizable and extendable to meet the unique needs of your project. To delve deeper into this model-driven marvel, check out the Model. Internal Workflow and Processing Perfection MDM boasts a remarkable set of features: Out-of-the-box change detection on load: MDM is a keen observer. It can detect changes in source instance records by tracking their unique source IDs. If a record has changed, it triggers the MDM process for that specific record. The granularity of

Hi everyone, In this post, we will continue our introduction to Master Data Management (MDM), if you have missed our first post you can find it here 👇🏻 This article will focus on the architectural details of MDM, breaking down the components, dependencies, and practical management tips ✨ The Pillars of MDM At the heart of MDM, we find four essential components: Keycloak: Our third-party identity management tool. MDM Server (formerly known as MDC): The robust Ataccama MDM processing engine. MDM Webapp (formerly known as MDA): The user-friendly Ataccama MDM web application. Relational Database: The sturdy backend database, supporting PostgreSQL, MS SQL, or Oracle. Each of these components is configured as a Linux service, allowing independent restarts and individual log access for issue identification. The Backbone of Databases MDM is compatible with PostgreSQL, MS SQL, and Oracle relational databases. However, it's important to note that Ataccama officially supports only PostgreSQL St

Hi everyone, happy Monday 👋🏻 After publishing more than 20 articles on ONE Desktop best practices, I’m happy to share that we are ready to take the next step into Ataccama's Master Data Management (MDM), a robust, scalable, and highly available platform designed to simplify and enhance your master data management tasks. Let’s start with the basics ⚡ What is MDM and how is it different? Unlike the traditional "data flow driven" Data Quality Center (DQC), Ataccama MDM stands out as a fully metadata-driven data processing system. It incorporates an array of powerful tools, including the Advanced Metadata Editor (AME), a cutting-edge data processing engine (NME), and the DQC Plan Executor (complete with its steps and components). By doing so, MDM naturally extends the capabilities of the DQC, offering comprehensive data quality management functionality. In essence, MDM combines Master Data Management with a strong emphasis on Data Quality as a fundamental part of the process, providing a

Hi everyone, happy Wednesday! In this post, we will walk you through Model projects! Model projects play a crucial role in configuring various Ataccama products like DQ Issue Tracker, ONE RDM, and ONE MDM. These model projects are structured based on model templates, which define a specific set of nodes, folders, and files during project creation or import. It's important to note that you cannot modify or remove nodes created by a template. The configuration within model projects is developed using the Advanced Metadata Editor (AME). In this context, metadata refers to the configurations made within the model project nodes, which are used to generate plans, components, web service configurations, XML files, and other necessary components for a particular solution. Developing solutions based on metadata is carried out in the Model Explorer view, and detailed instructions for each product can be found in the respective Developer Guides. Every Ataccama build includes a default model proje

📌 Links to the legacy documentation portal are no longer available. Read about the changes and how to access our documentation here. Hi community! In this post, we will discover how to create server connections in ONE Desktop for various tasks and workflow steps. Read on to find out more 👀 How to register a new server? To set up a new server connection, follow these steps: Right-click Servers in the File Explorer and select New Server. Choose the desired Environment. Learn more about Environments. Provide a unique server Name and select the appropriate Implementation. Configure the server connection according to your implementation, and click Finish. Once registered, the new server connection will appear in the File Explorer tree. Please note that, during development, right-clicking the server connection and selecting Connect is not considered a valid connectivity test, and it's not necessary for enabling step communication. Implementation Types Generic Use this implementation to con

Hi everyone, We are here with Part II of our VCIs best practice series and today we will delve deeper into two significant aspects of working with VCIs - connecting to natively supported data sources and non-natively supported data sources. In the first post, we explored the creation and transformation of Virtual Catalog Items (VCIs) within Ataccama ONE. You can check it out here 👇🏻 Connecting to Natively Supported Sources Ataccama ONE makes it simple to connect with data sources that are natively supported by following these steps: Create a VCI, as explained in the previous section. To read data from a natively supported source, add the "JDBC Reader" step to your plan. Depending on your transformation requirements, you can use the JDBC Reader step alone or combine it with existing catalog items. Configure the "JDBC Reader" step as follows: On the "General" tab, in "Data Source Name," provide the source identifier of the connected database. You can find the source identifier in ONE u

Hi everyone, In this post, we will talk about Virtual Catalog Items 🦋 You might have participated in our live training session that took place a few months back where we talked about how to create and work with VCIs. You can always watch back the session and check out the live demo here 👇🏻 Virtual Catalog Items (VCIs) provide flexibility and efficiency when working with data in the ONE Desktop platform and in this article you can find best practices for creating and transforming Virtual Catalog Items to make the most of your data management efforts. Let’s start with the basics: Why Use Virtual Catalog Items? VCIs are particularly useful in several scenarios: Applying Transformation Logic: When you need to apply ONE Desktop and in-source (SQL) transformation logic before working with raw data. This includes tasks such as filtering data, joining tables, and standardizing values. Integrating Non-Native Sources: When you want to integrate data from sources that are not natively supporte

Hi everyone, happy Monday! In this post, we will go through a few best practices on how you can work with data in ONE Desktop. Before getting into it, don’t forget to check out some posts you might find useful: Browsing Data in ONE Explorer From ONE Explorer, you have the ability to access various components of your data, much like you would in the Knowledge Catalog of the ONE Web Application. ONE Explorer in ONE Desktop includes: Catalog Items Components Lookup Items Monitoring Projects Rules Terms This seamless access to your data provides a comprehensive overview of your information, enabling you to manage your data assets with precision. Working with Data in ONE Desktop There are two primary methods for reading and working with your data within ONE Desktop: 1. Catalog Item Reader Step: This step allows you to access data from different sources defined in the Metadata Management Module (MMM). When you drag and drop a Catalog Item from MMM into your plan, the Catalog Item Reader step

Hi everyone, One of the core capabilities of ONE Desktop is metadata handling through ONE Metadata Reader and ONE Metadata Writer Steps. These steps allow users to read and write data from the Web Application, enabling a range of use cases and implementations. In this post, you’ll find out how to read & write metadata using the steps in ONE Desktop 👇🏽👀 ONE Metadata Reader The ONE Metadata Reader Step serves as a tool to read data from the Web Application, offering flexibility in usage: Common Implementations: Enriching data for external Business Intelligence tools (e.g., Tableau, Cognos) to create customized reports with additional attributes such as description, owner, and custom properties. Easily incorporating DQ rules into DQC plans, simplifying the process of finding and integrating rules based on name and input attributes. Constructing DQC plans with data transformations by utilizing data sources from the Metadata Management Module (MMM). Generating comprehensive HTML document

Hi community! In this post, we are covering working and searching in metadata. Efficiently working with metadata is crucial for ensuring data quality, governance, and effective decision-making. Ataccama has several tools within ONE Desktop to assist in metadata management, including the ONE Metadata Reader and ONE Metadata Writer Steps for reading and writing metadata, as well as the ONE Metadata Explorer for seamless navigation. Let’s dive in 👀 Navigating with ONE Metadata Explorer ONE Metadata Explorer allows you to connect directly to your Ataccama ONE Platform server from ONE Desktop, granting you access to your critical metadata and even "Meta Metadata" for more in-depth analysis. Metadata Exploration by Default When you first access ONE Metadata Explorer, it's configured for exploring your primary metadata. Delving into Meta Metadata However, if you wish to explore your "Meta Metadata," you can easily adjust the settings: In the ONE Metadata Explorer, click the "View Menu" icon.

Hi Community! This week on the menu we have how to work with the Ataccama ONE Platform. We will cover basics like how to connect your ONE Desktop to a bit more advanced topics like working with metadata. Connecting your ONE Desktop to the Ataccama ONE Platform allows you to seamlessly work with metadata, create data quality rules, and utilize virtual catalog items. Create a New Connection Prerequisites: Ensure ONE Desktop is properly set up and running. Your ONE instance should be running and accessible from the server where ONE Desktop is installed. Ensure that both ONE Desktop and ONE are using the same version. Follow these steps to create a new connection: Open ONE Desktop. In the ONE Explorer, select Create a new server. If you are adding a second ONE server, follow these steps instead: In File Explorer > Servers, right-click Servers and select New > ONE Platform. You can also find the same option in the Servers and Databases tab, which is part of your workspace by default. Provid