Build 15.0 Plan

The Planetary Data System (PDS) is a long-term archive of digital data products returned from NASA’s planetary missions, and from other kinds of flight and ground-based data acquisitions, including laboratory experiments. But it is more than just a facility - the archive is actively managed by planetary scientists to help ensure its usefulness and usability by the world wide planetary science community.

The following page outlines the planned PDS software enhancements, bug fixes, and impacted requirements for the upcoming Build .

A more detailed breakdown of these tasks by date and priority can be found in our Zenhub Roadmap (login required).

Key Dates

Key Dates for Discipline Nodes
Date	Name	Responsible Party	Description
08/13/24	SCR Freeze Date	DDWG	Freeze date for identifying SCRs to be implemented in this release.
08/22/24 - 10/03/24	Standards Documents Updates Due	Document Authoring Team	Updates to PDS4 standards documents due to EN for review.
10/24/24 - 11/14/24	Beta Testing Period	DNs, IPDA	Changes to PDS4 IM and system components available for beta testing.
10/24/24 - 11/14/24	dLDD Integration and Test	dLDD Stewards	Auto-generated dLDDs should be reviews by dLDD Stewards, and final updates to dLDDs should be completed during this time.
10/24/24 - 11/14/24	Standards Documents Review Due	Document Review Team	Review updates to PDS4 standards documents.
12/05/24	System Release	EN	PDS4 system is operationally deployed and website is updated accordingly.

Key Dates for Engineering Node
Date	Name	Description
09/12/24	Delivery to I&T	The PDS4 IM and all software updated during this build cycle are delivered to EN I&T.
10/03/24	Test Readiness Review (TRR)	PDS EN internal review to verify readiness to enter I&T phase.
12/03/24	Delivery and Deployment Review (DRR)	PDS internal review with PDS Software Working Group to verify readiness to deploy build system.
12/05/24	Operational Deployment	PDS4 system is operationally deployed and website is updated accordingly.

For a more detailed schedule, see https://pds-engineering.jpl.nasa.gov/content/schedules.

Planned PDS4 Information Model Changes

This section details the planned changes to the PDS4 Information Model for this build. These changes are deliverables by the PDS Data Design Working Group (DDWG) to the Engineering Node for implementation.

Planned Software Changes

This section details the planned software changes for this build.

Planned tasks for the next release cycle are grouped by software component, and sub-tasks are included where known at the time of this plan generation. Each section also includes additional information, such as:

Software description
Link to 🔍 User Guide
Link to 💻 Github Repo
Link to 🚑 Issue Tracking
Link to 📒 Backlog - future work not planned for this release cycle

Don’t see the tool you are looking for? This means there is no active development planned for this build cycle. Head to the PDS Tool Registry to see all possible tools available for PDS data.

Have a new feature or tool you think we should be working on? Create a ticket in the applicable Github repo or in our PDS EN Operations repo and we will see how that can fit into our plans moving forward.

validate

Validates PDS4 product labels, data and PDS3 Volumes

validate#696 Use New Registry API for Context Product Validation
- validate#592 As a user, I want to when a context product has been deprecated
- validate#675 Cutover to using new Registry API for generating context products json
validate#832 Review Handling of Special Constants and Field Formats
- validate#816 As a user, I want a WARNING to be thrown when a delimited or character table value does not match the expected field_format
- validate#817 As a user, I want an ERROR to be thrown when a character table value does not match the expected validation_format
- validate#831 validate incorrectly handles special constant high_instrument_saturation
- validate#837 In text tables, validate attempts to match pattern associated with data_type before checking Special_Constants
- validate#849 Validate stalls when validating collection inventory file with duplicates records

pds4-information-model

The software tools and data necessary for generating the Information Model including PDS4 ontology, data, and information model.

pds4-information-model#701 Initial Implementation of Cucumber Framework for PDS4 IM Repo
- pds4-information-model#714 Initial Implementation of Cucumber Framework for LDDTool Tests
- pds4-information-model#715 Initial Implementation of Cucumber Framework for Information Model / SCRs
pds4-information-model#728 B15.0 SCR Freeze
pds4-information-model#729 B15.0 Standards Documents Updates
pds4-information-model#730 B15.0 Information Model Delivery to I&T
pds4-information-model#731 B15.0 Information Model SCR Implementation
pds4-information-model#732 B15.0 Planetary Systems Target Ontology: Rings, Satellites Small Bodies Phase 1

harvest

