OpenAIRE Guidelines Promoting Repositories Interoperability and Supporting Open Access Funder Mandates July 2015 guidelines@openaire.eu Data Providers OpenAIRE Platform Services Content acquisition policy Publications in OpenAIRE Data in OpenAIRE OpenAIRE Guidelines for data sources Where we started… • ‘oai_dc’ 15 elements based on DCMES schema • As established and ‘lowest common denominator’ OAI format • Used in numerous interpretations -> interoperability issue • Requires agreements on syntax (use of OAI-PMH & oai_dc) and semantics (controlled vocabularies) • DRIVER Guidelines v2 introduced in 2008 • info:eu-repo Application Profile for encoding schemes •Mainly used to describe textual resources • Continued in OpenAIRE Guidelines since 2009 In the meantime… • OpenAIRE scope & requirements have expanded since then • By complementary types of data sources • For research data and research information • Non-textual content • Publication and data linking • Project contextualization • New global “authoritative” identifier based infrastructures • For authors/contributors • funders / projects • research outputs Guidelines Timeline OpenAIRE: EC + OA (2013) OpenAIRE: EC-FP7 (2010, 2012) DRIVER: OA (2008) Text Repositories Text Repos. Aggregators Text Rep. Aggr. Oai_DC Data-Rep. OAI_DATACITE CRIS CERIF Literature Repositories (and journal platforms) Dublin Core (DRIVER) Data Repositories (and archives/data centres) Datacite CRIS systems CERIF-XML 3 Guidelines for Data Providers Guidelines for Literature based Data Sources • Continues the DRIVER v2 Guidelines • Transfer protocol primarily but not limited: OAI-PMH •Metadata format (so far): oai_dc • Application Profile (so far): info:eu-repo • Extended by properties to describe • Funder / Project information • Embargo Period / Embargo End Date • Open Access Status / Access Rights • Alternative Identifier • Referenced Dataset(s) • Referenced Publication(s) OpenAIRE OAI-Set • To group metadata relevant for OpenAIRE • See https://www.openaire.eu/content-acquisition- policy/content-acquisition-policy/content-acquisition-policy • Metadata about Open Access Publications • Metadata about Publications funded in EC-FP7 / H2020 • Metadata about Publications funded by other funders • OpenAIRE provides information about supported funding information setName setSpec* The OpenAIRE set OpenAIRE openaire projectID Element name projectID DCMI definition dc:relation Usage Mandatory (if applicable) Usage instruction A vocabulary of projects is exposed by the OpenAIRE API: http://api.openaire.eu/#cha_projects_http , and available for all repository managers. Values include funder, project name and projectID. The projectID equals the Grant Agreement number, and is defined by the namespace: info:eu-repo/grantAgreement/Funder/ FundingProgram/ProjectNumber/ Jurisdiction/ProjectName/ProjectAcronym/ Example: info:eu-repo/grantAgreement/EC/FP7/123456 info:eu-repo/grantAgreement/EC/FP7/12345/EU//Acronym accessRights Element name accessRights DCMI definition dc:rights Usage Mandatory Usage instruction Use values from vocabulary Access Rights at http://purl.org/eu-repo/semantics/#info-eu-repo- AccessRights • info:eu-repo/semantics/closedAccess • info:eu-repo/semantics/embargoedAccess • info:eu-repo/semantics/restrictedAccess • info:eu-repo/semantics/openAccess Examples: info:eu-repo/semantics/openAccess embargoEndDate Element name embargoEndDate DCMI definition dc:date Usage Mandatory (if applicable) Usage instruction Recommended when accessRights = info:eu- repo/semantics/embargoedAccess The date type is controlled by the name space info:eu- repo/date/embargoEnd/, see http://wiki.surffoundation.nl/display/standards/info- eu-repo/#info-eu-repo-DateTypesandvalue. Encoding of this date should be in the form YYYY-MM-DD (conform ISO 8601). Examples: info:eu-repo/date/embargoEnd/2011-05-12 Alternative Identifier Element name Alternative Identifier DCMI definition dc:relation Usage Recommended Usage instruction List alternative identifiers for this publication that are not the primary identifier (repository splash page), e.g., the DOI of publisher’s version, the PubMed/arXiv ID. The term is defined by info:eu- repo/semantics/altIdentifier info:eu- repo/semantics/altIdentifier// where must be one of the following: ark,arxiv, doi, hdl, isbn, purl… Example info:eu-repo/semantics/altIdentifier/doi/10.1234/789.1 Referenced Dataset Element name Referenced Dataset DCMI definition dc:relation Usage Recommended Usage instruction Encodes links to research datasets connected with this publication. The syntax of info:eu- repo/semantics/dataset is: info:eu- repo/semantics/dataset// where must be one of the following: ark,arxiv, doi, hdl, isbn, purl… Example info:eu-repo/semantics/dataset/doi/10.1234/789.1 Referenced Publication Element name Referenced Publication DCMI definition dc:relation Usage Recommended Usage instruction Encode links to publications referenced by this publication. The syntax of info:eu- repo/semantics/reference is: info:eu- repo/semantics/reference// where must be one of the following: ark, arxiv, doi, hdl, isbn… Examples: info:eu-repo/semantics/reference/doi/10.1234/789.1 Meet H2020 OA Guidelines • https://www.iprhelpdesk.eu/sites/default/files/newsdoc uments/Open_Access_in_H2020.pdf Property DC Field Value EU funding acknowledgment dc:contributor “controlled” terms : ["European Union (EU)" and "Horizon 2020"]["Euratom" and "Euratom research and training programme 2014-2018"] Peer reviewed dc:type info:eu-repo/semantics/publishedVersion Embargo period dc:date dc:rights • info:eu-repo/date/embargoEnd/ • (as publication date) • info:eu-repo/semantics/embargoedAccess Project information dc:relation info:eu- repo/grantAgreement/EC/H2020/[ProjectID]/[Jurisdiction]/[ProjectName]/[Pr ojectAcronym]/ Persistent identifier dc:identifier or dc:relation License dc:rights URL of license condition Persistent IDs for authors and contributors dc:creator dc:contributor Reference to related research outcome dc:relation info:eu-repo/semantics/dataset// Guidelines for Research Data based Data Sources •Based on DataCite metadata scheme • Proven standard for heterogeneous data sources and cross-disciplinary archives •Maintained by a trusted and sustainable organization • Support of data citation •Metadata Format: oai_datacite • OAI-Set: openaire_data • Zenodo as reference implementation for OpenAIRE Data Repository Guidelines Guidelines for Research Data based Data Sources •Adaptations for OpenAIRE: • Incl. additional PID schemes to DOI, e.g.URN, ARC … • Recommends links to related publications & datasets • Recommends Contributor prop. to relate dataset to funding information • Date and Description prop. are mandatory • Enforces (info:eu-repo) encoding scheme on Rights property Guidelines for CRIS Managers based on CERIF-XML • CERIF as de facto standard for CRIS data model • Entities for organization, person, project, output, data .. • CERIF-XML as data exchange standard (in the CRIS world) •Maintained by euroCRIS as sustainable organization Relevant CERIF Entities for OpenAIRE Guidelines for CRIS Managers based on CERIF-XML •Adaptations for OpenAIRE: • Subset of CERIF entities relevant for OpenAIRE • Semantic Interoperability • Reuse of CERIF Semantics vocabularies for classification and definition of relationships between entities • Consistency with the other OpenAIRE Guidelines • E.g. resource types, access rights Guidelines for CRIS Managers based on CERIF-XML •Syntactic Interoperability •Distinct namespace for OpenAIRE CERIF schema •Nesting only of multi-lingual attributes, federated identifiers, linked entities •System Interoperability: • Transfer Protocol: OAI-PMH •OAI-PMH sets for • Each type of entity • The entire CERIF graph OpenAIRE Compatibility Status: Levels and OAI Sets OpenAIRE basic Only Open Access content via driver oai set OpenAIRE 2.0 EC funded content via ec_fundedres ources oai set OpenAIRE 2.0 + Open Access and EC funded content via driver and ec_fundedreso urces oai set OpenAIRE 3.0 Open Access and/or EC funded and/or National/other funded content via openaire oai set Future Directions Next steps Innovative Scholarly Services – Need of Improved Metadata Quality • Features • Disambiguation by identifiers for authors / contributors, funders / project grants, research outputs • Explicit links to landing pages and fulltext files • Explicit links between publications and other research outputs • Detailed bibliographic citation information • Explicit and machine readable license information • Future proof • Compatible with linked data principles • Extensibility towards Open Science properties • Backward compatibility and low-barrier upgrade • Following DCMI Guide on Publishing Metadata (dcterms) • COAR IG Controlled Vocabularies Innovative Scholarly Services – Need of Network Alignment •Alignment & collaboration needed between major repository initiatives • LA Referencia, SHARE, RIOXX, OpenAIRE, … • COAR-CASRAI OA Interoperability WG • Alignment on metadata elements and vocabularies • COAR IG Controlled Vocabularies • Community driven effort to supersede info:eu-repo application profile • Working on an up to date technological standard • Editorial Board to ensure expertise and long-term support Find and discuss at: https://guidelines.openaire.eu Contact us: guidelines@openaire.eu July 2015 Pedro Principe, University of Minho Jochen Schirrwagen, University of Bielefeld