Webinar@AIMS: How to practically support Open Access: Guidelines for Data Providers of the OpenAIRE scholarly communication infrastructure
Download as PPTX, PDF2 likes603 views
The document outlines guidelines for data providers within the OpenAIRE scholarly communication infrastructure, emphasizing the importance of open access to research outcomes in Horizon 2020. It discusses various OpenAIRE services, guidelines for data repositories, and the role of metadata in ensuring compliance with open access mandates. Future directions for OpenAIRE guidelines are also mentioned, highlighting the need for improved metadata quality and alignment with international standards.
![Mapping of Requirements from
H2020 OA Guidelines in Metadata
• https://www.iprhelpdesk.eu/sites/default/files/newsdocuments/Open_Access_in_H2020.pdf
15
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/<YYYY-MM-DD>
• <YYYY-MM-DD> (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
e.g.: info:eu-repo/semantics/altIdentifier/doi/10.1234/789.1
License dc:rights URL of license condition
Persistent IDs for authors
and contributors
dc:creator
dc:contributor
<Lastname, Firstname; id_orcid 0000-0000-0000-0000>
Reference to related
research outcome
dc:relation info:eu-repo/semantics/dataset/<scheme>/<id>](https://image.slidesharecdn.com/webinaraimsopenaire03122015schirrwagen-151204164538-lva1-app6892/85/Webinar-AIMS-How-to-practically-support-Open-Access-Guidelines-for-Data-Providers-of-the-OpenAIRE-scholarly-communication-infrastructure-15-320.jpg)
Webinar@AIMS: How to practically support Open Access: Guidelines for Data Providers of the OpenAIRE scholarly communication infrastructure
- 1. How to practically support Open Access: Guidelines for Data Providers of the OpenAIRE Scholarly Communication Infrastructure FAO AIMS webinar, 03 Dec 2015 Jochen Schirrwagen, University of Bielefeld
- 2. AGENDA 2 1. OpenAIRE explained briefly 2. Open Access in Horizon2020 3. The why, what and how about Guidelines for Data Providers 4. Future Directions of the OpenAIRE Guidelines
- 4. OPEN ACCESS INFRASTRUCTURE OpenAIRE for research in Europe 4 www.openaire.eu
- 5. From the OA Pilot in FP7 to the Key Infrastructure for the OA Mandate in H2020 5 OpenAIRE Dec. 2009 - Nov. 2012 OpenAIREplus Dec. 2011 – Dec. 2014 OpenAIRE2020 Jan. 2015 - Jun. 2018 of which ~700 are data provider
- 6. Project & Infrastructure Guided by OA funder policies (European Commission) • Participatory approach (human & e-infrastructure) Integrated Scientific Information System
- 7. Data Providers OpenAIRE Platform Services
- 8. OpenAIRE Service (in prod.) 8 Service or Tool Target Audience Description Validation / Aggregation Repository-Manager, Data Provider Metadata are collected following the OpenAIRE Guidelines Claiming Authors, Researchers, Project Coordinators Let users set links between research output and funding Deposit Authors Locating an appropriate repository to deposit research results Text-Data-Mining (Infrastructure Background Service) Extracting of project references, data citations, related publications, … Search / Discovery / API Users and machines Access to the OpenAIRE Information Space via Portal and API Monitoring / Reporting Funder, Project Coordinators Aggregated Statistics on funded research results, OA-Output, Publication lists per project FP7 Post-Grant OA Publishing Funds Pilot Authors from FP7 projects Making FP7 project results OA by covering APCs
- 9. OpenAIRE Service (in prep.) 9 Service or Tool Target Audience Description Data-Literature Interlinking Service Research Community; Stakeholder collaboration Prototype outcome of the RDA/WDS Publishing Data Group OA-Broker Service (in prep.) Repository Manger, Data Provider Distribution/Notification of enriched metadata to subscribed repositories; Usage Statistics / Analytics Service (in prep.) Repository Manager, Authors, Funder Assessing impact on Research Output; Contribution to Article-Level Metrics LOD Service (in prep.) Linked Data based knowledge discovery services Publishing the OpenAIRE Information Space into the Linked Data Cloud Open Peer Review Tender Project (in prep.) Researchers; Scholarly Communication Prototype development for tools and workflows to implement Open Peer Review aligned with the OpenAIRE infrastructure
- 10. Enriched Document Example 10 Plain Bibliographic information from metadata Multiple Instances host the same document (which is de-duplicated) Funding Info either from metadata or by text mining Findings from Text Mining / Inference
- 11. Beth & colleagues receive a grant 6 4 5 3 1 DM PFoster Open Science OpenAIRE EUDAT THOR EUDAT OpenAIRE INRA, FAO, EFSA, … Process & Analyze Access to facilities with fast network GEANT Common Access with EduGain Common identification with ORCID What is similar out there? Who can I collaborate with? What data will I create? How can I share it with my colleagues? What policies for use and re- use? How to best describe it? Where to store it? How to make it accessible? Preservation? How, what, when, where? Open Peer Review? How to enhance my Impact? EGI PRACE Where to run? What facilities? How to prepare and transfer? Further Analysis What tools to use? Do I have big data? Can I scan the literature for similar results? OpenAIRE OpenMinTeD EGI OpenAIRE EUDAT DOAJ Re3Data 2 TOPIC: identify water & air borne diseases and alert OpenAIRE Publish Store and Curate Source: Natalia Manola, “e-Infrastructures – The Starting Blocks for Open Science and Innovation”, 21-10-2015, ICT2015 panel
- 13. 13 FUNDERS Many funders have now stipulated Open Access to results! MANDATES Many have Open Access mandates in place! REPOSITORIES But how often are these outputs linked to funding details?
- 14. Open Access in Horizon 2020 The grant agreement states: “ENSURE OPEN ACCESS… AS SOON AS POSSIBLE AND AT THE LATEST ON PUBLICATION, DEPOSIT A MACHINE-READABLE ELECTRONIC COPY OF THE PUBLISHED VERSION OR FINAL PEER-REVIEWED MANUSCRIPT ACCEPTED FOR PUBLICATION IN A REPOSITORY FOR SCIENTIFIC PUBLICATIONS” http://ec.europa.eu/research/participants/data/ref/h2020/mga/gga/h2020-mga-gga- multi_en.pdf
- 15. Mapping of Requirements from H2020 OA Guidelines in Metadata • https://www.iprhelpdesk.eu/sites/default/files/newsdocuments/Open_Access_in_H2020.pdf 15 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/<YYYY-MM-DD> • <YYYY-MM-DD> (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 e.g.: info:eu-repo/semantics/altIdentifier/doi/10.1234/789.1 License dc:rights URL of license condition Persistent IDs for authors and contributors dc:creator dc:contributor <Lastname, Firstname; id_orcid 0000-0000-0000-0000> Reference to related research outcome dc:relation info:eu-repo/semantics/dataset/<scheme>/<id>
- 16. The Why, What and How about Guidelines for Data Providers 16 3/4
- 17. Content Acquisition Policy 17 Publications in OpenAIRE Data in OpenAIRE https://www.openaire.eu/content-acquisition-policy/content-acquisition-policy/content-acquisition-policy
- 18. Journals / Publishers / Aggregators as complementary data provider • Aggregators provide us with “reference metadata” • We do our best regarding metadata normalization • OpenAIRE supports additional APIs for collection in these cases • Journals, Data Repositories provide us with “detailed information”, e.g. grantIds, data citations, fulltext links • Need to comply with the OpenAIRE Guidelines 18 OJS Pub- lishers Data Repo Data Centres
- 19. 1 2 3Literature Repositories (and journal platforms) Dublin Core (DRIVER) Data Repositories (and archives/data centres) Datacite CRIS systems CERIF-XML Guidelines for Data Providers 19 https://guidelines.openaire.eu
- 20. OpenAIRE Compatibility – of Literature Repositories 20 OpenAIRE basic Only Open Access content OAI-Set: ‘driver’ OpenAIRE 2.0 EC funded content OAI-Set: ‘ec_fundedre sources’ OpenAIRE 2.0 + Open Access and EC funded content 2 sets: ‘driver’ ‘ec_fundedreso urces’ OpenAIRE 3.0 Open Access and/or EC funded and/or National/other funded content OAI-Set: ‘openaire’
- 21. Origin – OAI-PMH • ‘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 21
- 22. Relevant Properties: projectID 22 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: <dc:relation> info:eu-repo/grantAgreement/EC/FP7/123456 </dc:relation> <dc:relation> info:eu-repo/grantAgreement/EC/FP7/12345/EU//Acronym </dc:relation>
- 23. Relevant Properties: accessRights 23 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: <dc:rights> info:eu-repo/semantics/openAccess </dc:rights>
- 24. Relevant Properties: 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: <dc:date> info:eu-repo/date/embargoEnd/2011-05-12 <dc:date>
- 25. Relevant Properties: Alternative Identifier 25 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/<scheme>/<ident ifier> where <scheme> must be one of the following: ark,arxiv, doi, hdl, isbn, purl… Example <dc:relation> info:eu-repo/semantics/altIdentifier/doi/10.1234/789.1 </dc:relation>
- 26. Relevant Properties: Referenced Dataset 26 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/<scheme>/<identifier > where <scheme> must be one of the following: ark,arxiv, doi, hdl, isbn, purl… Example <dc:relation> info:eu-repo/semantics/dataset/doi/10.1234/789.1 </dc:relation>
- 27. Relevant Properties: Referenced Publication 27 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/<scheme>/<identifie r> where <scheme> must be one of the following: ark, arxiv, doi, hdl, isbn… Examples: <dc:relation> info:eu-repo/semantics/reference/doi/10.1234/789.1 </dc:relation>
- 28. Guidelines for Research Data Repositories •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 28
- 29. Guidelines for Research Data Repositories •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 29
- 30. Guidelines for CRIS Managers •CRIS as complement to institutional repositories •CERIF as de facto data model standard for CRIS • Entities for organization, person, project, output, data .. •CERIF-XML as data exchange standard for CRIS •Maintained by euroCRIS as sustainable organization 30
- 31. CERIF Entities in OpenAIRE 31
- 32. Addons, Patches and Plugins available for standard platforms: 32 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 Plugins: OpenAIRE + DRIVER http://pkp.sfu.ca/support/forum/viewtopic.php?f=28&t=7085 OPUS 4 http://www.kobv.de/entwicklung/software/opus-4/ MyCoRe, OpenAIRE-Compliance http://mycore.de/documentation/interfaces/oai.html#OpenAIRE-Compliance https://www.openaire.eu/repmanager-guide
- 33. 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/remository?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 Using the projects list provided by the OpenAIRE API 33 Allows users to search and include EC (+ WT + FCT) projects ID in the metadata of the records disposed in accordance with OpenAIRE
- 34. How to get Your Repository in OpenAIRE Make sure your repository is registered in OpenDOAR / r3data 1. Test Compatiblity • Of the OAI-PMH Protocol implementation • Of metadata compatibility with the OpenAIRE Guidelines 2. Register Your Repository, Journal or Aggregator • Await notification from OpenAIRE once successfully aggregated and indexed 3. Update Data Provider Configuration if needed 4. In preparation: agreement to TDM of fulltext files 5. In preparation: continuous validation reports over time https://www.openaire.eu/validator 34
- 35. Future Directions of the OpenAIRE Guidelines 35 4/4 V4 in preparation, to be released 2016
- 36. Alignment with other Networks - LA Referencia as an example • 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 36
- 37. 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 • Adoption of up to date technological standards for vocabularies • International Editorial Board to ensure expertise and long-term support • Draft COAR Resource Type Vocabulary (SKOS) 37
- 38. 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 • Ensuring mappings to the current oai_dc approach 38
Editor's Notes
- #22: We should just reason why we've started with oai_dc and info:eu-repo for the lit guidelines
- #23: projectID is needed to connect project information to the publication in the OpenAIRE information space. It equals to the Grant Agreement number as found in all documentation/correspondence between the EC and the researcher/coordinator. The projectID equals the Grant Agreement number, and is defined by the namespace info:eu-repo/grantAgreement/EC/FP7. The namespace defines the grant agreement number from the funder (EC) and funder program (FP7). The project information itself (project period, acronym, funding area etc.) will be ingested into the OpenAIRE information space by other means.
- #24: 1. accessRights will define the type of access to the publication.
- #25: When the value of accessRights is “embargoedAccess” embargoEndDate will define the date of the embargo period. This is a Recommended element when accessRights = info:eu-repo/semantics/embargoedAccess
- #26: 1. accessRights will define the type of access to the publication.
- #27: 1. accessRights will define the type of access to the publication.
- #28: 1. accessRights will define the type of access to the publication.
- #36: * Explain for oai_dc and oai_datacite
- #38: * COAR logo
- #39: * COAR logo