Do not offer UMLS vocabulary in interface if umls.properties is absent. #241
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
… into rel-1.12.0-alpha
…into rel-1.12.0-alpha
brianjlowe
changed the title
gneissone
approved these changes
Jun 2, 2021
litvinovg
approved these changes
Jun 9, 2021
ghost
pushed a commit
that referenced
this pull request
Feb 23, 2023
…t. (#241) * Replace hardcoded en locale with current locale in lang attributes * Do not offer UMLS vocabulary service in interface if umls.properties is absent
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.
https://jira.lyrasis.org/browse/VIVO-1992:
Does not include UMLS in the list of vocabulary sources if umls.properties is not present on the resource path.
How should this be tested?
Click "Add Concept".
List should include AGROVOC, GEMET, LCSH but not UMLS.
Interested parties
@VIVO-project/vivo-committers