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

From D4Science Wiki
Jump to: navigation, search
Line 21: Line 21:
 
: Relation to CoP Software
 
: Relation to CoP Software
 
: Relation to D4S technologies
 
: Relation to D4S technologies
 +
 +
Tickets in support to the realization of the functionaity are :
 +
[https://issue.imarine.research-infrastructures.eu/ticket/1228#comment:4 Visualisation Use Case: Quantitative properties]
 +
  
 
; Productivity
 
; Productivity

Revision as of 15:05, 6 February 2013

Product request

TrendyLyzer will apply long-term trend analysis on the OBIS data; what historic trends can we discover in the occurrence data. The expectations are similar to what can be achieved through trendalyzer / gapminder, and indeed, these should be considered as valid alternatives, where the e-InfrastructureAn operational combination of digital technologies (hardware and software), resources (data and services), communications (protocols, access rights and networks), and the people and organizational structures needed to support research efforts and collaboration in the large. would have a role in accessing and pre-processing the data to analyze.

The EA-CoPCommunity of Practice. expects that these requirements can be fulfilled through a Virtual Research EnvironmentA ''system'' with the following distinguishing features: ''(i)'' it is a Web-based working environment; ''(ii)'' it is tailored to serve the needs of a Community of Practice; ''(iii)'' it is expected to provide a community of practice with the whole array of commodities needed to accomplish the community’s goal(s); ''(iv)'' it is open and flexible with respect to the overall service offering and lifetime; and ''(v)'' it promotes fine-grained controlled sharing of both intermediate and final research results by guaranteeing ownership, provenance, and attribution.. This would allow the OBIS customers to access the data through the e-InfrastructureAn operational combination of digital technologies (hardware and software), resources (data and services), communications (protocols, access rights and networks), and the people and organizational structures needed to support research efforts and collaboration in the large., specify filters and groupings, select a statistical analysis model, adjust the algorithm parameters (if any), and monitor the progress. The results shall be representable in a variety of formats, and the selection of data, the algorithm and the result shall be contained in a report.


Priority to CoPCommunity of Practice.
List proposed solution priority following the 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 CoPCommunity of Practice. Software
Relation to D4S technologies

Tickets in support to the realization of the functionaity are : Visualisation Use Case: Quantitative properties


Productivity
Are the proposed measures effective?
Does it reduce a known workload?
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?