Ecosystem Approach Community of Practice: FAO tuna atlas

The FAO Tuna Atlas is one of the key products of the department of Fisheries of FAO.

It is accessible through an interactive map [here]. Process to feed the tuna atlas database is highly manual. iMarine ICIS offers an interesting solution to improve and automate data processing.
ICIS has been tested in the tuna atlas context. Several recommendations were made to add missing features. Features are currently been implemented to release a new version of ICIS.

Product

(Describe the expected service in maximum 3 sentences) ICIS v2 addressing Tuna Atlas needs is a time series processing tool (ICIS v1 to uplaod, curate and validate CSV time series files) with features to remove duplicated lines, persistence of user filters, handling merging of 2 columns unique identifier for geo reference (latitude/longitude) in a one column unique ID (Grid-ID).

Implementation activity

Development of new requested features can be tracked through TRAC:

Priority to CoPCommunity of Practice.

(List proposed solution priority following the iMarine Board priority setting criteria:)

• The target community can be split in 2: data contributors and data consumers.
  • data contributors are source information systems. This source information systems are not limited to the 3 current source information Systems;
  • data consumers are fisheries experts, fisheries professional and the wider public with an expressed interest in fisheries ;
• Users; there are 2 groups of users: the source information systems data managers, which can be any kind of open information systems publishing public data and the final data user.
• Potential for co-funding; High as other stakeholders could be interesting to develop Regional Information Systems based on the same concepts
• Structural allocation of resources; SmartFish hosting is already in place. Activities on annotation and indexing are currently in progress and should be achieved by December 2013 for a presentation in a stakeholder workshop mid December 2013.
• Referred in DoW;in BC3
• How does the proposed action generally support sustainability aspects? SmartFish being hosted in iMarine e-infrastructure is a sustainable solution compared to the initial foreseen solution of a local hosting a marine research institute in Kenya that showed its limits with another hosted statistical database;
• How consistent it is with regulations/strategies ?
• Re-usability – benefits – compatibility: SmartFish use case is the typical example of reuse of existing components (FLOD) and of improvement of these components. Benefits are immediate with the possibility to reuse existing components (saving development time) and to easily improve them (use of common open source technologies);

Parentage

Relation to CoPCommunity of Practice. Software

• FAO FLOD
• iMarine ConnectCube
• iSearch
• Xsearch

Relation to D4S technologies

Productivity

Are the proposed measures effective?

• Yes, as it proposes a faster and more efficient way of accessing data scattered among 3 source information systems.

Does it reduce a known workload?

• User gets in one result page proposals for information and data available in 3 IS. The user saves time and access information he might suspect not available in a given system (like statistical information scarcely available in WIOFish but widely available in FIRMS)

Presentation

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

• A portal has been created using a simple PHP technology and a PostgreSQL database to store the application ontology. Simple users interfaces provide user access to search engine and refinement tools to access the needed information. The application ontology aims to organize data access by relevant domains corresponding to common interest of fisheries experts or professional.

Policy

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

• data access and sharing policy of Smartfish [1]

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

xxxxxxx