Release Description Document (Build B15.0)

This release of the PDS4 System is intended as an operational release of the system components to date. The original plan for this release can be found here: plan B15.0

The following sections can be found in this document:

PDS4 Standards and Information Model Changes

This section details the changes to the PDS4 Standards and Information Model approved by the PDS4 Change Control Board and implemented by the PDS within the latest build period.

Ref	Title
pds4-information-model#753	CCB-16: Allow micro amps and nano amps as units of current
pds4-information-model#782	CCB-26: Fix definition of Units_of_Amount_of_Substance
pds4-information-model#784	CCB-18: Complete JIRA-CCB-325 lien implementation for Browse and Ancillary products
pds4-information-model#795	CCB-7: Missing schematron rule - bundle_to_targets
pds4-information-model#816	CCB-29: Incorrect schematron rules for Bundle (type:External), Collection (type:External), and Product_External logical_identifiers
pds4-information-model#823	CCB-27: DOI requires at least an author or editor
pds4-information-model#824	CCB-24: Replaced all of the unit_id standard value definitions
pds4-information-model#829	CCB-38: Added mrad/pixel to Units_of_Pixel_Resolution_Angular
pds4-information-model#830	CCB-47: Add permissible value W/cm**2/sr/μm to Units_of_Spectral_Radiance
pds4-information-model#831	CCB-42: Add Array_1D_Spectrum to File_Area_Ancillary, File_Area_Browse, and File_Area_Observational_Supplemental
pds4-information-model#838	CCB-10: Schematron/Schema Version Conflict (PDS-JIRA-366)
pds4-information-model#839	CCB-19: Never finished CCB-325 documentation updates (Title: Support for video and audio as product observational)

Software Changes

For each software repository, the changes are listed in 2 categories:

Planned Updates
Other Updates

The ‘Planned Updates’ are organized by ‘Themes’ (or ‘Release Themes’), which are defined in advance and approved by the PDS Software Working Group (see Plan B15.0).

The ‘Other Updates’ occurs during the build cycle without being planned or attached to a theme. They are organized by types (bug, enhancements, requirements, tasks). Any updates that require a de-scope of planned tasks are reviewed by the PDS Software Working Group.

The deliveries are validated by the development team and go through an additional Integration & Test process, as applicable, as indicated by the `Testing Status` column in the tables below. There are 3 possible statuses for testing:

🔵 Skip Testing - Testing is not needed for this ticket. These are determined at the discretion of the team based upon the technical or operational nature of the closed task.
🟡 Testing Needed
🟢 Testing Complete - Initial testing complete, and test cases/results documented.

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.

Planned Updates

data-upload-manager#51 Add User-Defined Object Metadata

Issue	I&T Status	Level	Priority / Bug Severity
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	🟡	requirement	p.must-have
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	🟡	requirement	p.should-have

data-upload-manager#84 Improve DUM Upload Performance and Avoid Replication of Files in the Cloud

Issue	I&T Status	Level	Priority / Bug Severity
data-upload-manager#92 As a user, I want to skip upload of files already in S3 (nucleus staging bucket)	🟡	requirement	p.must-have
data-upload-manager#98 As a user, I want an end summary report in logs to show statistics of files uploaded	🟡	requirement	p.should-have

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
data-upload-manager#110 DUM Client does not properly sanitize double-quotes from INI config	🟡	s.high
data-upload-manager#116 DUM Lambda Service can return pre-signed S3 URL’s to non-existing buckets	🟡	p.must-have
data-upload-manager#136 Backoff/Retry logic not firing for certain error codes	🟡	s.medium
data-upload-manager#135 DUM Client script does not respect configured logging level after a transfer failure/retry	🟡	s.medium

Deep-archive

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

Planned Updates

No planned updates realized for this build in this repository.

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
deep-archive#178 Issues with manifests after multiple slash update fix (#162)	🟡	s.medium
deep-archive#171 Failing build due to deprecated config	🔵	s.high
deep-archive#186 AIP now fails validation after #178 update	🔵	s.high

Requirements

Issue	I&T Status	Priority / Bug Severity
deep-archive#162 As a data custodian, I want the Deep Archive to work around invalid URLs in the Registry	🟡	p.must-have

Doi-service

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

Planned Updates

No planned updates realized for this build in this repository.

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
doi-service#430 Installation instructions are not entirely clear, and come back with issues about incompatible libraries in python 11	🔵	unknown

Edwg

PDS Editorial Working Group Working Area

Planned Updates

EdWG#6 Phase 1: Context Product Scrub

Other Updates

Enhancements

