Data Quality & Catalog ⚙️

Hi everyone,  Ever thought about where to start with DQ in Ataccama? Worry no more. Follow the journey we have created for you to take your first steps into becoming a DQ wizard  🪄 First things first - Start with reviewing our Beginner’s Guides 🧠  Let’s try a few rules ✖️➕➖   Explore some use cases and best practices from the community 💜 Don’t forget to check out our Training Resources page to access video resources under 2 minutes on how to create a Detection Rule to Creating DQ Validation Rules 🎥 Next up is… Monitoring Projects - so stay tuned. Subscribe to our forum to not miss out on the latest articles🔔  

Happy Friday everyone! We are here with the newest issue of the Data News Digest 🗞️ This week on the news is a new research by Joseph McKendrick “Taking on the Data Quality Challenge in the Age of AI” produced by Unisphere Research. New analytics and AI technology have been one of the highlights in 2023, if not the main discussion topic. There is a rising interest and high levels of investment from companies and while this research touches upon an important conversation it feels like it’s just the beginning. What are your thoughts? Any news you’d like to share? Your take on the latest news? What would you like to see more of? Post it in the comments below 👇

Hi everyone,  Are you just starting out with Data Governance or would like to brush off some of your skills? Check out our learning journey below and follow along to improve your Data Governance skills one article at a time⚡ First things first: Let’s start with the basics 📚 Continue with the essentials 🔑 Advance your skills 🔗 Need some brainstorming? Check out our digest issue 🧠 

Hi, I’m Oliver. a Solutions Consultant here at Ataccama.Workflows and governance are integral to any form of modern data management, be it MDM or RDM. But with so much to do in a typical workday, how do you respect the time of your end users and ensure they are informed when their input is required?Out of the box, Ataccama MDM and RDM include useful functionality to send emails to defined roles (i.e. groups of users) whenever records are moved through C(R)UD workflows. But what if we need to:Create consolidated, routine summaries for cases where data changes often and frequently? Allow users (e.g. project managers) who are not directly involved in the workflow to see progress? Notify users in different ways (e.g. Microsoft Teams, Slack, or Amazon SNS)? Create dashboards of daily workflow progress to report against?Once again, we can turn to Ataccama Plans & Scheduled Workflows! Notification WorkflowsIn this example, consider a pretend client using RDM, with a custom workflow whenev

Hi everyone,  Learning new skills or starting something from scratch can be daunting sometimes. We may feel a bit lost in all the information coming at us or scroll endlessly in the search results. That’s why in this post, I want to create a how to get started with ONE Desktop journey, compiling all the articles we have published in the last months. According to your experience, you can jump a few articles or click on the one you find the most challenging at the moment. Please also do share your feedback and questions in the comments section 👇🏻 Beginner Friendly - Learn the essentials: How to work with plans? aka  your canvas on ONE Desktop:  Main elements of ONE Desktop 🔥🌍💧💨 Tips & Tricks:  If you got the basics let’s move on..  Integrations 🖇️ Best Practices from the community 💪🏻      

 Happy Tuesday community 🙋‍♀️ This week we have a series of best practices on all things components on ONE Desktop. Component steps, often referred to as simply "components," are instrumental tools that come with unique capabilities. Here, we'll explore what makes components special and how to make the most of them in your data projects. What Sets Components ApartComponents are akin to plans but with distinctive attributes: Reusable: Components can be employed repeatedly, functioning like steps within other plan files. Parameterization: Components can have properties within their constituent steps mapped as parameters, allowing external plans to interact with them (learn more in the section on "Mapping Properties as Parameters"). Console Launch: Components can be executed directly from the console, with parameters for added flexibility. Example: The Component in ActionComponent files are identifiable by their ".comp" extension and can play pivotal roles within your data workflows.

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 SourcesAtaccama 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

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 ExplorerFrom 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 DesktopThere 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 is