
Listed as Free on Udemy when checked on 7 November 2026. No coupon or subscription trial is required for the listed lessons. Enrollment needs a Udemy account; availability can change.
About this course
Knowing that a table exists is only the beginning of making it useful to other people. A colleague also needs to understand its meaning, who can answer questions about it and whether the information is current. Ataccama Academy’s catalog course follows these connections inside ONE, from connecting a source to documenting assets, defining business terms and sharing information with appropriate users.
The free English course contains nine videos across five sections, totaling fifty-six minutes and twenty-four seconds. It is labeled Intermediate and expects UDY01 or basic familiarity with the Ataccama ONE web application. No engineering background is required. It is intended for stewards, analysts, catalog owners and governance leads. Access to the recordings does not establish that a platform license, connected data source or practice environment is provided.
| Official course | UDY02-Build and Govern Your Data Catalog with Ataccama ONE |
|---|---|
| Created by | Ataccama Academy |
| Platform | Udemy |
| Language | English |
| Level | Intermediate |
| Listed duration | 56 minutes; 9 lectures across 5 sections |
| Completion terms | Not included with a new free enrollment |
What you’ll learn
Follow the path from source connection and discovery to documented catalog items and linked business terms. Explore ownership, classification and asset sharing, then consider reports and observability as ways to assess catalog usefulness. Distinguish metadata visibility from access to actual values and interpret catalog coverage without treating it as proof of complete governance.
Skills you’ll gain
- Catalog workflow planning
- Metadata and profiling distinction
- Asset documentation
- Business glossary design
- Effective access awareness
- Catalog coverage interpretation
Define what makes the catalog useful
The foundations lesson frames a useful catalog around coverage, quality, ownership, discoverability and currency. These are practical questions to ask about a project: can people find relevant assets, understand them and identify someone responsible? A growing inventory may demonstrate progress, but a large number of entries does not show that users can make good decisions from the information attached to them.
Separate structure from data observations
The connection lesson introduces source setup and synchronization choices. Keep metadata import separate from profiling in your understanding of the workflow. Current Ataccama documentation describes metadata import as bringing in structure such as schemas and attributes without reading the data values themselves. Profiling and other discovery operations can then provide additional observations. The exact sequence depends on the configured documentation flow and the source connector.
Use discovery to guide questions
The discovery lesson examines statistics, distributions, missing values and patterns. These observations can reveal where documentation or quality checks need attention. They are not a substitute for understanding the business process that produced the values. A pattern that resembles sensitive information may warrant investigation, while a familiar-looking field name may still need confirmation from the people who use it.
Document purpose and responsibility
Documentation becomes more concrete in the catalog-item lesson, which covers descriptions, ownership, linked terms and classification. A useful description explains purpose and context rather than simply repeating a technical name. Ownership should identify a meaningful route for questions or decisions. Keeping those details current helps the next user understand both what an asset represents and where to seek clarification.
Connect terms with technical assets
The business-glossary lesson introduces definitions, synonyms, ownership and publication. Linking a term to attributes helps connect business language with technical structures. Review a definition for ambiguity before treating it as shared vocabulary. The course discusses a draft-to-published workflow, but exact review states and approval requirements depend on configuration; publication alone should not be interpreted as proof that every organization applied the same approval process.
Understand classification controls
Classification and sharing address related but distinct concerns. Current documentation describes data protection classifications that can restrict visibility of sensitive attribute values through terms and classification-tag permissions. The effect depends on the configuration and the user’s permissions, with administrative exceptions. A descriptive label is therefore not, on its own, evidence that all access routes are restricted or that legal compliance has been established.
Plan sharing from effective access
The sharing lesson introduces different levels of access for users and groups. Evaluate the actual recipient’s effective access, not only the label selected in one sharing action. Official guidance explains that group sharing interacts with governance roles, while direct sharing and multiple access paths can affect the resulting permissions. This is useful context for planning collaboration; the course does not authorize changing access to an organization’s real assets.
Report progress with clear limits
The reports lesson connects external business intelligence assets with the catalog and introduces coverage measures. Use reports to explain what is documented, linked or owned and what remains uncertain. Coverage can support a conversation about progress, but it cannot independently demonstrate that every definition is correct or that every report dependency is captured. The final observability lesson adds monitoring for changes and anomalies, which still need interpretation and an agreed response.
Match the workflow to your environment
The material was updated in September 2026 and discloses the use of artificial intelligence. It provides a concise introduction to a catalog workflow inside ONE, not a guarantee of adoption, compliance or governance maturity. Connector behavior, permissions, publication controls and available screens can vary by installation. Match practical work to the current documentation and the organization’s decisions about data ownership.
Draft one useful catalog entry
For optional practice, draft a catalog entry for a fictional equipment table. Write its purpose, an owner’s responsibility, two field descriptions and one business term. Specify which information a general reader needs and which values would require separate access. Add a question that the entry cannot answer yet. This editorial exercise is separate from the recorded demonstrations and requires no live connection or permission changes.
Related courses for your next step
- Explore data transformation foundationsFree SQL to Python pandas Course
Build context for how tables and transformations can relate to catalog documentation.
Intermediate
Frequently asked questions
Who is this course for?
It is aimed at stewards, catalog owners, analysts and governance leads familiar with the ONE web application through UDY01 or equivalent experience.
Does importing metadata mean all data values were profiled?
No. Metadata import records structure. Profiling and other configured discovery operations provide additional information and have their own access and processing requirements.
Does a classification label prove compliance?
No. Understand the actual classification controls, effective permissions and organizational requirements. A label or coverage report alone cannot establish compliance.
Questions & discussion
Share a useful question or correction. Comments appear after moderation. Please avoid personal or sensitive information.