Issue	I&T Status	Priority / Bug Severity
EdWG#15 Update context products with latest production versions	🔵	p.must-have

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).

Planned Updates

harvest#131 Enhance support for searching lid/lidvid references

Issue	I&T Status	Level	Priority / Bug Severity
harvest#127 ref_lid_* fields are not added to the Registry schema prior to load	🟡	bug	s.medium

harvest#135 As a user, I want the default archive_status for loaded products to be configurable

Other Updates

Enhancements

Issue	I&T Status	Priority / Bug Severity
harvest#158 As a data custodian, I want to load URLs / file paths without unnecessary / additional slashes	🟡	p.should-have

Monitoring

Monitoring configuration for PDS EN system, currently based on AWS CloudWatch

Planned Updates

monitoring#15 Develop MCP OU Structure, Cost Monitoring, and Cost Management Policies

Issue	I&T Status	Level	Priority / Bug Severity
monitoring#14 As a user, I want a daily budget reports sent to my email inbox	🔵	requirement	p.should-have

Nucleus

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

Planned Updates

nucleus#91 Implement Warm Backup Storage Solution (Data Backup Plan)

Issue	I&T Status	Level	Priority / Bug Severity
nucleus#73 As a user, I want to store a copy of my archive data in AWS Deep Archive / Glacier	🟡	requirement	p.must-have

nucleus#93 CSS MVP: Deploy Baseline Nucleus for Catalina Sky Survey in Test and Production Environments

Issue	I&T Status	Level	Priority / Bug Severity
nucleus#73 As a user, I want to store a copy of my archive data in AWS Deep Archive / Glacier	🟡	requirement	p.must-have

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
nucleus#101 Nucleus MWAA DAG tasks are unable to read remote logs from Cloudwatch	🟡	unknown

Pds4-information-model

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

Planned Updates

pds4-information-model#701 Initial Implementation of Cucumber Framework for PDS4 IM Repo

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

Issue	I&T Status	Level	Priority / Bug Severity
pds4-information-model#795 CCB-7: Missing schematron rule - bundle_to_targets	🟢	requirement	p.must-have

pds4-information-model#732 B15.0 Planetary Systems Target Ontology: Rings, Satellites Small Bodies Phase 1

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
pds4-information-model#818 LDDTool does not resolve the JUICE namespaces with IM 1J00	🔵	s.high
pds4-information-model#776 Unable to build LDDs for 1E00	🔵	s.medium
pds4-information-model#797 GEOM LDD schematron rules are not executing as expected <kernel_type> validation	🟡	s.critical
pds4-information-model#801 Lack of object initialization in the code leads to infinite when trying to run main more than once	🔵	s.high
pds4-information-model#770 ERROR 11179 data dictionary class is missing for overwrite	🔵	s.high
pds4-information-model#819 Regression in schematron improvements for references (#795)	🔵	s.critical

Requirements

Issue	I&T Status	Priority / Bug Severity
pds4-information-model#838 CCB-10: Schematron/Schema Version Conflict (PDS-JIRA-366)	🟡	p.must-have
pds4-information-model#753 CCB-16: Allow micro amps and nano amps as units of current	🟢	p.must-have
pds4-information-model#829 CCB-38: Added mrad/pixel to Units_of_Pixel_Resolution_Angular	🟡	p.must-have
pds4-information-model#816 CCB-29: Incorrect schematron rules for Bundle (type:External), Collection (type:External), and Product_External logical_identifiers	🟡	p.must-have
pds4-information-model#823 CCB-27: DOI requires at least an author or editor	🟡	p.must-have
pds4-information-model#839 CCB-19: Never finished CCB-325 documentation updates (Title: Support for video and audio as product observational)	🟡	p.must-have
pds4-information-model#824 CCB-24: Replaced all of the unit_id standard value definitions	🟡	p.must-have
pds4-information-model#831 CCB-42: Add Array_1D_Spectrum to File_Area_Ancillary, File_Area_Browse, and File_Area_Observational_Supplemental	🟢	p.must-have
pds4-information-model#830 CCB-47: Add permissible value W/cm**2/sr/μm to Units_of_Spectral_Radiance	🟡	p.must-have
pds4-information-model#782 CCB-26: Fix definition of Units_of_Amount_of_Substance	🟡	p.must-have

Enhancements

Issue	I&T Status	Priority / Bug Severity
pds4-information-model#803 [namespace-registry] add new namespace juice	🔵	p.must-have
pds4-information-model#794 [namespace-registry] add new namespace vikinglander	🟢	p.must-have

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.

Planned Updates

No planned updates realized for this build in this repository.

Other Updates

Requirements

