Move non-language-specific Vitro annotations to VIVO tbox firsttime d… #225
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
…tations.n3 and initialTBoxAnnotations.n3
roflinn
approved these changes
Mar 4, 2021
ghost
pushed a commit
that referenced
this pull request
Feb 23, 2023
#225) * Move non-language-specific Vitro annotations to VIVO tbox firsttime directory. * Update tbox/firsttime readme to document difference between vitroAnnotations.n3 and initialTBoxAnnotations.n3
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.
…irectory.
JIRA Issue:
What does this pull request do?
Moves non-language-specific vitro annotations from VIVO-languages into VIVO's home/resources/rdf/tbox/firsttime.
What's new?
Adds file home/resources/rdf/tbox/firsttime/vitroAnnotations.n3 with non-language-tagged content.
How should this be tested?
Should be tested in conjunction with vivo-project/VIVO-languages#95 .
After applying both pull requests, there will be no functional changes.
The following SPARQL query should show that vitro:fullPropertyNameAnnot values now have en-US tags:
SELECT ?o WHERE {
?x vitro:fullPropertyNameAnnot ?o
} ORDER BY ?o
All other vitro annotation properties should remain unchanged, but will be managed in different files. You can test this by modifying a displayLimitAnnot value in VIVO/home/src/main/resources/rdf/tbox/firsttime , redeploying and restarting. A query like the following will show your new value:
SELECT ?x ?o WHERE {
?x vitro:displayLimitAnnot ?o
} ORDER BY ?x ?o
Interested parties
@VIVO-project/vivo-committers