Support importing compound metadata#1206
Merged
Merged
Conversation
Add support for `name:` (alias `row_key:`) in field mappings with an `object:` key. This allows the mapping to specify the key under which the value will be written inside the object row, independently of the globally unique mapping key.
laritakr
changed the title
ShanaLMoore
approved these changes
Jun 12, 2026
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
2 participants
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.
Summary
name:/row_key:option to Bulkrax field mappings so an imported value can be stored under a chosen key inside anobject:row, independent of the unique mapping key.Supports 🚧 Rework yaml structure for compound metadata hyrax#7483
Details
object:writes each value into the object row under the mapping key by default. Mapping keys must be globally unique, so two objects could not both use the same in-row key (e.g. atitlein two different compounds).name:(aliasrow_key:) sets the in-row key explicitly, letting two uniquely-keyed mappings write the same row key into different objects — the case a sub-property shared across compounds, or one colliding with an existing scalar mapping, requires.name:/row_key:are unchanged.9-stablefor a 9.5.1 patch release.