Issue	I&T Status	Priority / Bug Severity
pds4-jparser#142 As a user, I want to read 4D arrays	🔵	p.should-have

Peppi

Planetary Data Explorere: Python (PEPPi) library (pds.peppi) to access Planetary Data from the Planetary Data System (formerly known as updart)

Planned Updates

No planned updates realized for this build in this repository.

Other Updates

Requirements

Issue	I&T Status	Priority / Bug Severity
peppi#7 As a user, I want to support search-after pagination	🟡	p.should-have
peppi#29 As a user, I want to search for products based upon a target LID	🟡	p.must-have

Planetary-data-cloud

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

Planned Updates

planetary-data-cloud#73 ATLAS MVP: Support Development of Initial Migration Plan and Architecture for ATLAS Survey Data

planetary-data-cloud#103 B15.0 Bi-annual Cloud Resource Housekeeping

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
planetary-data-cloud#108 [SECURITY] Ensure CloudFront distributions have logging enabled-PDS	🟡	s.high

Planetarydata.org

Website and related services for the International Planetary Data Alliance, nominally run at https://planetarydata.org/

Planned Updates

No planned updates realized for this build in this repository.

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
planetarydata.org#25 Typo	🔵	s.medium
planetarydata.org#23 Updates to web site content	🔵	s.low
planetarydata.org#24 Old link to PSA	🔵	s.medium

Portal-tasks

PDS Portal tasks repo used to track update requests for the website. Actual code and website are managed in separate private repo

Planned Updates

No planned updates realized for this build in this repository.

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
portal-tasks#95 Broken links for 1.21.0.0 and 1.22.0.0	🔵	s.high
portal-tasks#96 Bug with Tool Registry with new Registry	🔵	s.high
portal-tasks#97 Tool Registry no longer works with new Registry Servlet	🔵	s.critical

Portal-wp-tasks

PDS Web Design System

Planned Updates

portal-wp-tasks#58 Phase 1: Search Implementation

portal-wp-tasks#59 Phase 1: Investigations Directory Page Module Implementation

portal-wp-tasks#60 Phase 1: Investigation Landing Page Module Implementation

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.

Planned Updates

registry#185 Implement Registry Multi-tenancy with Cognito in the loop

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
registry#292 Secret detection is broken on branch titan_treks_utility_script	🔵	s.medium
registry#276 harvest created archive_status as an array and registry-mgr updates it as a string	🟡	s.medium

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.

Planned Updates

registry-api#424 API MVP to utilize Amazon OpenSearch Serverless

registry-api#428 Implement expected latest functionality for all endpoints

Issue	I&T Status	Level	Priority / Bug Severity
registry-api#435 As a user, by default, I want to resolve the latest version of a product when given a product logical_identifier (LID) (/products/{logical_identifier} endpoint)	🟡	requirement	p.must-have

registry-api#505 Multi-tenancy Migration MVP Tasks

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
registry-api#431 Investigate sporadic 500 and 504 errors with registry API	🔵	s.medium
registry-api#522 Fix code scanning alerts per logging	🔵	s.high

Requirements

Issue	I&T Status	Priority / Bug Severity
registry-api#426 As a user, by default, I want to search only for the latest versions of all products on the /products endpoint	🟡	p.should-have
registry-api#491 As a user, I want to apply an additional query filter (q=) to the /products/{identifier}/member-of result set	🟢	p.should-have
registry-api#488 As a user, by default, I want to search for the latest versions of all products on the /classes/{class} endpoint unless explicitly requested	🟡	p.should-have
registry-api#486 As a user, by default, I want to search for only the latest versions of all products on the /products/{identifier}/member-of endpoint	🟡	p.should-have
registry-api#506 As a user, I want to know what are all the possible properties I can search against (/properties)	🟡	p.must-have
registry-api#436 As a user, I want to get all product versions associated to one lid	🟡	p.must-have
registry-api#490 As a user, I want to apply an additional query filter (q=) to members of the members of an aggregate product (/products/{identifier}/members/members)	🟢	p.should-have
registry-api#497 As a user, I want to receive metadata only in the API responses (no binary blobs)	🟡	p.must-have
registry-api#485 As a user, by default, I want to search for only the latest versions of all products on the /products/{identifier}/members/members endpoint	🟡	p.should-have
registry-api#493 As a user, I want to apply an additional query filter (q=) to the /classes/{class} result set	🟢	p.should-have
registry-api#484 As a user, by default, I want to search for only the latest versions of all products on the /products/{identifier}/members endpoint	🟡	p.should-have
registry-api#495 As a user, I want to filter the products by any available PDS4 property by combining comparison operators using logical operators	🟢	p.must-have
registry-api#516 As a user, I want to get a description of the API when I request it from its base URL in a web browser	🟡	p.must-have
registry-api#492 As a user, I want to apply an additional query filter (q=) to the /products/{identifier}/member-of/member-of result set	🟢	p.should-have
registry-api#469 As a user, I want to filter the products by any available PDS4 property using a combination of comparison, logical, and precedence grouping operators	🟡	p.must-have
registry-api#434 As a user, I want to get a product description given a lidvid	🟡	p.must-have
registry-api#511 As a user, I want to get all the products for a specific PDS4 product class	🟡	p.must-have
registry-api#494 As a user, I want to filter the products by any available PDS4 property using comparison operators	🟢	p.must-have
registry-api#298 As a user, I want to apply an additional query filter (q=) to members of an aggregate product (/products/{identifier}/members)	🟢	p.must-have
registry-api#487 As a user, by default, I want to search only for the latest versions of all products on the /products/{identifier}/member-of/member-of endpoint	🟡	p.should-have

