Learn & Share

Hi all! We hope you’re enjoying our DQ Rules best practice series and finding useful tips & tricks to implement in your day-to-day work. In this post, we will cover aggregation rules and give an overview of creating and configuring aggregation rules to unlock the grouping capabilities.Aggregation rules in Ataccama's ONE can be used in various types of data quality rules, such as Validity, Uniqueness, Completeness, Timeliness, and Accuracy. Let's dive in! How to create aggregation rules?To create an aggregation rule, follow these steps:Select "Aggregation rule" as the rule type in the ONE web application.   The "Group by" section will now be available, allowing you to define the grouping criteria.You can create aggregation rules using either the condition builder or ONE expressions, both of which offer flexibility and ease of use. These methods allow you to select input attributes, apply transformations to create variables, and aggregate data based on the desired grouping. No Code

Hi community! In this post, we will explore how to create and implement DQ rules effectively. Rules play a crucial role in ensuring data quality, and understanding the process is essential for data management. So let’s get started! Creating Rules Manually To create a rule from scratch, follow these steps:Navigate to the Data Quality > Rules page. Click on Create in the upper-right corner. Provide the necessary information: Name: Give your rule a descriptive name. Description (optional): Add a brief description of the rule and its purpose. Rule definition source (optional): Specify the associated data source for the rule. Stewardship: Select the owner group responsible for the rule's accuracy and approval. Click Save to create a draft of the rule.     Before publishing or submitting for approval, you need to define the rule logic. Proceed to the Implementation tab for further steps. Implementing Rule Logic On the Implementation tab, you can perform the following tasks:Add a descr

Hi everyone, We are continuing with our Data Quality best practice series! In the next several posts we will cover everything from Rules to Monitoring Projects in Data Quality. If you have missed the introduction series to DQ you can start here:In this post, we'll explore the concepts of Detection rules and Data Quality (DQ) rules in Ataccama ONE's web application. Understanding these rules is crucial for effective data management. Let's dive in! Detection Rules Detection rules in Ataccama ONE are divided into two categories: Data-based detection rules and Metadata-based detection rules. These rules serve different purposes and can be accessed and created from the "Data Quality > Rules" section. Let's take a closer look:Data-based Detection Rules: These rules evaluate attribute data and are used to assign terms to attributes based on predefined conditions. For example, you can create a rule to assign the term "First Name" to attributes that contain values found in a specific lookup

Hi community,Here is the second part of our webinar series on Metadata Model Configuration for DG&DQ! If you have missed the first session you can find it here:During this episode, we will cover the following:Adjusting screen layout Creating custom entities and their instances Deriving new values from metadataAny questions? Comments? Let us know 👇

Hello everyone,I hope you have been finding our Data Governance and Data Quality introduction series practical and useful for your day-to-day work on the Ataccama platform! We are still in the midst of the Data Quality series but wanted to take a quick break to share step-by-step guidelines on Metadata Model Configuration for DG&DQ.Our expert consultant will lead this two-part webinar recording, which delves slightly deeper into the topic than our regular introduction series.This session marks the beginning of a series aimed at providing a better understanding of the metadata model-driven Data Catalog & DQ at the core of Ataccama ONE.During this episode, we will cover the following:Navigating Model concepts and default model overview Extending default entities Model-based advanced queries (AQL) and custom filters*Ataccama platform and functions featured here are reflecting the time the video was published. Stay tuned for the next episode and please don’t hesitate to let us know

Happy Wednesday community ☀️ Welcome back to our Data Quality series! In today's post, we'll delve deeper into configuring detection and validation rules in Ataccama ONE. If you missed our previous post, we recommend checking it out before continuing.Configure Detection LogicTo define your detection rule's logic, navigate to the "Implementation" tab when creating or editing a rule. If you're starting from scratch, select "Detection" as the rule logic. You can add multiple conditions using the Condition Builder, with each record needing to fulfill all conditions by default (using the logical operator AND). For less strict rules with the logical operator OR, try the Advanced Expression mode. Take advantage of Pattern Analysis results to create detection rules quickly. For instance, open the "Profile & DQ Insights" tab for the catalog item "customers," select the "email" attribute, and utilize the detected patterns by choosing "Use results in rule." Save your changes and don't forget

Hi everyone,In this post, we continue our discussion on Data Observability configurations today! Let's dive into some advanced settings, terms, and rules that will enhance your data observability experience. Observing Data with Selected TermsChoose your preferred method to select the data you want to observe. If you select Terms: Click on Add terms and select terms associated with important data from the available list. Once you've selected the terms, all associated catalog items will be chosen for monitoring. If necessary, you can exclude individual catalog items by selecting Edit selection. After choosing Edit selection, you will see all catalog items associated with the selected terms. Use the more options icon and select Exclude to exclude any of these items from monitoring. When you're ready, click Save. If you select AQL: Use Ataccama Query Language to define the data you want to observe. Once you've selected the terms, all associated catalog items will be chosen for

Hello everyone, and happy Wednesday! Today, we are continuing our Getting Started with ONE DG series with Catalog Items 📒 Catalog items are essentially records within the data catalog. To access your data profiles, simply click on "Catalog Items" located on the left sidebar. By default, Catalog Items are organized into different groups within their respective tabs:Anomaly Overview: This tab displays a list of all catalog items that have anomalies. Domain Suggestions: Here, you'll find a list of catalog items with suggested terms that you can accept or reject. Master Data: This tab contains a list of catalog items sourced from MDM (Master Data Management) data sources integrated with the Ataccama platform. Reference Data: In this tab, you can find a list of catalog items sourced from RDM (Reference Data Management) data sources integrated with the Ataccama platform. Not Monitored: This tab displays a list of catalog items that are currently not included in any monitoring projects. Repo