Revision as of 15:22, May 14, 2015

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 place for project documentation, content registration, and document sharing for your project; 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.

@@ Line 1: / Line 1: @@
 ''Back to:'' [[Products and Services]]
+=ESIP Testbed Crash Course=
-== Products and Services Testbed ==
+This section answers basic questions about the ESIP 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. Also see information on [[Past Testbed Tasks]] and the [[ESIP Testbed Crash Course]].
+== 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 place for project documentation, content registration, and document sharing for your project; 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 [http://testbed.esipfed.org/ ESIP Testbed Site] for information on funded Testbed Projects.
-=Current or Ongoing Testbed Activities =
+==Other Current or Ongoing Testbed Activities ==
+=== Amazon Web Services best practices ===
-== 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.
-== Testbed Portal ==
-(Chen Xu, Jing Li, Chaowei Yang)
-The ESIP Testbed needs a more prominent web presence, both for visibility to the ESIP community, but also for easy access and eventual utility of community as well.  The development team was tasked with developing a Testbed portal component in drupal that can be easily dropped into the latest ESIP portal.
-Ultimate Benefit: Allow ESIP members to interact with hosted testbed activities and testbed task developers, and make ESIP testbed activities more visible to the public.
-:''Comments:''
-== Discovery Services and Clients ==
-(Christine White)
-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).
-This testbed registers several Federation datasets to multiple naming conventions to evaluate the practical differences between them.
-* There is more information about this task provided here using a template for the [[media:StateOfTheArt_ESIP_Discovery_Testbed-20120307rev1.pdf | "ESIP State of the Art" documentation]]
-Ultimate Benefit:
-:''Comments:''
-== Data and information Quality ==
-(Abdelmounaam Rezgui, Zhipeng Gui, Min Sun, Chaowei Yang)
-An automatic classification/annotation system that assesses, monitors, and accurately reports on the quality of ESIP data and services.  The project will include: (1) a quality model and classification engine that will establish a set of quality metrics for data and services.  The engine will automatically derive the quality of ESIP products and services, (2) the effort will also work on metadata quality which is not usually addressed, and (3) the activity will take into account feedback from users to help rate quality of data and services.
-Ultimate Benefit:
-:''Comments:''
-== Re-usable Metadata Editor ==
-(Jerry Yun Pan, Nigel Banks) <br>
-Develop a generic, reusable software system to facilitate the support for multiple metadata standards and their variations.  THe tool will be flexible and reusable for multiple metadata standards, and allows an administrator to design and tailor the metadata authoring tool/editor according to the targeted metadata schema without writing new code.  The core of the tool suite consists of two parts: (1) a designing tool for "super" users who are responsible for designing the metadata editors, and (2) a rendering engine that makes use of a pre-made metadata editor definition.  The designing tool defines a metadata editor based on user inputs and saves the definition for reuse.  The rendering engine makes use of the definitions to facilitate metadata authoring and editing.  The "editor-of-editors" is schema driven.  The design tool allows for the selection of a subset of a whole schema (a "profile") to form an editor, or the selection of an extension of a schema.  The editor definitions can be exported and shared among multiple installations.
-Ultimate Benefit: : A general purpose metadata authoring and editing tool that is easily shareable across organizations.  The code is open source for free use.
-''Comments:''
-== Data Stewardship ==
-(Greg Janee and Nancy Hoebelheinrich)
-The  datasets  to  be  addressed  will  include  a  relatively  simple  image   collection  and  a  second  containing  granule-‐level  data  objects  such  as  a  longtime  series  from   multiple  sensors  /  satellites.  The project tasks include:     (1) Preparing,  transforming  and  performing  quality  control  tasks  on  the  metadata  for  each   dataset  in  a  storage  environment  that  can  be  queried,  and  appended  to  add  the  identifiers   from  each  scheme  to  each  entity  in  the  two  datasets,   (2) Map  the  existing  metadata  for  each  dataset  into  the  metadata  requirements  for  each   identifier  scheme  for  the  purposes  of  identification  and  citation,  (3) Track  and  discuss  the  implementation  issues  associated  with  each  task  per  the  questions   previously  identified  by  the  Data  Stewardship  &  Preservation  cluster  (see  the  initial  list  on   the  ESIP  wiki  at:     http://wiki.esipfed.org/index.php/Implementation_Issues_to_be_addressed  ),  and  others  as   they  arise, (4) Bring  implementation  issues  to  the  Data  Stewardship  cluster  as  needed  for  discussion   and  resolution/decision,   (5) Develop  list  of  practical  considerations  for  each  identifier  scheme, and (6)    develop  draft  set  of  best  practices  for  discussion  at future ESIP  Federation meetings.
-Ultimate Benefit: Provides a reference implementation/example of mapping dataset metadata requirements for the purpose of identification and citation.
-:''Comments:''
-== Testbed FY 2011 Proposal Effort ==
-The Products and Services committee submitted a proposal for new Testbed activities to the ESIP Finance and Appropriations Committee for suggested funding of the efforts.  The proposal is available for review here <b> [[Media:Pstestbed11rev9.doc | (doc)]] and [[Media:Pstestbed11rev9.pdf | (pdf)]]</b>  .
-The funding proposal was approved so below is the Request for Proposal solicitation to all ESIP members to encourage proposals for participation in building the new Testbed functionality.
-<b> [[Media:Testbed_RFP.pdf‎ | (pdf)]] </b>
-The Testbed Configuration Board decided Task 1 (Testbed Portal Development) needed to be kept more focused on the Drupal development of a site that would integrate with the ESIP portal, so it has been re-drafted and sent back out for new responses.  The revised RFP for Task 1 is here: <b> [[Media:Task1-rewrite-final.pdf | (pdf)]]. </b>

Difference between revisions of "Testbed"