Registry-client

A simple PDS Registry Client which authenticates users with PDS SSO and signs requests to the serverless OpenSearch (AOSS) hosting the Registry database.

Planned Updates

No planned updates realized for this build in this repository.

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
registry-client#3 pypi installation is broken	🟢	s.high

Registry-common

Library utilized by tools that manage and load data into the PDS Registry, including Harvest, Registry Manager, and Supplementer

Planned Updates

No planned updates realized for this build in this repository.

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
registry-common#50 Update registry-common library to support change to AWS interface	🔵	s.critical
registry-common#53 Update OpenSearch API call to use search() instead of get()	🔵	s.medium

Registry-legacy-solr

Legacy Registry Software components leveraging Apache Solr. Includes Legacy Harvest Tool, Registry Manager, PDS3 Catalog Tool, and Search Core library. These components provide the capabilities for loading PDS3 and PDS4 data into the Legacy Solr Registry, driving the PDS keyword search.

Planned Updates

No planned updates realized for this build in this repository.

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
registry-legacy-solr#130 Unable to set custom facet fields (facet.field)	🔵	s.critical

Enhancements

Issue	I&T Status	Priority / Bug Severity
registry-legacy-solr#76 Refactor legacy search-core dependencies to include classes explicitly in repo	🔵	unknown

Registry-mgr

