Schema Catalog
& Enrichments
The Catalog is the business-friendly view of your event schemas. While the Explorer shows raw schema content, the Catalog surfaces what matters to governance: who owns it, what it's for, how it's classified, and whether it has AsyncAPI documentation.
Provider-agnostic enrichments
Enrichments are stored in event7's own database — not in your schema registry. This is a deliberate design decision:
- ·Confluent tags require the Advanced license ($$)
- ·Apicurio labels have limited metadata support
- ·Enrichments survive registry migrations
- ·Same data model regardless of provider
- ·No vendor lock-in on business metadata
- ·Description — what this schema represents
- ·Owner team — who is responsible
- ·Tags — free-form labels (pii, gdpr, critical-path…)
- ·Classification — public / internal / confidential / restricted
- ·Data layer — RAW / CORE / REFINED / APPLICATION
The Schema Registry remains the source of truth for schemas. event7 stores what the registry doesn't know — business context.
Data classifications
Every schema can be classified to signal its sensitivity level:
Open data — can be shared externally. No PII, no business secrets.
Default. Available within the organization but not outside. Standard business data.
Sensitive business data. Restricted to specific teams. May contain PII.
Highest sensitivity. PCI, financial, regulated data. Requires encryption and audit.
Classifications feed into the governance score — a schema with "restricted" classification and no encryption rule gets a lower score.
Data layers
Data layers categorize schemas by their position in the data pipeline. Each layer has different governance expectations:
<topic-name>-valueIngestion layer. Minimal constraints — backward compatibility, source metadata. Schemas mirror the source system structure.
<domain>.<entity>.<version>Canonical model. Strict governance — full transitive compatibility, mandatory doc fields, PII encryption, ownership. The backbone of your data platform.
<domain>.<entity>.agg.<period>.<version>Aggregated data. Backward transitive compatibility. Must reference Core types for consistency. Aggregation period documented.
<app>.<domain>.<entity>.<version>Consumption views. Lightweight governance — backward compatibility, keep schemas simple (max 30 fields). Optimized for specific consumers.
Data layers appear as badges in the Catalog and are used by the governance templates to apply layer-specific rules.
Catalog interface
The Catalog table shows one row per schema subject with these columns:
| Column | Description |
|---|---|
| Subject | Schema subject name with format badge (AVRO / JSON) |
| Owner | Team responsible for this schema |
| Classification | Public / Internal / Confidential / Restricted badge |
| Data Layer | RAW / CORE / REFINED / APPLICATION badge |
| Broker | Broker types from channel bindings (Kafka, RabbitMQ, Redis…) |
| AsyncAPI | Documentation status — documented (✅ vN) / ready / raw (—) |
| Score | Governance score badge (A–F) with toggle visibility |
| Version | Latest schema version number |
| Updated | Relative timestamp (5m ago, 2d ago) |
Filters: search by subject name, filter by owner, classification, data layer, broker type, and AsyncAPI status (all / documented / undocumented / with-refs / with-asyncapi / no-asyncapi).
CatalogSheet viewer
Clicking a row opens a full-width sheet panel with two tabs:
Raw schema content with syntax highlighting, field structure, version selector, and references list.
If documented: rendered AsyncAPI spec with Docs / Edit / JSON sub-tabs. If not: one-click Generate button.
The inline enrichment editor (pencil icon) lets you edit description, owner, tags, classification, and data layer without leaving the table.
CSV export
Export the full catalog as CSV for governance reports, audits, or external tools. The export includes all enrichments, format, version count, reference count, and governance score.
GET /api/v1/registries/{id}/catalog/export?format=csvevent7 Catalog vs EventCatalog
event7's Catalog is a governance view of schema subjects — enrichments, scores, and documentation status. It lives inside event7 and is designed for day-to-day governance work.
EventCatalogis a separate product — a static documentation site for events, services, and domains. event7 exports to EventCatalog via the generator-event7 plugin.
Think of it as: event7 Catalog = governance workspace, EventCatalog = published documentation portal. They are complementary.