2011.12 Activity Report
From IMarine Wiki
This Activity Report captures the activities performed in November and December 2011.
This report is organized in two parts:
- Progress and Achievements at the WP level reports a concise overview of the activities, issues and corrective actions, and major achievements produced by each WP Leader;
- Progress and Achievements by WP and Beneficiary reports a detailed description of the activities, issues and corrective actions, and major achievements produced by each beneficiary at the level of Project task.
Progress and Achievements at WP level
WP1: Administrative and Financial Management
T1.1. Administration of the Grant Agreement and Related Activities
The period preceding the official project start of 1st November 2011 was already rich with activity concerning the negotiation phase of the project. The unique negotiation meeting was held on 6 April, followed by reiterations of the Description of Work. The final version of the DoW is dated 2011-07-04 and was received as Annex I to the Grant Agreement on 15 July. ERCIM then collected the A ("Accession") Forms from the beneficiaries.
In parallel, the Consortium Agreement was developed and a final version (V1.0_August 2011) was approved by the beneficiaries and signature pages were requested on 24 October. Three reiterations of the CA were required in order to achieve this goal, spanning a 3 month period.
The project Kick-Off Meeting was organized by CNR the 16-18 November, with the iMarine Board participating on the 16th and 17th. The Kick-Off Meeting was very well attended, and Carlos Morais Pires of the European Commission (Deputy Project Officer of iMarine) attended with a presentation. Following the meeting, Carlos asked that the Kick-Off presentations be made "public" in order to share with interested colleagues and potential collaborators.
The Governing Board (iMarine's ultimate decision-making body) and the Steering Board (strategic body) were established at the Kick-off Meeting or shortly thereafter (thus achieving Milestones MS1 and MS4).
With respect to collaborating agreements with other projects, a number of Memoranda of Understanding were drafted and/or finalized during this period. The MoU with ERINA+ was finalized. The MoU with TELDAP and EMI are in stages of final revision, having been circulated to the Steering Board. The MoU with GEOWOW was drafted, and should be sent to the GEOWOW project manager in January 2012.
Per request of the Steering Board, WP1 also made contact with James Muir, author of the D4Science Sustainability Plan, to inquire about continuing a collaboration for the production of an infrastructure-wide cost perspective. This activity should be envisaged and the SB needs to respond to a number of questions posed by James in order to move forward.
T1.2 Resource Management
On 26 September the iMarine interest-bearing account received 2,416,661.00 EUR from the Commission as pre-financing for the project's activities. Beneficiaries were informed that the 1st advance payment in the amount of 65% of the pre-financing (calculation based on beneficiaries' full duration budget allocations) would be transferred by the Coordinator upon reception of the signed Form A and Consortium Agreement signature page. ERCIM collected the banking coordinates and electronic and hard copies of the two aforementioned forms. To date, all of the beneficiaries except for one have received the 1st advance payment. The remaining partner has not yet returned the signed CA signature page, but WP1 is aware of no obstacle to signature, leading project management to assume that the delay is caused by administrative issues internal to the organization.
Per the request of the Project Executive Board (which includes WP Leaders), ERCIM implemented bi-monthly effort reporting to be produced by the beneficiaries and in parallel with the due dates of the WP Activity Reports. The first bi-monthly effort report is due on 6 January 2012. The declarations will be compiled and distributed to the PEB in time for the monthly teleconference of which the next is scheduled for 9 January.
T1.3 Quality Assurance
The Quality Assurance Task Force was partially established in this period. Some clarification on the composition of the QATF is still required. ERCIM will send monthly emails to the project members on the status of Milestones and Deliverables. Two such reports have been made covering the months of November and December.
The D1.1 Quality Plan has been drafted and will soon be ready for review (due end December).
No major issues
- Project officially started on November 1st 2011 with administrative paperwork (e.g., Grant Agreement and Consortium Agreement) in order;
- Project Kick-Off Meeting was held 16-18 November in Pisa (CNR);
- Project management boards established;
- Advance payments transferred to all beneficiaries (except one);
- A number of MoUs are ready for Steering Board review;
- Quality Assurance Task Force was partially established, monthly status reports were sent, and D1.1 Quality Plan was drafted.
WP2: Project Management
The project kick-off meeting was organized from the scientific and logistics point of views on 16-18 November 2011. A number of presentations were prepared to illustrate scientific, organizational and technical activity plans. Activities of the period, deliverables, and milestones were monitored and supervised. Monthly PEB and SB teleconferences were organized in December 2011. A wiki for internal activity and effort reporting was designed and set-up. Cooperation with external projects were established and a number of MoUs were drafted.
No major issues to declare
- Organization of a three days kick-off meeting;
- Monitoring and supervision of scientific, strategic and technical activities in the period;
- Organization of monthly PEB (5 December 2011) and SB (6 December 2011) teleconferences;
- Design and set up of a wiki for internal activity and effort reporting;
- Design and set up of a wiki for Infrastructure and VREs operation;
- Design and set up of technical tools, e.g. TRAC;
- Drafting of a number of cooperation MoUs with external project and initiatives;
- Achievement of Milestone MS4: Formation of the Project Management Boards.
WP3: Governance and Policy Development
T3.1 User Community Mediation
FAO actively engaged with the members of the i-marine board to establish rules and procedures for the establishment and operation of not only the Board, but also the wider EA-CoP. The board members were identified, and nearly all intended members have now accepted their nomination.
TRUST-IT has established the i-Marine channel which will be an important means of communication also with the user community.
T3.2 Governance Mechanism, Policies and Guidelines Development
During the reporting period, FAO presented the i-Marine capabilities during several high-level meetings that are of great importance to the development of the business cases. The extent to which i-Marine can support the VME business case will have to further discussed with the stakeholders, but it seems that the technology framework to manage and display spatially explicit information can have a central role.
T3.3 Harmonisation of Metadata, Semantics and Technologies
FAO continued the development of artifacts and content for the Fisheries Linked Open Data inititative, and presented achievements in a variety of in-house fora. The Open-SDMX implementation initiated with the assistance of FAO at the IRD and discussions on the adaptation of a complete statistical data management framework continues.
MS21; Business Case Selection; Information about the selected business cases are published through the iMarine Web Channel was not completed.
This is caused by the nature of the business cases that require continuous adjustements at detail level. However, the infrastructure and objectives to achieve the Milestone are made available. No corrective effort is required.
- The following Milestones were achieved:
- MS5; Establish Board at kick-off meeting; The iMarine Board is established and a dedicated page is published through the iMarine Web Channel.
- MS6; Establish Communication channels, wiki and other tools. Tools supporting the cooperation among the iMarine Board are released.
- MS21; Business Case Selection; Information about the selected business cases are published through the iMarine Web Channel. This was not completed. This requires no corrective action, since the activity has taken a clear direction. (See above)
- The following deliverables were produced:
- Deliverable D3.1 EA-CoP Operation is of nature on-going. The activity has started, but due to the ongoing nature of the deliverable, will continue.
WP4: Communication, Dissemination and Training
Communication and Dissemination Activities
- iMarine graphic design and branding developed;
- Generation of content for flyers, articles, news items, press releases and project fact sheet and powerpoint presentation - 10 news items / articles published on external media channels as a result;
- 4 Presentations including information on iMarine - CNR: EU Parliament Oct 2011 & Belgian Royal Academy Dec 2011, FAO: CWP Meeting Dec 2011, & NKUA: eScience 2011 Dec 2011;
- D4.1 Communication, Dissemination & Training Plan deliverable definition and generation;
- iMarine Dissemination and press & media databases generation;
- Definition of iMarine terminology and how the D4S e-infrastructure and other components will be communicated over the project lifetime.
iMarine Channel Activities
- Static web site was available on line in July 2011;
- Dynamic channel was launched at iMarine Kick-off meeting in Nov 2011;
- iMarine Board Area which includes a file repository and a discussion forum available in Dec 2011;
- fully-fledged channel is foreseen for end January 2012.
- Planning and discussion for the e-training tools to be used and integrated with the iMarine channel.
Delay on D4.1 Communication, Dissemination & Training Plan, will be discussed and defined during the first 3 weeks of January 2012.
The first of the three WP4 milestones - MS22 - iMarine Web Channel (PM2) - Project web site is publically available - has been achieved within the appropriate timeframe.
The project branding (including project and iMarine Board logos, flyer, poster, business card and pop-up banner graphic design) has been designed and delivered to the consortium.
Communication content generated: 1 article, 3 short texts, 1 video interview and various iMarine channel sections.
iMarine in the News
WP5: iMarine Data e-Infrastructure Deployment and Operation
The Deliverable D5.1 has been edited and it's ready for the internal work package review.
The Infrastructure upgrade to gCube 2.7.2 has been performed, to fix some incident tickets.
The upgrade of the VOMS server @ CNR-PROD-PISA to the EMI 1 version was requested to fix a problem on the VOMSAdmin interface.
The EMI-IMarine MoU has been prepared ( it contains mostly milestones related to WP5 activities).
The D4Science infrastructure Monitoring (Resource Management) has been upgraded to support the new resource type RuntimeResource
The D5.1 should have been submitted to the EC at the of end the M1, but some factors delayed the achievement of this date. Most important was the availability of the wiki server, ( the deliverable is of type other, so to be prepared as a WIKI) it was delayed till beginning of M2 and therefore only at that date the deliverable has started to be prepared.
- The deliverable D5.1 has been edited.
- Infrastructure upgrade to gCube 2.7.2
- VOMS Server upgrade to EMI 1 version
- The EMI-IMarine MoU has been prepared
- The D4Science infrastructure Monitoring with RuntimeResource support is available in the gCube 2.7.2 Version
- CERN performed test on the NRPE and SSH solutions for Nagios remote monitoring/Availability
WP6: Virtual Research Environments Deployment and Operation
The activities performed in this reporting period focused on (a) the maintenance of the existing VREs, (b) some resources and tools provision, (c) the deployment of the new portal offering the VREs, and (d) supporting both project members and third party users while using the gCube technology.
Overall, WP members defined and started to compile the Wiki pages documenting WP activities and deliverables.
For what concerns VREs operation, the 13 VREs defined and deployed in the context of the D4Science-II project have been maintained. In particular, they have been upgraded by relying on the latest versions of the software (gCube 2.7.2) supporting their functioning.
For what concerns Resources and Tools provision, WP members started analysing the requirements related to the porting of resources to the iMarine Infrastructure. In particular, this analysis concentrated on OBIS data source, IRD databases, statistical data existing frameworks (namely, Eurostat and Bank of Italy tools).
For what concerns VREs Common Interfaces and Tools, WP members focused on the development of the iMarine portal and the revision of some of the existing portlets. In particular, (a) a beta version of the portal expected to host the VREs has been implemented by relying on latest releases of the LifeRay Portal technology and (b) some of the existing portlets has been revised (namely enabling portlets, SearchManagerPortlet and PE2ng graphical user interface) to enhance their effectiveness.
For what concerns Development Support, WP members concentrated in supporting ISOFT team from Kiev that is willing to deploy and operate an infrastructure by relying on gCube technology. Moreover, FORTH members have been provided with support related to portlets design and development.
Deliverable 'D6.1 Virtual Research Environments Plan' (due date November 2011) has not been delivered. Because of its nature ('Other'), it is expected to be implemented by relying on Wiki and TRAC facilities that was not available at M1. Moreover, no requirements have been received yet from the CoP on VREs. In order to keep the delay as minimal as possible, an initial version of this deliverable will be produced at the beginning of January by focusing on the procedures and tools rather than on VREs.
- The Wiki documenting Work Package activities (Virtual Research Environments Deployment and Operation) has been designed and implemented;
- The 13 VREs defined and deployed in the context of the D4Science-II project have been maintained;
- An iMarine portal (beta version) has been deployed (http://be-portal.d4science.research-infrastructures.eu:8080/);
- IRD code lists have been exposed through SDMX by relying on openSDMX;
- IRD species codes have been aligned with FLOD;
- IRD databases have been exposed through OGC Web services;
- A new gCube-based infrastructure has been deployed and operated by ISOFT team in Kiev http://portal.grid.isofts.kiev.ua:8080/;
WP7: Enabling-technology Integration and Distribution
During the reporting period two gCube System releases have been carried out: gCube 2.7.1 and gCube 2.7.2. Both of them are maintenance releases that fixes high priority defects found in iMarine production infrastructure. All Work Package partners, both in T7.1 and T7.2, took part in the integration of the release.
A new activity has been undertaken with the final goal of letting developers able to use the Maven building tool for gCube components (currently all components use ant):
- E-IIS focused on the investigation of issues that derives from using Maven with the ETICS building tool. The activity focused on three main topics: a) understanding overlaps and complementarities between ETICS and maven and how to manage them, b) create a properly configured environment to run maven within ETICS builds, c) allow a seamless integration between gCube components that use maven and "legacy" components that use ant.
- CNR studied the Maven adoption from component developers' point of view. A Maven plugin has been implemented and further refined in order to easy the configuration adn building of gCube components based on Maven. The plugin performs also validation checks for auxiliary files (README, INSTALL, MAINTAINERS, etc.).
Editing of Deliverable D7.1 has been started in the reporting period: TOC has been defined and approved by the reviewer, most of content has been provided. The deliverable will be finalized in the next reporting period.
Release tools have been installed and made available to developers and release managers. In particular:
- E-IIS refreshened the BTRT installation and a new build repository has been set up;
- E-IIS performed an analysis to select hardware/software requirements for the testing infrastructure and select appropriate resources available in the E-IIS infrastructure. New virtual machines have been created addressing testing infrastructure needs. Those machines will host the gCube nodes and gCube services needed for the testing infrastructure;
- CNR installed two new Maven repositories (SNAPSHOT and RELEASE) have been installed and configured to accept gCube artifacts in order to support experimentation with Maven;
- maintenance release gCube 2.7.1 integrated, validated and released
- maintenance release gCube 2.7.2 integrated, validated and released
- implementation of maven tools for etics: mvn proxy and mavenizer
- tools for easing development of gCube components that uses Maven
- gcube-snapshots and gcube-releases maven repositories installed and configured
- new build repository for BTRT
WP8: iMarine Data e-Infrastructure Enabling Technology Development
WP8 had a very promising starting. T8.1 and T8.4 have been collaborating along all the reporting period because of their mutually correlated activities. T8.2 has moved its first steps in the analysis on how to overcome limitations of specific security issues coming from the previous project and search for more standard solutions. T8.3 has been working on the analysis and design of the evolution of the PE2ng Engine. The collaboration with WP7 triggered the development of the first tools for supporting the new building, deployment and distribution procedures. In conjunction with WP9, WP8 implemented two new libraries for abstracting the development of client-side libraries that interact with services from gCore and gCube details.
- T8.1 started to redesign the enabling layer components and assign new responsibilities following a new approach based on the evolution of the resource model;
- T8.1 implemented a Maven plugin for supporting the migration to Maven as new project management software;
- T8.1 migrated IS-Registry, ISPublisher and ISClient to Maven;
- T8.1 partially redesigned ResourceClientPublisher API, ResourceDiscovery API, Deployer and gHNManager;
- T8.1 implemented my-container, a testing tool for early integration;
- T8.1 extended the ISClient for supporting the discovery of Runtime Resources;
- T8.1 implemented common-client, a small set of service- and technology-independent abstractions for the development of client-side libraries that interact with services, and common-gcore-clients a specialisation of common-clients for classic gCore services;
- T8.2 performed an analysis of the functional and technological requirements for Identity Federation;
- T8.2, in collaboration with CNR, FAO, NKUA and CERN, analyzed the relationship between scoping and Authorization and of the possibilities to propose an Authorization model that comprises both;
- T8.3 identified a set of execution model abstractions, which will make workflows independent of the underlying execution platform and allow PE2ng to act as a unified point of execution for high level workflows originating from all the gCube infrastructure;
- T8.3 formulated a high-level workflow language, which will abstract over infrastructure and process concepts;
- T8.3 worked on supporting the persistency of execution job information;
- T8.4 has initiated a process of requirement analysis for the evolution of the resource model;
- T8.4 has associated the evolution of the resource model with a design methodology in collaboration with T8.1.
Finally, FAO and CNR had several conference calls and email exchanges towards the definition of the new resource model and its impact on the enabling technology. In the context of T8.2, a conference call among all the WP participants was held on 20/12/2011 (minutes are available here) to discuss the topic of the scope management.
- the evolution of scoping mechanisms is a pre-requisite for the definition of APIs for resource publication and discovery. The discussion ongoing in T8.2, and more broadly within the WP, needs to rapidly come to an indication on the dispensability of scope information from enabling interfaces;
- cross-WP discussions between WP8 and WP11 have not started yet.
- definition of a resource-centric methodology for redesigning the enabling layer interfaces
- partial redesign of ResourceClientPublisher API, ResourceDiscovery API, Deployer and gHNManager
- full mavenization of IS-Registry, ISPublisher and ISClient
- ISClient has been enriched to offer queries and discovery features on Runtime Resources
- identification of key requirements for the evolution of the resource model
- implementation of the first new enabling components in replacement and evolution of functionality currently in gCore
- implementation of the Maven-Service-Plugin
- implementation of the MyContainer tool
WP9: Data Management Facilities Development
The WP9 activity had to deal with a preliminary analysis on the components and technologies involved in the realization of the following features:
- Access heterogeneous data repository systems by common and standard protocols
- Generation and manipulation of data
- Quality assessment
- Harmonization of data and metadata
- Publication and sharing
- Efficient, secure, and reliable data transfer
T9.1 worked in the direction of aligning with the methodology presented at the project’s KOM for the task. In particular:
- FAO has liaised with CNR on the selection of a first group of relevant data sources, the characterisation of the models and access protocols, and the design of solutions to access them from within the infrastructure;
- Participants have investigated on the following data sources to be integrated with the Data Access service to be developed:
- FLOD, in representation of data sources that expose Open Linked Data via SPARQL access protocols;
- FAO’s SDMX repository, in representation of data sources that expose timeseries data in standard SDMX formats and access protocols;
- OBIS, in representation of data sources that expose biodiversity data in in standard Darwin Core formats and standard DiGIR protocols;
- WorldBank, in representation of data sources that expose structured data under ad-hoc models and ad-hoc protocols.
It has been decided to reuse and instantiate solutions already available in the Content Management subsystem of gCube, i.e. by developing plugins for the Content Manager service that translate the target protocols and models to the tree-based model and access API of the service.
The forking has resulted in 10 components oriented towards general tree management, including:
- the tree-manager service (a fork of Content Manager)
- the tree-manager-stubs (a fork of the Content Manager stubs)
- the tree-manager-library (a fork of the Content Manager Library)
- the tree-manager-framework (previously embedded in Content Manager)
- the tree-manager-sample-plugin (new)
- the streams library (previously embedded in Content Manager)
- the trees library (previously embedded in Content Manager)
- the document-model-library (forks the gCube Document Model Library)
- the oai-tm-plugin (forks the OAI plugin of the Content Manager)
- the tree-repository (new, replaces the SMS Plugin of the Content Manager as the internal storage solution)
the components are all built with Maven, are fully documented in the code, are under version control, and already integrated in the Etics infrastructure using the latest support for Maven builds which is about to be rolled out in WP7.
For what regards activity by CNR, extensions of storage functionalities of the StorageManager library had been planned. The activity ended with the following implementations:
- wrapper library implementation for gCube environment;
- functionality extensions:
- access control on remote resources: private, shared, public;
- locking system on remote resources;
- TTL manage for locked resources;
- Implementation of a protocol handler called "smp": StorageManagerProtocol;
- Support for asynchronous replication of data between servers for failover and redundancy
T9.2 worked on Data transfer facilities, in particular: activity by CERN team in the first period of the project with respect to this task has been focused on the study and identification of possible integration path between gCube and the FTS Service, the solution for File Transfer implemented at CERN and exploited by the WLCG Grid. Several meetings have been set up between the iMarine CERN team and the FTS team in order to understand the benefits of a possible integration of FTS in gCube and as well if the provisioned functionalities of the Data Transfer in gCube could be also exploited by the FTS. In Parallel iMarine CERN team has installed two version of the FTS service in order to test the functionalities. First the EMI 1 version ( FTS 2.2.6 ) has been set up on the node d4science-dt.cern.ch (https://d4science-dt.cern.ch:8443/glite-data-transfer-fts/services/FileTransfer) together with version 2.2.6 of the FTS Agent. Both component have been configured to join the glite VOVirtual Organization. d4science.research-infrastructures.eu and some test have been performed from the EMI ui installed at CNR ( ui.emi.d4science), in particular testing file transfers using url-copy between the Storage Elements installed at CNR and NKUA sites. In a second phase a new version of FTS and FTA ( 2.2.8 ) has been installed ( on the same node). This version is still in a pilot phase and it has not been released for EMI 1 yet. The new version includes a transfer monitoring mechanism which exploits the Messaging Infrastructure. based on ActiveMQ message brokers. The solution implemented so far in gCube for resources monitoring is also exploiting ActiveMQ brokers and therefore it could be easily integrated in gCube. In addition CERN edited an abstract concerning the study of the integration of the FTS service within gCube, which has been submitted to the EGI Community Forum 2012 to be held in Munich from 26 to 30 March.
Terradue participant worked mainly on geospatial data published in OGC format. The main activity was performed on the THREDDS software, for publishing netCDF files contents and on the release of a library for accessing the content via opendap. Tests in the gCube VTI environment with the new provided library were successful. This will be released in production environment with the gcube 2.7.2 release. The resulting architecture takes netCDF files from MyOcean and publishes them by means of the THREDDS software. In cases where data processing is required before supplying contents, a WPS service is used, provided by a 52North Software. THREDDS is currently running on Open Nebula installation on Terradue site. When ready, the whole system will be moved in the D4Science infrastructure production environment. The 52North WPS service will then be extended with plugins for performing resampling of netCDF data. It will be integrated in the infrastructure by means of a connector in the Data Access gCube Service.
T9.3 worked on the analysis and investigation of a framework for performing data assessment, harmonization and certification. The main idea was to use a possibly open source, state-of-the-art framework in order to manage import, harmonization and certification of data. The framework would manage sets of operations each one focused on a small task (e.g. import from CSV, replacement of data). The activity is currently running and did not produce definitive results. The need has come out for a workflow output to be stored externally to the engine. The team identified an existing technology for framework implementation. At the moment the use of data warehouse ETL tools is under analysis.
- Design of the new Data Access gCube service
- Implementation of extensions for the Content Manager service functionalities in order to manage novel data sources and data description languages
- Introduction of Maven building system for the gCube projects
- Development of a new distributed storage solution for the gCube infrastructure
- Investigation and testing on the integration of different versions of the FTS File Transfer System software with gCube
- Abstract concerning the study of the FTS integration within gCube has been submitted to the EGI CF 2012 ( Munich 26/30 March)
- Investigation of the functionalities of the THREDDS software for netCDF files content distribution
- Investigation and testing of the ETL datawarehouse tool for performing data import, harmonization and certification
WP10: Data Consumption Facilities Development
During the reported period, there has been collaboration between the Data Retrieval and Semantic Data Analysis tasks in order for the involved partners to discuss ways towards achieving the integration of semantic functionalities into the gCube Search System and to devise an initial work plan. Following discussions held at the Kick-off meeting, a conference call took place on Dec 13rd in which both involved partners discussed possible enhancements of the gCube Search System and Query Language and information on several aspects of the gCube System has been communicated in order to facilitate the familiarization of new partners with the system. An initial requirement for the support of search result snippets has been set and both partners agreed to communicate further requirements and ideas on semantic services which could be integrated into the gCube Search System.
In the area of Data Retrieval, work has been done towards enhancing the gCube search System by implementing a query cache to improve response times as perceived by users and fixing defects discovered in the Resource Registry and Search Operator libraries. The implementation of several features in the Resource Registry which will aid administration is also in progress. Moreover, most work on integrating support for search result snippets into the gCube Search System has been completed. The specification of the gCube Query Language is in schedule for the corresponding deliverable in M6, while the inclusion of semantic related extensions in the former will depend on the achievements of the next periods. FORTH worked towards familiarizing themselves with the API of the Search System.
In the area of Data Manipulation, the main activity concerned the evolution the gCube Data Transformation Service in order for the latter to perform computations in a parallel and distributed way by producing execution plans for the PE2ng process execution engine instead of performing the actual transformations locally. The redesign of the service is in progress and aims to preserve all useful existing features while new ones are being added.
In the area of Data Mining and Visualization, the main objective is to develop a service in the infrastructure which will be able to perform Data Mining operations on datasets, operate on several computational infrastructures, parallelize common algorithms, supply statistical analysis features and charts production and train systems for performing experiments about Ecological Modeling. The service is designed in a way that one will be able to plug-in best practice methods for data processing and will use standard formats for input and output datasets. The core of the statistical service has been designed and development of the service as a whole is in progress. The service supports the generative model of Aquamaps along with a monitoring tool for controlling the performances and enables common users to run computations in parallel mode and is able to take under control the occupation of the computational infrastructures it is able to manage.
In the area of Semantic Data Analysis FORTH has focused on familiarizing themselves with the gCube System with support from FAO and NKUA and has progressed in the direction of creating a demo application exploiting the gCube Search System, in order to gain understanding of the content model, possible extensions and as a stepping stone to developing fully fledged gCube applications.
The major issues faced in the reporting period and the identified corrective actions should be reported here
- The core of the statistical service for Data Mining and Visualization has been designed and development of the service as a whole is in progress.
- Implementation and testing of a query cache for the gCube Search System is complete.
WP11: Data e-Infrastructures Integration and Interoperability Facilities Development
Work in WP 11 during the 1st two months of the project is mostly around the assessment of the results of the iMarine technological forerunner project, D4Science - II.
Members of the WP participated in activities analyzing the specifications of gCube services interface principles, the main one being the discussion about the "Scope", another one being the discussion on the validity and value of some HTTP interfaces, such as the IR. An other area of analysis has been the domain of OCC specifications and services, mainly WCS and WCPS, but concrete results are not expected to emerge during the first periods of the project.
In the area of development
- new preliminary components have been developed in the area of Data Access as an exercise for proof of concepts to be considered in the framework definition.
- new features have been added to the public OpenSearch interface of gCube.
Finally a plan for the activities of the WP has been prepared, and its official validation, adoption and launch, will be performed early in the 3rd month of the project.
The workpackage launched its coordination activities with a delay. This delay originates from the fact that an assessment of previous results had to be made, due to two main reasons:
- Achievements of the latest parts of D4Science affects the work to be performed in iMarine, as gCube system API's evolved significantly since the submission of the proposal, in more valuable, yet different technologically, results than initially expected.
- During the last 3 reporting periods of D4Science, new sustainability options have been considered, and these are found to be quite related to the work of WP11.
It is not expected that this will affect the overall deliveries of the workpackage.
- Extension of gCube exposed OpenSearch interface to support OpenSearch-Geo extensions.
- First two general-purpose components for client API development stemming from Data Access subsystem
- First API for data access through the new Tree Manager service