Standalone Registry Manager application responsible for managing the PDS Registry (https://github.com/NASA-PDS/registry) schemas and indexes.

Planned Updates

No planned updates realized for this build in this repository.

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
registry-mgr#78 set-archive-status and delete-data subcommand do not work on OpenSearch serverless Registry	🟡	s.critical

Requirements

Issue	I&T Status	Priority / Bug Severity
registry-mgr#69 As a user, I want to set archive-status using packageId	🟡	p.must-have

Roundup-action

Do a “roundup”, a/k/a PDS-style continuous integration and delivery

Planned Updates

No planned updates realized for this build in this repository.

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
roundup-action#138 Maven deploy no longer works due to Maven central upgrade	🟡	s.high
roundup-action#142 Roundup failing on tagging stable release for pds4-information-model	🔵	s.high
roundup-action#139 Unstable Pipeline failing with unsatisfiable install dependency on Data Upload Manager repository	🟡	s.high

S3-browser-cloudfront

Web view for files in S3 buckets

Planned Updates

s3-browser-cloudfront#23 Adapt S3 Browser to work for PDC and ODR buckets

Issue	I&T Status	Level	Priority / Bug Severity
s3-browser-cloudfront#22 As a data user, I want to view ODR S3 bucket with S3 browser app	🟡	requirement	p.must-have

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
s3-browser-cloudfront#113 Links to data or label files are broken	🟡	unknown

Requirements

Issue	I&T Status	Priority / Bug Severity
s3-browser-cloudfront#68 As a manager, I want the S3-browser to be deployable and accessible from a ‘/some_path’ URL	🔵	p.should-have

Search-ui-legacy

Legacy Keyword Search UI querying the Legacy Registry through Apache Solr.

Planned Updates

No planned updates realized for this build in this repository.

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
search-ui-legacy#30 Fix code scanning alert per Log Injection	🔵	s.critical
search-ui-legacy#35 Faceting no longer works since XssUtils was introduced	🔵	s.critical

Software-issues-repo

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

Planned Updates

software-issues-repo#76 Distribute ISAs for Signature Cycle

software-issues-repo#86 Complete Tasks and Artifacts Supporting NASA A&A Process

software-issues-repo#98 B15.0 Release Planning

software-issues-repo#99 B15.0 Prep for I&T

software-issues-repo#100 B15.0 Code Freeze

System-i-n-t

Repo for PDS EN System I&T scripts and issue tracking

Planned Updates

system-i-n-t#52 B15.0 Delivery & Deployment Review Preparation

system-i-n-t#54 B15.0 System Integration & Test

system-i-n-t#55 B15.0 Test Readiness Review (TRR)

Validate

Validates PDS4 product labels, data and PDS3 Volumes

Planned Updates

validate#696 Use New Registry API for Context Product Validation

Issue	I&T Status	Level	Priority / Bug Severity
validate#675 Cutover to using new Registry API for generating context products json	🟡	enhancement	p.must-have

validate#832 Review Handling of Special Constants, Field Formats, and High Priority Bug Fixes

Issue	I&T Status	Level	Priority / Bug Severity
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	🟢	requirement	p.should-have
validate#817 As a user, I want an ERROR to be thrown when a character table value does not match the expected validation_format	🟢	requirement	p.should-have
validate#831 validate incorrectly handles special constant high_instrument_saturation	🟢	bug	s.medium
validate#837 In text tables, validate attempts to match pattern associated with data_type before checking Special_Constants	🟢	bug	s.medium
validate#849 Validate stalls when validating collection inventory file with duplicates records	🟢	bug	s.medium
validate#873 Validate 3.5.0-snapshot Giving Unexpected Errors for Matching Filenames in Separate Directories	🟢	bug	s.medium
validate#874 SXXP0003 Error when running on PDS3 data sets for v3.3.3 or v3.4.1	🔵	bug	s.medium
validate#903 Validate not retrying on sch load failure	🔵	bug	s.low
validate#905 Validate 3.5.0-snapshot gives error when encountering Document objects/files used in other Document products.	🟢	bug	s.medium

validate#860 Add Warning Messages for Context Product Name Mismatches

Issue	I&T Status	Level	Priority / Bug Severity
validate#857 As a user, I want to receive a WARNING message when the Observing_System_Component.name does not match the value in the context product	🟢	requirement	p.should-have
validate#861 As a user, I want to receive a WARNING message when the Target_Identification.name does not match the value in the context product	🟢	requirement	p.should-have

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
validate#915 context_ref_mismatch check only executes when -R pds4.label	🟢	s.low
validate#822 Check for unlabeled files no longer works	🟢	s.medium
validate#936 Validate does not show correct filename for PDF/A failures when validating a directory	🔵	s.medium
validate#902 Validate error during JPEG content validation	🟢	s.medium
validate#1034 validate –update-context-products no longer works with Solr upgrade	🟢	s.critical
validate#923 Configuration file parser does not reject incorrect options	🔵	s.medium
validate#1054 validate.bat no executes correctly on windows	🔵	s.critical
validate#950 –disable-context-mismatch-warnings only works for rule pds4.label	🟢	s.high
validate#919 Validate throws an error when UnsignedBitString has 61 bits	🟢	s.medium
validate#826 validate is slow or runs out of memory when validating a bundle	🔵	s.medium
validate#933 Missing operation documentation	🟢	s.high
validate#969 Slow performance with all content and product validation turned off	🔵	s.medium
validate#823 Validate V.3.4.1 reports file read errors on products which read correctly under V.3.2.0	🟢	s.medium

Enhancements

Issue	I&T Status	Priority / Bug Severity
validate#824 Check for PDF/A-1a only if Product_Document	🟢	p.should-have

Web-analytics

None

Planned Updates

web-analytics#30 Automate Log Sync to S3 and Athena

web-analytics#32 Document Strategy for Web Analytics System Migration to MCP

Other Updates

Bugs

Issue	I&T Status	Priority / Bug Severity
web-analytics#12 Sync script fails silently if aws call fails	🔵	s.medium

Requirements

Issue	I&T Status	Priority / Bug Severity
web-analytics#39 update repo with template files	🔵	unknown
web-analytics#24 As a user, I want a mission-specific dashboard showing instrument and product type download metrics	🔵	p.should-have

Liens

Issue	Title	Rationale

Engineering Node Software Catalog

The Engineering Node Software resources are listed in the Software Release Summary (B15.0)

Installation and Operation

PDS Engineering Node Software have 3 different venues/purposes for execution: Standalone, Discipline Node Deployment or Engineering Node-only Deployment For the Installation and Operation manual see the users manuals in the software summary sections below:

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 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 Deep Archive Software Requirements and Design Document (SRD/SDD)
PDS DOI Service Requirements and Design Document (SRD/SDD)