Add ENVO-OEO mapping-file #2068
Draft
+41
−0
Conversation
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
|
@stap-m To fully close #2010 we would have to change/remove the preexisting mappings via annotation property. Should this be handled in a separate PR or should I also do this here? |
stale
bot
added
the
stale
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.
Summary of the discussion
See #2010
The goal of this PR is to add a SSSOM file that includes previously via anotation property
skos:closeMatchmatched terms from ENVO.The match-type has been reassessed and often changed to
skos:exactMatch. For the reasons of this change please check this table.Type of change (CHANGELOG.md)
Add
Workflow checklist
Automation
Closes #
PR-Assignee
term tracker annotationReviewer