add ENVO import script #9 #13
Draft
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
|
@areleu this was never merged to oeo. Therefore I leave this PR open without merging. After having the new import pipeline, we can complete the ENVO import |
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.
As discussed in #812 some classes of the ENVO seem helpful for the OEO.
To extract the classes I adapted the script used for the IAO import. I mentioned the files we want to import in the txt files.
The classes that have to be imported are:
environmental systemhttp://purl.obolibrary.org/obo/ENVO_01001110environmental system processhttp://purl.obolibrary.org/obo/ENVO_02500000climate changehttp://purl.obolibrary.org/obo/ENVO_01000629greenhouse effecthttp://purl.obolibrary.org/obo/ENVO_02500004Since the three latter classes are related, I assume we want to import them with hierarchy.