Amend metadata block TSVs#38
Merged
qqmyers merged 1 commit intoGlobalDataverseCommunityConsortium:IQSS/9983-missing_unique_constraintsfrom Nov 8, 2023
Conversation
qqmyers
approved these changes
Nov 8, 2023
qqmyers
merged commit ecb5036
into
GlobalDataverseCommunityConsortium:IQSS/9983-missing_unique_constraints
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.
Change the metadata block field definitions where the field had
allowControlledVocabularyset toTRUEbut no vocabulary was provided. This would result in the field effectively being treated asallowControlledVocabularyset toFALSEbefore the change to isControlledVocabulary(). These fields are now explicitlyallowControlledVocabulary=FALSE.