Download to read offline
Uploaded byOpenAIRE
OpenAIRE Making your repository OpenAIRE compliant: tutorials and short videos
The document outlines an online workshop on making research repositories compliant with OpenAIRE guidelines. It covers the importance of open access for EU-funded research, the steps necessary for repositories to achieve compliance, and the specific requirements set by the European Research Council and the European Commission. Key topics include the types of documents to deposit, the timelines for making them open access, and the tools available to support repository managers in this process.
More Related Content
Similar to OpenAIRE Making your repository OpenAIRE compliant: tutorials and short videos
OpenAIRE Making your repository OpenAIRE compliant: tutorials and short videos
- 1. Pedro Príncipe &José Carvalho , University of Minho How to make your repository OpenAIRE compliant Online workshop – January 23 and 24, 2012
- 2. AGENDA 1) OpenAIRE and compliancy with the ERC Scientific Council Guidelines for Open Access and the European Commission Open Access Pilot in FP7, Pedro Príncipe 2) How to make your repository OpenAIRE compliant, Pedro Príncipe & José Carvalho 3)Compliancy for DSpace, José Carvalho 4) Questions and Answers. 2
- 3. OpenAIRE and compliancy withthe EC/ERC OA policies 1/4 OpenAIRE in a nutshell… How to comply with the EC/ERC OA policies
- 4. The European Comission and the European Research Council want to provide the widest dissemination and access to the results of the research they fund. OpenAIRE implements theOpen Access requirements in EU Member States 4
- 5.
- 6.
- 7. Open Access Pilot in FP7 August 2008 European Commission launched the Open Access Pilot in FP7 that will run until the end of the Framework Programme The pilot applies to 7 research areas: 1.Energy 2. Environment (including Climate Change) 3. Health 4. Information and Communication Technologies (Cognitive Systems, Interaction, Robotics) 5. Research Infrastructures (e‐ infrastructures) 6. Science in society 7. Socio‐economic sciences and the humanities 7
- 8.
- 9. Complying with FP7and ERC requirements »»»»» What to deposit? »»»»» Where to deposit? »»»»» When to deposit? 9
- 10. What to deposit? Published version –publisher’s final version of the paper, including all modifications from the peer review process, copyediting and stylistic edits, and formatting changes (usually a PDF document) OR Final manuscript accepted for publication – final manuscript of a peer‐reviewed paper accepted for journal publication, including all modifications from the peer review process, but not yet formatted by the publisher (also referred to as “post‐print” version). 10
- 11. Where to deposit? Institutional repository –of the research institution with which they are affiliated OR (If this is not possible) Subject based/thematic repository OR Orphan Repository provided by OpenAIRE for articles that can be stored neither in institutional nor in subject‐based/thematic repositories 11
- 12. When to deposit? Researchers should deposit their articles or manuscripts in a relevant repository immediately upon acceptance for publication, to be made open access within six or twelve month depending on the FP7 research area 6 Months Access Embargo12 Months Access Embargo ERC All grant recipients after 2007 FP7 in the thematic areas: "Health", "Energy", "Environment" (including Climate Change)", and "Information & communication technologies" (“Cognitive Systems”, “Interaction” and “Robotics”) in the activity: "Research infrastructures" (e‐infrastructures) in the thematic area: "Socio‐economic Sciences and the Humanities" in the activity: "Science in Society" 12
- 13. The pilot coversapproximately 20% of FP7 projects: 13
- 14. How to complyworkflow 14 REPOSITORY Submit manuscript to publisher Final author manuscript Reference of the article available on the OpenAIRE/EC sites, fulltext available to all (immediately or after embargo periodoin repository 14
- 15.
- 16. How to makeyour repository OpenAIRE compliant 2/4 Steps to make your repository OpenAIRE complaint OpenAIRE guidelines
- 17. Steps to makeyour repository OpenAIRE complaint 1.Register your repository in OpenDOAR OpenDOAR is an authoritative worldwide directory of academic open access repositories. 2. Test compliancy with OpenAIRE Make your repository OpenAIRE complaint – by implementing the OpenAIRE Guidelines 17 3. Add your repository in OpenAIRE OpenAIRE in collaboration with OpenDOAR provides you an easy web tool to help you register the repository.
- 18. 1. OpenDOAR The first step is to register your repository in OpenDOAR. If you are already registered in OpenDOAR: – Check if the information is update –Attention to the URL and admin email 18
- 19. 2. OpenAIRE Guidelines First of all, compliance to the OpenAIRE guidelines The purpose of OpenAIRE Guidelines is to make FP7/ ERC publications visible. To achieve this and allow central harvesting of FP7/ ERC publications, repositories must comply with some minimum technical requirements. “The OpenAIRE Guidelinesare simple metadata specifications for repositories that need to be OpenAIRE compliant. After complying to the OpenAIRE guidelines, the repository will become the single entry point for researchers that want to deposit FP7 publications.” 19
- 20. 2. OpenAIRE Guidelines Make your repository OpenAIRE compliant by implementing the OpenAIRE Guidelines Plugins(popular repository platforms) helps to implement the guidelines Repository should enable the deposition of publication files and metadata (also info relative to the EC projects funding) Get EC project data 20
- 21. 2. Test theOpenAIRE compliance After you have made some progress in implementing the guidelines you should run a compliancy test. The OpenAIRE provides a validator where you can verify if the repository is truly compatible with the guidelines. www.openaire.eu:8380/dnet‐validator‐openaire Enter the OAI‐PMH base URL of your repository and choose to test your repository against the OpenAIRE rule set. After running the test you can browse the results. Please make sure you have an ec_fundedresources set and that it contains at least one record. 21
- 22.
- 23. Compliant repositories –list in the portal 23
- 24. Find the repositoryin the portal 24
- 25. The portal informabout the repository compliance 25
- 26.
- 27. OpenAIRE Guidelines Released in July 2010 (V. 1.1 Nov. 2010) – The OpenAIRE guidelines are supplementary and built on top of the DRIVER Guidelines Plus fields: projectID, accessRights, embargoEndDate – All aspects of the DRIVER Guidelines are valid, with a very few exceptions. 27
- 28. OpenAIRE Guidelines OpenAIRE Set Content definitions: – The content to be inserted in the OpenAIRE set must be EC funded content Set naming setNamesetSpec* The OpenAIRE set EC_funded_resources set ec_funded_resources 28
- 29.
- 30. OpenAIRE guidelines projectID 30 Element nameprojectID DCMI definition dc:relation Usage Mandatory Usage instruction A vocabulary of projects will be exposed by OpenAIRE through OAI-MPH, and available for all repository managers. Values will include . The projectID equals the Grant Agreement number, and is defined by the namespace info:eu-repo/grantAgreement/EC/FP7 Example <dc:relation> info:eu- repo/grantAgreement/EC/FP7/12345 </dc:relation>
- 31. OpenAIRE guidelines accessRights 31 Element nameaccessRights DCMI definition dc:rights Usage Mandatory Usage instruction Use values from vocabulary Access Rights at http://wiki.surffoundation.nl/display/standard s/info-eu-repo/#info-eu-repo-AccessRights; values are: 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>
- 32. OpenAIRE guidelines embargoEndDate 32 Element nameembargoEndDate DCMI definition dc:date Usage Recommended 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>
- 33.
- 34.
- 35. OAI extended Addon OAI Extended Addon (or a patchto be more precise): – Extends the base functionality of the OAI‐PMH interface and delivers repository administrators more flexibility and functionalities to select and filter the information. – The purpose of the OAI Extended Addon was to modify the OAI Interface's output, showing only items that were compliant with the DRIVER Guidelines. – The Addon provides also the tools to create a set according to the requirements of the OpenAIRE Guidelines, helping European repositories to become OpenAIRE compliant. – Other features are: hability to show didl schema and ETDMS itens. May be completely adjusted to other environments and can easily be configured, changed or extended… 35
- 36. OAIextended Initially created for the DRIVER Guidelines – Now enables OpenAIRE compliance. How? – Filter all the records that have a dc.relationwith: info:eu‐repo/grantAgreement/EC/FP7/???? This set is used for OpenAIRE Portal
- 37. Addon OAI Extended OAI Extended Addonis a DSpace patch (1.6.2 & 1.7.2): Dspace 1.6.2 • OAIextended v.2 (08 Nov 2010) http://projecto.rcaap.pt/index.php/lang‐en/consultar‐recursos‐de‐apoio/remository?func=fileinfo&id=328 • OAIextended v.2.3 (26 Jul 2011) http://projecto.rcaap.pt/index.php/lang‐en/consultar‐recursos‐de‐apoio/remository?func=fileinfo&id=341 Dspace 1.7.2 – OAIextended v.2.4 (25 Oct 2011) http://projecto.rcaap.pt/index.php/lang‐en/consultar‐recursos‐de‐apoio/remository?func=fileinfo&id=344 37
- 38. Set EC FundedResources
- 39.
- 40. OpenAIRE Authority Control Dspace1.6.2 http://projecto.rcaap.pt/index.php/lang‐pt/consultar‐recursos‐de‐apoio/remository?func=fileinfo&id=342 Dspace 1.7.2 http://projecto.rcaap.pt/index.php/lang‐pt/consultar‐recursos‐de‐apoio/remository?func=fileinfo&id=345 40
- 41. Addon OpenAIRE Authority Control This Addon use Dspace “Authority Control” functionality: –provides a way to list and verify OpenAIRE projects (FP7); – the list of projects is maintained as a web‐service – a local cache is created in order to be queried by users – only adds the correct value in dc.relation field Main goals: – Simplify and standardize the projects (ID) identification in the deposit process; – Facilitates compliance with the OpenAIRE guidelines 41
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48.
- 49.
- 50. Questions and Answers 50 Pedro Príncipe pedroprincipe@sdum.uminho.pt –skype id ratodebiblioteca José Carvalho jcarvalho@sdum.uminho.pt – skype id josekarvalho www.openaire.eu