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

From D4Science Wiki
Jump to: navigation, search
m (moved Ecosystem Approach Community of Practice: NAF2FLUX to Ecosystem Approach Community of Practice: VTI2: The conversion of NAF formatted data to comply with the FLUX standard is no longer required.)
(No difference)

Revision as of 16:26, 16 September 2013

NEAFC has been offered a sub-contract to assist the iMarine consortium with the development of a set of services that enables NEAFC to securely share fisheries information. Some of these facilities can not be provided by Virtual Research Environments, as the data to feed these services can not leave the NEAFC premises. Therefore, a facility is required that can be installed, configured and controlled by NEAFC staff in the NEAFC infrastructure. This facility would be the 'gatekeeper' to the NEAFC repository. Similar 'connectors' or more often needed, and e.g. through the iMarine OpenSDMX initiative, example connectors have already been delivered. 

The NEAFC subcontract depends on these 'connectors', and hence can not commence until these have been validated by Q3 2013.
Product
The services sought by NEAFC should implement secure data exchange with ICES. In first instance, a data browser and data store will be developed for registered ICES staff. The mainly functions will be to 
1) develop a query tool to generate anonymized datasets from data stored in the NEAFC infrastructure, (Query parameters e.g. Species (group), period, area (EEZ / BBox / FAO), flag state, measure, or gear)
2) transform data to an ICIS recognizable format, as per ICES requirements, 
3) publish these anonymized datasets in an access controlled repository in the iMarine infrastructure (encrypted), 
4) ensure that these data-sets can be analyzed in a variety of other VREVirtual Research Environment.'s for e.g. statistical trend analysis, plotting, graphing and tabulation.
The activities of NEAFC will focus no the requirements engineering, validation of results, and use of the services. The software will be supplied and / or further developed by iMarine partners, covered under the sub-contract.
In order to ensure a sustainable use and maintenance of the delivered software to NEAFC, NEAFC will have to ensure that it can contribute hardware and software (JAVA) skills, and oversee the development of the connector to their confidential data.
Priority to EA-CoPCommunity of Practice., and more specifically, NEAFC
The proposed solution meets the following iMarine Board priority setting criteria:
  • Potential target community;
  • Users;
  • 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 NEAFC Software
This para is for NEAFC to fill
Relation to D4S technologies
* SDMX Registry
* Workspace
* ICIS
* CLM
* GeoExplorer
Productivity
Are the proposed measures effective? For ICES staff; reduce search effort and improves reliability. For NEAFC staff reduces support time to write / run ad-hoc queries and exchange the data.
Does it reduce a known workload? Yes, for both ICES and NEAFC staff.
Presentation
How must the component be delivered to users? (UI Design / on-line help / training material / support)
Policy
Are there any policies available that describe data access and sharing?
Have the Copyright / attribution / metadata / legal aspects been addressed from a user and technology perspective?
Retrieved from "https://wiki.d4science.org/index.php?title=Ecosystem_Approach_Community_of_Practice:_NEAFC2ICES&oldid=15117"