Search

This deliverable D13.3 - "Software Release Final Activity Report - JRA2" documents the software packages produced by the project to implement the functionalities of the ARIADNEplus infrastructure, accessible from https://ariadne.d4science.org. These open- source software releases followed the procedures described in D13.1 Software Release Procedures and Tools - JRA2 governing the release of software, methods, and tools for the ARIADNEplus infrastructure. D13.3 reports on (i) the ARIADNE VRE software releases, where a total of 29 different release cycles were performed during the project period. Each release contained EUPL licensed software, whose source is accessible on the Code Versioning System (CVS) platform publicly available online at https://code-repo.d4science.org/gCubeCI/gCubeReleases, and reports on (ii) the ARIADNE Portal software releases whose source is accessible on the Code Versioning System (CVS) platform publicly available online https://github.com/ARIADNE- Infrastructure/portal. These activities have been carried out in the context of Task 13.4 Software integration and release (JRA2.4) as part of Work Package 13 (WP13). This task managed the process of software maintenance, enhancement, and provisioning in JRA work packages. Thus, it i) defines the release and provisioning procedures; ii) establishes the release plan; iii) coordinates the release process; iv) operates the tools required to support the release and provisioning activities; v) validates the software documentation; vi) takes care of the distribution of the software and its provisioning. This task benefits from the practices established and experience gained within the D4Science infrastructure.

This deliverable D2.8 describes third and final release of the Blue-Cloud architecture as it is at Month 33 (June 2022) and it is and an update of the earlier 2nd release of the Blue-Cloud architecture document D2.7. Given the agreed extension allowed to the Blue-Cloud project until March 2023, there might be some further refinements to the architecture in the upcoming 9 months to allow to optimise some of its services to better respond to user needs. In order to make it easier for readers and reviewers, a table is included as part of Chapter 1, which indicates the elements and sections of this Deliverable 2.8, which have been updated or added in comparison with the earlier Deliverable 2.7. In this report, the current architecture and functionalities of each of the following components, part of the Blue-Cloud technical framework, are described in detail as well as the roles of partners that are developing and hosting modules: 1) the Blue-Cloud Data Discovery and Access service to serve federated discovery and access to blue data infrastructures; 2) the Blue-Cloud Virtual Research Environment (VRE) to provide a Blue-Cloud VRE as a federation of computing platforms and analytical services. The Blue-Cloud Data Discovery and Access service architecture is based upon a combination of the DAB metadata broker service of CNR-IIA, and the SeaDataNet CDI service modules as developed by MARIS, IFREMER, and EUDAT in the framework of the EU SeaDataCloud project. For the Blue-Cloud Data Discovery and Access service and its modules, additional developments were implemented in the period May 2021 - June 2022 such as adapting and upgrading existing services, adding new services, testing modules, integrating modules, and testing the integrated service, in order to achieve the planned functionality. The Blue-Cloud VRE is largely based upon the D4Science e-infrastructure as earlier developed and managed by CNR-ISTI [1]. This e-infrastructure hosted, already from the start, multiple Virtual Labs and offered a variety of services. These services have been adopted and adapted for Blue-Cloud, new services have been added and several original services have been upgraded. Moreover, new Virtual Labs have been constructed and deployed as part of the Blue-Cloud Demonstrators. The D4Science e- infrastructure also already included proven solutions for connecting to external computing platforms and means for orchestrating distributed services, which are instrumental for smart connections to the other e-infrastructures in the Blue-Cloud system, while further evolutions have taken place as part of the Blue-Cloud project, in response to the needs of the Virtual Labs and their users. With respect to the Virtual Labs, they are developed as real-life demonstrators embedded in the D4Science VRE and supported by data input from the Blue-Cloud Data Discovery and Access service, other data resources and additional computing services. They have been worked out in cooperation between WP3 and WP4 which have analysed their scientific workflows and identified the best technical set-up considering the D4Science VRE infrastructure and services. As part of their development, the demonstrators required upgrading of existing functionality and development of additional services. This is described, where relevant, in this document. In addition, consideration is given to integration aspects, such as two-way linking between the Blue- Cloud components, expanding the VRE with additional platforms for computing and algorithms, and direct access to data infrastructures where needed for specific Virtual Labs. Moreover, aspects of authentication and monitoring are considered on a full Blue-Cloud scale. The Blue-Cloud architecture as described in this report, is designed to be scalable and sustainable for near-future expansions, such as connecting additional blue data infrastructures, implementing more and advanced blue analytical services, configuring more dedicated Virtual Labs, and targeting more (groups of) users.

This document describes the Transparent Assessment Framework (TAF) VRE, the operational training environment available for registered users to use online TAF workflows and e-learning course-ware, and includes the usage reports of the latest two events. The training environment comprises a set of generic cloud services for communication, sharing and storage of information composing the e-learning course-ware, and a set of analytics services for online TAF workflows creation, publishing and execution on the computing resources maintained and operated by the D4Science Infrastructure.

The deliverable D1.3 MOVING Community of Practice (CoP) design and implementation report elaborates on the design and implementation of the MOVING CoP, with the aim of assessing its realisation and development during years 1 and 2. D1.3 has four specific objectives: o Analyse the performance and engagement of the Multi-Actor Platforms (MAPs) (regional and EU MAPs) in years 1 and year 2 towards achieving the MOVING and CoP objectives; o Identify issues in the implementation of the work plan; o Learn from the results achieved; o Propose recommendations, identify areas for improvements, and design actions and follow-up steps to be taken by the project to improve the implementation of the CoP (regional and EU MAPs). D1.3 may lead to an improved and more focused CoP work plan for the next two years including new proposals for actions. It will also lead to an improved Monitoring and Evaluation (M&E) tool for MAPs. This deliverable has been developed using a combination of methods for the analysis of the CoP as a whole (23 regional MAPs, 1 EU MAP and the involvement of external actors). The methodology includes: (i) the analysis of the performance and engagement of the regional MAPs using the M&E tool for regional MAPs; (ii) analysis of the performance and engagement of the EU MAP; (iii) analysis of the dedicated Virtual Research Environment (VRE) Labs and (iv) analysis of CoP results achieved and indicators included in the work plan. To complement this analysis, two surveys were conducted: (1) in August 2021 addressed to project partners related to the EU MAP - Ideas and expectations and (2) during May and June 2022 addressed to project partners and EU MAP members (external stakeholders) on the MOVING CoP - Ideas and expectations. Section 3 of the deliverable presents the MOVING CoP and its objectives. Section 4 provides detailed information on Regional MAPs and section 5 on the EU MAP. These sections explain their composition, their performance and engagement (including, among other aspects, an analysis of barriers and challenges as well as strengths and opportunities) and the results of the monitoring of these MAPs. In addition, section 5 presents the thematic areas and topics to focus upcoming EU MAP activities as well as the relevant knowledge, initiative, projects or experience to be shared among the members of the EU MAP. Finally, section 6 compiles the main results of the CoP that respond to the indicators included in the DoA for the expected project impacts. It includes the progress up to M22 (June 2022).

The SDG 14.4.1 e-training environment enables the conduct of training workshops with hands-on interactive facilities to learn how to use stock assessment data limited methods/algorithms. The operational training environment is also continuously available for trainees using the on-line SDG14.4.1 ·e-learning course. During the workshops requested by FAO, as per requirements described in the SLA, a maximum of 25 participants each by providing the necessary online resources and immediate technical support from at least one week before the start until one week after a workshop. This document reports on usage and consumption of resources. It encompasses usage both during workshops, between and after workshops. The document is accompanied by a Dashboard that can be used to analyse the exploitation of the VRE from its inception to the day before the access date.

Virtual Research Environments (VREs) are "systems" specifically conceived to provide their users with a web-based set of facilities (including services, data and computational facilities) to accomplish a set of tasks by dynamically relying on the underlying infrastructure. VREs are among the key products developed and delivered by the ARIADNEplus project to support the target communities and application scenarios in archaeology. The development of VREs is based on three main activities: (i) the development of software artifacts that realise a set of functions (including those needed for accessing certain datasets), (ii) the deployment of these artifacts in an operational infrastructure following the release procedures and tools presented in the deliverable D13.1 "Software Release Procedures and Tools JRA2", and (iii) the final deployment and operation of well-defined Virtual Research Environments by exploiting the facilities offered by the underlying D4Science infrastructure and its services [1]. This deliverable D13.4 - "VREs Operation Final Activity Report'' is the updated version of D13.2 - "VREs Operation Mid-term Activity Report ''. D13.4 documents the last of the above- mentioned three activities - i.e. the exploitation of the services and technologies offered by the underlying infrastructure to serve the needs of defined scenarios - as implemented in the second period, from January 2021 to November 2022 - of the ARIADNEplus project. Specifically, it focuses on how the components have been exploited and operated to support the development of the ARIADNEplus VRE gateway https://ariadne.d4science.org, its underlying infrastructure, and the VREs from M25 (January 2021) to M47 (November 2022). These activities have been carried out within Work Package 13. Specifically in Task 13.1 Infrastructure Operation (JRA2.1) and Task 13.3 VREs Operation (JRA2.3). In addition to the 5 VREs created and operated in the first period, 3 more VREs were created and operated in the second reporting period, for a total of 8 VREs. One VRE of the second reporting period, namely ARIADNEplus Lab (cf. Section 4.6), was created in July 2021 as the virtual laboratory to support developers, researchers, data managers, and data analysts belonging to the archaeological community worldwide. The "Geoportale Nazionale per l'Archeologia (GNA)" VRE (cf. Section 4.7) was created in January 2022, as the evolution of the existing Geoportal Prototype VRE (cf. Section 4.4), which was developed for the integration, validation, harmonization, visualization, and access of archaeological georeferenced datasets collected in Italy. Finally, the Esquiline VRE (cf. Section 4.8) was created in October 2022 for the integration and display of data originating from 19th century excavations and historical cartography in a spatio-temporal database, allowing the reconstruction of the transformation of an urban landscape through the centuries. As of November 2022, the VREs are serving the needs of more than 400 users in total spread across 21 countries and more than 10.000 user sessions. This required to deal with approximately 100 tickets (59 requests for support, 9 requests for incidents and bugs, 9 requests for Virtual Machine or Container creations).

This document describes the Transparent Assessment Framework (TAF) VRE, the operational training environment available for registered users to use online TAF workflows and e-learning course-ware. The training environment comprises a set of generic cloud services for communication, sharing and storage of information composing the e-learning course-ware, and a set of analytics services for online TAF workflows creation, publishing and execution on the computing resources maintained and operated by the D4Science Infrastructure.

This deliverable describes the activities carried out within Work Package 15 (WP15) of the ARIADNEplus project by the different partners and describes the results achieved. The work package consists of several individual tasks and subtasks with the overall goal to develop and provide useful services to archaeologists. This means the work package is by nature heterogeneous with stand-alone tasks and services. Efforts have been made to facilitate collaboration between the individual tasks through joint work package meetings. This has resulted in new cross-task contacts being made, and some sharing of expertise to improve services has been done. A service design template aligning the ARIADNEplus services with the requirements from European Open Science Cloud (EOSC) has been created. In connection with this, the ARIADNEplus AO-CAT ontology has been adapted to the requirements from EOSC Resource Data Model (Task 15.1). The Visual Media Service (Task 15.2.1) has had a new format added, allowing for 2D visualisation of LIDAR data in DEM format. In addition, three other standards have been added: gITF, ThreeJS and IIIF, supporting various functionality in the service. The service has also been adapted to support integration with the ARIADNEplus infrastructure in D4Science. A visual wizard has been defined to guide Visual Media Service users to add hotspots to a 3D scene easily and quickly. This extension, initially implemented in 3DHOP will allow archaeologists to create interactive links from the digital 3D model to the related documentation without writing any source code (Task 15.2.2). Task 15.2.3 reworked the Online 3D Database System for Endangered architectural and archaeological Heritage in the south Eastern MEditerRAnea area (EpHEMERA). EpHEMERA is a service provided by the Cyprus Institute to visualize in 3D archaeological excavations, ancient buildings, and their related documentation. In EpHEMERA, it is possible to visualise, online and through standard web browsers, 3D architectural and archaeological models (classified according to a specific type of risk), query the database system and retrieve metadata attached to each digital object, and extract geometric and morphological information about the Cultural Heritage asset. The visualisation and annotation tool of the TSS project have been ported to the OpenLime library and integrated into the Visual Media Service (Task 15.2.1). An additional layer of SVG annotations have been developed and added to the service. The Annotation service have been used and improved in three different pilot projects. (Task 15.3.2) Various strands of work have been done improving services for text mining and Natural Language Processing (Task 15.4). One of these efforts has been building upon the outcomes of the preceding ARIADNE project. A set of archaeological Named Entity Recognition NLP pipelines were reconfigured and deployed for easier use on the General Architecture for Text Engineering (GATE) cloud. Another effort has been on extracting temporal archaeological information using two different parallel approaches, normalisation and named entity recognition. A Python development platform has been used to unify the various services. A Vocabulary Annotation Tool (Task 15.3.1) was developed using the same platform, as part of Task 15.4. The tool facilitates the locating and tagging of vocabulary terms within free text and outputs suggested subject annotations in a range of formats. The GeoPortal service (Task 15.5) is a new REST service designed to manage complex spatio-temporal documents defined by metadata profiles. It was released as a component of the gCube framework. A prototype using the service was deployed and operated to manage archaeological excavation projects (Task 15.7). Two services for querying the RDF AO-Cat metadata records aggregated by the ARIADNEplus Infrastructure was established (Task 15.6): a full-text index service and a SPARQL endpoint. The full- text index service is based on OpenSearch and supports the needed query functionality of the ARIADNEplus portal. The SPARQL endpoint allows performance of semantic queries on the RDF records within the ARIADNEplus data and knowledge cloud.

InfraScience is a research group of the National Research Council of Italy - Institute of Information Science and Technologies (CNR - ISTI) based in Pisa, Italy. This report documents the research activity performed by this group in 2021 to highlight the major results. In particular, the InfraScience group confronted with research challenges characterising Data Infrastructures, eScience, and Intelligent Systems. The group activity is pursued by closely connecting research and development and by promoting and supporting open science. In fact, the group is leading the development of two large scale infrastructures for Open Science, i.e. D4Science and OpenAIRE. During 2021 InfraScience members contributed to the publishing of 25 papers, to the research and development activities of 18 research projects (15 funded by EU), to the organization of conferences and training events, to several working groups and task forces.

This document describes the Transparent Assessment Framework (TAF) VRE, the operational training environment available for registered users to use online TAF workflows and e-learning course-ware, and includes the usage reports of the latest two events. The training environment comprises a set of generic cloud services for communication, sharing and storage of information composing the e-learning course-ware, and a set of analytics services for online TAF workflows creation, publishing and execution on the computing resources maintained and operated by the D4Science Infrastructure.

D4Science is an IT infrastructure specifically conceived to support the development and operation of Virtual Research Environments by the as-a-Service provisioning mode. This report documents the activities performed in 2022 to develop this infrastructure and support several projects and exploitations.

The deliverable D1.4 DECO Activity Report is conceived as a self-assessment exercise that has the ultimate purpose of identifying improvements in the activities and tasks, making them the most appropriate to the needs of the project, based on the experiences of the activities implemented so far. Focused on the development of the dissemination, exploitation, communication and outreach (DECO) strategy (hereinafter the "Strategy") (D1.1), the D1.4 has two specific objectives: o Analyse the performance of communication, dissemination and exploitation activities implemented by the project in years 1 and 2 towards achieving MOVING's objectives. o Draw lessons, identify areas of improvements, and design actions and follow-up steps to be taken by the project so as to improve the communication, dissemination and exploitation activities. D1.4 may lead to an Activity Report of the Strategy by assessing and reporting on all different channels, activities and products to maximise MOVING's impact. This deliverable has been produced using a combination of quantitative and qualitative methods project's partners, especially the Communication Task Force, was performed A total of 23 responses from 21 partners have been received. The survey results have been used to collect information to better understand: a) how partners are using the communication channels and products of the project; b) in which areas they would need further support; c) what challenges they find to communicate about the project; etc. To complement both the quantitative analysis and the survey, a workshop was held to provide a space for the MOVING Communication Task Force to discuss and collect ideas on how to improve communication and dissemination performance and impact. The main results of the workshop have been used to produce the content in sections 4.5.3 Key Exploitable Results (KER), 4.6 Lessons learned and recommendations and 4.7 Review of the contingency plan within the DECO Strategy. Section 4 of the deliverable on main communication activities and results, includes an overview of the status of the Key Performance Indicators (KPIs) outlined in the DECO Strategy. For some of them, a new and more ambitious target in M48 has been set, given the good progress achieved so far of the initial targets. Further in section 4, the deliverable analyses MOVING's communication channels, in particular the website, the Virtual Research Environment, the MOVING Community of Practice, the different social media accounts and the newsletter. Regarding MOVING's communication products, the following have been evaluated: the visual identity of the project, news and blogs, policy briefs, videos and other products (press releases, infographics, brochures, etc.). External channels for outreach have also been monitored. In particular, the focus has been on: (i) partners' communication and dissemination activities; (ii) link to other networks and projects; (iii) participation in third-party events; (iv) relation with press and media; and (v) publications and scientific journals. The deliverable has considered the communication training and guideline provided so far and how partners value them, and has identified further training needs of the partners to improve their participation in dissemination, exploitation, communication and outreach activities. In section 4.5, the Exploitation Plan is developed as follows: introduction to this plan, objectives and Key Exploitable Results (KERs). It includes a table linking KER with lead partner from each work package (owner of KER); the description of the KER (including type of result) and the exploitation route(s) or potential use (commercial/industrial, academic, societal, policy). Section 4.6 presents the lessons learned and recommendations drawn throughout the process of elaboration of this deliverable. Finally, section 4.7 reviews the contingency plan within the DECO Strategy. The deliverable includes three annexes: (i) detailed analysis of the survey results; (ii) categories used to classify MOVING's social media posts; and (iii) resources on communication evaluation used to inform this deliverable.

This document describes the services exploited by the Open-ASFA Virtual Research Environment (OPEN-ASFA VRE) at final term. It reports metrics of usage, the status of the activities, including service upgrades, and a summary of the issues solved or to be solved, from November 1st 2021 to April 30th 2022.

N,N,N-trimethylanilinium salts are known to display dual reactivity through both the aryl group and the N-methyl groups. These salts have thus been widely applied in cross-coupling, aryl etherification, fluorine radiolabelling, phase-transfer catalysis, supramolecular recognition, polymer design, and (more recently) methylation. However, their application as electrophilic methylating reagents remains somewhat underexplored, and an understanding of their arylation versus methylation reactivities is lacking. This study presents a mechanistic degradation analysis of N,N,N-trimethylanilinium salts and highlights the implications for synthetic applications of this important class of salts. Kinetic degradation studies, in both solid state and solution phases, have delivered insights into the physical and chemical parameters affecting anilinium salt stability. 1H NMR kinetic analysis of salt degradation has evidenced thermal degradation to methyl iodide and the parent aniline, consistent with a closed-shell SN2-centred degradative pathway, and methyl iodide being the key reactive species in applied methylation procedures. Furthermore, the effect of halide and non-nucleophilic counterions on salt degradation has been investigated, along with deuterium isotope and solvent effects. Finally, new mechanistic insights have enabled the investigation of the use of trimethylanilinium salts in O-methylation and in improved cross-coupling strategies.

The SDG 14.4.1 e-training environment enables the conduct of training workshops with hands-on interactive facilities to learn how to use stock assessment data limited methods/algorithms. The operational training environment is also continuously available for trainees using the on-line SDG14.4.1 ·e-learning course. During the workshops requested by FAO, as per requirements described in the SLA, a maximum of 25 participants each by providing the necessary online resources and immediate technical support from at least one week before the start until one week after a workshop. This document reports on usage and consumption of resources. It encompasses usage both during workshops, between and after workshops. The document is accompanied by a Dashboard that can be used to analyse the exploitation of the VRE from its inception to the day before the access date.

This deliverable D2.7 describes the Blue Cloud architecture as it is known at Month 20. It is the second release of the architecture and an update of the earlier 1st release of the Blue-Cloud architecture document D2.6. It is expected that there will be further developments and refinements to the Blue Cloud system. For that purpose, one more release of the architecture document is planned, namely report D2.8 in Month 27. In order to make it easier for readers and reviewers, a table is included as part of Chapter 1, which indicates the elements and sections of this Deliverable 2.7, which have been updated or added in comparison with the earlier Deliverable 2.6. The technical framework of the pilot Blue-Cloud features: 1) the Blue Cloud Data Discovery and Access service component to serve federated discovery and access to blue data infrastructures 2) the Blue Cloud Virtual Research Environment (VRE) component to provide a Blue Cloud VRE as a federation of computing platforms and analytical services. In this report, the current architecture and functionalities of each of these components are described in detail as well as the roles of partners that are developing and hosting modules. The Blue Cloud Data Discovery and Access service architecture is based upon a combination of the DAB metadata broker service of CNR-IIA, and the SeaDataNet CDI service modules as developed by MARIS, IFREMER, and EUDAT in the framework of the EU SeaDataCloud project. For the Blue-Cloud Data Discovery and Access service and its modules, additional developments were needed such as adapting and upgrading of existing services, adding new services, testing modules, integrating modules, and testing the integrated service, in order to achieve the planned functionality. The Blue Cloud VRE is largely based upon the existing D4Science e-infrastructure as developed and managed by CNR-ISTI. This e-infrastructure from the start hosted already multiple Virtual Labs and offered a variety of services. These services have been adopted and adapted for the Blue Cloud and new services have been added, while also new Virtual Labs have been constructed and deployed as part of the Blue-Cloud Demonstrators. The D4Science e-infrastructure also already had proven solutions for connecting to external computing platforms and means for orchestrating distributed services, which are instrumental for smart connections to the other e-infrastructures in the Blue-Cloud system. The Blue Cloud demonstrators are developed as Virtual Labs embedded in the D4Science VRE e- infrastructure and supported by data input from the Blue Cloud Data Discovery and Access service and other data resources, and additional computing services. The demonstrators are worked out in a cooperation between WP3 and WP4, analysing their scientific workflows and technical set-up, and considering the D4Science VRE infrastructure and services that provide the basis platform. As part of their development, the demonstrators have required upgrading of existing functionality and development of additional services. This is described, where relevant, in this document. In addition, consideration is given to integration aspects, such as two-way linking between the 2 Blue Cloud components, and expanding the VRE with additional platforms for computing and algorithms, and where needed for specific demonstrators, direct access to data infrastructures. Moreover, aspects of authentication and monitoring are considered on full Blue Cloud scale. The Blue Cloud architecture as described in this report, is designed to be scalable and sustainable for near-future expansions, such as connecting additional blue data infrastructures, implementing more and advanced blue analytical services, configuring more dedicated Virtual Labs, and targeting more (groups of) users.

This deliverable D13.2 - "VREs Operation Mid-term Activity Report" describes the activities carried out during the first 24 months of the ARIADNEplus project within Work Package 13. Specifically, in Task 13.1 Infrastructure Operation (JRA2.1) and Task 13.3 VREs Operation (JRA2.3). It reports the procedures governing the operation of the VREs as well as the status of the aggregated resources at mid-term in the ARIADNEplus infrastructure.

The enhancements in IT solutions and the open science movement are injecting changes in the practices dealing with data collection, collation, processing and analytics, and publishing in all the domains, including agri-food. However, in implementing these changes one of the major issues faced by the agri-food researchers is the fragmentation of the “assets” to be exploited when performing research tasks, e.g. data of interest are heterogeneous and scattered across several repositories, the tools modellers rely on are diverse and often make use of limited computing capacity, the publishing practices are various and rarely aim at making available the “whole story” with datasets, processes, workflows. This paper presents the AGINFRA PLUS endeavour to overcome these limitations by providing researchers in three designated communities with Virtual Research Environments facilitating the use of the “assets” of interest and promote collaboration.

This deliverable describes the activities carried out during the first 18 months within Work Package 9 for the SoBigData e-Infrastructure operation activity since its deployment, including a detailed set of usage indicators (i.e. the number of users, accesses to resources, usage of resources from scientists, etc.). It also reports the deployment and procedures governing the operation of the Virtual Research Environments, the catalogue, and the ones for the services devoted to Data Analytics. A total of 15 Virtual Research Environments (VREs) have been created and are operational. In particular, the SoBigData gateway provide its users with: 6 Exploratories VREs paired with the use cases (Demography, Economy & Finance 2.0; Migration Studies; Societal Debates and Misinformation Analysis; Social Impacts of AI and Explainable Machine Learning; Sports Data Science; Sustainable Cities for Citizens); 2 Virtual Lab VREs - SoBigDataLab and OpenScienceGraphLab to exploit and experiment tools and solutions; 3 Applications VREs - TagME, SMAPH, M-Atlas; 2 Project Internal VREs - SoBigData.eu VRE for the communications and collaboration among project and initiative members and SBD-InfraCore VRE for supporting SoBigData-PlusPlus WP9; and 2 Literacy And Training VREs - the SoBigDataLiteracy, supporting Critical Data Literacy of task T.2.4, creating a curated collection of literature of interest for the SoBigData Community, and the e-Learning_Area VRE to host training materials developed within the SoBigData project. As of June '21, the 15 existing VREs served more than 8,000 users by a total of more than 30,000 working sessions, with an average of 1500 working sessions per month with increasing trend. This required to deal with approximately 40 issue tracker tickets (14 requests for support, 6 requests for incidents and bugs, 9 requests for new features, and 9 requests for Virtual Machine or Container creations).

The enhancements in IT solutions and the open science movement are injecting changes in the practices dealing with data collection, collation, processing, analytics, and publishing in all the domains, including agri-food. However, in implementing these changes one of the major issues faced by the agri-food researchers is the fragmentation of the “assets” to be exploited when performing research tasks, for example, data of interest are heterogeneous and scattered across several repositories, the tools modelers rely on are diverse and often make use of limited computing capacity, the publishing practices are various and rarely aim at making available the “whole story” including datasets, processes, and results. This paper presents the AGINFRA PLUS endeavor to overcome these limitations by providing researchers in three designated communities with Virtual Research Environments facilitating the use of the “assets” of interest and promote collaboration. © 2020 John Wiley & Sons Ltd

This deliverable D5.2 "Virtual Research Environment Operation Report years 1-2" describes the activities carried out during the first 24 months of the DESIRA project within Work Package 5. Specifically in Task 5.1 "Knowledge Infrastructure: the DESIRA Virtual Research Environment" and Task 5.2 "Integration of Services and Tools, and Use Reporting". It reports the procedures governing the operation of the VREs as well as the status of the aggregated resources at mid-term in the DESIRA infrastructure. Virtual Research Environments (VREs) are "systems" specifically conceived to provide their users with a web-based set of facilities (including services, data and computational facilities) to accomplish a set of tasks by dynamically relying on the underlying infrastructure. VREs are among the key products to be developed and delivered by the DESIRA project to support Project coordination, Living Labs activities and Rural Digitization Forums activities. The development of VREs is based on three main activities: (i) the development of software artefacts that realise a set of functions (including those needed for accessing specific datasets), (ii) the deployment of these artefacts in an operational infrastructure following the release procedures and tools, and (iii) the final deployment and operation of well-defined Virtual Research Environments by exploiting the facilities offered by the underlying D4Science infrastructure and its services [1, 2]. This report documents the last of the above three activities - i.e. the exploitation of the services and technologies offered by the underlying infrastructure to serve the needs of defined scenarios - as implemented in the context of the DESIRA project from June 2019 to May 2021. The DESIRA Infrastructure Gateway actually offers end-user access to 14 VREs. As of June 2019, 1 VREs were created and operated. Specifically, the DESIRA Project VRE (cf. Sec 3.1.1) was created before the project kick-off. As of May 2021, these VREs have served the needs of more than 370 users and more than 7.000 user sessions. This required dealing with 177 tickets (103 related to the project management, 28 requests for support and enhancements, five requests for incidents and bugs, 14 requests for VRE creations).

The Blue-Cloud project is piloting a cyber platform bringing together and providing access to multidisciplinary data from observations and models, analytical tools, and computing facilities essential to support research to understand better and manage the many aspects of ocean sustainability. This goal is realised by developing, deploying and operating the Blue-Cloud platform whose architecture consists of two major families of components: (a) the Blue Cloud Data Discovery and Access System to serve federated discovery and access to 'blue data' infrastructures; and (b) the Blue Cloud Virtual Research Environment (VRE) component to provide a Blue Cloud VRE as a federation of computing platforms and analytical services. This Deliverable D4.4 "Blue Cloud VRE Common Facilities (Release 2)" is the revised version of the D4.2 "Blue Cloud VRE Common Facilities (Release 1)". This revised version of the document covers the second period of the project, from M13 up to M27, including the up-to-date information of the services reported on D4.2 and the new services that have been developed and added to the VRE common facilities in the reporting period to serve the needs of the Blue Cloud community. The major changes and new services this deliverable introduces are: an Orchestrator (cf. Sec. 3.3), i.e. a software that allows for a declarative, technology agnostic definition of workflows to coordinate the execution of tasks across diverse services and systems; enhancements to the Workspace service to support tailored storage persistence and satisfy different application scenarios (cf. Sec. 4.1); enhancements in the Publishing Framework (cf. Sec. 6), namely the catalogue extension to deposit catalogue items to Zenodo and the facility to publish geospatial data from the workspace; the facility to interface with the Data Discovery & Access System (cf. Sec. 7.1) to transfer datasets of interest into the workspace for future uses; the notebook to facilitate the exploitation of the WEkEO Harmonised Data Access (HDA) API (cf. Sec. 7.2). This deliverable also updates the Identity and Access Management (cf. Sec. 3.1) and the Analytics Framework (cf. Sec. 5.1 and Sec 5.2) with minor changes reflecting the activities performed in the reporting period. A description of all the services previously documented in D4.2, not modified in the period, is preserved for this document to be self-contained and provide the reader with an overall description of the whole VRE Common Facilities offering. A total of 15 services and components are described in this deliverable by reporting their design principles, architecture and main features. These services and components contribute functionalities to the Blue Cloud VRE Enabling Framework (Identity and Access Management, VRE Management, Orchestrator), Collaborative framework (Workspace and Social Networking), Analytics Framework (Software and Algorithm Importer, Smart Executor), Publishing Framework (Catalogue Service) and improved support for RStudio, JupyterHub, ShinyProxy, and Docker Applications. Additionally, two new VRE services, aiming at bridging two VRE external systems such as the the WEkEO1 catalogue from Copernicus and the Data Discovery and Access from Blue-Cloud with the VRE tools are described. Services and components discussed in this deliverable have contributed to 14 gCube releases, from gCube 4.26 (November 2020) to gCube 5.6.0 (November 2021). They have been used to develop and operate the Virtual Laboratories of the Blue Cloud gateway https://blue-cloud.d4science.org and its underlying infrastructure. At the time of this deliverable the Blue-Cloud gateway and its services are serving more than 730 users with a total of 19000+ working sessions.

InfraScience is a research group of the National Research Council of Italy - Institute of Information Science and Technologies (CNR - ISTI) based in Pisa, Italy. This report documents the research activity performed by this group in 2020 to highlight the major results. In particular, the InfraScience group confronted with research challenges characterising Data Infrastructures, e\-Sci\-ence, and Intelligent Systems. The group activity is pursued by closely connecting research and development and by promoting and supporting open science. In fact, the group is leading the development of two large scale infrastructures for Open Science, \ie D4Science and OpenAIRE. During 2020 InfraScience members contributed to the publishing of 30 papers, to the research and development activities of 12 research projects (11 funded by EU), to the organization of conferences and training events, to several working groups and task forces.

Nel contesto del progetto di ricerca denominato "SerGenCovid-19 (Serum Genetic Covid-19 study) Indagine sierologica e genetica sull'immunità e la suscettibilità all'infezione da SARS-CoV-2 e creazione di una biobanca", l'ISTI `e coinvolto come responsabile nel Work Package 6: Progettazione e implementazione della piattaforma informatica per la gestione di "Raccolta, conservazione e consultazione dei dati sanitari relativi ai prelievi ematici". In questo rapporto di progetto viene descritta la prima fase del progetto dove vengono realizzate la parte di backend e le due piattaforme, una per il partecipante e una per l'operatore.

This document describes the services exploited by the Open-ASFA Virtual Research Environment (OPEN-ASFA VRE) at mid-term. It reports metrics of usage, the status of the activities, including service upgrades, and a summary of the issues solved or to be solved, from June 1st 2021 to October 31st 2021.

The DESIRA Virtual Research Environment provided by the D4Science Infras supporting computation and storage. The operations and management of those resources are performed via a set of enabling technologies while guaranteeing the reduction of costs of ownership and a set of ensuring secure monitoring, alerting and provisioning. The services layer is organized into layered software frameworks that increasingly hide the complexity of the cloud-based infrastructure.

This deliverable reports the design principles and software architectures characterising the release and development of the SoBigData e-Infrastructure common facilities, namely the social mining computational engine, the online coding and workflow design frameworks, and the online science monitoring dashboard. This report is the first of two versions of the document, each of which describing the design associated with a specific version of the infrastructure to be made available at M12 (December 2020) and at the end of the third year (SoBigData e-Infrastructure common facilities 2, December 2022). Specifically, the deliverable focuses on the design principles and reference architectures included in the first release of the SoBigData e-Infrastructure common facilities at M12. The deliverable consists of six sections. Section 1 briefly introduces the role of this deliverable for the development and delivery of the SoBigData e-Infrastructure common facilities. Section 2 describes the SoBigData e-infrastructure logical architecture contextualising the common facilities and how they relate with the rest. Section 3, section 4 and section 5 document the first release of the e-Infrastructure common facilities included in this report and available at M12, reporting the design principles and reference architectures of the released solutions. Specifically, section 3 describes the social mining computational engine, Section 4 presents the online coding and workflow design frameworks - which includes the RStudio and the Jupyter Notebooks via JupyterHub - and Section 5 reports the online science monitoring dashboard. Finally, section 6 concludes the report illustrating the whole Release Management process and its components for continuous integration.

This report documents the D4Science Virtual Research Environment released for the I-GENE Project. Two sections illustrate the activities performed and the characteristics of the I-GENE Virtual Research Environment. Section 2 is the introduction. Section 3, instead, describes the Infrastructure gateway, accessible via the URL https://i-gene.d4science.org/ expected to be the end-user entry point to the I-GENE services, and the I-GENE Project Virtual Research Environment (VRE) and its features, all of which are accessible via the above-described entry point. Section 4 describes the use of VRE for implementing the project scopes. The Science and Technology Institute (ISTI) of the CNR (National Research Council), a third party linked to UNIPI, is responsible for this activity.

The Blue-Cloud project plans to pilot a cyber platform bringing together and providing access to multidisciplinary data from observations and models, analytical tools, and computing facilities essential to support research to understand better and manage the many aspects of ocean sustainability. To achieve this goal, Blue-Cloud is developing, deploying, and operating the Blue-Cloud platform whose architecture consists of two families of components: (a) the Blue Cloud Data Discovery and Access service component to serve federated discovery and access to 'blue data' infrastructures; and (b) the Blue Cloud Virtual Research Environment (VRE) component to provide a Blue Cloud VRE as a federation of computing platforms and analytical services. This deliverable presents the Blue Cloud Virtual Research Environment constituents by focusing on both new services and revised existing services that have been developed in the reporting period to serve the needs of the Blue Cloud community. In particular, this deliverable describes a total of 11 services and components. These services and components contribute functionalities to the Blue Cloud VRE Enabling Framework (Identity and Access Management, VRE Management), Collaborative framework (Workspace and Social Networking), Analytics Framework (Software and Algorithm Importer, Smart Executor), Publishing Framework (Catalogue Service) and improved support for RStudio, JupyterHub, ShinyProxy, and Docker Applications. The services are described below by reporting their design principles, architectures, and main features. The deliverable also describes the procedures and approaches governing services and components released by highlighting how Gitea (as Git hosting service), Jenkins (as automation server), and Maven (as project management and comprehension tool) are used to guarantee continuous integration processes. Services and components discussed in this deliverable contribute to 11 gCube open-source software system releases (from gCube 4.16 up to gCube 4.25.1) and are in the pipeline for the next ones. They have been used to develop and operate the Virtual Laboratories of the Blue Cloud gateway https://blue-cloud.d4science.org and its underlying infrastructure. At the time of this deliverable (November 2020), the gateway hosts a total of 8 VREs and VLabs, including five specifically conceived to support the co-development of some of the Blue-Cloud demonstrators (namely, the Aquaculture Atlas Generation for Demonstrator #5, the Blue-Cloud Lab for several demonstrators, the GRSF pre for Demonstrator #4, the Marine Environmental Indicators for Demonstrator #3, the Zoo-Phytoplankton EOV for Demonstrator #1). This gateway and its tools serve more than 400 users that (since January 2020) performed a total of more than 5000 working sessions, more than 1700 accesses to the Workspace, and more than 750 analytics tasks. These exploitation and uptake indicators are likely to grow in the coming months thanks to data updates and continued use, further development of existing VLabs, and finally, the creation of new ones.

This document, jointly drafted with the FAO consultants, reports on the training sessions and results achieved during the first 2 months of the project, from September 1st to October 31st. We report the objective, the topics discussed and the technology presented for each of the training sessions that took place during the period. A section on the training results highlights the technology choices, the agreements reached, and the development work plan.

The objective of the EOSCpilot data interoperability task (6.2) is to demonstrate how to ensure availability of research data to services and users through an open cloud infrastructure. To do so, this task has produced a set of recommendations driving a coherent strategy, as well as a set of technical solutions to help users and programmatic services to find and access datasets across several disciplines, enabling the EOSC to be built around a more coordinated and aligned data ecosystem. The six recommendations driving our proposed strategy are: - The data guidelines and technical solutions proposed by the EOSC should be specific, common, simple, lightweight and collaborative. - All the data resources contributing to the EOSC should expose structured metadata. - The EOSC should reuse or build upon existing standards and formats, and promote the use of common best practices across scientific domains. - The EOSC should propose minimum information guidelines across scientific domains especially targeting key operational metadata which is important for services consuming data. - The EOSC should support an interconnected ecosystem of metadata catalogues as a fundamental service component to facilitate data discovery. - The EOSC should implement a monitoring service to validate standards and recommendations proposed by the EOSC. The four technical solutions that comprise the data strategy are: - A common minimum information metadata guideline for datasets in the EOSC. - Recommendations to establish a coordinated and interconnected ecosystem of dataset metadata catalogues. - Adoption of ResearchSchemas as a means to drive research data discoverability and accessibility. - A set of recommendations for common properties across multiple data types.

The DESIRA Virtual Research Environment specification consists of a hardware layer and a service layer. The former is made available by the D4Science Infrastructure 1 [1, 2] and it is organized as a dynamic pool of virtual machines, supporting computation and storage. The operations and management of those resources is performed via a set of enabling technologies selected to ensure availability and reliability of the infrastructure while e guaranteeing reduction of costs of ownership and a set of supporting technologies selected to ensure secure monitoring, alerting and provisioning. The service layer, illustrated in Figure 1, consists of three service frameworks, which can be summarized as a follows: o Enabling Framework: the enabling framework, framework , based on the gCube System [3], includes services required to support the operation of all services and the VREs supported by such services. As such it includes: a resource registry service, to which all e-infrastructure infrastructure resources (data sources, services, computational nodes, etc.) can be dynamically (de)registered and discovered by user and other services; Authentication and Authorization services, as well as Accounting Services, capable of both granting ing and tracking access and usage actions from users; and a VRE manager, capable of deploying in the collaborative framework VREs inclusive of a selected number of "applications", generally intended as sets of interacting services; o Storage Framework: the storage framework includes services for efficient, advanced, and on on-demand management of digital data, encoded as: files in a distributed file system, collection of metadata records, and time series in spatial databases; such services are used by all other services in the architecture, exception made for the enabling framework; o Collaborative framework : the collaborative framework includes all services deployed for the scientists and for each of them provides social networking services, user management services, shared workspace services. In addition, addition it comprises the part on the Web UI access to the Virtual Research Environment.

This deliverable D13.1 - "Software Release Procedures and Tools JRA2" describes the activities carried out during the first six months of the ARIADNEplus project within Task 13.4 (T13.4) Software integration and release (JRA2.4) (Work Package 13 - WP13) and describes the procedures governing the release of software, methods, and tools for the ARIADNEplus infrastructure. This task is in charge of managing the process of the software maintenance, enhancement, and provisioning in JRA work packages. Thus, it i) defines release and provisioning procedures; ii) establishes the release plan; iii) coordinates the release process; iv) operates the tools required to support the release and provisioning activities; v) validates the software documentation; vi) takes care of the distribution of the software and its provisioning. This task benefits from the practices established and experience gained within the D4Science infrastructure. The procedures are documented through a set of documentation pages for single facilities hosted by the gCube wiki. In particular, this report provides the instructions and rules for three main patterns governing the provision of software and tools to the ARIADNEplus infrastructure. The first pattern is related to the provision of software to the gCube infrastructure enabling technology. This pattern describes the procedures for the storage of software and its management; the continuous integration of the software to build releasable software artefacts; and the generation of software distribution packages. The second pattern is related to the provision of software methods elaborated by the ARIADNEplus community requiring execution within the ARIADNEplus infrastructure. The third pattern is instead related to the provisions and integration of tools into the ARIADNEplus infrastructure.

Deliverable D10.10 "Resource adaptation to register to the e-infrastructure 3" is the revised version of the Deliverable D10.9 "Resource adaptation to register to the e-infrastructure 2" and Deliverable D10.8 "Resource adaptation to register to the e-infrastructure 1" intended to report the experiences of partners from different infrastructures at integrating their services, methods, and applications as SoBigData resources. The first section describes the general integration patterns, while the second section reports the experiences from the individual partners, revealing the effort required, in terms of time and technical complexity, and earned benefits. This revised version of the document covers the whole period of the project, including the up to date information of the D10.9 deliverable and the new experiences of partners at integrating their services, methods, and applications as SoBigData resources, developed through the project's lifetime.

Virtual Research Environments and Virtual Laboratories are among the key products the BlueBRIDGE project is called to develop and to deliver to serve its target communities and application scenarios. The deployment and operation of a Virtual Research Environment is a task that involves the reuse of existing technologies as well as the development of new technologies aiming at offering new facilities. The development of the technology, both the generic as well as that which is oriented to serve the specific needs of a given community/target scenario, is captured by other deliverables. This report describes the activities performed to provide the BlueBRIDGE community with the set of Virtual Research Environments (VREs) and Virtual Laboratories (VLabs) hosted by the BlueBRIDGE portal during the entire duration of the project. A total of 66 VREs / VLabs have been deployed and operated, overall serving more than 3000 users across 32 countries and 124 different organizations. Such VREs / VLabs include "private" ones (66% circa), i.e. environments whose membership is by invitation only, "restricted" ones (15% circa), i.e. environments that users can request to join yet the requests have to be explicitly approved by the managers, and "open" ones (18% circa), i.e. environments that any user can request to join and no approval is needed. The 45% circa of the served users is exploiting "open" environments, the 34% circa is exploiting "private" environments, and the 19% circa is exploiting "restricted" environments. During the project, more than 980 requests for support, incident or bug have been resolved (441 requests for support and 546 requests for incidents and bugs).

Deliverable D10.9 "Resource adaptation to register to the e-infrastructure 2" is the revised version of the D10.8 deliverable "Resource adaptation to register to the e-infrastructure 1", intended to report the experiences of partners from different infrastructures at integrating their services, methods, and applications as SoBigData resources. The first section describes the general integration patterns, while the second section reports the experiences from the individual partners, revealing the effort required, in terms of time and technical complexity, and earned benefits. This revised version of the document covers the whole period of the project, including the up to date information of the D10.8 deliverable and the new experiences of partners at integrating their services, methods, and applications as SoBigData resources, developed through the project's lifetime.

Deliverable D9.2 - "BlueBRIDGE VRE Commons Facilities: Revised Version" is the revised version of the D9.1 deliverable, intended to report the release of the BlueBRIDGE facilities for Data Access, Data Discovery, Data Storage, Data Analytics and Data Publishing. It is conceived to include the latest developments and releases that took place between the 2 versions of the reports. The deliverable is of type "Other" and the following document is intended to provide its readers with an easy-to-use description of the actual components, services and systems contributing to form the BlueBRIDGE VRE Commons Facilities. This document is structured as follows: a description for each facility is available, in conjunction with links to the project's wiki, providing more detailed descriptions and additional information for each component. This revised version of the document aims at providing a complete picture of the available facilities for Accessing, Discovering, Storing Data, Analysing and Publishing Data developed through the project's lifetime. The deliverable is divided in two main sections. The first one follows the structure of Work Package 9; specifically, it documents the various releases and versions of the facilities available for Accessing, Discovering and Storing Data (T9.1), for Analysing Data (T9.2) and for Publishing Data (T9.3). The second section comprises facilities for managing and using VREs that span across all the three WP9 tasks. Specifically, it includes dedicated parts documenting the various releases and versions of services for defining, creating and deploying VREs (VRE Management facilities) together with a set of applications allowing to use the VRE through a thin client (VRE Enabling facilities). The deliverable provides, for each facility, a description, the documentation for developers and system administrators, how-to guides and usage instructions for different use cases and links to open source code and binaries. Further details and the complete documentation for the facilities are available on the gCube wiki at https://wiki.gcube-system.org/gcube/About_gCube. The intended readers of this deliverable are (a) the community in the large willing to be informed on the solutions BlueBRIDGE offers for VRE management, Data Access, Discovery, Storage, Analytics and Publishing, and (b) the gCube developer community to know how to integrate, use and build on top of the facilities described by the document.

l cancro di intervallo (CI) è un’entità patologica che viene descritta solo nell’ambito dei programmi di screening organizzato. Si intende per CI un carcinoma successivo ad un processo di screening negativo e comparso prima del passaggio di screening successivo. Qualsiasi sia la motivazione della loro genesi, i CI rappresentano un insuccesso del programma di screening che, in teoria, mira a diagnosticare tutti i carcinomi in fase di screening, e a non consentire la comparsa di CI. L’analisi dei CI (loro frequenza di comparsa nel tempo, caratteristiche morfologiche e cliniche, revisione della precedente mammografia di screening) è un momento fondamentale della valutazione di performance dello screening.Per questo motivo a 10 anni dall’attivazione del programma di Screening a Trieste, si è voluto confrontare i fattori prognostici dei carcinomi screening-detected (CSD) e dei (CI), alla luce dell’ampio dibattito in letteratura riguardo la maggior aggressività di questi ultimi.

The D6.3 Report on the implementation of the Joint Resource Registry documents the interim implementation of the Joint Resource Registry (JRR). It complements the D5.2 Report on the design of the Joint Resource Registry deliverable by providing details on how to interact with and exploit the functionalities it provides. The JRR hosts the PARTHENOS entities represented according to the PARTHENOS Entities Model defined in WP5. As such, it represents an information system for the PARTHENOS community and the PARTHENOS universe of tools and services designed for and released in the PARTHENOS infrastructure. This deliverable presents, in Section 2, the principles and guidelines that govern the implementation of the JRR which has been designed to support the persistence of the PARTHENOS Entities. The JRR is implemented as a tailored information system capable of satisfying the evolution of the model itself, the main features of which are described in section 3 since the facet based resource model is extensively referred to throughout this report. Entities, Resources, Facets and Relations are described in detail. Section 4 describes the set of technical components comprising the JRR and APIs, covering the architecture which includes the Resource Registry Service, Context Client, Schema Client, Publisher and Client. Section 5 provides information regarding how to interact with the Resource Registry Service by exploiting the Context and Schema Port Types. The REST APIs are also presented for each functionality. Section 6 covers the backend database, OrientDB, a Multi-Model Open Source NoSQL DBMS that brings together the power of graphs and the flexibility of documents into one scalable high-performance operational database. The final section provides information on the Studio GUI used by the Content Administrator for searching between the created types and inspection of their schema.

Gli indicatori relativi ai tempi di attesa sono difficili da rispettare, come recentemente evidenziato al XIII Convegno ONS 2015 . Per questo motivo è fondamentale identificare in quale momento della gestione dei carcinomi screening-detected si concentrino i ritardi e stabilirne le cause (se attribuibili alla paziente o all’organizzazione del programma o intrinseci al tipo di lesione) così da proporre mirate modifiche migliorative. Metodi: L’analisi riguarda 146 carcinomi screening-detected consecutivi (biennio 2013-2014). Sono stati misurati i tempi tra le varie fasi diagnostiche (Mammografia di I° livello, Richiamo II° livello, I° approfondimento cito/microistologico, Comunicazione diagnosi) e i tempi chirurgici (Visita chirurgica, Intervento chirurgico, Referto istologico con marcatori biologici, Visita oncologica). Per ogni fase sono stati calcolati i tempi medi/mediani rappresentati tramite box plot e giustificati gli outliers.Risultati: La latenza nella presa in carico chirurgica è legato alla complessità degli esami preoperatori (3) (tempo mediano tra richiamo al II° livello ed intervento: 53 giorni (se unico esame pre-operatorio) vs 73 (se più di un esame pre-operatorio, p

The role of breastfeeding as protective factor for breast cancer incidence is controversial among scientific literature. The Interdisciplinary Senology Unit of Trieste has analyzed the relation between breast cancer incidence and lactation habits among a total of 4307 Trieste’s women. In this study, the statistical analysis revealed that over having children, the breastfeeding is a further protective factor for breast cancer. In particular, the decrease of breast cancer risk by breastfeeding resulted to be significant for lactation more than 12 months. It is worth noting that breastfeeding resulted protective only for women in childbearing age and it didn’t result to decrease breast cancer risk among post-menopausal women.

Virtual Research Environments and Virtual Laboratories are among the key products the BlueBRIDGE project is called to develop and to deliver to serve its target communities and application scenarios. The deployment and operation of a Virtual Research Environment is a task that involves the reuse of existing technologies as well as the development of new technologies aiming at offering new facilities. The development of the technology, both the generic as well as that which is oriented to serve the specific needs of a given community/target scenario, is captured by other deliverables. This report describes the activities performed to provide the BlueBRIDGE community with the set of Virtual Research Environments (VREs) and Virtual Laboratories (VLabs) hosted by the BlueBRIDGE portal from September 2015 to November 2016. A total of 38 VREs VLabs have been deployed and operated, overall serving more than 1500 users across 22 countries. This requested to deal with approximately 600 tickets (32 tickets for VRE creationupdate, 244 requests for support, 315 requests for incidents and bugs).

This deliverable provides the list and pointers to the software packages produced by the project to implement the functionalities of the SoBigData infrastructure, accessible from http://sobigdata.d4science.org. Such functionalities have been described in Deliverable 10.2.

This report describes the gCube solutions implementing its Authentication, Authorization and Accounting Infrastructure. gCube is a software system enabling the realization and operation of hybrid data infrastructures capable of supporting the concept of Virtual Research Environments (VREs), i.e., collaborative, web-based working environments through which community of practice members are provided with the entire spectrum of resources (data, services, and computing facilities) needed to accomplish their research tasks in an effective and efficient manner.

Science is in continuous evolution and so are the approaches and methodologies scientists demand to apply by requesting for appropriate supporting environments. These environments offer new scientific investigation possibilities by exploiting recent technology advances. In this report, we present the D4Science IT infrastructure, developed to serve the needs of various communities of practice yet based on a technology which is domain agnostic, and the D4Science web-based working environment describing the social networking applications composing it. These applications are conceptually borrowed from social networks yet adapted to deal with the scientific data practices. They offer the possibility of effectively sharing "Big Data" or scientific products by exploiting a scalable and elastic access to tools and computing capabilities provided by D4Science. We discuss an approach for a Search Framework, to be used on top of these applications originated data, offering full-text search capabilities through the use of services compliant with the cloud paradigms. We describe the key features, the use cases and the architecture design, together with its implementation, of the Search Framework explaining in detail the software components characterising it.

Deliverable D9.1 - "BlueBRIDGE VRE Commons Facilities" reports the release of the BlueBRIDGE facilities for Data Access, Data Discovery, Data Storage, Data Analytics and Data Publishing. Those facilities are implemented through web services, libraries, and mediators over technologies that are offered as services operated and made accessible through VREs This deliverable is of type "Other" and consists of a set of wiki pages hosted by the BlueBRIDGE project wiki [1] plus a set of documentation pages for single facilities hosted by the gCube wiki [2].