Multi‑Format Schema Ingestion

Every ingest writes a SchemaIngested entry to the ULID‑keyed, SHA‑256 hash‑chained audit ledger — Avro, XML Schema, JSON Schema, Excel, Erwin XML, JDBC, or a custom importer. The source fingerprint is stamped into the entry; nothing reaches the MetaModel without a ledger row.

Magellan accepts schemas from a wide variety of sources and formats, eliminating the need for manual conversion or custom tooling.

Supported formats include Avro, XML Schema (XSD), JSON Schema, Excel spreadsheets, Erwin XML repository exports, and direct relational model connections via JDBC.

For formats not covered out of the box, Magellan provides a custom schema import module framework. Teams can build their own importers to ingest proprietary, legacy, or niche schema formats into Magellan's unified MetaModel.

Custom import modules follow a well‑defined interface: parse the source format, map its constructs to MetaModel elements, and register the module with Magellan's ingestion pipeline. Once registered, custom formats appear alongside built‑in formats in the import workflow.

Every imported schema — whether from a built‑in or custom module — is automatically transformed into Magellan's unified MetaModel, providing a consistent internal representation regardless of the original format.

Each ingest writes a `SchemaIngested` entry to the audit ledger, recording the source fingerprint (sha256 of the raw bytes), the importer module identifier and version, the actor's role at time of action, and the assigned schema ULID. A reviewer can replay the chain to prove that the MetaModel state was derived from a specific source artifact.

Audit ledger entries written by this feature

Each action in this feature appends one of the following entry types to the ULID‑keyed, SHA‑256 hash‑chained audit ledger. A reviewer can replay the chain to reconstruct exactly what happened, when, and under which role.

SchemaIngestedSchemaParsedImporterModuleRegistered

Read the full Audit & Trust architecture