Difference between revisions of "Discovery Testbed Work Plan"

From Earth Science Information Partners (ESIP)
m
Line 5: Line 5:
 
* Compliance should be done for services. Clients will validate their own compliance.
 
* Compliance should be done for services. Clients will validate their own compliance.
 
** on registration, checks for compliance. if yes, then gets registered.
 
** on registration, checks for compliance. if yes, then gets registered.
* To improve impact to Cluster, want others (other than ESRI) in Clusters to contribute to testbed.
+
* To improve impact to Cluster, want others (other than Esri) in Clusters to contribute to testbed.
  
 
=== Hosting environment ===
 
=== Hosting environment ===

Revision as of 18:43, December 13, 2011

Assumptions

  • Solution will be based on the Esri Geoportal Server software, an open source product managed by the Esri SDI Solutions team.
  • Development work will be done by the Esri SDI Solutions team as part of the development to the Esri Geoportal Server product. All development work that results from this project can be included in subsequent releases of the Esri Geoportal Server.
  • Compliance should be done for services. Clients will validate their own compliance.
    • on registration, checks for compliance. if yes, then gets registered.
  • To improve impact to Cluster, want others (other than Esri) in Clusters to contribute to testbed.

Hosting environment

  • The hosting environment for the solution will be identified by the ESIP Discovery Cluster Testbed Configuration Board, and will meet the system requirements as defined by the Esri Geoportal Server Preinstallation documentation.
  • The ESIP Products and Services Committee, ESIP Discovery Cluster, or an ESIP Discovery Cluster member organization will host the testbed instance.

Use Cases

Requirements

  • Requirements for customizations to the Esri Geoportal Server will be identified by the ESIP Discovery Cluster and reviewed with the Esri SDI Solutions team.
  • Requirements will be based upon the description of the work as described in the Testbed RFP.
  • Requirements that are identified as out-of-scope for this project can be addressed in future work by Esri and /or the ESIP Discovery Cluster.
  • Should focus on server-compliance first.
  • The Geoportal shall support ingest of Discovery-compliant endpoint services
  • The Geoportal shall cast out registered services.


Schedule and Milestones

  • Definition of use cases and requirements for customized geoportal.
  • Presentation of prototype based on requirements, by Esri to ESIP Discovery Cluster.
  • Feedback of prototype and iterative updates to geoportal testbed instance.
  • Delivery of customized geoportal distribution to ESIP Discovery Cluster.
  • Participation of Esri and ESIP staff in deployment activities for geoportal on ESIP system.
  • Tech Transfer presentation to ESIP Discovery Cluster on how to use customized geoportal.
  • Testing of deployment by ESIP Discovery Cluster.

Workforce

  • The ESIP Discovery Cluster will identify suitable technical staff to assist Esri staff with the deployment of the Geoportal Server software.
  • The ESIP Discovery Cluster will identify suitable staff to administer the implemented geoportal instance.
  • The ESIP Discovery Cluster will participate in testing the implemented geoportal and providing feedback.
  • Discovery Cluster Technical Staff: the technical person who will help with the deployment of the Geoportal Server on the ESIP system.
  • Discovery Cluster Geoportal Administrator(s): staff that will approve published resources on the Geoportal and make decisions if content is appropriate.
  • The ESIP Discovery Cluster Project Team – define requirements, provide input on prototype, help with testing deployed solution


Out of Scope (future items)