Update Bulkrax config to work with Hyku's per-tenant field mappings #275
Conversation
This file contains 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
Thanks to a new feature in Hyku, Bulkrax field mappings will be configurable on a per-tenant basis via an Account setting. This method should be favored over configuring field mappings in the knapsack initializer; new Accounts will be initialized with the default field mappings configured in Bulkrax, so adding customizations to them at this level is unnecessary and may cause confusion
bkiahstroud
force-pushed
the
update-bulkrax-config-to-work-with-per-tenant-field-mappings
branch
from
cb7d707 to
f48c5e5
Compare
bkiahstroud
deleted the
update-bulkrax-config-to-work-with-per-tenant-field-mappings
branch
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.
Thanks to a new feature in Hyku, Bulkrax field mappings will be
configurable on a per-tenant basis via an Account setting. This method
should be favored over configuring field mappings in the knapsack
initializer; new Accounts will be initialized with the default field
mappings configured in Bulkrax, so adding customizations to them at this
level is unnecessary and may cause confusion