Difference between revisions of "Testbed"

From Earth Science Information Partners (ESIP)
(→‎What resources are provided to Testbed projects?: added GitHub repository, and clarified the testbed portal is the Drupal repository)
 
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
''Back to:'' [[Products and Services]]
 
''Back to:'' [[Products and Services]]
 +
=ESIP Testbed Crash Course=
 +
This section answers basic questions about the ESIP Testbed.
 +
== What is the ESIP Testbed? ==
 +
The ESIP Testbed was developed as a framework for moving Earth science ideas and projects (software, data, etc…) through a development life cycle. The Testbed facilitates collaboration and innovation across all sectors of the ESIP Federation improving the availability, access, and mutual benefit of new technologies.
 +
== What resources are provided to Testbed projects? ==
 +
ESIP supports Testbed projects at each stage of the development life cycle in accordance with established best practices including, but not limited to:
 +
* Technology assessment appropriate to each stage of the development life cycle;
 +
* Assessment of project value to Earth Science community;
 +
* Match-making with other projects/ESIP groups/opportunities;
 +
* Solicitation of feedback from the ESIP Community;
 +
* Breakout sessions at the twice-annual ESIP meetings for planning, feedback and presentation of your work, and other project-related meetings;
 +
* Cloud computing infrastructure (within budget constraints);
 +
* Access to the Testbed Portal (testbed.esipfed.org), a site based on Drupal for project documentation, content registration, and document sharing for your project;
 +
* Access to the GitHub repository (github.com/esipfed), a project repository that provides basic management and wiki capability; and
 +
* Development funds.
  
== Products and Services Testbed ==
+
== How does a project benefit from going through the Testbed? ==
'''Objectives''': Provide a test environment where prototype standards, services, protocols, and best practices can be explored and evaluated.  The testbed serves as a forum for innovative collaborations across all sectors of the Federation to improve availability and access to our member products and services for mutual benefit. Comments about each testbed activity can be shared on this page.
+
ESIP provides Testbed projects with domain-specific expert input, visibility, and validation within the ESIP and Earth science communities.
 
