Receivables

The expected receivables for the system and the applicable party responsible for the delivery.

The following outlines the Software Change Requests:

• Deliverer: DDWG / CCB
• Date: 08/28/2020

SCRs:

• pds4-information-model#159 - CCB-209: Correct Definitions of Tagged_*_Object
• pds4-information-model#160 - CCB-273: Remove permissible values from id_reference_type
• pds4-information-model#161 - CCB-276: Implement Query Models – Phase 2
• pds4-information-model#162 - CCB-281: Make File_Area_Observational nillable in Product_Observational
• pds4-information-model#163 - CCB-282: Naming Rule Inconsistencies for Directories and Bundle and Collection Products
• pds4-information-model#164 - CCB-283: Add reference_type value document_to_data
• pds4-information-model#165 - CCB-284: Streamline process for adding or removing standard values.
• pds4-information-model#166 - CCB-285: GeoTIFF format as operational PDS4 image
• pds4-information-model#117 - CCB-222: Add citation_text to Citation_Information

Deliverables

None

Milestone Reviews

Pds4 Ldd Issue Repo

Documentation: https://github.com/pds-data-dictionaries/PDS4-LDD-Issue-Repo/

Validate

Documentation: https://nasa-pds.github.io/validate/

Pds4 Jparser

Documentation: https://nasa-pds.github.io/pds4-jparser/

PDS4 Information Model

Documentation: https://nasa-pds.github.io/pds4-information-model/

Registry

Documentation: https://nasa-pds.github.io/pds-registry-app

Harvest

Documentation: https://nasa-pds.github.io/pds-registry-app

Pds Deep Archive

Documentation: https://nasa-pds.github.io/pds-deep-archive/

Pds Doi Service

Documentation: https://github.com/NASA-PDS/pds-doi-service/

Pds Registry App

Documentation: https://nasa-pds.github.io/pds-registry-app/

Pds.Nasa.Gov Search

Documentation: None

Pds Api App

Documentation: None

Purpose

Overview

The primary objectives of this release are:

• Development of new and improved search interface and search services.
• Improvements and bug fixes to existing PDS4 Stewardship Software components.
• Improvements and bug fixes to existing PDS4 Infrastructure Software components.

See the Planned Software Changes section for more details.

Reference Documents

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

• PDS Level 1, 2 and 3 Requirements, April 20, 2017.
• PDS4 Project Plan, July 17, 2013.
• PDS4 System Architecture Specification, Version 1.3, September 1, 2013.
• PDS4 Operations Concept, Version 1.0, September 1, 2013.
• PDS General System Software Requirements Document (SRD), Version 1.1, September 1, 2013.
• PDS Harvest Tool Software Requirements and Design Document (SRD/SDD), Version 1.2, September 1, 2013.
• PDS Preparation Tools Software Requirements and Design Document (SRD/SDD), Version 0.3, September 1, 2013.
• PDS Registry Service Software Requirements and Design Document (SRD/SDD), Version 1.1, September 1, 2013.
• PDS Report Service Software Requirements and Design Document (SRD/SDD), Version 1.1, September 1, 2013.
• PDS Search Service Software Requirements and Design Document (SRD/SDD), Version 1.0, September 1, 2013.
• PDS Search Scenarios, Version 1.0, September 1, 2013.
• PDS Search Protocol, Version 1.2, March 21, 2014.
• PDAP Search Protocol, Version 1.0, March 21, 2014.
• PDS Security Service Software Requirements and Design Document (SRD/SDD), Version 1.1, September 1, 2013.
• PDS NSSDC Delivery Software Requirements and Design Document (SRD/SDD), Version 0.1, October 29, 2019.

Preferred Environment Overview

Java Runtime Environment

Many of the components developed by PDS Engineering Node require Java Runtime Environment (JRE). The software was specifically compiled for and tested with Java version 1.8, however, other versions may still work, dependent upon the component.. The following commands test the local Java installation in a UNIX-based environment:

          % which java
          /usr/bin/java
          
          % java -version
          java version "1.8.0_101"
          Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
          Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
        

The first command above checks whether the java executable is in the environment's path and the second command reports the version. If Java is not installed or the version is not at least 1.8, Java will need to be downloaded and installed in the current environment. Consult the local system administrator for installation of this software. For the do-it-yourself crowd, the Java software can be downloaded from the Oracle Java Download page. The suggested software package is the Java Standard Edition (SE) 8, either the JDK or the JRE package. The JDK package is not necessary to run the software but could be useful if development and compilation of Java software will also occur in the current environment.

Java Application Server

The other main system requirement pertains to providing a Java application server for hosting certain components (e.g., Registry, etc.). The suggested application server for this release is Apache Tomcat with a minimal version of 7.0.X. Version 8.5.X is also supported in this release. Consult the local system administrator for installation of this software. For the do-it-yourself crowd, see the Tomcat Deployment document for installation and configuration details.

Web Server

The installation of a web server to act as a front-end interface to the Java application server is desired. The suggested web server for this release is the Apache HTTP Server. Consult the local system administrator for installation of this software. For the do-it-yourself crowd, the Apache HTTP Server software can be downloaded from the Apache HTTP Server page.