The document outlines the OpenAIRE guidelines for content providers, introducing a new metadata application profile aimed at improving the linkage between funding information and research outputs. It emphasizes the need for upgrades from various perspectives, including authors, funders, and service providers, to enhance metadata quality and interoperability. Key features include compliance with funder mandates, the provision of author identifiers, and the establishment of controlled vocabularies for better resource identification.

1. @openaire_eu
OpenAIRE Guidelines for
Content Providers
V4 – Introducinga NewMetadataApplicationProfile
JochenSchirrwagen
BielefeldUniversity,Germany

2. Current state

3. (November2017)
Support of OpenAIRE Guidelines by Content Providers
3
Compatibility level # of supporting content provider
OpenAIRE Basic (formerly DRIVER-OA) 433
OpenAIRE 2.0 (with EC funding info) 29
OpenAIRE 2.0+ (DRIVER-OA & EC funding) 97
OpenAIRE 3.0 346
OpenAIRE Data 15
• 22.6 M publications,606K datasets,700K items linked to funding

4. FromGuidelinesforDataProviders
LiteratureRepositories(ande-journals)
1
DataRepositories
2
CRIS-CERIF
3
4

5. • SoftwareRepositories
• Catch-allRepositories
• CRIS
• DataRepositories
• Catch-allRepositories
• Institutional&thematic
repositories
ResearchLiterature
• ThematicRepositories
• InstitutionalRepositories
• E-journals
ResearchSoftware/
otherReserach Products
ResearchData
ResearchInformation
ToGuidelinesforOpenScienceContentProviders
5

6. Why we need an
upgrade

7. • Funder perspective
• Linkfundinginformationwithresearchoutput
• Author andReader perspective
• Linkauthorsandcontributorswiththeirresearchoutputandeasenamedisambiguation
• Serviceproviderperspective
• Avoidoverloadingofoai_dcmetadata
• Makemaintenanceandmappingsofcontrolledvocabularieseasierbyhelpofidentifiers
• Makeidentificationofresourceseasier(e.g.forTDM)
• Improvealignmentwithotherregionalrepositorynetworks
• Agree on a shared set of metadata properties and controlled vocabularies
• Allow for region specific extensions
• Examples: LA Referencia, JAIRO (Japanese Institutional Repositories Online)
Upgrade needs from different perspectives
7

8. What is included?

9. Application Profile
Overview

10. • Buildan application profilebased on establishedand widely
used metadata schemes in repositories
• DublinCoreandDataCitev4.1
• Allowfor additional propertieswhen needed
• Align with other repositorynetworks
Approach

11. • Support the provisionof author identifiersin metadata
MetadataProperty aboutauthorand contributoridentifier
11
<datacite:creator>
<datacite:creatorName>Wallentin, Carl‐Johan
</datacite:creatorName>
<datacite:nameIdentifier
nameIdentifierScheme="ORCID"
schemeURI=“http://orcid.org">
http://orcid.org/0000-0003-1983-9378
</datacite:nameIdentifier>
</datacite:creator>

12. • Complywithfundermandates
• MakeuseofCrossRefFundingData
• Insomecaseswemayneedanattribute„fundingstream“
Metadata Property about funding information
12
<datacite:fundingReference>
<datacite:funderName>European Commission</datacite:funderName>
<fundingStream>H2020 Marie Skłodowska-Curie Actions</fundingStream>
<datacite:funderIdentifier
funderIdentifierType="Crossref Funder ID">
</datacite:funderIdentifier>
<datacite:awardNumber
awardURI="http://cordis.europa.eu/project/rcn/195983_en.html">660668
</datacite:awardNumber>
<datacite:awardTitle>ACT against AMR</datacite:awardTitle>
</datacite:fundingReference>

13. • Accessrights– how can I accessthe resource
• License– what am I allowedto do with the resource
• Use URIswhenver possible
Metadata Property about License and Access rights
13
<dc:rights
rdf:resource="http://purl.org/coar/access_right/c_abf2">
open access
</dc:rights>
<dc:rights
rdf:resource="http://creativecommons.org/licenses/by-nc/4.0/">
Creative Commons Attribution‐NonCommercial
</dc:rights>

14. • URL of one or more fulltext files
• Attributesabout accessright, mimetype, objecttype
Metadata Property about Fulltext Location
14
<file
accessRights=http://purl.org/coar/access_right/c_abf2
mimeType="application/pdf“>
http://europepmc.org/articles/PMC5574022?pdf=render
</file>

15. • Re-use and adaptation of controlledvaluesused in the
DataCiteschema
• E.g.identifiertypes,roletypes,relationtypes
• Controlled Vocabulariesdefined by the COAR community
• E.g.resourcetypes,accessrights,versiontypes
• Controlled Vocabulariesdefined in OpenMinTeD Guidelines
• E.g.licenses
Controlled Vocabularies
15

