Built by Maven

Release Plan - Build 10.1.0

Key Dates

Receivables

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

Receivable Deliverer Date
CCB-138 - Mismatch between context object types and values of <type> in <Observing_System_Component> class DDWG 02/14/2020
CCB-204 - Define and enforce best practices for discipline and project dictionaries DDWG 02/14/2020
CCB-209 - Correct Definitions of Tagged_*_Object DDWG 02/14/2020
CCB-212 - Add Modification_History to Ingest_LDD DDWG 02/14/2020
CCB-220 - Add ability to specify many source products via table DDWG 02/14/2020
CCB-222 - Add citation_text to Citation_Information DDWG 02/14/2020
CCB-255 - Namespace version dependencies are not documented in the Information Model. DDWG 02/14/2020
CCB-260 - PDS4 label files do not have a unique file extension DDWG 02/14/2020
CCB-268 - Add optional attribute to class <Terminological_Entry> DDWG 02/14/2020

Deliverables

None

Milestone Reviews

Review Date
Test Readiness Review (TRR) TBD
Delivery and Deployment Review (DDR) TBD

Planned Software Changes

This section details the planned software changes for this build.

Don't see the tool you are looking for? This means there is no active development planned for this build cycle.

Have a new feature or tool you think we should be working on? Create a ticket in the applicable Github repo or email us at pds-operator@jpl.nasa.gov and we can work to see if this fits into our priorities.

PDS API Server

Documentation:

Improvements

Defects

  • None

Validate

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

Improvements

  • validate#56 - Validate that Table_Character/Table_Binary fields match the field length definitions in the label
  • validate#87 - Update validate to apply catalog file and local schemas to discipline schema resolution
  • validate#30 - Enhance content validation to decrease validation time to <=50% of current benchmark
  • validate#51 - Provide the capability to specify multiple locations for pds4.bundle validation
  • validate#63 - Validate Table_Character groups and their specified lengths match the specified group_length
  • validate#132 - Add validated product counter to pass/fail reporting and end summary
  • validate#10 - Check that the LID for a collection product has the LID of its parent bundle as its base
  • validate#29 - Improve pds4.bundle validation performance
  • validate#123 - Enhance validate performance to average <1 second with content validation enabled
  • validate#124 - L5.PRP.VA.42 The tool shall average less than 1 second execution time when content validation is disabled.
  • validate#7 - Update to support ComplexLSB8 data types and investigate Floating point exception
  • validate#69 - Verify all context objects specified in observational products are referenced in the parent bundle/collection Reference_List

Defects

  • validate#9 - Update content validation to fail when the value of an ASCII_Integer is all spaces

Registry

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

Improvements

  • registry#5 - Revise Next Gen Registry and Search requirements
  • registry#9 - Enhance weighting and expected search results per Search UI upgrades

Defects

  • None

PDS4 Information Model

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

Improvements

Defects

Harvest

Documentation:

Improvements

Defects

  • None

Generate

Documentation: https://pds-engineering.jpl.nasa.gov/development/pds4/current/preparation/generate/index.html

Improvements

Defects

  • None

DOI Service

Documentation: None

Improvements

  • doi-service#1 - Develop initial requirements and design for DOI Service

Defects

  • None

GEO Data Services Pilot

Documentation: None

Improvements

Defects

  • None

AIP Gen

Documentation: None

Improvements

  • aip-gen#13 - Open Source NSSDCA Interface Software
  • aip-gen#3 - Develop design and requirements for aip-gen software
  • aip-gen#1 - Implement SIP generation offline capabilities
  • aip-gen#15 - Document SIP Gen component into Node Delivery procedures
  • aip-gen#18 - Test SIP Gen with NSSDC

Defects

  • None

Search UI

Documentation: None

Improvements

  • search-ui#11 - Improve UI to work with PDS Integrated Search API (Phase 1)
  • search-ui#5 - Improve UI to work with PDS Integrated Search API (Phase 2)
  • search-ui#10 - Initial integration with Search UI: Link to SBN-PSI
  • search-ui#12 - Alpha release and user testing improvements

Defects

  • None

Other Information

Purpose

The purpose of this document is to describe the scope and schedule for PDS4 System Release v10.1.0.

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.

System Requirements, Dependencies, and Assumptions

This section details the high-level system requirements for installing and operating a majority of the software released by PDS Engineering Node. Due to the varying requirements and technologies used by the tools, specific system requirements for each component can be found in their respective Installation documents. Additionally, explicit software dependencies and libraries can also be found in each individual software component.

Preferred Environment Overview

Product Version
Java Runtime Environment 1.8.x
Apache Tomcat 7.x or 8.x
Apache Web Server 2.x

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.

Engineering Node Software Catalog

The following list links to all of the software components currently being maintained and operated by the PDS Engineering Node as of the deployment of this build.