+
== What types of projects can enter the Testbed? ==
== Testbed Task 1: Expert Skills Database ==
+
The Testbed is currently accepting projects in the Incubation stage of the development life cycle, i.e. projects in the realm of good ideas ready to move beyond the proof-of-concept stage. The Testbed will soon support projects at the Prototype stage.
The Federation collectively includes an exceptionally wide range of expertise among its participating members. These expert skills of Federation members will be categorized in a knowledge base and offered as a service. We use the master ESIP email list of over 700 names and Drupal tools to enable any member to associate their name to a skill and associated expertise level. Currently, the skill list consists of 60 information technology (IT) skills, but members can add additional categories. A GUI enables users to search this skill list by multiple criteria.
+
== How can a project enter the Testbed? ==
http://www.esipfed.org/expert
+
The ESIP Testbed is managed by the Products & Services (P&S) committee. The P&S committee will release periodic requests for proposals (RFP) for projects to enter the Testbed.  The Testbed Configuration Board decides which projects will enter the Testbed and at what stage.
Ultimate Benefit: Promotion of expert skills available within the Federation.
+
= Current and Past Testbed Tasks =
:''Comments:''
+
See [[Past Testbed Tasks]] and the [http://testbed.esipfed.org/ ESIP Testbed Site] for information on funded Testbed Projects.
 
+
 
 
+
==Other Current or Ongoing Testbed Activities ==
== Testbed Task 2: Unique Data Identifiers ==
+
=== Amazon Web Services best practices ===
The Preservation and Stewardship Cluster and the NASA Technology Infusion Working Group have been considering permanent naming schemes for data products http://wiki.esipfed.org/index.php/Preservation_and_Stewardship.  These identifiers can serve as references in journal articles and must include versioning representations.  Many naming options have been promoted, but the best choices for Earth science data require careful examination.  Two datasets may differ only in format, byte order, data type, access method, etc., creating facets (dimensions) not relevant to classification schemes for books (Library of Congress, Dewey Decimal).
+
ESIP has opened an Amazon Web Services account that can be leveraged to provide virtual instances for accessing the testbed projects. In an effort to save pain and share experiences, please read and contribute to the [[ESIP Testbed Amazon Web Services Best Practices]] topic if you are going to work on the Amazon instances or have and want to contribute insight.
This testbed registers several Federation datasets to multiple naming conventions to evaluate the practical differences between them.
 
Ultimate Benefit: Permanent, unique names for data Federation data products.
 
:''Comments:''
 
 
 
From Nancy Hoebelheinrich:
 
I think the more precise term is "identifier" rather than "naming" schemes.  I suggest the following paragraph be used for this Task description:
 
 
 
The Preservation and Stewardship Cluster and the NASA Technology Infusion Working Group have been considering permanent identifier schemes for data products http://wiki.esipfed.org/index.php/Preservation_and_Stewardship.  These identifiers can serve as references in journal articles as well as inventory nodes in data archives and must include representations for versions of the entity being identified.  Many identifier options have been proposed for different kinds of data, but the best choices for Earth science data require careful examination.  For example, two datasets may differ only in format, byte order, data type, access method, etc., creating distinctions between them that may not be addressed adequately by identifier schemes used for typical "published" items such as books and journals.  Last year's activity included a recommendation on identifier schemes to use for Earth Science data, but did not address the implementation issues that arise with the identifier schemes considered.  The next Task for this work is to examine several different kinds of Federal datasets, assign identifiers from up to nine identifier schemes considered in the previously mentioned paper,  evaluate and compare the implementation implications and other practical considerations associated with the use of each identifier scheme applied, and develop recommendations. Practical considerations may include the need to integrate with other metadata schemes such as ISO, and application to data citation formats and practices. 
 
 
 
Ultimate Benefit: Permanent, unique names for Federation data products and recommendations for practice based on testbed experience.
 
 
 
== Testbed Task 3: Semantic Registration of Data and Services ==
 
The Semantic Web Cluster has been developing ontologies for Data Service, Data types, and science concepts http://wiki.esipfed.org/index.php/Data_Service_Ontologies.  The testbed enables providers to register their products and services semantically, which will provide more precise descriptions of their offerings.  
 
Ultimate Benefit: Better classification and discovery of specialized Federation products and services
 
:''Comments:''
 
 
 
 
 
== Testbed Task 4: Application-Specific Portals ==
 
The Air Quality Working Group has been developing an inventory of air quality data and data services.  Other GEOSS Societal Benefit Areas could benefit from a similar capability to highlight offerings from Federation members.  For this task, the Air Quality has been cloned for use by other application areas. Initially, a Water portal has been developed.
 
Ultimate Benefit: Better marketing of targeted Federation products and services.
 
:''Comments:''
 
 
 
== Testbed FY 2011 Proposal Effort ==
 
The Products and Services committee plans to submit a proposal for new Testbed activities to the ESIP Finance and Appropriations Committee for suggested funding of the efforts.  Please review and comment on the <b>release candidate of the 2011 Proposal [[Media:Pstestbed11rev7.doc | (doc)]] and [[Media:Pstestbed11rev7.pdf | (pdf)]]</b>  .  If approved the P&S committee would the release a solicitation to all ESIP members to encourage proposals for participation.
 
:''Comments:''
 
 
 
'''Tyler:'''
 
<br>
 
In regards to the testbed activity on Data and Information Quality, we should work with the Information Quality cluster, because they are working on similar quality related activities.
 
 
 
In regards to the testbed activity on Metadata for Customized Product-Services, we should consider how these metadata will conform and be compatible with ISO. The federal agencies will have to conform and/or translate their metadata to ISO when describing their data and services.
 
 
 
'''Ken:'''
 
<br>
 
Also waiting for input from the Semantic Web cluster.  I will try to track contact with the Information Quality cluster.
 
 
 
'''Ken:'''
 
<br>
 
The Discovery cluster has ideas for testbed activity related to federated discovery technologies, e.g. open search, data/service/info casting.  Hook Hua is working on a brief description.
 

Latest revision as of 10:16, July 17, 2015

Back to: Products and Services

ESIP Testbed Crash Course

This section answers basic questions about the ESIP Testbed.

What is the ESIP Testbed?

The ESIP Testbed was developed as a framework for moving Earth science ideas and projects (software, data, etc…) through a development life cycle. The Testbed facilitates collaboration and innovation across all sectors of the ESIP Federation improving the availability, access, and mutual benefit of new technologies.

What resources are provided to Testbed projects?

ESIP supports Testbed projects at each stage of the development life cycle in accordance with established best practices including, but not limited to:

  • Technology assessment appropriate to each stage of the development life cycle;
  • Assessment of project value to Earth Science community;
  • Match-making with other projects/ESIP groups/opportunities;
  • Solicitation of feedback from the ESIP Community;
  • Breakout sessions at the twice-annual ESIP meetings for planning, feedback and presentation of your work, and other project-related meetings;
  • Cloud computing infrastructure (within budget constraints);
  • Access to the Testbed Portal (testbed.esipfed.org), a site based on Drupal for project documentation, content registration, and document sharing for your project;
  • Access to the GitHub repository (github.com/esipfed), a project repository that provides basic management and wiki capability; and
  • Development funds.

How does a project benefit from going through the Testbed?

ESIP provides Testbed projects with domain-specific expert input, visibility, and validation within the ESIP and Earth science communities.

What types of projects can enter the Testbed?

The Testbed is currently accepting projects in the Incubation stage of the development life cycle, i.e. projects in the realm of good ideas ready to move beyond the proof-of-concept stage. The Testbed will soon support projects at the Prototype stage.

How can a project enter the Testbed?

The ESIP Testbed is managed by the Products & Services (P&S) committee. The P&S committee will release periodic requests for proposals (RFP) for projects to enter the Testbed. The Testbed Configuration Board decides which projects will enter the Testbed and at what stage.

Current and Past Testbed Tasks

See Past Testbed Tasks and the ESIP Testbed Site for information on funded Testbed Projects.

Other Current or Ongoing Testbed Activities

Amazon Web Services best practices

ESIP has opened an Amazon Web Services account that can be leveraged to provide virtual instances for accessing the testbed projects. In an effort to save pain and share experiences, please read and contribute to the ESIP Testbed Amazon Web Services Best Practices topic if you are going to work on the Amazon instances or have and want to contribute insight.