[ENG-10234] 1.1.6 BE: Implement mapping to convert from DataCite resource types to schema.org resource types #11586
+830
−1
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
…ers from parent project / registry / preprint
…eed tests updates and maybe some type yield logic )
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Ticket
Purpose
We currently use DataCite URI/terminology to refer to an object’s type (e.g. AudioVisual, Book, BookChapter, etc). FAIR Signposting expects these object types to be represented using schema.org terms/URIs. We will need to a mapping to convert between DataCite and schema.org when we get the linkset doc for a given object.
For projects, registrations, and preprints, if a user has specified a resourceType using the DataCite resource type terminology (AudioVisual, Book, BookChapter), then we should use that and map it to an appropriate schema.org URI. Otherwise, we should just the OSF object type (Project, Registration, Preprint) and map that to an appropriate schema.org URI. Projects, registrations, and preprints should have a second type link: “Provide a second link that has as target https://schema.org/AboutPage in the common case where an actual landing page is concerned” from FAIR Signposting Profile - Signposting the Scholarly Web
Changes
Implementing mapping for datacite to scheme
(created from the following one linkset related PR #11571 to keep its changings )
Side Effects
QE Notes
CE Notes
Documentation