Difference between revisions of "Ecosystem Approach Community of Practice: ICIS"

Revision as of 13:34, 15 January 2014

ICIS

The ICIS VREVirtual Research Environment. is a complete data-management suit that exploits many of the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. technologies.

It allows the upload of data from a variety of sources (csv, workspace, SDMX), and offers many data management facilities for sorting, filtering, merging, etc. It also includes advanced work-flow support, with each modification captured as a 'metadata' type information. the resulting TimeSeries are rich objects, which can be:

• geospatially explicit (georeferenced) and diplayed in an integrated MapViewer;
• exported to an integrated R-environment;
• saved and reused in the integrated reporting environment, such as in FCPPS;
• etc.

An extensive description of the requirements is available through the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative.-II wiki: ICIS-Senario

ICIS is accessible throuh the portal if you have been provided with user credentials

The user-guide of ICIS is available here: guide

SPREAD

The SPatial REallocation of Aquatic Data (SPREAD) aims to provide the movement of geospatial explicit data from one resolution to another.

The Use Cases were already descibed in D4ScienceAn e-Infrastructure operated by the D4Science.org initiative.-II, and can be found under the Advanced Curation Use Case.

It was included there, because in the context of D4ScienceAn e-Infrastructure operated by the D4Science.org initiative.-II, the starting point for a re-allocation is a TS-Object, and the re-allocation was perceived as a precision of geospatial location of a reported capture without much reasoning or change of the reported values; an advanced type of curation.

A progress report on SPREAD accomplishments and opportunities can be found on BSCW (SPREAD120207.docx).

OpenSDMX

An important feature of ICIS is the growing support of parts of the SDMX standard. To foster a community development effort, FAO initiated the OpenSDMX initiative. For current requirement, read more on the Cluster page for OpenSDMX.

Features supporting OpenSDMX are expected to be made available through the ICIS, CodeListManager and CodelistMapper VREs.

ICIS VREVirtual Research Environment.

Product

Describe the proposed solution in maximum 3 sentences:

With ICIS capture time-series can be:

1. Ingested
2. Curated
3. Validated with a rule frame

After the Time-series has been produced, it can be

1. Manipulated with a DML facility
2. Merged with previous / other TS
3. Mapped in a geoexplorer
4. Analyzed
5. Shared and published

Thus, ICIS offers a complete data environment for Time Series.

Priority to CoPCommunity of Practice.

Several real-life use-cases exist for ICIS to serve key-groups to the project sustainability. The description below follows the the iMarine Board priority setting criteria for the top potential clients. These are:

BC1: ICIS, VALID,

BC2: TBTI,

BC3:

http://wiki.i-marine.eu/index.php/Rule_frame#VALID_project_Action_rules

FAO ICIS

The first FAO use of ICIS will be in support of the Tuna Atlas data management.

• The Identified community: consists of the Tune Atlas Data Managers (< 3 persons) responsible for the collation of the tuna atlas data sets.
• The Potential for co-funding will be substantial if ICIS proves it can support work-flows and life-cycle.
• The Structural allocation of resources is covered for the development side through StatsCube development resources, yet for the work-flow develompent no funding has been secured. This also blocks a commitment of exploitation resources, as these can only e released for a complete solution.
• The Tuna Atlas is Referred in DoW, and ths of high-priority.
• The Tuna Atlas is a core component for Business Case 1
• The Tuna Atlas is the explotation bench-mark and thus in support of sustainability aspects. The validation of the Tuna Atlas will reveal how other communities can benefit from the released components.
• How consistent it is with EC regulations/strategies (eg INSPIRE, ... ):
• The Tuna Atlas is conceptualized to enable Re-usability of components, with benefits such as data compatibility clearly at the front of the developments.

VALID

• Identified community:
• Users now: DG MARE requires that country commit to producing data that are compliant to several regulatinos. ICIS offers the services to produce these quality data sets.
• Potential for co-funding is high, if the base functionality for validation through webservices can be shown
• Structural allocation of resources: ICIS is mainly developed by CNR
• Referred in DoW: YES
• Business Cases: BC1
• How does the proposed action generally support sustainability aspects
• How consistent it is with EC regulations/strategies: VALID is defined and designed to meet the follwing EC regulations
• Re-usability – benefits – compatibility. VALID builds on the layers developed for ICIS, and thus re-uses many existing iMarine services. This benefits not only the users of VALID, but as OS validation rules, can also feed back to ICIS and related VREVirtual Research Environment.'s.

TBTI

• Identified community: Users now:
• Potential for co-funding:
• Structural allocation of resources:
• Referred in DoW:
• Business Cases:
• How does the proposed action generally support sustainability aspects
• How consistent it is with EC regulations/strategies (eg INSPIRE, ... ):
• Re-usability – benefits – compatibility

NEAFC

• Identified community: Users now:
• Potential for co-funding:
• Structural allocation of resources:
• Referred in DoW:
• Business Cases:
• How does the proposed action generally support sustainability aspects
• How consistent it is with EC regulations/strategies (eg INSPIRE, ... ):
• Re-usability – benefits – compatibility

Another data tool

• Identified community: Users now:
• Potential for co-funding:
• Structural allocation of resources:
• Referred in DoW:
• Business Cases:
• How does the proposed action generally support sustainability aspects
• How consistent it is with EC regulations/strategies (eg INSPIRE, ... ):
• Re-usability – benefits – compatibility

Parentage

Relation to CoPCommunity of Practice. Software Relation to D4S technologies

Does the proposed solution solve other problems associated with EA-CoPCommunity of Practice. Business Cases?

If the proposed solution can be used in another SW scenario (not users!) please describe.

Public

How big is the expected user community after delivery?

Productivity

Are the proposed measures effective?

Does it reduce a known workload?

Price

Is the proposed solution cheap?

Expected effort in PM:

Presentation

How is the component delivered to users? (Design / on-line help / training material / support).

Privacy

Are they safe? Need the proposed solution to manage confidential info at data / dataset / organizational level? Describe security and privacy issues:

Policy

The policies available that describe a.o. data access and sharing? are described here

The Copyright / attribution / metadata / legal and other issues pertaining to use and re-use of data and resources are covered in the data access and sharing pages of iMarine.

Perils

Do they introduce moral hazard? (A hazard here is the risk that users will behave more recklessly if they are insulated from the effects of the software, or if they do noit understand what it produces, where data come from, what they represent etc. .)