Built by Maven

Release Description 1.0.0

This release of the PDS4 System represents Build 1 and is intended as a prototype release in support of the assessment of the PDS4 standards. The following sections can be found in this document:

Reference Documents

This section details the controlling and applicable documents referenced for this release. The controlling documents are as follows:

  • Planetary Data System (PDS) Level 1, 2 and 3 Requirements, March 26, 2010.
  • Planetary Data System (PDS) 2010 Project Plan, February 2010.
  • Planetary Data System (PDS) 2010 System Architecture Specification, Version 1.1, May 5, 2010.
  • Planetary Data System (PDS) 2010 Operations Concept, February 2010.
  • Planetary Data System (PDS) General System Software Requirements Document (SRD), Version 0.1, September 27, 2010.
  • Planetary Data System (PDS) Harvest Tool Software Requirements and Design Document (SRD/SDD), Version 0.4, September 28, 2010.
  • Planetary Data System (PDS) Preparation Tools Software Requirements and Design Document (SRD/SDD), Version 0.1, October 6, 2010.
  • Planetary Data System (PDS) Registry Service Software Requirements and Design Document (SRD/SDD), Version 0.6, September 28, 2010.
  • Planetary Data System (PDS) Report Service Software Requirements and Design Document (SRD/SDD), Version 0.7, September 28, 2010.
  • Planetary Data System (PDS) Security Service Software Requirements and Design Document (SRD/SDD), Version 0.6, September 28, 2010.

The applicable documents are as follows:

  • NASA Planetary Data System (PDS) 2010 System Build I Test Plan

Capabilities

This section details the new, modified and corrected capabilities that comprise this release. They are summarized here for a system-level view. A more detailed list of capabilities can be found in the release notes and change logs for each component. Since this is essentially the first release, all of the capabilities are considered new. They are as follows:

  • Ingestion Subsystem
    • Provide the Registry Service for registration and retrieval of product metadata (e.g., bundles, collections, data, documents, etc.), associations and services.
    • The Registry Service provides a REST-based interface for interacting with the service over HTTP.
    • Provide the Harvest Tool for crawling product collections, extracting metadata from product labels and registering discovered products with the Registry Service.
    • Provide the Registry User Interface for browsing products and associations registered with the Registry Service.
    • Provide the Security Service for controlling access to specific interfaces.
    • Provide the Report Service for gathering and reporting on metrics.
  • Data Provider Tool Suite
    • Provide the initial Core Library where functions for validating product labels reside.
    • Provide the Validate Tool for validation of products against their associated XML Schemas.
    • Provide Installation and Operation documentation for the recommended Design Tools, Oxygen and Eclipse.

Liens

This section details the liens against the capabilities that have yet to be implemented or are partially implemented. They are summarized here for a system-level view. A more detailed list of liens can be found in the release notes for each component.

  • Need to expand the Registry Service functionality to include registration of federation and registry objects. Also need to expand the query support for objects beyond products and associations.
  • Need to add support for validation of products to the Harvest Tool.
  • Need to expand the Registry User Interface to support browsing of objects beyond products and associations. Also need to add support for updating status and single product registration.
  • Need to correct the issue with defining policy for multiple HTTP methods on the same URL for the Security Service.

System Requirements

This section details the system requirements for installing and operating the software. The custom software contained in this release was developed using Java and will run on any platform with a supported Java Runtime Environment (JRE). The software was specifically developed under Sun Java version 1.6 and has only been tested with this version.

The other main system requirement pertains to providing an application server for hosting certain components (Registry Service, Registry User Interface, Report Service and Security Service). The suggested application server for this release is Apache Tomcat with a minimal version of 6.0.20.

Specific system requirements for each component in this release can be found in their respective Installation documents.

Installation/Operation

This section details the installation and operation of the software in this release. This release is intended for deployment in the Engineering Node operations environment with certain components deployed in the environments of participating Nodes. Details regarding the release for each of these components, including installation of the packages and operation of the associated software, can be found in the documentation for each component. This release is comprised of the following components:

  • Harvest Tool - Release 0.2.0
  • Preparation Tools
    • Core Library - Release 0.1.0
    • Design Tool - Release 0.1.0
    • Validate Tool - Release 0.1.0
  • Registry
    • Registry Service - 0.5.0
    • Registry User Interface - 0.2.0
  • Report Service - 0.1.0
  • Security Service - 0.2.0

EN Environment

This section details deployment to the EN operations environment. The following diagram details the deployment of the major components of this release and gives a very high-level view of the interfaces between the components and system resources:

EN Deployment
If viewing this document in online form, click the image for a larger version.

The above components (web-based) can be found at the following endpoints:

Node Environment

This section details the deployment to a participating Node environment. The following diagram details the deployment of selected components:

Node Deployment

The endpoints for the web-based components are dependent on the Node host machine.