Standalone Harvest client application providing the functionality for capturing and indexing product metadata into the PDS Registry system (https://github.com/nasa-pds/registry).

harvest#131 Enhance support for searching lid/lidvid references
- harvest#127 ref_lid_* fields are not added to the Registry schema prior to load

software-issues-repo

Issue tracking repository as a centralized entry point for general PDS software bugs and feature requests.

software-issues-repo#97 B15.0 Bi-Annual Triage CodeQL Static Code Analysis Scan Results

portal-wp-tasks

PDS Web Design System

portal-wp-tasks#57 Phase 1: Bundle/Collection Landing Pages Modules Implementation
portal-wp-tasks#58 Phase 1: Search Results Page Module Implementation
portal-wp-tasks#60 Phase 1: Investigation Landing Page Module Implementation
- wds-react#1 Create Hero Component
- wds-react#3 Create spacecraft selection component
- wds-react#4 Create tab bar component
- wds-react#13 Keep Exploring, Card Variant
- wds-react#14 Landing Page Hero
- wds-react#15 Landing Page List Content
- wds-react#16 Landing Page Sort Table Content
- wds-react#17 Landing Page Tag List Content
- wds-react#18 Landing Page Text Content
- wds-react#19 Latest News and Data Releases
- wds-react#20 Local Nav (“Interior Page Jump Links”)
- wds-react#21 Recent Publications
- wds-react#22 Spacecraft Breaker (formerly “Quick Actions”)

operations

Tickets for the PDSEN Operations Team

operations#424 Add Data Registration Validation and Deep Archive Execution to Nominal Data Release Process

planetary-data-cloud

PDS Cloud Migration documentation, issue, tracking and simple tools for assisting in the PDS hybrid cloud study and migration efforts.

planetary-data-cloud#73 ATLAS MVP: Support Development of Initial Migration Plan and Architecture for ATLAS Survey Data
planetary-data-cloud#80 Develop PDC Tenant Roles and Shared Responsibility Model
planetary-data-cloud#100 Phase 2 Migration of Existing Production JPL AWS Infra to MCP
- planetary-data-cloud#95 Create baseline IAM policies for AWS resources in MCP
- portal-tasks#89 Migrate pdscloud-* instances and pds.nasa.gov on MCP
- planetary-data-cloud#97 Set up appropriate policies for Dev/Test/Prod environments
- planetary-data-cloud#98 Migrate data and users from JPL AWS to MCP

devops

Parent repo for PDS DevOps activities

devops#69 Phase 2: Develop CI/CD for NPM/React projects
- wds-react-legacy#95 Setup NPM Audits as part of CI on React projects
- devops#62 Develop Branch Testing Github Action
- devops#64 Develop Stable GitHub Action CI/CD to I&T production venue
- devops#65 Develop PR Review GitHub Action CI/CD to Developer Staging venue
- devops#66 Develop Initial Architecture and Action Flow for React CI/CD Deployments

nucleus

Nucleus is a software platform used to create workflows for the Planetary Data (PDS).

nucleus#54 Validate and Load all PDS4 MESSENGER data products with Nucleus
nucleus#91 Implement Warm Backup Storage Solution (Data Backup Plan)
- planetary-data-cloud#75 As a user, I want a warm backup of my archive data to be available in the event of corruption of of primary archive data
- nucleus#73 As a user, I want to store a copy of my archive data in AWS Deep Archive / Glacier
nucleus#92 Pilot project with IMG processing using Nucleus
nucleus#93 CSS MVP: Deploy Baseline Nucleus for Catalina Sky Survey in Test and Production Environments
- nucleus#73 As a user, I want to store a copy of my archive data in AWS Deep Archive / Glacier
- nucleus#89 Deploy Nucleus in Test env
- nucleus#90 Deploy Nucleus in Production env
- nucleus#94 Remove data from staging S3 bucket at the end of PDS basic use case
- nucleus#95 Remove data from EFS at the end of PDS basic use case

registry

PDS Registry provides service and software application necessary for tracking, searching, auditing, locating, and maintaining artifacts within the system. These artifacts can range from data files and label files, schemas, dictionary definitions for objects and elements, services, etc.

registry#181 Support Registration and Search of Products Replicated Across Archives
- registry-api#306 If >1 products with the same LIDVID are registered by different nodes, we should respond with one of them
- registry#245 As a user, I want to register data product(s) that is mirrored across 2 or more organizations
registry#230 Enable Support for Changing Field Types
registry#266 Implement design for alternate data file paths
- registry#86 As a user, I want to harvest and register alternate data file paths
- registry#96 As a user I want to change the file paths of products in the registry
- harvest#123 As a Node Operator, I want to specify an alternate file paths for 1 or more archive products
- registry-mgr#76 As a user, I want to manually update a product’s file location (file_ref)

registry-api

Web API service for the PDS Registry, providing the implementation of the PDS Search API (https://github.com/nasa-pds/pds-api) for the PDS Registry.

registry-api#285 Implement Faceting
- registry-api#283 As a client developer, I want to facet on 1 or more fields in the registry
- registry-api#284 As an API user, I want to know the unique values for a specific API field.
- registry-api#323 As a user, I want the /properties endpoint to display counts for products having each property
- registry-api#324 As a user, I want the /properties endpoint to display range/enum type and values for each property
- registry-api#325 As a user, I want the /properties endpoint to include a link to explanatory documentation (i.e. DD or similar)

data-upload-manager

Data Upload Manager (DUM) component for managing the interface for data uploads to the Planetary Data Cloud from Data Providers and PDS Nodes.

data-upload-manager#51 Add User-Defined Object Metadata
- data-upload-manager#50 As a user, I want to include a MD5 checksum in the the user-defined object metadata being sent in the upload payload
- data-upload-manager#87 As a user, I want to include the modification datetime in the the user-defined object metadata being sent in the upload payload

Other Information

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

See individual applications for specific dependencies and system requirements.