Build 11.1 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

Date

Name

Description

03/19/2021

Delivery to I&T

The PDS4 IM and all software updated during this build cycle are delivered to EN I&T.

04/05/2021

Test Readiness Review (TRR)

PDS EN internal review to verify readiness to enter I&T phase.

05/27/2021

Delivery and Deployment Review (DRR)

PDS internal review with PDS Software Working Group to verify readiness to deploy build system.

06/11/2021

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

User Guide

Github Repo

Issue Tracking

Backlog

Stable Release

Dev Release

  • validate#250 Improvements to meet updated Standards Reference since initial requirements implementation
    • validate#5 Improve file base name check according to Standards Reference

    • validate#6 Improve pds4.bundle unlabeled files check to handle files without a file suffix

    • validate#11 Update allowable field_format values per Standards Reference definition regarding [+|-] characters

    • validate#81 Validate and throw error when duplicate LIDs are found in Bundle

    • validate#153 Update validate to throw error when a file has a space in the filename

    • validate#230 Update validate per SR requirements for collection inventories

    • validate#240 Unexpected error for data collection in a sub-directory

    • validate#242 Update LID validation to meet latest PDS4 SR Requirements

  • validate#249 Improvements for validating accumulating bundles / collections
    • validate#51 Provide the capability to specify multiple locations for pds4.bundle validation

    • validate#231 For accumulating bundles, validate latest version of collections only

    • validate#238 validate does not perform full bundle validation when using a specific bundle.xml

    • validate#246 Add output directory flag to validate-bundle tool

    • validate#256 validate should only do integrity checking on latest version of a collection when referenced by LID


pds4-jparser

Java Library providing APIs for parsing and exporting information on PDS4 products, including table and image objects to various formats including CSV, PNG, VICAR, FITs, etc.

User Guide

Github Repo

Issue Tracking

Backlog

Stable Release

Dev Release


pds4-information-model

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

User Guide

Github Repo

Issue Tracking

Backlog

Stable Release

Dev Release


pds-deep-archive

PDS Open Archival Information System (OAIS) utilities, including Submission Information Package (SIP) and Archive Information Package (AIP) generators

User Guide

Github Repo

Issue Tracking

Backlog

Stable Release

Dev Release


pds-doi-service

Service and tools for generating DOIs for PDS bundles, collections, and data sets

User Guide

Github Repo

Issue Tracking

Backlog

Stable Release

Dev Release


pds-registry-app

Registry application enabling a PDS node to register all its data products for long term preservation and sharing with the rest of the PDS system.

User Guide

Github Repo

Issue Tracking

Backlog

Stable Release

Dev Release



pds-api

PDS API Application with client and server integrated into one package

User Guide

Github Repo

Issue Tracking

Backlog

Stable Release

Dev Release

  • pds-api#31 Streamline testing of API server implementation

  • pds-api#17 Response format conventions and parameter definition
    • pds-api#18 Refine format conventions defined by the API WG

    • pds-api#19 Define default response fields

    • pds-api#20 Define required response fields

    • pds-api#21 Define response formatting for default vs “additional” metadata fields

    • pds-api#22 Update API Spec with refined response format conventions and field definitions

    • pds-api#23 Implement response format definition in API Service

  • pds-api#35 Initial Federated API implementation

  • pds-api#34 Deploy PDS API v0 (beta) for beta testing
    • pds-api#32 Deploy PDS API v0 (beta) on pds-gamma test server

    • pds-api#33 Update public PDS API Spec in Github

  • pds-api#30 SwaggerHub CodeGen Server adaptation and integration how-tos
    • pds-api-pythonlib#1 Test and write a procedure to develop a python implementation from swaggerHub

    • pds-api#26 Document basic adaptation capabilities from pds-api-service

  • pds-api#28 DN Pilot API Project(s)
    • pds-api#16 Implement EN query of DN API service

    • pds-api#26 Document basic adaptation capabilities from pds-api-service

    • pds-api#27 Identify nodes and define scope for piloting pds-api-service adaptation

    • pds-api#29 Implement EN query passing to DN search UI

  • pds-api#24 Define PDS handling of enriched / supplemental metadata

  • pds-api#25 PDS API extension convention for discipline-specific search engines

  • pds-api#15 Query passing and search integration design

  • pds-api#14 Define intra-discipline (product-level) search scope

  • pds-api#12 Initial Query Syntax Lexer Implementation

  • pds-api#7 Initial discipline/node-specific search parameter definition


pdsen-corral

*umbrella project to manage the build cycle (continuous integration and stable release) for the PDS EN tools. *

User Guide

Github Repo

Issue Tracking

Backlog

Stable Release

Dev Release


PDS.nasa.gov-UX

PDS.nasa.gov User Experience Task Issue and Prototype repository

User Guide

Github Repo

Issue Tracking

Backlog

Stable Release

Dev Release


pdsen-operations

Tickets for the PDSEN Operations Team

User Guide

Github Repo

Issue Tracking

Backlog

Stable Release

Dev Release


pds-tracking-service

Provides functionality for tracking status and other aspects pertaining to PDS products that are not captured in the Registry Service.

User Guide

Github Repo

Issue Tracking

Backlog

Stable Release

Dev Release

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.