
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
A data catalog becomes easier to use when its fields and screens reflect the work people actually do. Ataccama Academy’s customization course explores that connection inside Ataccama ONE. It follows a change from the underlying metadata model to the catalog search experience, navigation menus and entity detail screens, giving administrators a focused route through the platform’s extension concepts.
The English course contains eight videos across three sections, totaling about forty-nine minutes. Watching the lessons is free on Udemy. Following the configuration demonstrations requires administrator or superuser access to an appropriate ONE instance; the listing does not promise to supply that access. The provider expects its UDY01 introduction first and recommends, but does not require, the UDY10 GraphQL course.
| Official course | UDY11-Customize the Ataccama ONE Platform |
|---|---|
| Created by | Ataccama Academy |
| Platform | Udemy |
| Language | English |
| Level | Professional |
| Listed duration | 48 minutes; 8 lectures across 3 sections |
| Completion terms | Not included with a new free enrollment |
What you’ll learn
Understand how properties, traits and namespaces contribute to the metadata model. Navigate relationships in the metadata graph, extend an existing object type with a custom property, and consider how a trait supports catalog filtering. Follow the configuration of navigation and detail screens while assessing the impact of a proposed system change.
Skills you’ll gain
- Metadata model interpretation
- Property design
- Trait selection awareness
- Catalog facet planning
- Navigation configuration
- Change impact assessment
Start with a meaningful information need
The opening lesson uses differing organizational needs to explain why a single default model may not be enough. A field that is useful for one organization may be irrelevant to another. The practical starting point is therefore a requirement: what information should users record, why does it matter, and where should they encounter it? Customization becomes easier to evaluate when it answers a specific need.
Read the model before extending it
The next lessons separate properties from traits and namespaces. A property represents a field in the model; a trait can affect presentation or behavior, while a namespace helps organize definitions. Ataccama documents traits for both properties and entities, so they should not be understood as decorative labels alone. The metadata graph then provides a way to inspect how these definitions and relationships connect.
Specify the property clearly
Adding a property involves more than choosing a name. The course description includes selecting its data type and cardinality, assigning its namespace and checking how it appears on a detail screen. Those choices express what kind of value is expected and whether the information is singular or multiple. A clear definition helps colleagues enter consistent information and helps future maintainers understand the purpose of the extension.
Connect the field to catalog search
The filtering lesson applies a trait so that a custom property can participate in faceted catalog search. This connects the model to a user task: finding relevant assets without reading every record. Before treating a new filter as useful, consider whether values have been populated consistently and whether the intended users can locate and interpret it. Adding the option to the interface is only part of making it helpful.
Plan changes as operational work
The course includes an explicit lesson on assessing system changes, trying them in a non-production environment and understanding rollback options. Current Ataccama documentation describes publishing model changes through System Changes, with maintenance mode, a database backup and conflict handling. These are operational concerns to plan with the platform owner. The short course does not establish a universal rollback procedure or guarantee that a change will be safe on every installation.
Make the extension usable
The interface section starts with navigation menus. Its description covers linking to a custom object type, changing item order and controlling visibility by role. A useful menu points people toward the objects relevant to their work. Visibility should still be considered alongside the platform’s authorization rules; hiding an entry is not a substitute for establishing which operations and records a user may access.
The final lesson turns to entity detail screens. It describes displaying the added property and grouping related fields into sections. This is the point where a model extension becomes understandable to someone completing a routine task. Review the labels, grouping and surrounding context from that person’s perspective, then confirm that the intended users can see the result under their normal access conditions.
Match the course to your role
The source labels this course Expert and identifies platform administrators, solution architects and technical consultants as its audience. It was updated in September 2026 and discloses the use of artificial intelligence. Choose it as a concise orientation to ONE customization, with the documentation for your installed release alongside it. It is not a promise of enterprise access, certification, regulatory compliance or a complete implementation engagement.
Sketch a change before applying it
For an optional planning exercise, sketch a proposed “review frequency” property for a catalog object on paper. Define its meaning, allowed values, intended owner, search use and position on the detail screen. Then list the approvals, test checks and recovery information needed before implementation. This editorial exercise is separate from the recorded examples and requires no changes to a live platform.
Related courses for your next step
- Explore the relationship between data and structureFree GraphQL Course
Review schemas and API concepts before considering how metadata is exposed to integrations.
Beginner
Frequently asked questions
Does the free course include an Ataccama ONE license?
The listing establishes free access to the lessons, not a supplied platform license or administrator account. Appropriate access is required to follow the configuration demonstrations.
Is the GraphQL course a prerequisite?
UDY10 is recommended rather than required. The provider asks learners to complete UDY01 and have platform administrator or superuser access for practice.
Will a custom property work identically on every installation?
Do not assume that. Check the metadata model, permissions and documentation for the installed release, and assess and test changes with the platform owner before applying them.
Questions & discussion
Share a useful question or correction. Comments appear after moderation. Please avoid personal or sensitive information.