e-VRE provides a comfortable homogeneous interface for users by virtualising access to the heterogeneous datasets, software services, resources of the e-RIs and also provides collaboration/communication facilities for users to improve research communication.  Finally it provides access to research management /administrative facilities so that the end-user has a complete research environment.

eVRE technical architecture

An approach based on Microservices has been chosen. As a result, the building blocks of the Technical Architecture are autonomous services cooperating with each other to implement the functional areas.

e-VRE software

The source code is available on GitHub. It can be downloaded and re-used according to Apache V2 license. Building blocks technical design is described in Deliverable 3.5, the installation manual is reported in the appendix of this deliverable.

Read more

Demonstrators

Demonstrators show the possible integration of the e-VRE system in an external application. The proposed Use Case is to use the e-VRE-Taverna plugin that shows how Taverna can use the e-VRE functionalities to enable users to create workflows (using resources from EPOS (European Plate Observing System), as an example). The demonstrators source code is available on GitHub.

Read more

Common Reference Prototype

The Common Reference Prototype (CRP) is an implementation of the e-VRE Architecture, it is used by demonstrators and Metadata portals. It is available at http://v4e-lab.isti.cnr.it:8080

Read more

Metadata Portal

The Metadata Portal is the platform that facilitates the exploration, discovery and management of VRE4EIC catalogue. Available at http://v4e-hub.isti.cnr.it:8099/#!/login

Read more

Mapping Memory Manager - 3M

The VRE4EIC Mapping Memory Manager - 3M is a web application suite containing several software sub-components and exploiting several external services. Its main functionality is to assist users during the mapping definition process, using a human-friendly user interface and a set of sub-components that either suggest or validate the user input. The deployment of the VRE4EIC 3M instance contains all the mappings done during the VRE4EIC project.

Read more

Documentation

The detailed specification of the interfaces of the components can be found in VRE4EIC D3.1 Architecture design 2016

The description of the Building Blocks is available in VRE4EIC D3.3

The source code is released under the Apache License, Version 2.0 [ALv2]

e-VRE stands for enhanced Virtual Research Environment (VRE) and proposes a reference architecture structured along three logical tiers:

• The Application tier: functions to manage and expand the system.
• The Interoperability tier: functions to discover and use resources, to publish functionalities and enable applications to interact with each other.
• The Resource Access tier: functions to enable e-VRE components to interact with resources.

eVRE Key features

• Rich use-case and requirement collection and analysis from existing RIs and VREs
• Domain independent, 3-tier Reference Architecture for new VREs and an evolutionary target for existing VREs
• Micro-service based Technical Architecture for easy adoption of specific components
• Scalability and cross-RI interoperability by Design
• Trust, Security and Privacy aware
• Rich RI-Resource data model for widest adoption with matching from the main used standards of metadata models
• Existing VREs enhancement show case
• Open source

The origin of eVRE

The e-VRE platform has been designed and developed by a consortium of 8 members within the Horizon 2020 Research and Innovation action VRE4EIC, under the leadership of ERCIM

Read more about the Software (eVRE technical architecture, Canonical Reference Prototype, GUI Design)