4664 OpenAIRE compliance: AlternativeTitle and geoLocations #3
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
juancorr
changed the title
fcadili
pushed a commit
that referenced
this pull request
Aug 26, 2019
Merge upstream changes to 2043-split-gb-table branch
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.
This pull request is only related to change "Alternative Title" by "AlternativeTitle" and Geolocations related code. http://schema.datacite.org/meta/kernel-4.1/include/datacite-titleType-v4.xsd, marks valid title types and http://schema.datacite.org/meta/kernel-4.1/metadata.xsd , the geoLocations structure. Is not easy to put Datavese gelocation coordinates in OpenAIRE. Dataverse requests North, South, East and West coordinates, but OpenAIRE requests a point or a polygon. If the four coordinates are sets, OpenAIRE polygon can be defined but sometimes it is not the case.
New Contributors
Welcome! New contributors should at least glance at CONTRIBUTING.md, especially the section on pull requests where we encourage you to reach out to other developers before you start coding. Also, please note that we measure code coverage and prefer you write unit tests. Pull requests can still be reviewed without tests or completion of the checklist outlined below. Thanks!
Related Issues
Pull Request Checklist