Store precision as a resource on DOI claiming #3960
Merged
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
brianjlowe
approved these changes
Mar 20, 2024
|
Tested per procedure in issue: confirmed that literal is stored instead of URI in current code, rendering the publication date editing inoperable. With this PR, date is editable and precision is correctly stored as a URI reference. |
|
Small bugfix PR, so can merge with single review. |
chenejac
pushed a commit
that referenced
this pull request
Apr 5, 2024
Co-authored-by: Georgy Litvinov <[email protected]>
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.
VIVO GitHub issue
What does this pull request do?
Fixes imported date precision.
What's new?
Store imported date precision as a resource, not string literal.
How should this be tested?
Interested parties
@VIVO-project/vivo-committers