RDF converter: subclassing file fix #332
Merged
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
Closes G-Node#212 The `section_subclasses.yaml` file is moved from the `doc` folder to the new `odml/resources` folder. This allows usage of the file with all install options.
- fix invalid DOI link in Dragly reference - add Sprenger DOI reference
jgrewe
approved these changes
Nov 7, 2019
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.
The PR
changes the location of the
section_subclasses.yamlfile from thedocfolder to the newodml/resourcesfolder. It also ensures, that the file is properly installed/exported when locally installing viasetup.py,pipor when preparing for a PyPI package.updates the available odml->RDF subclasses by new datacite
Sectiontypes.also includes a small RDFWriter fix - the writer was still using the deprecated
Propery.valueattribute. It now properly maps the file formatPropery.valueonto the currentPropertyattributevalues.The PR also adds updates to the DOI section of the project documentation page: