2012
Software
Metadata Only Access
gCube Software gateway service
Cirillo R
The Software Gateway service is a gateway over N Maven Repositories for the enabling layer on gCube infrastructure. the service also certifies which software is deployable withing the gCube infrastructureProject(s): IMARINE
Cirillo R
The Software Gateway service is a gateway over N Maven Repositories for the enabling layer on gCube infrastructure. the service also certifies which software is deployable withing the gCube infrastructureProject(s): IMARINE
See at:
CNR IRIS 
2012
Software
Metadata Only Access
Storage Manager Library for gCube.
Cirillo R
The storage manager library implements access and storage facilities, POSIX-Like API which supports the organisation and operations normally associated with local file systems whilst offering scalable and fault-tolerant remote storage.Project(s): D4SCIENCE-II
Cirillo R
The storage manager library implements access and storage facilities, POSIX-Like API which supports the organisation and operations normally associated with local file systems whilst offering scalable and fault-tolerant remote storage.Project(s): D4SCIENCE-II
See at:
CNR IRIS | www.gcube-system.org
2015
Software
Metadata Only Access
gCube Whn manager
Cirillo R
The Whn-Manager is a smartgears based service that operates in the context of gCube providing an interface for remotely managing a Web Hosting Node. In particular, this service is responsible for: the management and changes of the scope of the node and the locally deployed service instances according to the Scope Management rules; publishing in the Information System the gCube Resource representing the wHN.Project(s): IMARINE
Cirillo R
The Whn-Manager is a smartgears based service that operates in the context of gCube providing an interface for remotely managing a Web Hosting Node. In particular, this service is responsible for: the management and changes of the scope of the node and the locally deployed service instances according to the Scope Management rules; publishing in the Information System the gCube Resource representing the wHN.Project(s): IMARINE
See at:
CNR IRIS | www.gcube-system.org
2015
Software
Metadata Only Access
Storage manager library for gCube
Cirillo R
The storage manager library implements access and storage facilities, POSIX-Like API which supports the organisation and operations normally associated with local file systems whilst offering scalable and fault-tolerant remote storage.Project(s): D4SCIENCE-II
Cirillo R
The storage manager library implements access and storage facilities, POSIX-Like API which supports the organisation and operations normally associated with local file systems whilst offering scalable and fault-tolerant remote storage.Project(s): D4SCIENCE-II
See at:
CNR IRIS | www.gcube-system.org
2017
Software
Metadata Only Access
SSTorage gCube service
Cirillo R
A RESTful service providing functions for create, update, read a json object on MongoDB cluster.
Cirillo R
A RESTful service providing functions for create, update, read a json object on MongoDB cluster.
See at:
CNR IRIS | www.gcube-system.org
2022
Software
Metadata Only Access
gCubeDeployer
Cirillo R
Pipeline scritta in groovy che permette il "deploy" automatico di software su macchine remote. La pipeline viene usata attivamente nell'Infrastruttura D4Science per la realizzazione del "Continuous Deployment" (CD). E' possibile lanciare la pipeline sia in modalita' manuale, sia agganciata a "Jenkins Jobs" oppure "triggered" dalla pipeline di Build, denominata "gCubeBuilder". Il software della infrastruttura D4Science viene distribuito sulle macchine remote, tramite l'uso di script basati sul sistema di provisioning denominato Ansible.Project(s): Blue Cloud
Cirillo R
Pipeline scritta in groovy che permette il "deploy" automatico di software su macchine remote. La pipeline viene usata attivamente nell'Infrastruttura D4Science per la realizzazione del "Continuous Deployment" (CD). E' possibile lanciare la pipeline sia in modalita' manuale, sia agganciata a "Jenkins Jobs" oppure "triggered" dalla pipeline di Build, denominata "gCubeBuilder". Il software della infrastruttura D4Science viene distribuito sulle macchine remote, tramite l'uso di script basati sul sistema di provisioning denominato Ansible.Project(s): Blue Cloud
See at:
code-repo.d4science.org | CNR IRIS
2022
Software
Metadata Only Access
gCubeBuilder
Cirillo R, Simi M
Pipeline scritta in linguaggio "groovy", modella l'intero processo di build di una gCube Release, a partire da un file YAML passato in input. Il file contiene una lista di JenkinsJobs da buildare, raggruppati in gruppi logici di componenti, in modo da garantire il giusto ordine di build. I Job vengono eseguiti in modo concorrente all'interno dei gruppi logici in modo da ottimizzare i tempi di release. Gli stage della pipeline sono dinamici, in base ai gruppi logici presenti sul file YAML di input. L'esecuzione dei vari stages e` sequenziale. Alla fine del processo, la pipeline restituisce via mail un report al release manager, in cui vengono specificati i dettagli relativi ad ogni build eseguito.Project(s): Blue Cloud, SoBigData
Cirillo R, Simi M
Pipeline scritta in linguaggio "groovy", modella l'intero processo di build di una gCube Release, a partire da un file YAML passato in input. Il file contiene una lista di JenkinsJobs da buildare, raggruppati in gruppi logici di componenti, in modo da garantire il giusto ordine di build. I Job vengono eseguiti in modo concorrente all'interno dei gruppi logici in modo da ottimizzare i tempi di release. Gli stage della pipeline sono dinamici, in base ai gruppi logici presenti sul file YAML di input. L'esecuzione dei vari stages e` sequenziale. Alla fine del processo, la pipeline restituisce via mail un report al release manager, in cui vengono specificati i dettagli relativi ad ogni build eseguito.Project(s): Blue Cloud
, SoBigData
See at:
code-repo.d4science.org | CNR IRIS
2019
Software
Metadata Only Access
gCube maven parent
Cirillo R, Simi M
The gCube Maven parent POM (or super POM) is used to avoid redundancies or duplicate configurations using inheritance between POM files on gCube platform. It helps in easy maintenance in long term. Every gCube component java based must declare the maven-parent as parent pom. The gCube maven parent contains enforcement rules in order to be compatible with the gCube world; a set of build profiles that defines: repositories where the dependencies are resolved, rules based on the specific build profile, the target repository where the artifact will be deployed and a set of common-plugin. Furthermore there are also common build profiles and a set of plugin repos common across profiles. Furthermore there are a set of common properties used by every gCube component.Project(s): Blue Cloud, SoBigData-PlusPlus
Cirillo R, Simi M
The gCube Maven parent POM (or super POM) is used to avoid redundancies or duplicate configurations using inheritance between POM files on gCube platform. It helps in easy maintenance in long term. Every gCube component java based must declare the maven-parent as parent pom. The gCube maven parent contains enforcement rules in order to be compatible with the gCube world; a set of build profiles that defines: repositories where the dependencies are resolved, rules based on the specific build profile, the target repository where the artifact will be deployed and a set of common-plugin. Furthermore there are also common build profiles and a set of plugin repos common across profiles. Furthermore there are a set of common properties used by every gCube component.Project(s): Blue Cloud
, SoBigData-PlusPlus
See at:
code-repo.d4science.org | CNR IRIS
2013
Other
Open Access
IMarine - IMarine data infrastructure enabling software
Antoniadis A, Cirillo R, Formisano C, Fortunati L, Gerbesiotis J, Lelii L, Panagiotis L, Savini A, Simeoni F, Travaglino E
iMarine Data Infrastructure Enabling Software contains the description of software and pointers to the documentation and artifacts of the related components that comprise the e-Infrastructure Management suite delivered from M11 to M24Project(s): IMARINE
Antoniadis A, Cirillo R, Formisano C, Fortunati L, Gerbesiotis J, Lelii L, Panagiotis L, Savini A, Simeoni F, Travaglino E
iMarine Data Infrastructure Enabling Software contains the description of software and pointers to the documentation and artifacts of the related components that comprise the e-Infrastructure Management suite delivered from M11 to M24Project(s): IMARINE
See at:
goo.gl 
| CNR IRIS | ISTI Repository | CNR IRIS
2014
Software
Metadata Only Access
gCube registry publisher
Cirillo R, Lelii L
The gCube Registry Publisher is a java library that operates in the context of gCube framework. This library represents, in conjunction with the IC-Client library, the mediation layer gCube Services, it will rely on to interact with the Information Service as a whole in order to publish, update, delete any kind of shared resource in the gCube context.Project(s): IMARINE
Cirillo R, Lelii L
The gCube Registry Publisher is a java library that operates in the context of gCube framework. This library represents, in conjunction with the IC-Client library, the mediation layer gCube Services, it will rely on to interact with the Information Service as a whole in order to publish, update, delete any kind of shared resource in the gCube context.Project(s): IMARINE
See at:
CNR IRIS
2015
Software
Metadata Only Access
gCube resource manager
Simi M, Cirillo R
The Resource Manager is a SOA based service in charge of managing gCube Scope contexts. The Resource Manager 2.0, by coordinating five distinguished services (Deployer, Software Gateway, Resource Broker, gCube Hosting Node Manager, Web Hosting Node Manager), realizes the VRE dynamic deployment by, respectively, collecting service implementations, selecting target nodes for deployment within the infrastructure, and hosting resources implementations at selected nodes. The primary role assigned to this service is to collects and manage all the resources and service implementations related to a specific Virtual Organization.Project(s): IMARINE
Simi M, Cirillo R
The Resource Manager is a SOA based service in charge of managing gCube Scope contexts. The Resource Manager 2.0, by coordinating five distinguished services (Deployer, Software Gateway, Resource Broker, gCube Hosting Node Manager, Web Hosting Node Manager), realizes the VRE dynamic deployment by, respectively, collecting service implementations, selecting target nodes for deployment within the infrastructure, and hosting resources implementations at selected nodes. The primary role assigned to this service is to collects and manage all the resources and service implementations related to a specific Virtual Organization.Project(s): IMARINE
See at:
CNR IRIS | www.gcube-system.org
2014
Other
Open Access
iMarine - iMarine Data Management Software
Coro G, Lelii L, Manzi A, Drakopoulos N, Marioli V, Cirillo R, Simeoni F, Antoniadis A, Brito F, Caumont H
The iMarine Data Management Software comprises a number of components and subsystems offering facilities for accessing, transferring and harmonising a rich array of data typologies. This document describes the novelties within the iMarine Data Management Software from M12 (Oct.'12) to M27 (Jan.'14). It complements D9.2 [10] which describes iMarine Data Management Software up to M11 (Sept.'12). This deliverable is intended for documentation purposes only. The actual deliverable is represented by the software artifacts and their accompanying documentation.Project(s): IMARINE
Coro G, Lelii L, Manzi A, Drakopoulos N, Marioli V, Cirillo R, Simeoni F, Antoniadis A, Brito F, Caumont H
The iMarine Data Management Software comprises a number of components and subsystems offering facilities for accessing, transferring and harmonising a rich array of data typologies. This document describes the novelties within the iMarine Data Management Software from M12 (Oct.'12) to M27 (Jan.'14). It complements D9.2 [10] which describes iMarine Data Management Software up to M11 (Sept.'12). This deliverable is intended for documentation purposes only. The actual deliverable is represented by the software artifacts and their accompanying documentation.Project(s): IMARINE
See at:
CNR IRIS | ISTI Repository | CNR IRIS
2014
Other
Open Access
IMARINE - iMarine Data e-Infrastructure Operation Report
Candela L, Cirillo R, Manzi A, Pagano P
The iMarine Data e-Infrastructure is a living system whose development is mainly driven by requirements and feedback produced by the iMarine CoP. This deliverable is the third of the series of reports on the activities performed while operating such a system. The deliverable describes the state of the Data e-Infrastructure in terms of nodes available, software deployed, quality of the service, and usage as of September 2014.Project(s): IMARINE
Candela L, Cirillo R, Manzi A, Pagano P
The iMarine Data e-Infrastructure is a living system whose development is mainly driven by requirements and feedback produced by the iMarine CoP. This deliverable is the third of the series of reports on the activities performed while operating such a system. The deliverable describes the state of the Data e-Infrastructure in terms of nodes available, software deployed, quality of the service, and usage as of September 2014.Project(s): IMARINE
See at:
CNR IRIS | ISTI Repository | CNR IRIS
2018
Other
Open Access
BlueBRIDGE - BlueBRIDGE VREs operation activity: final report
Assante M, Candela L, Cirillo R, Dell'Amico A, Pagano P
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).Project(s): BlueBRIDGE
Assante M, Candela L, Cirillo R, Dell'Amico A, Pagano P
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).Project(s): BlueBRIDGE
See at:
CNR IRIS | ISTI Repository | CNR IRIS
2018
Other
Open Access
ENVRIplus - Interoperable data processing services for environmental RI projects: prototype
Candela L, Cirillo R, Coro G, Pagano P, Panichi G
This deliverable documents the implementation of the data processing solution defined in D7.1 "Interoperable data processing for environmental RIs projects: system design". The actual deliverable consists of the software realising the envisaged solution and the instances of it made available to the ENVRI community in the large. The distinguishing features of the proposed solution are (a) to be suitable for serving the needs of scientists involved in ENVRI RIs, (b) to be open and extensible both with respect to the algorithms and methods it enables and the computing platforms it relies on to execute those algorithms and methods, (c) to be open-science-friendly, i.e. it is capable of incorporating every algorithm and method integrated into the data processing framework as well as any computation resulting from the exploitation of integrated algorithms into a "research object" catering for citation, reproducibility, repeatability and provenance. The proposed solution is part of a larger software system named gCube and has been provisioned to ENVRI RIs via several Virtual Research Environments operated by D4Science.Project(s): ENVRI PLUS
Candela L, Cirillo R, Coro G, Pagano P, Panichi G
This deliverable documents the implementation of the data processing solution defined in D7.1 "Interoperable data processing for environmental RIs projects: system design". The actual deliverable consists of the software realising the envisaged solution and the instances of it made available to the ENVRI community in the large. The distinguishing features of the proposed solution are (a) to be suitable for serving the needs of scientists involved in ENVRI RIs, (b) to be open and extensible both with respect to the algorithms and methods it enables and the computing platforms it relies on to execute those algorithms and methods, (c) to be open-science-friendly, i.e. it is capable of incorporating every algorithm and method integrated into the data processing framework as well as any computation resulting from the exploitation of integrated algorithms into a "research object" catering for citation, reproducibility, repeatability and provenance. The proposed solution is part of a larger software system named gCube and has been provisioned to ENVRI RIs via several Virtual Research Environments operated by D4Science.Project(s): ENVRI PLUS
See at:
CNR IRIS | ISTI Repository | CNR IRIS
2019
Other
Restricted
DESIRA - Deliverable 5.1 - Virtual Research Environment: specification report
Assante M, Cirillo R, Dell'Amico A, Frosini L, Pagano P
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.
Assante M, Cirillo R, Dell'Amico A, Frosini L, Pagano P
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.
See at:
data.d4science.net | CNR IRIS | CNR IRIS
2019
Other
Open Access
SoBigData - D10.7 - SoBigData e-infrastructure and VRE release
Assante M, Candela L, Cirillo R, Frosini L, Lelii L, Mangiacrapa F, Pagano P
This deliverable describes the software that has been deployed to serve the needs of the SoBigData community, by delivering the platform and the VREs planned in "D10.4 SoBigData e-Infrastructure release plan 3". In particular, it reports on how such software has been exploited to make available the envisaged components, i.e. the SoBigData portal (and the underlying Virtual Organisation), the SoBigData Catalogue and the SoBigData Virtual Research Environments, together with the list and pointers to the software packages produced by the project and implementing such components, whose operation today constitutes the SoBigData e-infrastructure accessible from http://sobigdata.d4science.org.Project(s): SoBigData
Assante M, Candela L, Cirillo R, Frosini L, Lelii L, Mangiacrapa F, Pagano P
This deliverable describes the software that has been deployed to serve the needs of the SoBigData community, by delivering the platform and the VREs planned in "D10.4 SoBigData e-Infrastructure release plan 3". In particular, it reports on how such software has been exploited to make available the envisaged components, i.e. the SoBigData portal (and the underlying Virtual Organisation), the SoBigData Catalogue and the SoBigData Virtual Research Environments, together with the list and pointers to the software packages produced by the project and implementing such components, whose operation today constitutes the SoBigData e-infrastructure accessible from http://sobigdata.d4science.org.Project(s): SoBigData
See at:
data.d4science.net | CNR IRIS | ISTI Repository | CNR IRIS
2016
Other
Open Access
BlueBRIDGE - D9.1 BlueBRIDGE VRE Commons Facilities
Assante M, Candela L, Cirillo R, Coro G, Koltsida P, Marioli V, Perciante C, Sinibaldi F
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].Project(s): BlueBRIDGE
Assante M, Candela L, Cirillo R, Coro G, Koltsida P, Marioli V, Perciante C, Sinibaldi F
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].Project(s): BlueBRIDGE
See at:
ISTI Repository | CNR IRIS | CNR IRIS
2016
Other
Open Access
BlueBRIDGE - BlueBRIDGE VREs operation activity: interim report
Assante M, Candela L, Cirillo R, Dell'Amico A, Pagano P, Perciante C
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).Project(s): BlueBRIDGE
Assante M, Candela L, Cirillo R, Dell'Amico A, Pagano P, Perciante C
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).Project(s): BlueBRIDGE
See at:
CNR IRIS | ISTI Repository | CNR IRIS
2023
Other
Metadata Only Access
The gCube geoportal platform
Candela L, Cirillo R, Mangiacrapa F, Pagano P, Sinibaldi F, Vannini G L
The gCube Geoportal platform is a component of the gCube open source software system conceived to support the creation and publication of georeferenced research objects, i.e. multi-part and multimedia research objects characterised by geospatial and temporal features. The Geoportal platform enables user communities to fully customise the data model characterising their instance by defining the structure, the content and the workflow of the potential research objects to be managed. `this report carefully describes the technology and documents how it was exploited to serve the development of a national catalogue for archaeological artifacts.DOI: 10.32079/isti-tr-2023/012
Project(s): ARIADNEplus, Blue Cloud
Metrics:
Candela L, Cirillo R, Mangiacrapa F, Pagano P, Sinibaldi F, Vannini G L
The gCube Geoportal platform is a component of the gCube open source software system conceived to support the creation and publication of georeferenced research objects, i.e. multi-part and multimedia research objects characterised by geospatial and temporal features. The Geoportal platform enables user communities to fully customise the data model characterising their instance by defining the structure, the content and the workflow of the potential research objects to be managed. `this report carefully describes the technology and documents how it was exploited to serve the development of a national catalogue for archaeological artifacts.DOI: 10.32079/isti-tr-2023/012
Project(s): ARIADNEplus
, Blue Cloud Metrics:
See at:
CNR IRIS