Source‑to‑Target Mapping
Every draft, edit, and field‑level change writes MappingDrafted or MappingRevised to the ledger — including the actor's role at the moment of the action. There is no silent overwrite, no lost authorship, no after‑the‑fact reconstruction.
Magellan's mapping interface uses an intuitive 'source on the left, target on the right' layout that mirrors how data professionals naturally think about transformations.
The hierarchical view lets users drill into nested structures, expanding and collapsing nodes to focus on the level of detail they need.
Mappings can be created via drag‑and‑drop, making the process accessible to data domain experts and business SMEs — not just engineers.
Each mapping relationship captures not just the source‑to‑target link but also any transformation logic, business rules, and validation criteria that apply.
Every save writes a `MappingDrafted` (first version) or `MappingRevised` (subsequent versions) entry to the audit ledger. The entry carries the mapping ULID, the actor's role at time of action, and a sha256 of the canonical mapping payload — so a reviewer can prove which draft a downstream artifact was generated from.
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.
MappingDraftedMappingRevisedFieldMappingChangedRelated glossary terms
Definitions for the technical, regulatory, and standards terms referenced on this page. Each link opens the term in the full glossary.
Open the full glossary