2012.12 WP6: Virtual Research Environments Deployment and Operation Monthly Activity By Task and Beneficiary

From IMarine Wiki

Jump to: navigation, search

Contents

This WP6 Activity Report described the activities performed in Month 14 by Beneficiary and Task.

It is part of Monthly Activity Report.

T6.1 Virtual Research Environments Operation

CNR Activities

CNR team focused on the maintenance of the deployed Virtual Research Environments. In particular, the requests for joining existing VREs have been evaluated and approved.


No major deviation;


None to report.

FAO Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

T6.2 Virtual Research Environments Resources and Tools Provision

FAO Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

ERCIM Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

CNR Activities

The CNR has been involved in the following activities:

  • Enhancing NCBI database update, in order to be performed without affecting NCBI plugin activity in SPD Service (#848).
  • Writing documentation and guidelines for SPD plugins, corresponding fields in Darwin Core for Taxonomy Item and Occurrence (#940).
  • Created a testsuite for SPD plugins (#822).
  • Fixed bugs in WoRMS plugin: Worms plugin was not able to contact WoRMS webservice (#495).


None


FIN Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

UNESCO Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

CRIA Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

IRD Activities

Work on WPS (metadata and processings), work on data providers metadata (CSW, 19115, 19119) and data access through WFS. Update of storage system for Ecoscope.


  • Not for WPS.
  • Change in URIs of Ecoscope. Storage of RDF triples with Quad store.


  • 2 additional WPS have been sent to terradue.
  • Discussions with Emmanuel Blondel about how to describe WPS with OGC metadata.
  • Creation of WFS data access for the tuna atlas use case.
  • Replacement of "#" with "/" in Ecoscope URIs.

T6.3 Virtual Research Environments Common Interfaces and Tools

CNR Activities

The CNR activity focused on the development and the release of the following software applications:

  • Home Library 4.3 - Sharing functionality #217
    • The Home Library provides now the WorkspaceSharedFolder items. Related ticket: #932
    • A notification system has been integrated (using Social Networking Library) to notify the users of a WorkspaceSharedFodler for actions of adding, removing or updating of shared items. Related ticket: #1071
  • Social Portal, Social Data Sharing implementation #865
    • gCube Application News Widget
      • All the gCube applications can now publish news about newly generated products using a uniform way.
      • Related ticket: #1021
    • Social Networking Library
      • gCube applications use the Social Networking Library (SNL) as a common library for exploiting the Social Data Sharing facilities. SNL acts as a bridge for the applications (the pass through the ASL Social Extension described below) and the data infrastructure. So far the following features have been implemented:
        • Publishing Users Posts
        • Retrieving Users Feeds, Comments, Likes
        • Managing User Connections
        • Managing User Notifications
      • Related ticket: #874
    • ASL Social Extension
      • gCube Applications do not interact with the Social Networking Library directly. Rather they exploit this ASL-Extension capability.
      • Related ticket: #876
    • IS Check Health Widget
      • The IS Check Health Widget was 'moved out' from Resource Management Portlet (RMP). It is now a Reusable Widget. Also the technology for displaying charts was changed to HighCharts.
      • Related ticket: #1081
    • IS Resource Sweeper Widget
      • The Resource Sweeper Widge was 'moved out' from Resource Management Portlet (RMP). It is now a Reusable Widget.
      • Related ticket: #1080
  • GIS Publisher Service implementation
    • Implemented a pluggable service to publish GIS data into Geoserver/Geonetwork/Thredds
    • Related ticket : #597
  • Web Application Management Portlet
    • Made WAR deploy service class independent
    • Fixed WAR deployment with last RM changes
  • Species Products Discovery Portlet
  • New functionalities (check all item, uncheck all item etc.) to better usability of SPD portlet are available.
  • A new persistence layer/library is under development to better support the portlet in search and visualization operations. Related ticket: #1002


Software Upload Wizard:

  • A bug has been found regarding the deployment of maven artifacts: when multiple artifacts need to be deployed by SUW those are deployed using two different maven commands thus generating artifacts with different timestamps (hence versions). The bug has been fixed (#985).
  • "Maven dependencies" wizard card has been removed from wizard as it is unnecessary for self-contained web applications (#1009).
  • A new version of Software Upload Wizard will be released in january with gCube 2.12.0.

Resource Management Portlet (RMP) & RMP Support Library:

  • The Resource Management Portlet was completely reengineered. This portlet integrates various modules (widgets) for offering its functionalities. The common code for the modules was moved to an external common library called RMP Support Library. The modules are now imported on demand only when they are actually needed saving lot of bandwidth.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

NKUA Activities

  • Worked on porting the Android gCube search application in maven
    • Related ticket is: #836
  • ApplicationSupportLayerContent extension is enhanced to support the transformation of results coming from Tree collections
    • Currently is under testing (See ticket #1033


NONE


NONE

T6.4 Virtual Research Environments Development Support

NKUA Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

CNR Activities

  • Supporting users activities for data generation / retrieval
  • Bug fix #490


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

Personal tools