Remember Me
Or use your Academic/Social account:


Or use your Academic/Social account:


You have just completed your registration at OpenAire.

Before you can login to the site, you will need to activate your account. An e-mail will be sent to you with the proper instructions.


Please note that this site is currently undergoing Beta testing.
Any new content you create is not guaranteed to be present to the final version of the site upon release.

Thank you for your patience,
OpenAire Dev Team.

Close This Message


Verify Password:
Verify E-mail:
*All Fields Are Required.
Please Verify You Are Human:
fbtwitterlinkedinvimeoflicker grey 14rssslideshare1

OpenAIRE 2020 Work Packages, Tasks, Deliverables

  • This work package carries out the management tasks and the exploitation of the OpenAIRE services/infrastructure by setting up a legal entity in the first year of the project.

    LEADER: Univ. of Athens
    CONTACT: (name, email)

    • Task 1.1: Coordination

      This tasks oversees the project coordination and management. As OpenAIRE2020 is a large conortium (50 partners) the management is divived among three organizations: Univ. of Athens is the overall coordinator, Univ. of Gottingen oversees the OpenAIRE network and CNR the technical activities.


      Task 1.2: Exploitation

      This task addresses the setup of a legal entity for OpenAIRE. It will investigate existing business plans and governance structures of similar initiatives to inform the Project Steering Committee of alternative solutions. The partners in this task will be assisted by subcontractors who will take care of related legal, accounting and business aspects.

    • D1.1 Project Quality Plan (M2, Confidential)

      D1.2 Goals and strategy of legal entity (M7, Public)

      D1.3 Progress Report (M12, Confidential)

      D1.4 Governance model for OpenAIRE legal entity (M12, Public)

      D1.5 Progress Report II (M30, Confidential)

      D1.6 Final Progress Report (M42, Confidential)

      D1.7 Detailed Activity Report (M42, Public)

  • (WP short description)

    LEADER: University of Goettingen
    CONTACT: (name, email)

    • Task 2.1: Production of dissemination material

      This task will create a resource-base of relevant material to promote OpenAIRE such as brochures, postcards, leaflets, success stories, web based material, press releases. Existing materials will be updated to reflect the requirements of Horizon 2020, and in keeping with OpenAIRE branding. All materials will be made available via the portal, and  adapted to local NOAD requirements. The task will work closely with WP4 to tailor materials to relevant stakeholders (e.g. researchers, administrators, EC project managers, funders, publishers, repository managers, institutional data initiatives, CRIS administrators) and will direct targeted messages to each stakeholder about the services the OpenAIRE
      infrastructure can offer. Discipline-level differences in open access adoption, and data management practices will be considered when creating specific briefing papers. Materials will be used as instruments by NOADs to approach specific stakeholders, e.g. decision makers, funders, and will be used as advocacy materials as appropriate. Dissemination materials will focus on the range of services that OpenAIRE provides and will make succinct and understandable summaries of project research outputs. Work on promoting the OpenAIRE guidelines within WP4 will be bolstered by specific leaflets, slides. Briefing papers for NRPs to focus on specific aspects of policy implementation will be prepared.

      LEADER: UoA

      Task 2.2: Dissemination channels

      This task will manage the dissemination of OpenAIRE’s outreach material and gather input for its dissemination activities. The task will also provide bi-monthly updates via a blog within the consortium. The development and maintenance of a communication plan for scheduling output and content gathering will support this task in order to schedule regular contributions from the regional NOAD network and targeted stakeholders. This task will coordinate the newsletter. Thematic sections will include: open access and data policy update; scholarly communication activities; research data activities; featured EC projects and innovative publishing services. NOADs will be encouraged to
      contribute highlights from their regions to the regular OpenAIRE newsletter which will be managed by the regional coordinators on a cyclical basis. Spotlights on featured EC projects that demonstrated good practice strategies for open access and data management in Horizon 2020 projects will also be gathered from NOADs and published. A light-weight and flexible dissemination roadmap will be produced. This will plan for, and target events where OpenAIRE can raise visibility of open access obligations and promote its infrastructure, examples include: leveraging NOADs contact with National Reference Points (NPRs), National Contact Points (NCPs); making a concerted effort to contact Horizon2020 projects at kick-off, in close communication with the EC, in order to disseminate the toolkits (slides, presentations, briefing papers) from WP3. Activities to communicate the post-project Gold OA funds to relevant projects in WP5 will be planned in this task and draw on existing FP7 communication channels. All dissemination activities are closely aligned with liaison to relevant stakeholders in WP5 and all materials are aligned with international outreach.


      TASK 2.3: Organisation of outreach events
      This task will coordinate events and activities which will raise awareness of OpenAIRE and its associated activities. Each NOAD will schedule a national workshop which will be coordinated and supported by this task. These outreach workshops will focus on the uptake of the OA mandate in their country, discuss national policy and infrastructure interoperability, and involve different stakeholders (relevant infrastructure providers, research administrators, project coordinators, researchers), and where appropriate align with Pasteur4OA events. An additional series of four public workshops will be organized by the regional coordinators and held in each of their regions, to coincide with key conferences, and where possible with the European presidency. The workshops, each focusing on a topical subject in infrastructure development, will also reflect the outcomes of the research studies in the project and be open to a wide, diverse audience. Contributions from international efforts and initiatives will be encouraged, in order to align emerging practices. Each workshop will be video recorded (where possible) and the results immediately disseminated via the OpenAIRE portal. Preliminary titles are as follows:  “Innovative publishing models to support open science” This could be held in conjunction with the Academic Publishing in Europe, 2015;“Legal issues in the context of the Open Research Data Pilot”; “Measuring OA impact”; “Sharing research data and data publishing practices; “Text and Data Mining in scientific publications”


    • D2.1 Dissemination (M4, Public)

      D2.2 National Workshops: lessons learned (M40, Public)

      D2.3 Dissemination Roadmap II (M18, Public)

  • (WP short description)

    CONTACT: (name, email)

    • Task 3.1: Global Alignment of repository networks

      This task will focus on the alignment of regional networks of repositories in order to create an infrastructure that can connect across geographic boundaries. Alignment will help to avoid regional silos and support global interoperability of open access e-infrastructures. While regional diversity is important and will support innovation, there are a number of common approaches that can be adopted to facilitate exchange of data across repositories and the development of global value added services. These include the harmonization of some policy elements, and adoption of standardized impact measures, publication tracking methods, metadata elements, vocabularies, researcher IDs and so on. This task will review the current state of alignment of repository networks and work towards further integration at key networks around the work including Latin America, North America, China and Australasia. This will lead to a report of current state of repository alignment across the world (deliverable 3.1). In order to promote global interoperability, communications with regional/national/thematic networks as well as other stakeholders will play a central role. The task will also involve facilitating ongoing dialogue with other repository networks around the world to identify priorities and determine mechanisms for working together. This task will also ensure that other communities are aware of the value of alignment by liaising with other communities including policy makers, the research data community, publishers, and research administrative systems. The task will involve organization of meetings to bring together representatives from repository networks (see list of milestones) and liaising with other stakeholder communities worldwide, including presentations at major international conferences and attendance at important meetings. It will also support communications across regions to raise visibility of global trends and inform about open access developments in institutional repositories and research infrastructures. A report on the progress of international alignment of repository infrastructures will conclude activities, including an analysis of the role of Europe and its research institutions in international collaborations (D3.5). Activities in this task will be closely connected to WP 2 (Dissemination and Advocacy) and WP4 (Training and Support).


      Task 3.2: LIAISING with related initiatives

      Given the rapid pace of change in this environment, it will be extremely important that OpenAIRE maintains an ongoing dialogue with other key players. This task will involve liaising with other related initiatives working in the area of research infrastructures and open access issues including Research Data Alliance, Global Research Council, Science Europe, G8 Working Group, UNESCO, FAO, NGOs, OKFN, W3C, SPARC, DataCite, euroCRIS, and ESFRI projects. Concretely, activities in this task will include the identification and selection of issues and goals that need cooperation of initiatives and networks. This will result in a liaison strategy as a deliverable. Presentation at major international conferences will complement activities and activities will be included in dissemination activities, e.g. newsletter highlights.


      TASK 3.3: Pilot(s) showcasing global interoperability
      This task will expand the adoption of guidelines developed through OpenAIRE in Latin America in order to demonstrate of the feasibility of repository interoperability. OpenAIRE has developed practices and technologies that enable users (including funders) to track publications in the repository network according to research project, funding agency and so on. The use of common guidelines and technologies in both Latin America and Europe, two large regions, would promote further adoption in other regions and build momentum for global alignment. The task will assess the current state of adoption of DRIVER and OpenAIRE Guidelines in Latin America and identify barriers to their implementation. It will then promote the adoption of guidelines in the region through a workshop, and develop a roadmap outlining the strategy for implementation in different countries. Information will be disseminated in various ways including a virtual workshop. The CNR and UoA will adapt the OpenAIRE validator for Latin America (with LaReferencia branding). CNR and UoA will also assess the feasibility of implementing a LaReferencia instance of the D-NET aggregator in Europe that will demonstrate the value of the adoption of guidelines in Latin America.

    • D3.1 Liaison Strategy (M7, Public)

      D3.2 Report of current state in Latin America (M16, Public)

      D3.3 Report on current state of repository alignment globally and roadmap (M20, Public)

      D3.4 Final report on guidelines in Latin America (M30,  Public)

      D3.5 Status report (M38, Public)

  • (WP short description)

    LEADER: University of Minho
    CONTACT: (name, email)

    • Task 4.1: NOAD Network Coordination

      This task will closely oversee the management of the NOADs. Supporting the task is the NOADs programme plan, a constantly updated folder and set of documents which, with all regional coordinators, will oversee tasks and update activities. NOADs will have access to a detailed task list which groups their activities into Contact and Outreach; Helpdesk Support; Dissemination; Portal Presence; Planning; NPR outreach. NOADs will also be asked to provide input to dissemination channels on a regular basis. Monthly monitoring and regional meetings by the regional coordinators will ensure a clear communication path to central coordination. Assessment and support will be carried out in a structured way to ensure that tasks are being conducted to best ability. Action plans and activity reports will be completed regularly. This includes notifying regional coordinators about outreach activities to project coordinators, researchers, administrators, national points of reference and funders, and national workshops from T2.3. In addition, information about consortium activities, in particular evolution of the OpenAIRE services, upgrades to the infrastructure/portal, Zenodo, guidelines will be communicated to NOADs via webinars and briefing sessions to keep partner abreast of developments in the project.


      Task 4.2: H2020 OA policy training and support

      This task will provide the body of resources to facilitate the easy uptake and comprehension of the OA mandate to publications among a wide range of stakeholders, coinciding with the start of Horizon2020 projects. Working closely with WP2 and leveraging on the work produced within FOSTER project, a range of materials will be produced or repackaged at the start of the project and later on-demand according to emerging needs. OpenAIRE will deliver training materials, briefing papers, webinarsfor each target group, as well as chance to exchange ideas and good practice via OpenAIRE’s social media channels. This task will support key stakeholders in the following ways: Researchers and project managers: Given the widened remit of H2020 OA policies, many researchers will need basic information about OA (e.g. what is and how to provide OA to publications, copyright and quality issues in OA), while all of them need to know how to comply with the H2020 OA requirements. Training will be offered on H2020 compliance requirements as well as on the OpenAIRE tools (e.g. MyOpenAIRE) and how they can be used to monitor mandate compliance at different organisational levels (e.g.,project, institution) this will incorporate notifications about project publications and other features e.g. related datasets. A ‘starter kit’ will be made available in digital format to project managers, to be distributed among the project partners at kick-off meetings. Working closely with, and co-hosting with FOSTER, special reference will be paid to disciplines less aware of OA (e.g. Humanities and Social Sciences). Funders, research administrators and EC project officers: targeted programmes will be developed to communicate OA obligations and adherence to the mandate, including use of OpenAIRE infrastructure and services. Webinars as well as face to face meetings (particularly for EC staff) at relevant outreach events. NOADs: NOADs will be encouraged to attend training for specific stakeholders in order to understand how to support the EC mandate within theircountries. NOADs will also be offered webinars to support OpenAIRE developments. All training will be carried out using a variety of methods from face-to-face training attached to other project events and workshops to presentations and webinars.


      TASK 4.3: Research Data Management training and support

      This task will support the EC’s Open Research Data Pilot, and promote and propagate relevant resources to assist research data management planning, in close collaboration with E-INFRA-1. A support kit will be produced. The task will be directed at a range of stakeholders: EC staff (project officers) to make them aware of the pilot’s obligations and how to monitor progress; project managers eligible for the Open Research Data pilot; EC grantees and researchers who will contribute to the data planning and creation; research administrators who support projects at institutional level. Content for the task will be developed in accordance and close collaboration with FOSTER, and any generic materials can be reused and tailored especially for the EC pilot. DANS, Delft and Jisc as NOADs will contribute given their special expertise in this area. Support and outreach will consist of the following: templates for RDM, advice on data centres, Zenodo updates, legal issue guidance (from WP7, preliminary results will be incorporated at Month 10), support on the Open Research Data Pilot (opt-in/out clauses, information for project coordinators).A range of outreach and training techniques will be employed: Webinars, presentations, face to face training, briefing papers and FAQs.

      LEADER: DANS/Delft

      TASK 4.4: Guidelines for data providers and OpenAIRE service APIs

      Since 2010, the OpenAIRE Guidelines have been used to provide guidance to data providers on how to expose their content, to promote interoperability, to validate and harvest repositories and other data sources into the OpenAIRE infrastructure. This task will provide the needed updates to the guidelines for Data Source Administrators, as a result ofthe community involvement insustaineduse of the guidelines, and the development of related “standards”, like the CERIF model and the DataCite Metadata Schema. On the evolution of the Guidelines, OpenAIRE will actively seek engagement, collaboration, alignment and convergence with other relevant organizations and initiatives (like EuroCRIS, DataCite, COAR, UK-RIOXX and V4OA, CASRAI, etc.). Simultaneously, new standards (like the ResourceSync Framework) aiming for a more efficient exchange and synchronization of scholarly web resources between data providers and consumers will be explored. In order to facilitate the uptake and use of OpenAIRE public services, this task will also provide a body of documentation, guidance and support information on OpenAIRE service APIs. This task will mainlyconsolidate and update all OpenAIRE guidelines for data providers to meet H2020 requirements (e.g. Open Data Pilot), including minimumrequirements for collecting other (national or international) funder information.


      TASK 4.5: Helpdesk support

      This task will run the Helpdesk ticketing system, create and maintain the body of resources and references, in conjunction with T 4.3 and WP2, to provide an overall and ongoing support for both the OA mandate to publications and the Open Research Data Pilot. Helpdesk topics, knowledge-base and FAQs will be updated and expanded to reflect the widening remit of NOADs and the scope of Horizon 2020:
       -H2020 OA compliance: targeted information for stakeholders on how to comply with the Horizon 2020 will
      be provided to researchers, project managers, publishers, repository managers, research institutions’ EC project administration.
       -Data Managers: support will be given on guidelines compatibility, with focus on data repository and CRIS guidelines.
      - Open Data Pilot: materials created in T4.4 will also be repurposed via the portal and used to answer Helpdesk requests.
      - Licensing information: IPR details including support for reuse of data.
      - Gold Open Access: information about details of the Gold OA funds and how to claim payments.
      NOADs will be involved in answering questions from their countries, with the support of the core OpenAIRE team, and all requests will be answered within two working days. The helpdesk will be run and maintained by the University of Minho.

    • D4.1 Helpdesk System Toolkit (M4, Public)

      D4.2 Support kit for OA policy in H2020 (M10, Public)

      D4.3 Support kit for Open Research Data Pilot (M11, Public)

      D4.4 Helpdesk Operation Report (M40, Public)

      D4.5 Training Programme Report (M40, Public)

  • (WP short description)

    CONTACT: (name, email)

    • Task 5.1: POlicies & roadmapping

      This task will focus on defining the policies and specifications under which APC payments will be made. The first step in implementing the pilot will be to make clear what projects and authors are eligible to claim from the APC pilot fund and any limits that may apply (e.g. maximum number of papers funded per project). The policies will be drawn up bearing in mind that the aim of the pilot is to build an evidence base and therefore should have minimal barriers to eligibility for funding so as to maximise the number of open access articles funded. The task will also develop specifications for articles funded under this pilot. These specifications will be used as a basis for negotiating payment schemes with publishers.
      Establishment of compliance criteria/specifications for articles
      The specifications will be drawn from desk research on practices/polices applied by funders and projects (e.g. SCOAP3, PEER) within Europe and internationally as well as from the technical requirements for integration into the OpenAIRE infrastructure. It is important to develop best practice in this area so that there is a possibility for libraries and funders to reuse these specifications when conducting their own APC negotiations. The specifications will include a cap per APC for both articles and monographs and will be validated by a small group of open access experts.Encouraging publishers to adopt these specifications will contribute to the development of a healthy market for open access by reducing the complexity of licensing, ensuring interoperability and the long term availability of content, increasing transparency around APC charges, as well as making it possible to develop metrics on how the market is developing. The policies and specifications will be included in guidelines for project managers and publishers. NOADs, research administrators and librarians will also be informed through these guidelines in order to promote this opportunity for reimbursement of APCs to researchers in FP7-funded projects.
      Market/economic impact study
      LIBER will engage an outside expert to conduct a market/economic impact study. The purpose of the study will be to contribute to a vision of what a sustainable and competitive market for open access publishing should look like. The study should look at whether open access publishing has impacted subscription prices, where the money for APCs is going, and what steps need to be taken in order to ensure a sustainable scholarly publishing ecosystem. If, towards the end of the pilot a significant amount of the APC fund remains unspent this funding will be reallocated to expand the economic impact study to include case studies from institutions and funder in order to provide a more detailed mapping of the landscape. Roadmapping of a sustainable and competitive open access publishing market The results of the impact study will be presented at a workshop for librarians, funders, publishers and other stakeholders. A roadmap will be drafted building on the study, the information derived from the metrics and implementations of specifications in the pilot, and input gathered from the workshop.


      Task 5.2: workflow development and implementation

      The final workflow will be agreed taking into account that the process is made as easy as possible for the researcher and also to ensure that the necessary data is captured. Input regarding the workflow will be gathered from institutions with experience in APC processing (UCL, UGOE) as well as from Jisc. The bulk of the APC claims should come directly from the publisher, however, it will also be necessary to make it possible for researchers/institutions to submit claims directly so that the pilot is not initially dependent on agreements with publishers to begin the APC claims processing work. LIBER will manage the operation of the payments; dealing with APC claims submitted directly or via the NOADs, but also making bulk payments to publishers. The pilot will start at M2 andrun for 24 months or until the APC fund is exhausted.


      TASK 5.3: monitoring and technical alignment

      The OpenAIRE infrastructure will be modified to maintain information that provides transparency and feedback related to the pilot. The APCs workflows and policies will inform the technical alignment so that the monitoring of the implementation of policies and the generation of data regarding the spread of articles funded by the pilot can be automated. A Webpage to facilitate the submission of APC claims will also be integrated into the OpenAIRE front end services.
      Over the course of the pilot the uptake will be closely monitored in terms of numbers of articles to be expected for publishing (based on data already collected by OpenAIRE, see Task 5.3), articles processed and costs incurred for reimbursement of APCs (collected in Task 5.2). On this basis, regular reports on the number of articles funded, amount spent, average and median cost per articles and comparisons across domains and publication type will be produced. Based on the first-half year report on APCs uptake and metrics gathered (D5.2, M14 or earlier if spending exceeds initial expectations) the results will be discussed in the Strategic Guidance Board of the project. This will conclude in a realignment of strategies and priorities within the work package where needed, but also in a reassignment of work across the project if a significant under -or over-spending is foreseen.


      TASK 5.4: promotion and engagement
      Promotion and engagement will occur at three levels (1) towards the target community of FP7 grantees via the NOADs in order in encourage uptake of the pilot (2) with publishers (and their associations) in order to agree payment schemes and promote best practice, and, ultimately, (3) with the funders of open access publishing such as research funders, institutions and libraries in order to raise awareness of the pilot outcomes and contribute to the development of a vision for a sustainable and competitive open access publishing market. Both the SURF and Jisc networks will be leveraged in order to maximise engagement.This task will link with WP4 to promote awareness of open access publishing and the APC fund, and to WP2 to ensure that information regarding the pilot is included in OpenAIRE dissemination materials.
      Identification of target market/market analysis
      FP7 grant data will be analysed by ARC/UoAto identify projects and former grantholders that are eligible to apply for APC funding under the pilot. Those identified will be informed of their eligibility for APC funding and guided on how to submit claims. At the end of the pilot uptake will be assessed and a survey will be sent out to explore attitudes to the pilot.
      Publisher engagement
      This is central to the success of the pilot. The specifications developed in task 1 will be used as the basis for the negotiation of delivery and payment schemes with publishers. A call will invite publishers to submit proposals for APC prepayments. Proposals must meet the minimum specifications and also provide justification for estimates of number of expected FP7 articles. Publishers’ engagement and awareness will be key for encouraging the uptake of the APC fund.
      Stakeholder engagement
      The work and outcomes of the pilot will be promoted widely to institutions and funders so that they may provide input into and reutilize the policies and workflows developed in the pilot. Early on in the pilot a workshop to raise awareness of the pilot and to gather feedback will be held at the LIBER conference.

    • D5.1 Article policy/specifications guidelines (M3, Public)

      D5.2 First periodic report on APC uptake and metrics (M14, Public)

      D5.3 Market/Economic impact study (M26, Public)

      D5.4 Second periodic report on APC uptake and metrics (M28, Public)

      D5.5 Roadmap for a sustainable and competitive market for open access publishing (M28, Public)

  • (WP short description).

    LEADER: ICM (University of Warsaw)
    CONTACT: (name, email)

    • Task 6.1: Infrastructure maintenance

      ICM and CERN will support the continuous operation of the OpenAIRE infrastructure and the Zenodo repository according to procedures ensuring maximal system uptime and availability. Continuing the current activities, both systems will be deployed in professional data centre environments capable of guaranteeing their robust operation. In particular, the OpenAIRE infrastructure will benefit from the agreed-on and tested administration policies developed during the past project OpenAIREplus, which establish the rules of seamless deployment of new software releases in production and thus ensure a robust and controlled production system. The task covers activities of system administration, monitoring (e.g. routine and emergency maintenance procedures, and system security, availability and data integrity), software deployment (OpenAIRE packages for new releases and updgrades), and master-slave replica deployment to address resilience to failures by service-level redundancy and software/content backup with restore procedures (ICM). It also includes the mandatory overtime activities (CNR, ARC, ICM, Fraunhofer IAIS) of software upgrades (OS, libraries, open source products) and service software refactoring (i.e. revision of existing implementation to match new requirements).


      Task 6.2: Software lifecycle

      CNR will provide tools for supporting software life-cycle and will be coordinating and supervising system release plans, from development to testing and final release in production. Such activities will continue on the same line of the OpenAIREplus project development, by establishing and enforcing distributed development policies, planning proper software releases, guaranteeing their successful delivery and intervening with centralized and coordinated corrective actions to overcome the obstacles and still achieve the expected results. Activities include: (a) administration of tools for software development, testing, and integration (SVN, TRAC, build system, etc); (b) administration of development, testing and integration infrastructures; (c) coordination activities to facilitate software integration and respect software delivery deadlines and production release plans.


      TASK 6.3: infrastructure operation: workflow management

      The task focuses on the activities necessary to define, refine, configure, schedule, and monitor the infrastructure workflows necessary to combine OpenAIRE services to implement the phases of: (a) data source validation (including literature and data repositories and CRIS systems), registration, and collection, (b) de-duplication and inference over aggregated content, (c) publishing of Information Space via portal and export APIs.


      TASK 6.4: infrastructure operation: information space curation and Quality monitoring

      The task includes “continuous” (over-time) data curation and validation activities of the OpenAIRE Information Space, and identification of quality processes as new developments are integrated in the infrastructure. Data curators (UNIBI) will define harmonization and validation mappings for OpenAIRE compatible data sources and make sure the quality of the resulting Information Space will be up to the quality measures. Activities include overtime fine-tuning of deduplication algorithms for publications, authors, and organizations and of inference algorithms (CNR, ICM, UoA). Monitoring and validation of Information Space quality will be possible thanks to tuning and reporting from the validator service (UoA), the certification of flows and dynamics via services to be developed in WP8-T8.4 (CNR), and both automatic curation tools and careful manual curation intervention (UNIBI). The task includes metadata/file curation activities for the Zenodo repository (CERN).



      The aim of the OpenAIRE infrastructure is to offer services to third-party services. To make this possible, the infrastructure needs to collect and export metadata and files by interacting with third-party providers. This task offers technological and legal support (i.e. API definition and SLA drafting) to approach third-party providers in a technologically sustainable and legal way. The definition of APIs will take into account existing interfaces defined in relevant communities (for example EuroCRIS/CERIF API). Activities include the establishment of legal frameworks for the provision of advanced services to all stakeholders involved (publishers, repositories, data archives, etc.) to enable metadata and file processing (e.g., mining, de-duplicating, classifying, clustering).



      The aim of this Task is to define, describe and implement the data management policies for OpenAIRE2020, as requested by the EC Data Pilot. At the core of the activities, ICM, CNR and CERN will draft a document addressing the management plan regarding adopted metadata and standards, data archiving and preservation, data sharing (i.e. access rights) regarding the OpenAIRE information space and the content of Zenodo. The document will be kept up-to-date to reflect possible policy changes due to ongoing evolution of project requirements.


      This task will dedicate its efforts to the collaboration of the OpenAIRE services with the EC backend information. These will initially manage the reporting of the publications/data of H2020 projects, i.e., how can OpenAIRE info be retrieved from the EC services in an agreed upon methodology. This work will require possible refinement and/or enhancement of the OpenAIREAPIs and underlying workflows as H2020 progresses and more requirements are gathered.

    • D6.1 OpenAIRE specification and release plan (M2, Public)

      D6.2 Legal frameworks to enable data exchange (M6, Public)

      D6.3 Data management plan (M6, Public)

      D6.4 Maintenance report (M21, Public)

  • (WP short description)

    LEADER: University of Goettingen
    CONTACT: (name, email)


      In this study, legal barriers to data sharing in the context of the Open Research Data Pilot will be analysed. The study will focus on two legal issues which are of great relevance for the implementation of the Pilot; namely those of data protection law and public sector information (PSI). For the first issue, several privacy issues will be raised within the context of the Open Research Data Pilot and OpenAIRE. Different forms of protection of personal and sensitive data will be analysed (e.g. data protection/privacy law/confidentiality). It will be examined which data that is used and shared in an e-infrastructure such as OpenAIRE and the Open Research Data Pilot is covered by data protection rules and what consequences this has for the usage and sharing of those data.In order to assist the technical developments within OpenAIRE, legal principles for the sharing of personal and sensitive data will be developed and recommendations for legal and technical measures will be given.The second issue that will be analysed is that about public sector information. It will be evaluated, to what extend OpenAIRE and its partners, including the partners taking part in the Open Research Data Pilot, fall under obligations specified by EU and Member States for public-sector bodies (PSBs) on PSI with regard to access and re-use of this information, and what the exact consequences of those obligations are.The findings of this second subtask will show to what extent access and reuse of PSI is harmonised within the EU and how the regime of PSI influences the OpenAIRE Open Research Data Pilot. To illustrate the results, guidelines as to PSI and participating in the OpenAIRE Open Research Data Pilot will be prepared, for example when is it necessary/possible/useful to opt out of the Open Research Data Pilot.


      Task 7.2: Measuring OA impact

      This task will carry out one or more studies that will describe the multidimensional indicators of scholarly performance based on data retrieved by the OpenAIRE platform, which has linked databases on projects, publications, data, institutions, data providers and researchers. Analysis will include activity indicators, impact indicators and positional indicators. The task will investigate indicators for second level impact that link OA to possible social, cultural and economic impact (patents, EU stats, social media, web impact, etc.). In addition, it will:
      • Explore the interaction between open access practices at the level of research groups and potential indicators of impact
      and quality (including strategic responses by the scientific community to new indicators).
      • Explore which data sources should be the basis for OpenAIRE indicators.
      • Define the core principles on which standards for OpenAIRE metrics for evaluation should be based.
      • Define the principles on which an infrastructure of OpenAIRE indicators should be based.


      TASK 7.3: Literature-data integration

      In this task, DANS, PANGAEA (UniHB), and EMBL-EBI will engage with the OpenAIRE infrastructure towards consolidating a global data publishing and citation ecosystem, by experimenting with interlinking/integrating literature and datasets in the public domain, using data citations as a basis. Studies (EBI, PANGAEA (UniHB),, DANS) will focus on (1) building requirements and standards that facilitate literature-data integration and (2) understanding the scope and extent of data citation within and across different disciplines (e.g. granularity, citation purposes). Such analysis will be performed by involving relevant communities in workshops and will serve as input to the development of prototypes: (1) A data citation interlinking service (PANGAEA (UniHB),, CNR, EBI, DANS) resolving cross-references between PIDs of datasets and PIDs of publications collected from publishers, data repositories (DANS, PANGAEA (UniHB), and EMBL-EBI will serve as use-cases) and the OpenAIRE infrastructure; (2) Setting the basis for a global, open Data Citation Index Service, in order to study its implications and impact on different disciplines. Both demonstrators will be implemented as Open Source projects, in the context of the RDA/WDS Working Group Data Publication Services, with the cooperation of science publishers and further data centres, as appropriate. The resulting services will be hosted
      (mirrored) by a number of sites, including OpenAIRE and the ICSU WDS. Governance and maintenance of the service will be set up in a way that includes Open Access principles, where all relevant stakeholders (publishers, data centres, repositories/libraries, and added value service providers) contribute content and participate openly.


      TASK 7.4: Open review to literature and beyond
      This task will carry out a landscape scan and evaluation of new forms of publishing and (open) peer review. It will consider various routes of publishing (formal and informal) as well as types of publications (journal articles, monographs, proceedings, etc.). In particular, it will describe and classify new forms of peer review mechanisms (workflows, quality assurance, community involvement, benefits for authors and reviewers, integration with open access e-Infrastructures, etc.). Information will be gathered through literature research and a survey involving research communities, publishers, innovative projects, etc. As a prototype for the Humanities and Social Sciences, hypotheses.org, a platform hosting academic blogs, will carry out experiments to model the workflow from blog articles (original articles, reviews about publications, case studies, etc.) for the selection, review and revision of these articles towards peer reviewed publications (journal articles and edited books).Two additional prototypes in the area of open peer review will be carried out and evaluated (tender call M4, award of tender in M6, delivery of results M12). It is foreseen that the results of the study will be published in a similar fashion, with open review based on the facilities
      provided by the prototypes.

    • D7.1 Open Review: tender call evaluation report (M9, Public)

      D7.2 Analysis of OpenAIRE indicators (M14, Public)

      D7.3 Governance and requirements of interlinking service (M15, Public)

      D7.4 Novel models for open peer review (M16, Public)

      D7.5 Data citation standards and index requirements (M15, Public)

      D7.6 The Open Research Data Pilot: Personal Data and PSI Rules (M24, Public)

  • (WP short description)

    CONTACT: (name, email)

    • Task 8.1: OpenAIRE data model maintenance

      The OpenAIRE information space data model will be adapted to support the new back-end, front-end and knowledge extraction services. The changes will be collected and applied overtime as a consequence of the design and development of the services, and will be tracked on an ongoing deliverable, open to the public. Envisaged changes will regard: (a) the integration of publication licenses (ROMEO services), (b) description and interlinking with software entities, (c) modeling of annotations (Open Annotation Model), (d) features of data pilot plans associated to projects, (e) alignment of multiple author identifier schemes (e.g. ORCID, GoogleScholarID), (f) alignment with updates in new releases of the CERIF data model,and many more. CNR will be responsible for the collection of data model update requests, check for their applicability, and, when accepted, communicate the impact of such changes to other services.


      Task 8.2: LOD SERVICES

      As a result of this task OpenAIRE will increase its technical interoperability, engage with additional user communities and explore synergies with and added value to related open content initiatives (e.g. in the Open Educational Resources). The Services will be deployed by UBONN/ARC in order to map all metadata objects in the OpenAIRE Information Space onto suitable standard vocabularies (e.g. Dublin Core, SIOC, EDM, CERIF LD) and made available as Linked Open Data as data dumps being published in regular intervals with more frequently published incremental updates. UBONN with ARC will (a) operate the interlinking between OpenAIRE LOD objects with other Linked Data resources such as DBLP, ACM, Citeseer DBpedia, and (b) liaise with all relevant communities (PSI, DBpedia, LOD, W3C SWEO etc.) to leverage and outreach to additional stakeholders and multipliers. CNR will provide technical support for synchronizing content of the OpenAIRE Information Space with LOD services and vice versa, in the case content can be moved from enriched LOD representation to the OpenAIRE Information Space.



      The task will focus on the realization of general-purpose services for measurement of research impact w.r.t. a “research initiative”. Such services will identify relationships between publications/datasets and a given “research initiative” (e.g. research infrastructures) by offering: (i) inference by mining functionality and (ii) end-user claim functionality (i.e. endusers declare links). Services will also offer UIs for visualizing statistics and measuring research impact over time. As a use-case, the task will focus on the development of pilots with selected National funding agencies (e.g. NWO, DFG, NCBR) and infrastructure initiatives (e.g. EGI, PRACE) in order to serve them with the OpenAIRE research impact suit of services. ARC and CNR will: (a) select funding agencies with the help of the NOADs, (b) offer technical support for interoperability with funding agencies data sources in order to collect project information from them, and (c) identify the data model changes required to support the integration.


      TASK 8.4: Data flows and dynamics monitoring services

      These services will be used to monitor overtime all data flows in the OpenAIRE infrastructure, in order to verify the expected quality of a newer version of the Information Space before making it available to the public via portal and APIs. To this aim, the services will evaluate and certificate data flows and dynamics over time, since the last Information Space was released. Examples of Information Space certification elements may regard “Expected Information Space variance”: e.g. the percentage of OA vs non-OA material should not exceed a given ratio; the number of inferred relationships can increase but should not have down-peaks of 10% with respect to previous status; different harvestings of the same data sources should increase in the number of collected objects. Data curators will be able to: (a) configure the services to verify specific data flows and dynamics w.r.t. given measures and thresholds, (b) be consequently notified of misbehaviors or technical issues in order to fix them or, if tolerable, publish the Information Space as is; (c) have access to an history of “status certificates” of current and past Information Spaces. Data curators will also be able to configure and follow the overall monitoring activities via user interfaces, which will offer a graphical representation of the activities. CNR will be in charge of the design and development of the service, while UNIBI will serve the requirements of data curators.



      This task has the twofold aim of: (a) Aligning policies and standards: allowing data sources used for research dissemination (e.g. publication and data repositories, CRIS systems) to align their policies and share standards for gathering and sharing usage data and stats, (b) Collecting and analyzingusage data to produce metrics: realizing OpenAIRE infrastructure workflows and services to aggregate usage data and stats from heterogeneous data sources, investigate usage data metrics, and integrate usage statistics in the OpenAIRE portal. Studies include: guidelines for exporting usage data and stats (ARC, UMINHO, Jisc); legal frameworks for usage data sharing (Jisc, UMINHO); examining aggregated usage data in the light of established metrics (e.g., citation analysis); study and integrate alternative types of usage data related to researcher social behavior (altmetrics). Developments include: tools for repository platforms (e.g. DSpace) to export/import usage data (UMINHO); large-scale analytics infrastructural services to process the aggregated data (ARC, UNIBI); APIs (ARC, UNIBI) so that different providers can study, pilot and produce different types of metrics.

    • D8.1 OpenAIRE data model (M6, Public)

      D8.2 LOD Services (M8, Public)

      D8.3 Research impact services (M10, Public)

      D8.4 Data flows and dynamics monitoring services (M11, Public)

      D8.5 Usage statistics services (M24, Public)

  • (WP short description)

    LEADER: Athena Research and Innovation Centre
    CONTACT: (name, email)

    • Task 9.1: OpenAIRE Portal and sErvices

      The OpenAIRE portal will be enriched with a number of services that will allow better utilization of the underlying (harvested, cleaned, inferred, interlinked) information space. These services will enhance the existing multi-faceted and dynamic access (search and browse) to support queries on the new extensions of the data model (software, publisher/ journal info, metrics) and the new knowledge inferred from WP10. It will improve the depositing and claiming processes with links to new infrastructures (e.g., PSI) and registries. It will provide recommendations based on similar documents and usage data. It will integrate authentication and authorization mechanisms to serve the end user researchers (ORCID, LinkedIn) and link to the European AAI infrastructure (EduGain). It will consolidate and enhance the end user alert and notification services to adapt on specific H2020 programmes and needs. Based on the Annotation Service developed in the OpenAIREplus it will create personal spaces with the “MyProjects” functionality.


      Task 9.2: Statistics, reporting and visualization services

      This task will enhance the tool that allows privileged users to design and deliver on-demand statistics and reports. The service will be expanded to incorporate new data types from the extended data model and new graphic layouts. An advanced, interactive visualization service will be developed to showcase the results of the knowledge extraction processes in WP10, i.e., directed graphs of networks and structure (citations, authors) over topic, space and time.


      TASK 9.3 Catch-all data pilot Services: Zenodo

      This task will deliver data repository services that are capable of satisfying the needs of the Horizon2020 data pilot, through provision of Zenodo. Any researcher without an appropriate community data repository can therefore rely on the Zenodo service to share and preserve any data from the EU funded programmes. This task will extend the Zenodo current service to support the broad range of data publishing initiatives in OpenAIRE2020 making it an appropriate testbed for communities to try out these concepts. This includes data linking, data citation, and anonymized data, and the closely related services for software description and preservation. An important aspect of the service to be developed is the establishment of connections with other data repositories for data export and exchange. In addition, the current service will be extended to align with emerging norms for uniquely identifying researchers, funders and other relevant entities.


      TASK 9.4: Open Access publication broker Service
      This task will design and develop an Open Access Publications Broker Service, which will notify interested (subscribed) repositories and CRIS systems of publication metadata information available in OpenAIRE. This information may range from (i) Open Access status: e.g., full open access, embargo date, etc., (ii) Inferred information: e.g., project funding, data and publication citations and similarities, download statistics, impact measures, etc. and (iii) Standard bibliographic fields: e.g., persistent identifiers (e.g. DOIs), publication type, link to files. The service will be designed and developedby CNR, with the technical support of ARC and the input from JISC, UNIBI, MINHO, and COUPERIN. It will identify metadata records of publications that are (potentially) of interest to subscribed repositories and CRIS systems and send the records to the repository and CRIS managers who will then be able to (i) complete their metadata records with information they have not collected from their users, or (ii) collect metadata records they are still missing. A range of subscription/notification strategies will be followed so as to provide a flexible and efficient service, while a Dashboard application will be designed and developed for monitoring the results. This effort will be aligned with the UK Repository Junction Broker and the US-SHARE Notification service initiative.



      TASK 9.5: OpenAIRE 3rd-party applications

      The OpenAIRE infrastructure opens up its content and services via several APIs in order to foster and facilitate the realization of applications by third-party service providers and/or young innovators. This task will offer the logistics and technical support required to develop such applications with special focus on innovative ideas improving the uptake of the OpenAIRE infrastructure or the cause of Open Access. Such applications may cover a wide range of aspects, such as linking OpenAIRE content to external content, researcher social networks, mobile applications. This process will be favoured by two tendersand three hackatons on specific “application areas”, to be defined by ARC, CNR and ARC. These partners will form a committee in charge of defining the rules, advertising, and evaluating the results of such competitions. The OpenAIRE portal will be enriched with a static page, pointing to all applications using the OpenAIRE APIs.


      TASK 9.6: Data Anonymization Services

      This task will develop two services to be publicly available to research communities and assist them in the Open Research Data Pilot: (i) an anonymization service for microdata that will allow scientists who wish to publish their data to do so without endangering the anonymity of the data sources, and (ii) a safety mechanism that will detect multiple publications of the same dataset and will prevent publishers from sharing the dataset using inconsistent privacy guarantees.

      CONTACT: (name, email)
    • D9.1 OpenAIRE portal services (M9, Public)

      D9.2 Statistics, reporting and visualization services (M9, Public)

      D9.3 Zenodo services (M9, Public)

      D9.4 OA Repository Broker Services (M12, Public)

      D9.5 Tender and hackatons (M14, Public)

      D9.6 Anonymization services (M18, Public)

      D9.7 Innovative Services report (M40, Public)

  • (WP short description)

    LEADER: ICM (University of Warsaw)
    CONTACT: (name, email)

    • Task 10.1: IIS workflow management

      This task further enhances the Information Inference Service (IIS) initially developed in OpenAIREplus, a flexible framework for large-scale information processing. It will integrate enhanced resource management tools for efficient workflow execution and provide support for so-called “training workflows” for automated, periodic calibration of machine learning algorithms. It will develop a visual workflow editor for the administration of the IIS components. It will accommodate changes and enhancements of the OpenAIRE data model in WP8, and will improve the result feedback processes to the production system.


      Task 10.2: Classification and clustering

      The existing supervised classification and visualization modules, trained on a wide range of categorizations, will be modified and applied on large datasets of publications, taking into consideration the temporal process of the contentanalytics results. The unsupervised mechanisms (topic modelling) will be integrated in the IIS and will be enhanced for spatiotemporal modelling for trend analysis over the years, or among different countries; semi supervised analysis based on topic modelling will analyze incorporating labelled and structured information in topic modelling (e.g., pdb codes, MeshTerms, ACM classification etc.). Cross-language techniques will be introduced and applied on the above
      mechanisms publications in regional repositories and OA journals.

      CONTACT: (name, email)

      TASK 10.3: Entity resolution and linking

      This task will develop state-of-the-art methods for extracting information from individual publications. It will include further calibration of existing metadata extraction tools (CERMINE) and will extend them with capabilities, for authororganization affiliation parsing. It will include: domain-specific concept mining (gene symbols, chemicals, organisms), citation sentiment analysis using the CiTO ontology for the next generation of metrics, and rudimentary narrative pattern analysis (structure of a document, e.g. for classification purposes). Enhancement to introduce linking publications with software and data repositories (BioMedBridges, GitHub, Zenodo, PSI datasets). This task will also develop vocabularies and ontologies for representing information extracted in those tasks in semantic formats. Results of this task will allow to share and distribute information about scholarly communication maintaining high level of interoperability with existing and projected systems.


      TASK 10.4: Scholarly communication network analysis
      Based on the information extracted on T10.2 and T10.3 (citations and classification/clustering) this task will focus on the creation of a comprehensive map of relations in the academia between people (e.g., open citation index, co-authorship network), institutions, publications, funding sources, topics, data sets, software, etc. It will create knowledge networks based on discipline, time, location to identify structuring effects on specific research areas (e.g., health:diabetes), lasting effects of networks, creation of scientific societies or structures. It will employ advanced graph mining algorithms (e.g., PageRank) to provide deeper insight to the analysis. For known author-organization affiliations, the publication topic-author network will be further mapped to the European member states and map the organization involvement and interconnection. These tools will be used by experts in specific research fields to analyse and evaluate scientific quality and assess the long-term impact.

    • D10.1 Visual workflow editor (M10, Public)

      D10.2 Clustering algorithms (M18, Public)

      D10.3 Entity resolution algorithms (M18, Public)

      D10.4 Training workflows (M30, Public)

      D10.5 Map of academic relations (M40, Public)