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.
What does this do?
Why are we doing this? (with JIRA link)
Jira: https://collectionspace.atlassian.net/browse/DRYD-1650
This brings in new terms from the 8.1 release into the
base-instance-vocabularies.xml
for the OHC tenant.Until there's some more work done to reduce duplication of config in CollectionSpace it seemed like we can continue updating this file for the time being because OHC has customized the
entrymethod
term list. When making changes to the anthro term lists in 8.1 I didn't anticipate tenants which used it as a base profile.How should this be tested? Do these changes have associated tests?
Dependencies for merging? Releasing to production?
None
Has the application documentation been updated for these changes?
No
Did someone actually run this code to verify it works?
@mikejritter built locally and ran a diff on the terms (note that the first difference is from
entrymethod
):