Facilitate Open Science Training for European Research Facilitate Open Science Training for European Research Repository managers: guidelines to meet H2020 requirements Ricardo Saraiva - University of Minho rsaraiva@sdum.uminho.pt Overview 1. The context: OpenAIRE infrastructure 2. OpenAIRE guidelines for data sources 3. Adoption and mapping with other repository networks 4. Future Directions 5. Tools for repositories compatibility The context: OpenAIRE infrastructure 1/5 OPEN ACCESS INFRASTRUCTURE OpenAIRE for research in Europe www.openaire.eu Project & Infrastructure Guided by OA funder policies (European Commission) Participatory approach (human & e-infrastructure) Integrated Scientific Information System Data Providers OpenAIRE Platform Services Content acquisition policy Publications in OpenAIRE Data in OpenAIRE OpenAIRE Guidelines for data sources 2/5 • ‘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 Where we started… 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 1 2 3Literature Repositories (and journal platforms) Dublin Core (DRIVER) Data Repositories (and archives/data centres) Datacite CRIS systems CERIF-XML 3 Guidelines for Data Providers How do they work? • Identification of Open Access and funded research results by OAI-Sets: • ‘ec-fundedresources’ • ‘openaire’ • ‘openaire_data’ • Latest schema guarantees backwards-compatibility with previous versions. • Enhancing research results by metadata enrichment in OpenAIRE. “Repository managers will be able to enable authors to fulfill the EC Commission Open Access requirements” 16 www.openaire.eu 1 2 3Literature 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 OpenAIRE elements projectID access_rights embargo_end_date 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/123456info: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/embargoedAccessThe 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/newsdocume nts/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:datedc: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]/[ProjectAcronym]/ Persistent identifier dc:identifier or dc:relation License dc:rights URL of license condition Persistent IDs for authors and contributors dc:creatordc:contributor Reference to related research outcome dc:relation info:eu-repo/semantics/dataset// 1 2 3Literature 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 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 1 2 3Literature 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 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 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 Adoption and Mapping with other repository networks 3/5 LA Referencia aligned with OpenAIRE Guidelines •Latin America Open Access Repositories Network •Central metadata elements and use of vocabularies •Access rights: openAccess; embargoedAccess •Use of Creative Commons licenses recommended •Considers regional aspects compared to OpenAIRE regarding •Mandatory , mandatory if applicable and recommended use of metadata fields •Collaboration between LA Referencia and OpenAIRE ensures future compatibility of the guidelines OpenAIRE Guidelines, RIOXX and the case in UK •RIOXX to support UK repositories for compliancy with funder OA policies (RCUK, HEFCE) •Introduction of element / attributes to encode project / funder information •Based on oai_dc + rioxx terms and rioxx attributes •Supports NISO-ALI •Support of EC-H2020 OA mandate is (currently) done via agreed mapping between RIOXX and OpenAIRE Literature Guidelines Future Directions Next steps 4/5 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 Tools for Repositories Compatibility Validator, API, software add-ons 5/5 Data Provider Registration Via validator tool www.openaire.eu/validator Test the OpenAIRE Compliance The OpenAIRE provides its validator service: www.openaire.eu/validator Users can: •Verify if the repository is truly compatible with the guidelines. •Run a compatibility test (enter the OAI-PMH base URL). Run Compatibility Test: View/Select Rules for Usage Use of OAI-DC (M) Use of OAI-PMH: 'openaire' or 'ec_fundedresources' or 'driver' set must exist (M) Use of OAI-PMH: 'openaire' set must exist (M) driver set must exist (R) ec_fundedresources set must exist (openaire2.0) for Content Field Access Level (M) Field Alternative Identifier (R) Field Audience (R) Field Contributor (R) Field Coverage (R) Field Creator (M) Field Date of Publication (M) Field Description (MA) Field Embargo End Date (MA) Field Format (R) Field Language (R) Field License Condition (R) Field Project Identifier for ecfundedresources (M) Field Project Identifier for openaire(MA) Field Publication Type (M) Field Publication Version (R) Field Publisher (MA) Field Referenced Dataset (R) Field Referenced Publication (R) Field Resource Identifier (M) Field Source (M) Field Subject (MA) Field Title (M) http://api.openaire.eu/ http://api.openaire.eu/ Need to integrate project and funding information into your institutional repository based on DSpace or ePrints? •Go for the DSpace/ePrints endpoints. Do you prefer a TSV with the list of projects by funding? •TSV endpoint is meant for Addons, patchs or plugins for Repositories & Journals software Dspace add-ons and versions compliance https://wiki.duraspace.org/pages/viewpage.action?pageId=33238567 OpenAIRE Plug-in (OpenAIRE 2.0) http://files.eprints.org/649/ EPrints - OpenAIRE compliance example (3.0) https://gist.github.com/alenkovich/9596992 OAI_DC_OpenAIRE implementation for Zenodo https://github.com/zenodo/zenodo/blob/master/zenodo/base/format_templates/OAI_DC_OpenAIRE.xsl OJS Plugin: OpenAIRE http://pkp.sfu.ca/support/forum/viewtopic.php?f=28&t=7085 + OJS DRIVER-Plug-In https://www.openaire.eu/rep-managers/rep-man-toolkit/repository-managers OpenAIRE compatibility for different DSpace versions 51 Via OAIextended add-on and also via XOAI add-onDspace 1.8.2 • Compatibility with OpenAIRE 2.0 guidelines OAI 2.0 is a standard part of DSpace 3.0DSpace 3 • Compatibility with OpenAIRE 2.0 guidelines via XOAI. • (fix ‘info:eu-repo/grantAgreement/EC/FP’ on the filter ‘openairerelationFilter’) OAI 2.0 is a standard part of DSpace 4.0DSpace 4 • OpenAIRE 2.0 compatibility via XOAI OAI 2.0 is a standard part of DSpace 5.0DSpace 5 • OpenAIRE 2.0 compatibility via XOAI and will be partially compatible with OpenAIRE 3.0 guidelines via patch (to be presented) . OAI 2.0 What is OAI 2.0? OAI 2.0 is a Java implementation of an OAI-PMH data provider interface that uses XOAI, an OAI-PMH Java Library. Why OAI 2.0? Projects like OpenAIRE, DRIVER have specific metadata requirements. As the OAI-PMH protocol doesn't establish any frame to these specifics, OAI 2.0 can have more than one instance of an OAI interface (feature provided by the XOAI core library) so one could define an interface for each project. OAI 2.0 is a standard part of DSpace 3.0, 4.0 and 5.0 OAI 2.0 • With a Filter is possible to select information from the data source. • A Transformer allows to make some changes in the metadata before showing it in the OAI interface • OAI 2.0 also adds a new concept to the OAI-PMH basic specification, the concept of context.  http://www.example.com/xoai/driver  http://www.example.com/xoai/openaire  http://www.example.com/xoai/request Concepts: Filter, Transformer and Context OAI 2.0 Contexts could be seen as virtual distinct OAI interfaces  http://repositorium.sdum.uminho.pt/oai/driver  http://repositorium.sdum.uminho.pt/oai/openaire  http://repositorium.sdum.uminho.pt/oai/request DRIVER OPENAIRE OAI 2.0 (record in openaire set) https://repositorium.sdum.uminho.pt/oai/openaire? verb=GetRecord&metadataPrefix=oai_dc&identifier=oai:repositorium.sdum.uminho.pt:1822/34546 Dspace Add-ons for project ids •OpenAIRE Authority Control •Dspace 3.2 • http://goo.gl/cEPTZN (updated March 2014) •Dspace 1.8.2 • http://projeto.rcaap.pt/index.php/lang-en/consultar-recursos-de-apoio/re mository?func=fileinfo&id=354 •OpenAIRE funders projects list addon (NEW) • In use on the RCAAP Project (PT repositories) • https://gitlab.fccn.pt/dev-rcaap/addon-openaire/tree/OpenAIRE5.X • https://gitlab.fccn.pt/dev-rcaap/addon-openaire/tree/OpenAIRE3.X Allows users to search and include EC (+ WT + FCT) projects ID in the metadata of the records disposed in accordance with OpenAIRE Using the projects list provided by the OpenAIRE API OpenAIRE Authority Control Add-on •Allows users to search and include FP7 project IDs in the metadata of the records disposed in accordance with the guidelines * Needs the OAIextended Add-on to create the set (ec_fundedresources) OpenAIRE Funders Projects List Add-on Searching by the name, acronym or the project id number Select the project and accept… the necessary namespace will be filled Example: http://hdl.handle.net/1822/21091 Metadata edition Unlocking dc.relation and searching by the name, acronym or the project id number Select the project and accept… the necessary namespace will be filled Some results in OpenAIRE… Useful Links: Find and discuss the guidelines at: https://guidelines.openaire.eu Test and register the repository at: http://validator.openaire.eu Find support at: https://www.openaire.eu/support/helpdesk Access the OpenAIRE API documentation: http://api.openaire.eu About COAR Repository Interoperability: http://coar-repositories.org/activities/repository-interoperability Find the guide for Repository Managers at: https://www.openaire.eu/rep-man-toolkit/repository-managers Search for OpenAIRE data providers at: https://www.openaire.eu/search/openaire-data-providers See the OpenAIRE Content Acquisition policy at: https://www.openaire.eu/openaire-s-content-acquisition-policy/download Thank You! Find and discuss at: https://guidelines.openaire.eu Contact us: guidelines@openaire.eu Ricardo Saraiva, rsaraiva@sdum.uminho.pt