Catalog Steward

Manage catalog governance and enrich metadata for SAP Datasphere assets.

25|7|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/MarioDeFelipe/sap-datasphere-plugin-for-claude-cowork --skill catalog-steward
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Catalog Steward
Source: https://github.com/MarioDeFelipe/sap-datasphere-plugin-for-claude-cowork/tree/main/skills/datasphere-catalog-steward
Command: npx skills add https://github.com/MarioDeFelipe/sap-datasphere-plugin-for-claude-cowork --skill catalog-steward

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Catalog Steward addresses poor discoverability, inconsistent terminology, and weak governance in SAP Datasphere catalogs by providing structured workflows to enrich metadata, standardize glossary terms, define and validate KPIs, enforce tag taxonomies, and analyze lineage-driven impact before changes are applied. It reduces time spent by analysts hunting for trustable datasets, prevents accidental breakage of downstream consumers, and improves data literacy across teams.

Core Features & Use Cases

  • Metadata Enrichment: Identify undernamed or under-documented assets, suggest business-friendly names and descriptions, and apply bulk updates with audit trails.
  • Glossary Management: Create, version, and link business glossary terms to technical assets so business and technical users share common definitions.
  • KPI Definition & Validation: Define KPI formulas, map KPIs to underlying measures, validate calculations against source data, and manage KPI lifecycle and ownership.
  • Tag Taxonomy & Automated Tagging: Design controlled vocabularies and auto-suggest tags based on column analysis with confidence scores, then apply tags at scale with owner review.
  • Impact Analysis & Governance: Trace lineage to enumerate direct and indirect consumers, produce impact reports, and recommend phased rollouts or backward-compatible migration strategies.
  • Real-world Example: During a migration, use the skill to find deprecated columns, list downstream dashboards and KPIs that depend on them, propose a migration plan with test phases, and notify owners.

Quick Start

Enrich the catalog by finding assets with cryptic names, propose business-friendly names and tags, link relevant glossary terms, and produce an impact analysis for any proposed renames or deprecations.

Frequently Asked Questions about Catalog Steward

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enrich metadata for SAP Datasphere assets with cryptic names?

Metadata enrichment identifies under-documented Datasphere assets and suggests business-friendly names and descriptions. It applies bulk updates with audit trails to improve asset discoverability and data literacy across teams.

How does lineage-based impact analysis work for Datasphere migration?

Lineage-based impact analysis traces Datasphere lineage to enumerate direct and indirect consumers of deprecated columns. It produces audit-ready impact reports and recommends phased rollouts or backward-compatible migration strategies to prevent downstream breakage.

Can I automate tagging and design taxonomies for SAP Datasphere catalogs?

Tag taxonomy design creates controlled vocabularies for Datasphere catalogs. Automated tagging analyzes columns to auto-suggest tags with confidence scores, enabling large-scale application subject to owner review.

How do I map business glossary terms to technical assets in SAP Datasphere?

Bidirectional glossary-to-asset mapping links business glossary terms to technical Datasphere models, views, and tables. This ensures business and technical users share common definitions and standardizes terminology.

What is the best way to define and validate KPIs in SAP Datasphere?

KPI definition and validation maps KPI formulas to underlying Datasphere measures and validates calculations against source data. It traces KPI-to-measure lineage to manage KPI lifecycle and ownership accurately.

Do I need owner approvals before applying bulk metadata updates to Datasphere models?

Owner approvals are required for bulk update templating and phased rollouts across Datasphere assets. This governance step ensures proposed renames, deprecations, and metadata changes are tracked in audit-ready impact reports.