Difference between revisions of "Ecosystem Approach Community of Practice: VME DB"

Revision as of 12:01, 13 October 2013

The VME-DB is developed for practitioners in the field of Vulnerable Marine Ecosystems cataloging and mapping. It is designed to collect, collate, analyze and publish information related to the location, characteristics and exploitation of marine areas.

It is envisaged that iMarine collaborates with FAO to deliver two main parts:

• The VME-VREVirtual Research Environment.; a VREVirtual Research Environment. for Fact sheets editing;
• And later: a GeoExplorer enriched with interactive features to identify and comment spatially explicit data on VME location, encounters, survey-data, bio-physical data, and exploitation data.

The current VREVirtual Research Environment. described below focuses on the first part. It will use a report template to structure the VME fact-sheets, and reports to capture the fact-sheet information. The exchange with the FAO VME-DB has to be defined, and the discussion is recorded here: Ecosystem_Approach_Community_of_Practice:_VME_iMarine

Product

The VME-DB VREVirtual Research Environment. will offer a tool to describe marine areas based on a template to produce a factsheet in an organized work-flow. The VREVirtual Research Environment. manager invites users to contribute to sections of a fact-sheet, and decides when a fact-sheet can be released for publication through the VME-DB website. The data are synchronized with this website through a web-service facility that will have to be developed.

Implementation activity

The implementation can be tracked through TRAC:

• The initial request was described here [[1]]
• Main enhancements to the delivered facility are described by e.g.:
  • Data exchange [[2]]
  • Quick Search to update an existing VME description;
  • Stateless 'reports'
  • Fact-sheets can contain 'dynamic' sections with e.g. a overview of latest encounters / statistics;
  • Confidential sections (not all fact-sheets are public);
  • Evolving fact-sheets (Some changes over time have to be kept; compare this to e.g. the EU-membership that evolve over time);
  • Tablet or other media support.

Priority to CoPCommunity of Practice.

The proposed solution priority follows several key iMarine Board priority setting criteria:

• The target community can be split in 2: data contributors and data consumers.
  • data contributors are scientists, policy makers, industry,
  • data consumers are and the wider public with an expressed interest in ;
• Users; data entry will be done by any registered scientist, policy support officer, biologist, industry representatives. With such a large and diverse user group, requirements to clearly separate content and ensure confidentiality requiremstn are obvious.
• Potential for co-funding; High
• Structural allocation of resources; The VREVirtual Research Environment. is expected to be prototyped towards the end of 2013. The GeoExplorer development has started, and the deliverables can be aligned with the release of VREVirtual Research Environment. components.
• Referred in DoW;in BC2
• How does the proposed action generally support sustainability aspects;
• How consistent it is with regulations/strategies ?.
• Re-usability – benefits – compatibility;

Parentage

Relation to CoPCommunity of Practice. Software

• FAO VME-DB
• FAO Webservices for reference data and code lists
• FAO Master Data Management
• FiGIS schema, fact sheet engine and website

Relation to D4S technologies

• D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Reporting tool is the base for VME-DB VREVirtual Research Environment.
• D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Work-flow tool will marshal the editing work-flow
• D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Web-services will update reports in the FAO database

Productivity

Are the proposed measures effective?

• Yes, as it enables a controlled multi-groups and multi-user editing network.

Does it reduce a known workload?

• When completed the VME-VREVirtual Research Environment.

Presentation

How must the component be delivered to users? (UI Design / on-line help / training material / support)

• The interactive Map User interface is expected to be able to describe / edit the properties (attributes) of a polygon or point.
• Collecting these features, defined through their featuretype, is expected to be done either through a VREVirtual Research Environment. or a connected stand-alone GIS Application. The feature type (the schema) can e.g. be defined in a VREVirtual Research Environment. for re-use in a desk-top GIS.
• The geoExplorer should be enriched with a style editor, and style settings should be persisted for a next login.

Policy

Are there any policies available that describe data access and sharing?

• Fact-sheet related policies are not needed.
• Later: data access and sharing policy of geospatial and OGC data [3]

Have the Copyright / attribution / metadata / legal aspects been addressed from a user and technology perspective?

For Yann / Aureliano.