Ingestion mappings (read-only)
Outcome
An operator can read the mapping a feed runs today, and knows where a new importer or a change to one is built.
What changed (#6745)
The hand-built mapping editor in the RCM app is retired: New draft, Edit
as draft, the visual builder, Suggest mapping, Draft with Lumi, the real-file
dry run, regression samples and Publish are gone, and Configuration no
longer lists Mappings. New importers, and changes to existing ones, are
built in the Import Desk (/import-desk, staff with an Import Desk role).
Nothing a feed runs was removed: every published mapping_definition version
keeps loading files.
What changed (#6746)
The server's YAML authoring path is gone as well: POST /ingestion/mappings,
mapping drafts, Suggest mapping, Draft with Lumi, crosswalk and rule
suggestions, the mapping dry run and the regression run no longer exist, so
nothing can create a new YAML mapping version. The tenant Import Library
screen (clone, inherit, overrides, adopt, promote a YAML importer) is retired;
a library-linked feed's Library tab is read-only.
In ADM, a YAML library version can no longer be created, edited, published or approved from a promotion. A curator can still Retire a published YAML version and Delete a YAML draft. No live tenant used a YAML mapping, so the RCM-36 inventory was not required before this change.
Read a feed's mapping
- Configuration → Feeds, open the feed, choose Mapping (read-only).
- The page lists the feed's Versions, newest first; select one to see it as YAML or as Field lineage.
- A row's lineage (Artifacts → Browse records → Lineage) and a charge's Import source panel link to the exact version that row ran with.
A bookmarked editor URL (/admin/ingestion/mappings/<feed>/edit…) lands on
the same read-only view.
Change a mapping
Open the feed in the Import Desk (the read-only page links there for an Import Desk role holder) and compile, review and publish a new importer. Library feeds still adopt and override from the feed's Library tab.