Difference between revisions of "Ecosystem Approach Community of Practice Overview"

From D4Science Wiki
Jump to: navigation, search
(Publications)
 
(109 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
{| align="right"
 +
|| __TOC__
 +
|}
 
This page is dedicated to document the activities of the Ecosystem Approach Community of Practice (EA-CoP).
 
This page is dedicated to document the activities of the Ecosystem Approach Community of Practice (EA-CoP).
  
It will contain:
+
It is organised in the following three areas:
* the '''[[VRE planning]]''' page;
+
* The [[Ecosystem_Approach_Community_of_Practice:_The_iMarine_Board | iMarine Board]] area which introduces the board, the rules governing its functioning, the working plan and the meetings;
* the '''[[iMarine Business Cases]]''' page;
+
* The [[Ecosystem_Approach_Community_of_Practice:_The_iMarine_Board#Overall_workplan | Overall Workplan]] section which provides an overview of the iMarine Board identified activities throughout the project life span
* the '''[[EA-COP Cluster collaboration]]''' page;
+
* The [[Ecosystem_Approach_Community_of_Practice:_The_iMarine_Board#Implementation_results | Implementation results]] area which describes the outputs of iMarine Board's activities, namely (i) the results of mediation activities, the Governance mechanisms and policies governing the envisaged infrastructure, the harmonization of systems resulting from the requirements characterising the expected infrastructure, and the validation of delivered products.
* the '''[[EA-CoP Milestones]]''' page;
+
* the '''[[EA-CoP Data Access and Sharing Policies]]''' page;
+
* the '''[[EA-CoP Discussion]]''' page;
+
  
The '''Virtual Research Environment (VRE) planning page''' describes the EA-CoP desiderata in terms of a composition of services and resources, delivered as a packaged single unit to the CoP. A VRE provides a defined set of services for a specific group of users that collaborate on a specified task or workflow. An alternative approach to VREs are gCube apps. In the context of the CoP desiderata, no difference is made.
+
== [[Ecosystem_Approach_Community_of_Practice:_The iMarine_Board | The iMarine Board]] ==
  
The power of a large infrastructure is evidenced by the quick mobilization of resources to be chained in a workflow. A set of VRE's or other resources could be composed where the output of one becomes the input of the next. One such example is SPREAD where based on Timesseries objects and Geospatial intersections, both provided through a VRE, a re-allocation must be made based on a range of assumptions. Such a group of interactive VRE's may also be in need of external data that can be quite dynamic, and rely on interoperable infrastructures.
+
The '''[[Ecosystem_Approach_Community_of_Practice:_The iMarine_Board | iMarine Board]]''' is a key mechanism for guaranteeing constant interactions with the EA-CoP initiatives involved in the project. This board is described through a number of pages:
  
The '''iMarine Business Cases''' combine technical requirements with organizational, political and managerial issues; they specify larger organizational concepts that may be supported by one or more VRE's. The page on business cases describes these from the technology perspective. After all, this is the technical wiki. Other information on organization and operation in support of the Business Cases can be found in the iMarine Board Channel.
+
* the '''[[Ecosystem_Approach_Community_of_Practice:_The_iMarine_Board#Overview | EA-CoP Board]]''' page describes the functioning of this Board;
 +
* the '''[[Ecosystem_Approach_Community_of_Practice:_The_iMarine_Board#Rules_and_Procedures | iMarine Board Rules and Procedures]]''' page describes the regulations and principles supporting the operation of this board;
 +
* the '''[[Ecosystem_Approach_Community_of_Practice:_The_iMarine_Board#Overall_workplan | work plan]]''' page describes the work plans of the scheduled governing board activities; 
 +
* the '''[[Ecosystem_Approach_Community_of_Practice:_Meetings | meetings]]''' page documents the iMarine Board and Advisory Council meetings, and other events organised to support the board's activity including their reports, recommendations and conclusions;
  
The '''cluster collaboration''' describes how the CoP organizes the requirements collection and discussion on high-level topics in a set of organic, but also technological clusters; geospatial, biodiversity, statistics, and semantic technologies all are supported by technologies that overlap in functionality with other clusters, yet are still easily identifiable as falling within one of the clusters.
+
== Outcome ==
  
The '''Milestone page''' here will organize content that relates to the realization of EA-CoP Milestones, and that does not specifically belong to the cluster or requirements sections.  
+
The Outcome of Board’s activities are to be found at the wider level of the EA Community of Practice, and reflect where Board’s outputs have an impact on the wider EA Community of Practice.
  
The '''EA-CoP Discussion page''' will contain different sections on internal meetings, links to documentation, links to relevant iMarine Board Channel sections etc.
+
The Outcome of the Board, and indeed the entire project, activities is documented at the page dedicated to the iMarine [[Ecosystem_Approach_Community_of_Practice:_iMarine_Business_Cases | Business Cases]]

Latest revision as of 08:07, 3 September 2013

This page is dedicated to document the activities of the Ecosystem Approach Community of PracticeA term coined to capture an "activity system" that includes individuals who are united in action and in the meaning that "action" has for them and for the larger collective. The communities of practice are "virtual", ''i.e.'', they are not formal structures, such as departments or project teams. Instead, these communities exist in the minds of their members, are glued together by the connections they have with each other, as well as by their specific shared problems or areas of interest. The generation of knowledge in communities of practice occurs when people participate in problem solving and share the knowledge necessary to solve the problems. (EA-CoPCommunity of Practice.).

It is organised in the following three areas:

  • The iMarine Board area which introduces the board, the rules governing its functioning, the working plan and the meetings;
  • The Overall Workplan section which provides an overview of the iMarine Board identified activities throughout the project life span
  • The Implementation results area which describes the outputs of iMarine Board's activities, namely (i) the results of mediation activities, the Governance mechanisms and policies governing the envisaged infrastructure, the harmonization of systems resulting from the requirements characterising the expected infrastructure, and the validation of delivered products.

The iMarine Board

The iMarine Board is a key mechanism for guaranteeing constant interactions with the EA-CoPCommunity of Practice. initiatives involved in the project. This board is described through a number of pages:

  • the EA-CoP Board page describes the functioning of this Board;
  • the iMarine Board Rules and Procedures page describes the regulations and principles supporting the operation of this board;
  • the work plan page describes the work plans of the scheduled governing board activities;
  • the meetings page documents the iMarine Board and Advisory Council meetings, and other events organised to support the board's activity including their reports, recommendations and conclusions;

Outcome

The Outcome of Board’s activities are to be found at the wider level of the EA Community of PracticeA term coined to capture an "activity system" that includes individuals who are united in action and in the meaning that "action" has for them and for the larger collective. The communities of practice are "virtual", ''i.e.'', they are not formal structures, such as departments or project teams. Instead, these communities exist in the minds of their members, are glued together by the connections they have with each other, as well as by their specific shared problems or areas of interest. The generation of knowledge in communities of practice occurs when people participate in problem solving and share the knowledge necessary to solve the problems., and reflect where Board’s outputs have an impact on the wider EA Community of PracticeA term coined to capture an "activity system" that includes individuals who are united in action and in the meaning that "action" has for them and for the larger collective. The communities of practice are "virtual", ''i.e.'', they are not formal structures, such as departments or project teams. Instead, these communities exist in the minds of their members, are glued together by the connections they have with each other, as well as by their specific shared problems or areas of interest. The generation of knowledge in communities of practice occurs when people participate in problem solving and share the knowledge necessary to solve the problems..

The Outcome of the Board, and indeed the entire project, activities is documented at the page dedicated to the iMarine Business Cases