Add source mapping configuration to sources page - #454
Draft
jal347 wants to merge 4 commits into
Draft
Conversation
jal347
marked this pull request as draft
July 21, 2026 22:00
…o metadata/field endpoint
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request enhances how source field mappings are handled and exposed in metadata, especially for multi-uploader sources. It ensures that per-source field mappings are merged, properly formatted, and only exposed in development mode, while also adding field-to-source annotations in the
/metadata/fieldsendpoint.Source mapping handling and exposure:
_meta.src.<source>.mapping) during metadata collection, ensuring multi-uploader sources have a unified mapping. [1] [2]/metadata?dev), flattening them to match the/metadata/fieldsrepresentation, and strips them from public responses._transform_source_mappingsto safely apply transformations (e.g., flattening or removing mappings) to each source's mapping without mutating cached metadata.Field annotation improvements:
/metadata/fieldsresponse with the main source(s) that define it, based on the merged and flattened per-source mappings, making data provenance clearer for consumers.Imports and dependencies:
merge_structandcopyto support the new merging and deep-copy logic. [1] [2]