Release Description Document (Build B13.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 B13.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 |
|---|---|
CCB-348: Add Units_of_Mass_Density as a unit of measure |
Software Changes
The changes types are ‘Bug’, ‘Enhancement’ or ‘Requirement’. 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 B13.0’) The ‘Other Updates’ occurs during the build cycle witout being planned or attached to a theme. They are organized by types (bug, enhancements, requirements…). 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 a specific icon in the following tables.
Cloud Tasks
PDS Cloud Migration documentation, issue, tracking and simple tools for assisting in the PDS hybrid cloud study and migration efforts.
Planned Updates
cloud-tasks#28 B13.0 Upgrade Registry Deployments to OpenSearch
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
Other Updates
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
cloud-tasks#37 Make the current version of the API implementation (v1.0) be published under url 1.0 (instead of 0.4) |
unknown |
PDS Design Team and Web Modernization
PDS.nasa.gov User Experience Task Issue and Prototype repository
Planned Updates
design-team#138 Continue High-Fidelity User Journey Designs: Homepage, Search, Mission Portal
Issue |
I&T |
Level |
Priority / Bug Severity |
|---|---|---|---|
design-team#129 Design Investigations Portal high-fidelity designs (draft 1) |
task |
unknown |
|
design-team#130 Develop high-fidelity design for data / web search journey (draft 1) |
task |
unknown |
|
design-team#132 High-fidelity design for PDS Homepage |
task |
unknown |
|
design-team#135 Develop discipline node high fidelity design for GEO (draft 1) |
task |
unknown |
|
design-team#136 Develop data set landing page high-fidelity designs (draft 1) |
task |
unknown |
|
design-team#141 Design Investigations Portal high-fidelity designs (draft 2) |
task |
unknown |
|
design-team#143 Develop high-fidelity designs for data / web search journey (draft 2) |
task |
unknown |
|
design-team#152 Make the Investigation page for Cassini |
task |
unknown |
|
design-team#153 Iterate on MSL Investigations landing high-fidelity designs (draft 3) |
task |
unknown |
|
design-team#154 Iterate on Cassini Investigations landing high-fidelity designs (draft 2) |
task |
unknown |
design-team#139 Refine WDS based upon High-Fidelity Designs
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
design-team#140 Usability Testing Phase 1 - Introduction
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
Devops
Parent repo for PDS DevOps activities
Planned Updates
devops#11 B13.0 Implement Continuous Deployment Strategy
Issue |
I&T |
Level |
Priority / Bug Severity |
|---|---|---|---|
devops#2 As a developer, I want a developer staging system with the latest dev versions of PDS services deployed |
|
requirement |
p.should-have |
devops#22 As a developer, I want access to the latest and continuously deployed exposition API |
|
requirement |
p.should-have |
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
devops#24 Automatic image creation needs to parameterize Dockerfile |
s.low |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
devops#27 As a developer, I want to have a documentation for the Continuous Deployment in the DEV STAGING venue |
|
p.should-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 |
Priority / Bug Severity |
|---|---|---|
`doi-service#341`_ Fix broken build |
s.medium |
|
doi-service#350 dataCite reserve error on title |
|
s.critical |
doi-service#331 doi sync failing for SBN-PSI DOIs |
|
s.medium |
`doi-service#336`_ DOI-service application inaccurately reports LID as being invalid |
|
s.medium |
`doi-service#328`_ Valid PDS4 xml input is converted into an invalid json that fails internal datacite validator |
|
s.medium |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
doi-service#13 The software shall validate the DOI metadata when reserving, releasing, or updating a DOI. |
|
p.must-have |
doi-service#224 As a DOI user, I would like to know the licensing information PDS data |
|
p.should-have |
doi-service#335 As a DOI user, I would like to know the copyright for PDS data |
|
p.should-have |
doi-service#344 As a user, I want to release a DOI with a label that does not contain the DOI |
|
p.must-have |
DOI User Interface
The web interface for the PDS DOI Service providing the ability management PDS archive DOIs. See the DOI Service for more details on the available capabilities. https://nasa-pds.github.io/doi-service/
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
doi-ui#137 [SECURITY] Triage and determine severity of dependabot and code scanning vulnerabilities |
s.medium |
|
doi-ui#151 Error messages are inconsistent |
|
s.medium |
doi-ui#130 Remove vulnerabilities from the package per npm audit |
|
s.high |
doi-ui#160 Sometimes there is a null error message when there is no error |
|
s.medium |
doi-ui#155 Keywords text box and info icon do not appear correctly |
|
s.medium |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
`doi-ui#92`_ As a user, I want to get an error message with support contact when the backend API is unavailable |
|
p.could-have |
doi-ui#145 As a user, I want to access the DOI UI from outside JPL |
|
p.must-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
doi-ui#149 create an ASR for the application |
|
unknown |
doi-ui#143 Deploy doi-ui in production on AWS |
unknown |
|
`doi-ui#146`_ Upgrade deployment of DOI UI to patched v1.0.1 |
unknown |
|
doi-ui#147 Replace authentication with Cognito on DOI UI and DOI service |
|
unknown |
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
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
harvest#90 Incorrect “lidvid” and “_id” fields are ingested (trailing zeros are truncated) |
|
s.critical |
Nucleus
None
Planned Updates
nucleus#1 B13.0 Initial Design and Trade Study
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
Pds-api
PDS API Application with client and server integrated into one package
Planned Updates
pds-api#129 Prep for API v1.0 Release
Issue |
I&T |
Level |
Priority / Bug Severity |
|---|---|---|---|
pds-api#169 As a user, I want to have a PDS Search API user guide |
|
requirement |
p.must-have |
Issue |
I&T |
Level |
Priority / Bug Severity |
|---|---|---|---|
pds-api#173 Replace summary-only=true by limit=0 |
|
enhancement |
unknown |
pds-api#202 Complete refactoring per API WG discussion on end-point redesign |
enhancement |
p.must-have |
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds-api#209 clarifications needed for fields reference in documentation |
s.low |
|
`pds-api#206`_ fix broken link in API docs |
s.low |
|
pds-api#216 is “bites” a typo for “bytes” or “bits”? |
s.low |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds-api#148 As a user, I want to search for past versions of a product where the LID changed during the product history |
|
p.should-have |
pds-api#60 As an API user, I want to know the Bundle for a given Product. |
|
p.must-have |
pds-api#101 As a user, I want to receive a JSON response that contains the PDS4 label metadata in JSON format (application/vnd.nasa.pds.pds4+json) |
|
p.must-have |
pds-api#125 As a user, I want to receive a XML response that contains the PDS4 label metadata in XML format (application/vnd.nasa.pds.pds4+xml) |
|
p.must-have |
pds-api#191 As a user, I want to get directions whenever I arrive on an API URL |
|
p.should-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds-api#183 Create a cookbook page on the content negotiation for the PDS Search API |
|
p.should-have |
`pds-api#189`_ Update README to reflect best practices of other PDS repositories |
p.must-have |
|
pds-api#172 Create user guide for the search api |
|
p.should-have |
Pds4-information-model
The software tools and data necessary for generating the Information Model including PDS4 ontology, data, and information model.
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds4-information-model#468 LDDTool is generating multiple Schematron rules to test the same condition |
|
s.medium |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds4-information-model#499 CCB-348: Add Units_of_Mass_Density as a unit of measure |
|
p.must-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds4-information-model#460 [namespace-registry] move namespace “wave” |
p.must-have |
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 |
Priority / Bug Severity |
|---|---|---|
planetarydata.org#6 IPDA Charter blocked by login |
|
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
portal-tasks#35 Initial Migration of PDS.nasa.gov to New CMS
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
portal-tasks#38 fix filenames for CASSINI_1B00_1300 in online archive |
|
s.medium |
portal-tasks#22 Fix odd spacing in header for keyword search and data set status |
|
s.medium |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
portal-tasks#26 As a node user, I want guidelines for handling DOI metadata for accumulating data sets |
p.should-have |
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#55 Re-imagine Registry Handling of Product Versioning
Issue |
I&T |
Level |
Priority / Bug Severity |
|---|---|---|---|
registry#57 Design the PDS4 definition for describing superseded LIDs via product metadata |
task |
unknown |
registry#45 Preparations to Support B12.1 Registry Upgrades
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry#64 Scalable Harvest does not replace file paths with the appropriate URL prefix |
|
s.high |
registry#84 Missing INSIGHT LDD v1600 |
s.low |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry#67 As a registry node user from JPL, I want to use my JPL login to access the Registry’s OpenSearch |
|
p.should-have |
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#138`_ Response Metadata Improvements
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry-api#134 wildcard search in query parameter returning odd results |
|
s.high |
registry-api#121 Fix vulnerabilities raised by sonalift |
|
s.high |
`registry-api#141`_ / is not returning swagger API doc |
|
s.medium |
registry-api#162 fields parameter does not return values if more than one value is requested for CSV format |
|
s.high |
`registry-api#171`_ summary does not contain the property values |
|
s.high |
`registry-api#137`_ [SECURITY] Log4j vulnerability in lexer |
|
s.critical |
`registry-api#150`_ bundle of a product does not return result |
|
s.medium |
`registry-api#128`_ Registry API Service docker container fails to start with error: Unable to access jarfile /usr/local/registry-api-service/registry-api-service.jar |
|
s.high |
registry-api#172 fields query parameter does not work consistently across all response formats |
|
s.high |
registry-api#167 summary-only does not work as expected |
|
s.medium |
registry-api#178 The /products, /bundles & /collections endpoints are missing from the API |
|
unknown |
registry-api#179 limit=0 is not providing list of properties (fka summary-only) |
|
s.medium |
`registry-api#152`_ summary-only does not work on products of a collection |
|
s.high |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry-api#109 As a user, I want to have an administrator contact when I am getting an error 500 from the server |
|
p.should-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
`registry-api#108`_ Remove the home controller from the swagger-ui |
|
p.must-have |
`registry-api#131`_ Refactor API endpoints for simpler architecture/design/implementation to maintain/extend |
|
p.should-have |
registry-api#117 Support override of application.properties for AWS Docker image |
p.must-have |
|
registry-api#122 [SECURITY] Upgrade jackson dependencies to remove vulnerability |
s.low |
|
`registry-api#140`_ Add back the Dockerfile used for the AWS/Fargate deployment |
|
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 |
Priority / Bug Severity |
|---|---|---|
registry-mgr#53 bug with pagination limitations per OpenSearch config |
|
s.high |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry-mgr#50 As a user I want to search on ref_lid_* |
|
p.should-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 |
Priority / Bug Severity |
|---|---|---|
`roundup-action#82`_ roundup versioning not working properly on nested maven repositories |
|
s.medium |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
`roundup-action#81`_ Update SNAPSHOT / DEV versioning to always increment minor version |
p.should-have |
Software-issues-repo
Issue tracking repository as a centralized entry point for general PDS software bugs and feature requests.
Planned Updates
software-issues-repo#36 Prep and Improvements for B13.0 Build and Deployment
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
Other Updates
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
software-issues-repo#35 Improve internal deployment documentation |
p.should-have |
Template-repo-python
*template repository for PDS python developments *
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
template-repo-python#56 As a developer, I want to perform continuous integration tests on branches |
p.should-have |
Validate
Validates PDS4 product labels, data and PDS3 Volumes
Planned Updates
validate#496 Support new lblx file extension
Issue |
I&T |
Level |
Priority / Bug Severity |
|---|---|---|---|
validate#482 As a user, I want to validate labels/bundles/collections using the LBLX file extension |
|
requirement |
p.must-have |
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
validate#516 validate embedded in an app bundled as a fat-jar raise exception on product validation |
|
s.low |
`validate#479`_ validate erroneously flags PDF/A-1a compliant file |
|
s.medium |
validate#507 validate having issues checking some file content on windows |
|
s.high |
`validate#503`_ validate passes confusing message to the command window |
|
s.high |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
`validate#241`_ As a developer, I want an API method enable specifying of non-registered context products |
p.must-have |
|
validate#524 As a user, I want to receive an error when no products are found within the validation target |
|
p.should-have |
Wds-web
PDS Web Design System - Basic web implementation
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
wds-web#31 App bar issue identified on ATM website |
|
s.medium |
Liens
Issue |
Title |
Rationale |
|---|---|---|
pds-swg_17 [CR] Defer Cloud Pilot projects to B13.1 |
[CR] Defer Cloud Pilot projects to B13.1 |
All pilot projects are being tabled until next FY when the EN Team has a better grasp of NGAP and how we are able to easily architect and deploy these applications, services, and data into NGAP. |
Engineering Node Software Catalog
The Engineering Node Software resources are listed in the Software Release Summary (B13.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)