Ecosystem Approach Community of Practice: iMarine Guidelines and Best Practices

From D4Science Wiki
Revision as of 15:52, 24 September 2013 by Anton.ellenbroek (Talk | contribs) (Introduction)

Jump to: navigation, search

Introduction

For an effective exploitation of 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., EA-CoPCommunity of Practice. users must familiarize with the options. They also need to be made aware of the limits and potential risks of exploiting 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.. This requires that data access and sharing policies as well as software policies are in place. These define the terms and conditions under which 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. services are made available and can be exploited. The actual implementation of these policies require more practical and user oriented description (the “how to”), turned into a set of guidelines where they are compulsory and best practices where they are voluntary rules.

During the first iMarine Board meeting in Rome, March 20-22, the iMarine Board initiated the definition of comprehensive data access and software policies.

Development of Guidelines and Best Practices

The development of the Guidelines and Best Practices will proceed through several interacting work streams:

  • Implement existing EA-CoPCommunity of Practice. Guidelines and Best practices. The EA-CoPCommunity of Practice. already has developed many Guidelines and Best Practices, ranging from complete policy frameworks such as the Ecosystem Approach to Fisheries, to very detailed metadata management or dissemination requirements. These are best aligned with project outputs when respective VREVirtual Research Environment. or other 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. resources supporting EA-CoPCommunity of Practice. needs are in the development pipeline.
  • Adapt resources to meet EA-CoPCommunity of Practice. desiderata. Throughout the entire project life cycle, the development of guidelines and best practices will have to consider the requirements put forward by the EA-CoPCommunity of Practice., but also of the project partners.
  • Research and reflexion on applicable guidelines and best practices outside the project context but in the wider EA-CoPCommunity of Practice. operational framework. This may include guidelines and best practices for:
  1. new models that should be further defined;
  2. existing models that require elaboration;
  3. stakeholders, their contributions, role and responsibilities;
  4. the identification of EA-CoPCommunity of Practice. support needs;
  5. the decision making process after the defining phase and Board involvement.

iMarine Best Practices Development

The Best Practices for the iMarine communities of Practice will evolve around a set of guiding principles agreed upon by the iMarine Board. In order to facilitate the process, first a set of high level and key domain of best practices are identified, each equipped with specific best practices.

The following topical areas describe these focused best practices. The live document, for the time being compiled as a GoogleDoc, contains the latest improvements and can be accessed upon request.

Business Metadata

Metadata formats and standards

Types of CC licenses

Shared data vs. Public data

Derivative products - Secondary use

Data collection

How to Cite