16. • General aspects
• Uniqueidentificationofvocabularyconcepts
• Improvedgranularity
• MultilingualSupport
• ImplementedinSKOS
• ResourceTypes
• http://vocabularies.coar-repositories.org/documentation/resource_types/
• AccessRights
• http://vocabularies.coar-repositories.org/documentation/access_rights/
COAR Resource Types and Access Rights
16

17. Concepts in the Resource Type Vocabulary v1.1
17

18. <resource xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:datacite="http://datacite.org/schema/kernel-4"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:vc="http://www.w3.org/2007/XMLSchema-versioning"
xmlns="http://namespace.openaire.eu/schema/oaire/"
xsi:schemaLocation="http://namespace.openaire.eu/schema/oaire/ ../schemas/openaire-v4.xsd">
<datacite:creator>
<datacite:creatorName>Wallentin, Carl‐Johan</datacite:creatorName>
<datacite:nameIdentifier nameIdentifierScheme="ORCID" schemeURI="">http://orcid.org/0000-0003-1983-9378</datacite:nameIdentifier>
</datacite:creator>
<datacite:fundingReference>
<datacite:funderName>European Commission</datacite:funderName>
<fundingStream>H2020 Marie Skłodowska-Curie Actions</fundingStream>
<datacite:funderIdentifier funderIdentifierType="Crossref Funder ID"></datacite:funderIdentifier>
<datacite:awardNumber awardURI="http://cordis.europa.eu/project/rcn/195983_en.html">660668</datacite:awardNumber>
<datacite:awardTitle>ACT against AMR</datacite:awardTitle>
</datacite:fundingReference>
<datacite:alternateIdentifier alternateIdentifierType="DOI">10.1002/chem.201701589</datacite:alternateIdentifier>
<datacite:relatedIdentifier relatedIdentifierType="EISSN" relationType="IsPartOf">1521-3765</datacite:relatedIdentifier>
<dc:title xml:lang="eng">Redox‐Neutral Dual Functionalization of Electron‐Deficient Alkenes</dc:title>
<dc:description xml:lang="eng">Visible‐light photoredox catalysis ...</dc:description>
<dc:language>eng</dc:language>
<dc:date>2017-05-10</dc:date>
<dc:type rdf:resource="http://purl.org/coar/resource_type/c_6501">journal article</dc:type>
<dc:identifier>http://europepmc.org/articles/PMC5574022</dc:identifier>
<dc:publisher>John Wiley and Sons Inc.</dc:publisher>
<dc:rights rdf:resource="http://purl.org/coar/access_right/c_abf2">open access</dc:rights>
<dc:rights rdf:resource="http://creativecommons.org/licenses/by-nc/4.0/">Creative Commons Attribution‐NonCommercial</dc:rights>
<dc:subject>acyl radicals</dc:subject>
<dc:subject>carboxylic acids</dc:subject>
<dc:subject>cascade transformation</dc:subject>
<dc:subject>multicomponent reactions</dc:subject>
<dc:subject>photoredox catalysis</dc:subject>
<file accessRights="http://purl.org/coar/access_right/c_abf2" mimeType="application/pdf" objectType="">http://europepmc.org/articles/PMC5574022?pdf=render</file>
</resource>
Sample
record
18

19. • Versionstoolkit2008:
http://www.lse.ac.uk/library/versions/VERSIONS_Toolkit_v1_final.pdf
• NISO-JAVrecommendations:http://www.niso.org/workrooms/jav
Construction Area – COAR Version Type Vocabulary
19
Term info:eu-repo/ Used By Definition (short)
AO authorVersion JAV, RIOXX Author’s Original
SMUR submittedVersion JAV, RIOXX Submitted Manuscript under Review
AM acceptedVersion Accepted Manuscript
P - JAV, RIOXX Proof
VoR publishedVersion JAV, RIOXX Version of Record
CVoR updatedVersion Corrected Version of Record
EVoR updatedVersion Enhanced Version of Record
NA - Not applicable
- draft DRIVER Early version; work in progress

20. • COAR Vocabularyon version types
• Modelinghierarchical structure
• E.g.inMODS–relatedItem.type„host“,part,detail
• To describe bibliographic citation details
Construction Area – COAR Version Type Vocabulary
20

21. • Draft:http://openaire-guidelines-for-literature-repository-
managers.readthedocs.io/en/latest/introduction.html
• Blog:https://blogs.openaire.eu/?p=2397
• Schemaand examplerecordsongithub
• https://github.com/openaire/guidelines-literature-repositories
• DC:http://dublincore.org/documents/dces/
• DataCitemetadataschema:https://schema.datacite.org/
• OpenMinTeD:https://guidelines.openminted.eu/
• RIOXX: http://rioxx.net/
References
21

22. • Now startingthe consultationphasewith the community
• CommentinOpenAIREblogpost,
• Annotateinthedraftdocument
• Sendemailtoguidelines@openaire.eu
• Updateof the validator service
• Forcingimplementation support in repositoryplatforms
How can You participate / next steps

23. 23
jochen.schirrwagen@uni-bielefeld.de
guidelines@openaire.eu