The hierarchical catalog view displays your technical and business assets in a tree structure that mirrors your actual data organization. This view lets you see the complete context and relationships between your data assets in a single, organized interface. The typical hierarchy for technical assets follows this structure: Datasource > Schema > Dataset > Field.
About the hierarchy structure
- Datasource (Top level): The root connection representing your external or internal datasource, such as Snowflake, Databricks, or Amazon S3.
- Intermediate elements: Structural components that uniquely identify asset locations but do not fall into the datasource, dataset, or field categories. Examples include schemas, databases, folders, and other organizational containers. These elements provide essential context for understanding asset location.
- Dataset (Table level): A logical grouping of data extracted from a datasource, typically representing a table or data collection.
- Field (Column level): Individual data attributes or columns within a dataset.
Use the Asset Location filter
The Asset Location filter provides a hierarchical tree view that allows you to navigate and filter assets by their parent-child relationships. It offers powerful features to help you find exactly what you need.
Filter assets by type, status, quality, governance, and custom attributes
Use filters to narrow your asset views beyond hierarchical location. Combine multiple filters to find exactly the assets you need. Each filter narrows your view by different criteria.
- Asset Type filter: Filter by asset classification (Datasource, Dataset, Field, or custom technical types). Use this when you know the asset type but not its location in your hierarchy. This filter works across Datasets, Fields, Business assets, and Technical assets.
- Status filter: Filter by asset lifecycle stage. Common statuses include Certified (production-ready), Draft (work in progress), and Under Review (pending approval). Use this to focus on assets at a specific maturity stage or identify what needs attention.
- Quality Score filter: Filter by data quality metrics (Good, Average, or Poor). Use this to identify which datasets meet your standards and which need remediation. This helps you prioritize data quality work and assess asset reliability.
- Governance Score filter: Filter by governance score ranges to find assets meeting your compliance requirements or spot governance gaps. Use this to ensure your data landscape aligns with organizational policies.
- Custom fields filter: Filter by custom field values specific to your asset types (business unit, cost center, data owner, or other attributes). This gives you granular control over your asset views.