Release Description Document (build B12.1)
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 B12.1
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-339: add Units_of_Power with SI watts as option |
|
CCB-344: Add data_to_partially_processed_product to reference types for Internal_Reference |
|
CCB-343: Revise Product_Metadata_Supplemental |
|
CCB-340 : <Local_Internal_Reference>.<local_identifier_reference> cardinality |
|
CCB-335: Inventory Specification Allows Too Many Delimiters |
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 B12.1’) 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#3 B12.1 pds.nasa.gov Website Lift-and-Shift Pilot Project
Issue
I&T
Level
Priority / Bug Severity
cloud-tasks#9 AWS testing for PDS and PDS Engineering sites
task
p.must-have
cloud-tasks#4 B12.1 pds-engineering.nasa.gov Website Lift-and-Shift Pilot Project
Issue
I&T
Level
Priority / Bug Severity
cloud-tasks#9 AWS testing for PDS and PDS Engineering sites
task
p.must-have
cloud-tasks#7 B12.1 Refine AWS Registry Deployment Strategy
Issue
I&T
Level
Priority / Bug Severity
cloud-tasks#1 As a manager, I want a cost monitoring capability for AWS deployments
requirement
p.must-have
cloud-tasks#13 Registry ES version incompatible with available available AWS managed ES / OpenSearch versions
bug
s.critical
cloud-tasks#8 Develop Roadmap and Cost Model for PDS Cloud (this theme has not epics in this repository)
cloud-tasks#10 Initialize PDS-ESDIS NGAP Pilot Project
Issue
I&T
Level
Priority / Bug Severity
cloud-tasks#22 create users for NGAP
enhancement
p.must-have
cloud-tasks#11 B12.1 Deploy Node Registries
Issue
I&T
Level
Priority / Bug Severity
cloud-tasks#12 Deploy production registries
task
unknown
cloud-tasks#14 Implement CCS across node registries
task
unknown
cloud-tasks#15 Design and Develop Registry Upgrade Strategy (this theme has not epics in this repository)
Deep-archive
PDS Open Archival Information System (OAIS) utilities, including Submission Information Package (SIP) and Archive Information Package (AIP) generators
Planned Updates
deep-archive#115 Revisit PDS Deep Archive Integration with Registry
Issue
I&T
Level
Priority / Bug Severity
deep-archive#107 Update PDS Deep “Registry” Archive and remove workaround + implement latest-only-feature per API updates
enhancement
p.should-have
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
deep-archive#124 Unexpected fatal error when running pds-deep-archive against bundle |
|
s.medium |
Design-team
PDS.nasa.gov User Experience Task Issue and Prototype repository
Planned Updates
design-team#77 Initial Information Architecture (this theme has not epics in this repository)
design-team#100 B12.1 Continuation of User Persona and User Story Development
Issue
I&T
Level
Priority / Bug Severity
design-team#99 Document initial User Stories using WMWG feedback
task
unknown
design-team#103 Iterate on WMWG feedback
task
unknown
design-team#107 Tag user stories to modules and templates
task
unknown
design-team#101 Deploy new Citing PDS Data Web Pages (this theme has not epics in this repository)
design-team#109 Develop Initial User Journey Designs
Issue
I&T
Level
Priority / Bug Severity
design-team#115 Develop Module List
task
unknown
design-team#116 Develop Template List
task
unknown
design-team#117 Prioritize Module List
task
unknown
design-team#118 Prioritize Template List
task
unknown
design-team#119 Define User Journeys
task
unknown
design-team#120 Identify Key User Journeys
task
unknown
design-team#121 Develop Low-fidelity User Journey Designs
task
unknown
design-team#128 Brainstorm additional modules based upon remaining user journeys
task
unknown
design-team#110 Define Initial Content Strategy
Issue
I&T
Level
Priority / Bug Severity
design-team#122 Define Navigation Strategy
task
unknown
design-team#123 Define Homepage / Landing Page Strategy
task
unknown
design-team#111 Define Current Information Architecture
Issue
I&T
Level
Priority / Bug Severity
design-team#127 Finalize current information architecture
task
unknown
Devops
Parent repo for PDS DevOps activities
Planned Updates
devops#13 Continuous improvements to Continuous Integration
Issue
I&T
Level
Priority / Bug Severity
devops#10 Rollout template updates to existing repos
task
unknown
devops#12 Remove Versioneer
task
unknown
devops#14 Update Stable Major Releases of PDS software with DOIs
requirement
p.must-have
devops#15 Update stable releases to handle Java repos
task
unknown
devops#20 Update documentation for creating new repo to add DOI webhook
task
unknown
Other Updates
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
devops#23 Develop github action to publish docker images on docker hub |
|
p.must-have |
Doi-service
Service and tools for generating DOIs for PDS bundles, collections, and data sets
Planned Updates
doi-service#203 Improve DOI Service Documentation
Issue
I&T
Level
Priority / Bug Severity
doi-service#201 As an operator, I want to know how to deploy and use the API from the Sphinx documentation
requirement
p.should-have
doi-service#202 As an operator, I want one place to go for all DOI Service / API / UI documentation
requirement
p.must-have
doi-service#256 Develop DOI documentation for PDS Operator
task
p.must-have
doi-service#251 B12.1 Enhancements to PDS DOI Metadata
Issue
I&T
Level
Priority / Bug Severity
doi-service#102 Add new alternateIdentifier to match SBN schema
enhancement
p.must-have
doi-service#294 Update all past DOIs for consistent metadata
enhancement
unknown
doi-service#303 identifiers vs alternateIdentifiers appear disconnected from current DataCite schema
bug
s.high
doi-service#270 B12.1 DOI Metadata and Update Functionality Improvements
Issue
I&T
Level
Priority / Bug Severity
doi-service#257 As a PDS Operator, I want to perform a bulk update of a specific field across many DOI records
requirement
p.should-have
doi-service#278 As a user, I want to update the LIDVID associated with a DOI
requirement
p.must-have
doi-service#287 B12.1 DOI Service Integration with Registry
Issue
I&T
Level
Priority / Bug Severity
doi-service#312 Develop script to sync SBN DOIs with DOI Service
task
unknown
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
doi-service#326 Fix issues related to integration with Web UI |
|
s.critical |
doi-service#291 Spreadsheet parsers do not handle blank rows gracefully |
s.low |
|
doi-service#318 Corruption in local database with invalid JSON |
s.high |
|
doi-service#299 DOI Service does not assign adequate permissions to transaction database/history |
|
s.low |
doi-service#310 Test DOIs are showing up in pds-gamma DOI search now linked from operations Citing PDS Data page |
|
s.medium |
doi-service#214 Remove test and other transaction log data from public pypi distro |
s.medium |
|
doi-service#258 Spreadsheet parser does not validate parsed contents of rows |
|
s.medium |
doi-service#324 Deprecate VCO and Akatsuki DOIs |
|
s.medium |
doi-service#273 Default keywords/subjects are not always added to DOI records |
|
s.medium |
doi-service#305 –no-review argument has potential to be confused with -n (node ID) argument |
|
s.low |
doi-service#321 deactivate registered cassini doi 10.17189/1517823 |
s.medium |
|
doi-service#259 Spreadsheet parser does not validate/sanitize format of expected header row |
s.medium |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
doi-service#279 As a user, I want to update the bundle/collection metadata associated with a DOI for accumulating data sets |
|
p.must-have |
doi-service#317 Add Radio Science to set of possible nodes |
p.must-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
doi-service#231 Improve upon application security for write access |
|
unknown |
doi-service#289 As a user, I want to obtain json label format from a list command query |
|
unknown |
doi-service#260 Improve spreadsheet parser error handling |
|
p.must-have |
Doi-ui
web UI for pds-doi-service
Planned Updates
doi-ui#60 DOI Search Component (this theme has not epics in this repository)
doi-ui#111 Complete DOI UI Implementation
Issue
I&T
Level
Priority / Bug Severity
doi-ui#95 Adapt the UI to the new API workflow
enhancement
unknown
doi-ui#106 Update DOI UI app to use NPM package
enhancement
unknown
doi-ui#115 deploy latest doi service on pds-dev3
enhancement
unknown
doi-ui#123 Null error message stays in a release/update scenario
bug
s.critical
doi-ui#124 typo in a request parameter when submitting doi
bug
s.critical
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
doi-ui#88 Pre-existing keyword show in a weird way in the UI |
|
s.medium |
doi-ui#130 Remove vulnerabilities from the package per npm audit |
|
s.high |
doi-ui#125 Error and warning message width should match with the rest of the form |
|
s.medium |
doi-ui#87 When I try to reload a reserve which has been updated, the web page does not update |
|
s.high |
doi-ui#117 Fix DOI Search And DOI UI Integration Bugs |
|
s.critical |
doi-ui#67 Issue with displaying the content of an uploaded file after multiple selections |
|
s.high |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
doi-ui#63 As an administrator, I want to deploy the ui from a release and be able to change the back-end API urls |
p.should-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
doi-ui#102 Have a single entry for the backend API url configuration |
|
p.should-have |
doi-ui#68 Improve Search UI behavior to only show results when search button is selected |
|
p.should-have |
Feedback-widget
Javascript widget for user feedback
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
feedback-widget#17 Feedback does not let submissions through for SBN |
|
s.medium |
feedback-widget#16 widget not working on pds.nasa.gov or pds-gamma.jpl.nasa.gov |
s.medium |
Harvest
Provides software provides functionality for capturing and indexing product metadata in PDS Registry. A sub-component of the PDS Registry App (https://github.com/NASA-PDS/pds-registry-app)
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
harvest#75 harvest stops rather than skips a file with bad permissions |
|
s.high |
harvest#78 Error ingesting an XML boolean with values of 0/1 |
|
s.high |
harvest#70 Harvest fails on yyyyZ date time |
|
s.high |
harvest#90 Incorrect “lidvid” and “_id” fields are ingested (trailing zeros are truncated) |
|
s.critical |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
harvest#64 Add release datetime to version output |
p.must-have |
|
harvest#84 Change the option -o help message |
p.must-have |
Mi-label
Metadata Injector for PDS Labels (MILabel) provides a command-line interface for generating PDS4 Labels using a user provided PDS4 XML template and input (source) data products.
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
mi-label#21 Product-Tools parsing mode cannot parse units |
|
s.medium |
Pds-api
PDS API Application with client and server integrated into one package
Planned Updates
pds-api#111 B12.1 Response Format Improvements (this theme has not epics in this repository)
pds-api#114 Improve PDS API Development Workflow and Versioning
Issue
I&T
Level
Priority / Bug Severity
pds-api#122 analysis of current workflow, ideas for improvment
task
unknown
pds-api#123 create a super registry+api repository
task
unknown
pds-api#139 As a user, I want to see API stable release specifications
requirement
p.must-have
pds-api#140 Merge unnecessary individual repository
enhancement
unknown
pds-api#142 flesh out the registry repository
enhancement
unknown
pds-api#150 Update the swagger web tool from the specification
task
unknown
pds-api#117 [pds-api] B12.1 API Response Improvements
Issue
I&T
Level
Priority / Bug Severity
pds-api#66 As an API user, I want to get an XML response
requirement
p.must-have
pds-api#125 As a user, I want to get the metadata in a pds4+xml response
requirement
p.must-have
pds-api#127 As a user, I want to clearly see which formats are accepted by the API when a 406 error is raised
requirement
p.should-have
pds-api#151 Update fields parameter definition to note that it does not apply to pds4+json and pds4+xml response formats
task
p.should-have
pds-api#152 As a user, I want the API response media types to be compliant with RFC 6838
requirement
p.must-have
pds-api#153 As a user, I want to receive error messages when an invalid request is submitted to the API
requirement
p.must-have
pds-api#154 Refactor meta section of pds4+json and pds4+xml to use ops namespace
enhancement
p.must-have
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds-api#121 Deployed API + Registry does not contain product metadata for pds4+json response |
|
s.high |
pds-api#155 products/{identifier} missing properties object in application/json response |
|
s.high |
pds-api#124 Changes to API per last tagged release not in SwaggerHub |
s.critical |
|
pds-api#164 version number invalid according to PEP validation in CI |
s.critical |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds-api#106 As a API manager, I want to restrict access to registered products that should not be publicly accessible |
|
p.should-have |
pds-api#72 As an API user, I want to search by a temporal range as an ISO-8601 time interval. |
|
p.must-have |
pds-api#120 As an API user, I want a CSV response format option |
|
p.must-have |
pds-api#51 As a developer, I want a continuous deployment of the API available for testing |
|
p.must-have |
pds-api#65 As an API user, I want to get only the fields I explicitly requested |
|
p.could-have |
pds-api#134 As an API user, I want to get a key-value-pair JSON response |
|
p.must-have |
pds-api#74 As an API user, I want to specify whether I get the latest or all versions of a product |
|
p.must-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds-api#110 Extend application/pds4+json support to all endpoints |
|
p.must-have |
pds-api#112 As an API client user, I want to consistently and robustly start local servers for development and testing |
unknown |
|
pds-api#108 Update API endpoints to use identifier instead of lidvid |
|
p.should-have |
pds-api#136 Revise the pds-api README so that it gives a perspective on non search api (e.g. doi) from pds |
|
unknown |
pds-api#172 Create user guide for the search api |
|
unknown |
pds-api#145 Remove the x-total-count header from the API specification |
|
unknown |
pds-api#158 Improve linkages from Registry App Docs to API Docs |
|
p.must-have |
pds-api#133 clarify what keyword parameter is for |
|
unknown |
pds-api#137 As a user, I want to have a detailed description of the API q parameter syntax |
|
unknown |
Pds-api-client
PDS API Client
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds-api-client#19 The demo provided on pds-api-client quickstart gives a 500 error |
|
s.high |
pds-api-client#18 Links to client API details are broken on GitHub site |
|
s.high |
pds-api-client#17 Import failure for pds.api_client.CollectionsApi using PIP package 0.8.0 |
|
s.critical |
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. This repo builds, packages, and documents all the services and tools related to the ingestion and access of the data.
Planned Updates
pds-registry-app#184 B12.1 Registry Tools Performance Improvements
Issue
I&T
Level
Priority / Bug Severity
pds-registry-app#179 As a user, I want the registry app components to be able to ingest data sets containing 1+ million products
requirement
p.must-have
pds-registry-app#200 As a user, I want big data ingestion tools packaged and dockerized together
requirement
p.must-have
pds-registry-app#217 Clearly define best practices configuration for harvest/registry-mgr
task
unknown
pds-registry-app#218 Document big data harvest / registry manager / crawler installation and operation
task
unknown
pds-registry-app#190 Provide Initial Support for Restricted Access vs. Public Data
Issue
I&T
Level
Priority / Bug Severity
pds-registry-app#201 As a user, I want to be able to ingest a set of files specified in a file listing
requirement
p.should-have
pds-registry-app#223 As a user, I want to change the archive status for a collection and it’s associated products
requirement
p.should-have
pds-registry-app#224 As a user, I want to switch a bundle and it’s associated collections and products from a protected status to operational.
requirement
p.should-have
pds-registry-app#228 Develop design documentation for staging vs production data for review with SWG
task
unknown
pds-registry-app#199 Dockerize Registry Components for Dev and Ops Deployments
Issue
I&T
Level
Priority / Bug Severity
pds-registry-app#187 As a developer, I want to be able to access the registry related docker images from https://hub.docker.com/
requirement
p.must-have
pds-registry-app#208 As a developer I want to start the registry with a single command
task
unknown
pds-registry-app#226 B12.1 Upgrade Registry App to OpenSearch
Issue
I&T
Level
Priority / Bug Severity
pds-registry-app#227 Update docs to reference OpenSearch
task
unknown
pds-registry-app#250 test registry docker compose with opensearch instead of elasticsearch
task
unknown
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds-registry-app#238 pom.xml on main is broken |
s.high |
|
pds-registry-app#205 Harvest network I/O errors can cause corrupted JSON |
|
s.high |
pds-registry-app#177 stable continuous integration don’t generate the packages tar.gz and .zip properly. |
s.medium |
|
pds-registry-app#220 harvest flags as mandatory a config elements the docs describe as optional |
|
s.low |
pds-registry-app#231 the snapshot releases are not created for big-data-harvest-client |
s.critical |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds-registry-app#253 As a user, I want the registry loader tools to continue after the ingestion of a product fails |
|
p.should-have |
pds-registry-app#241 Simplify the readme and procedure to start the registry with docker-compose |
p.should-have |
|
pds-registry-app#186 As a developer, I want to deploy the registry with a single docker-compose command |
|
p.must-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds-registry-app#230 As a developer, I want to update and run the integration tests from the ‘registry’ repository |
unknown |
|
pds-registry-app#260 Make CICD work on registry-api repository |
p.must-have |
|
pds-registry-app#237 Rename bigdata repositories |
unknown |
|
pds-registry-app#90 Develop cost model and reporting for Registry deployments |
p.must-have |
|
pds-registry-app#240 Add AWS Quickstart, Cloud/On-Prem architecture, and basic Kibana setup pages to website |
|
unknown |
pds-registry-app#244 Registry App docs need a scrub for inconsistency and outdated information |
|
p.must-have |
pds-registry-app#263 Update the user documentation of the registry with the docker compose deployments |
|
unknown |
pds-registry-app#245 Update the README of the harvest service repositories |
p.must-have |
|
pds-registry-app#257 Simple wrappers to call the pds-batch-loader and pds-service-loader docker compose services |
|
unknown |
Pds-report-service
PDS Report and Metrics Service with ELK stack
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds-report-service#9 Expand number years included in OREx and New Horizons tasks |
unknown |
Pds-web-mgmt
PDS Web Management and Unification Team
Planned Updates
pds-web-mgmt#1 Initial Assessment of Today’s Web Management Landscape (this theme has not epics in this repository)
pds-web-mgmt#2 Preliminary Design of Migration (this theme has not epics in this repository)
pds-web-mgmt#3 Initial High-level Implementation Plan (this theme has not epics in this repository)
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#306 Refactoring of IMTool
Issue
I&T
Level
Priority / Bug Severity
pds4-information-model#239 Refactor Class information from config to Data Dictionary Protege ontology
enhancement
unknown
pds4-information-model#281 Tag ops classes/attributes in IM so they are easily identifiable by users
enhancement
unknown
pds4-information-model#428 IMTool Refactoring - Phase 2 - Move deprecated values to Protege ontology file
enhancement
unknown
pds4-information-model#440 remaining code cleanup / refactoring
enhancement
p.must-have
pds4-information-model#444 XML Schema files generated by LDDTool should not write the source file names in the header
enhancement
p.should-have
pds4-information-model#356 Kick-off PDS4 Information Model in GraphDB (this theme has not epics in this repository)
pds4-information-model#401 B12.1 LDDTool Improvements
Issue
I&T
Level
Priority / Bug Severity
pds4-information-model#269 The PDS4 IM Specification Document is not consistent in the ordering of Permissible Values
bug
s.medium
pds4-information-model#341 As a user, I want to specify an IngestLDD using a relative path
requirement
p.should-have
pds4-information-model#415 CCB-342: NASA, CODMAC, and PDS Processing Levels for Science Data Sets (this theme has not epics in this repository)
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds4-information-model#463 LDDTool 14 is not generating against past versions of the IM correctly |
|
s.high |
pds4-information-model#375 LDDTool documentation inconsistency |
|
s.low |
pds4-information-model#351 Contradictory DISP rule assertions exist in the PDS4 IM from legacy ingestion |
|
s.medium |
pds4-information-model#434 ASCII_Date_Time_* do not sufficiently check valid days of a month or seconds |
|
s.high |
pds4-information-model#418 Inconsistent naming of JSON schema files |
|
s.medium |
pds4-information-model#424 Missing JSON LDDs (alt & particle) |
s.low |
|
pds4-information-model#459 LDDTool is not combining Schematron Contexts correctly when adding to an auto-generated context |
|
s.medium |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds4-information-model#443 CCB-339: add Units_of_Power with SI watts as option |
|
p.must-have |
pds4-information-model#453 CCB-335: Inventory Specification Allows Too Many Delimiters |
|
p.must-have |
pds4-information-model#448 CCB-343: Revise Product_Metadata_Supplemental |
|
p.must-have |
pds4-information-model#446 CCB-344: Add data_to_partially_processed_product to reference types for Internal_Reference |
|
p.must-have |
pds4-information-model#450 CCB-340 : <Local_Internal_Reference>.<local_identifier_reference> cardinality |
|
p.must-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds4-information-model#421 [namespace-registry] add new namespace “<neas>” |
p.must-have |
|
pds4-information-model#435 [namespace-registry] add new namespace “lt” |
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
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
pds4-jparser#55 Improve ArrayObject accessor with new methods for improved access to the array label information |
p.could-have |
Plaid
APPS PDS Label Assistant for Interactive Design (PLAID). See an overview of the software on YouTube. https://www.youtube.com/watch?v=WCo8erW_rL8
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
PLAID#32 Base image used by APPS PLAID is not supported |
|
s.high |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
PLAID#30 Revise Docker and deployment docs for open source access |
|
p.must-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
PLAID#37 Add explicit instruction on how to launch the application with docker compose |
s.high |
|
PLAID#16 Document processes for deploying PLAID |
|
unknown |
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 |
Priority / Bug Severity |
|---|---|---|
portal-tasks#19 viewBundle not working properly for DOI search logic |
|
s.high |
portal-tasks#6 links not working on data dictionary pages |
|
s.high |
portal-tasks#9 Broken link to PDS4_PDS_1H00.zip |
s.high |
|
portal-tasks#10 DD Search and Tool Registry not working on pdscloud-gamma |
|
s.critical |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
portal-tasks#7 As a user, I want to see a DOI on all DOI landing pages |
p.should-have |
|
portal-tasks#3 improvement on citing page |
|
unknown |
Registry
Core registry services
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry#31 Upgrade the initialization of the ES/OS database following latest upgrade of components |
p.must-have |
Registry-api
web API service of the PDS registry
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry-api#5 AWS cost analysis tag is not ‘Alpha’ but instead ‘Alfa’ |
s.high |
|
registry-api#79 LID -> LIDVID conversion not consistent in registry-api |
s.low |
|
registry-api#73 blob/json_blob should not be included in default response |
|
s.high |
registry-api#106 documentation does not match behavior |
|
s.medium |
registry-api#113 Update all endpoints to only allow access to public data. |
|
s.high |
registry-api#121 Fix vulnerabilities raised by sonalift |
|
s.high |
registry-api#89 Fix unstable integration build failure |
s.medium |
|
registry-api#114 Invalid or corrupted registry-api-service.jar file in registry-api-service docker image |
|
s.high |
registry-api#2 CICD did not publish the jar on artifactory |
s.medium |
|
registry-api#81 Service using JSON blob in pds4+xml response when it should use ops blob |
s.medium |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry-api#80 As an API caller(user) I want to specify fields for endpoints given a lidvid |
|
p.could-have |
registry-api#8 As a user, I want to see the version of the API specification in the URL of the service |
|
p.should-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry-api#102 add ops:Tracking_Meta/ops:node_name and ops:Tracking_Meta/ops:harvest_date_time to meta section of API response |
|
p.should-have |
registry-api#10 Rename engineering package naming to registry |
unknown |
|
registry-api#105 lidvid resolution need to use _search instead of _doc elasticsearch requests |
p.must-have |
Registry-api-service
PDS Registry API service. Complies with PDS API specification
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry-api-service#79 simple url requested in a browser generate a 500 error |
|
s.critical |
registry-api-service#85 AWS target groups created in terraform do not have intended targets |
|
s.medium |
registry-api-service#88 api should handle request with no Accept header |
|
s.medium |
registry-api-service#102 when fields are selected in the ‘application/kvp+json’ format some extra fields are found |
|
s.medium |
registry-api-service#97 Revert ES High Level Java API version 7.13.3 |
s.critical |
|
registry-api-service#87 service is not handling value of ES login correctly |
|
s.high |
registry-api-service#103 All the supported format don’t show in the swagger-ui |
|
s.medium |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry-api-service#52 As a developer, I was to be able to use AWS Secrets Manager with registry api service |
p.must-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry-api-service#78 Add aws cost tagging and secret/parameter creation to ECS terraform script |
unknown |
|
registry-api-service#81 Support for node-specific routing in API paths |
unknown |
|
registry-api-service#95 add creation of routing rule to terraform script |
s.high |
Registry-common
Common code used by both Harvest and Registry Manager
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry-common#20 Missing support for datetime conversion for ASCII_Date_Time_DOY_UTC |
|
s.low |
Registry-mgr
Tool for managing the Elastic Search back-end Registry Service for tracking, searching, auditing, locating, and maintaining artifacts within the Planetary Data System. See new PDS Registry App for more details (https://github.com/NASA-PDS/pds-registry-app)
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry-mgr#43 Improve error message for corrupted registry_docs.json |
|
s.medium |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
registry-mgr#31 Update registy-mgr to use schema from schemaLocation in file |
|
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#14 B12.0 Prep for I&T
Issue
I&T
Level
Priority / Bug Severity
software-issues-repo#15 Generate Draft B12.0 RDD
task
unknown
software-issues-repo#16 Final testing and delivery to I&T
task
unknown
software-issues-repo#17 B12.1 Generate Release Plan (this theme has not epics in this repository)
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
software-issues-repo#19 viewHostProfile.jsp never returns useful information |
|
s.medium |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
software-issues-repo#9 Update login logic for Resource Manager |
|
s.low |
Template-repo-java
Template for new NASA PDS repositories. For Python software, see https://github.com/nasa-pds/pds-template-repo-python
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
template-repo-java#9 Update README to include more details similar to python template repo |
|
unknown |
Validate
Validates PDS4 product labels, data and PDS3 Volumes
Planned Updates
validate#409 B12.1 PDF/A Handling Improvements
Issue
I&T
Level
Priority / Bug Severity
validate#388 Improve PDF/A validation to include more robust reporting on failures
requirement
p.could-have
validate#412 Update PDF validation to check against flavour specified in PDF metadata
enhancement
unknown
validate#426 B12.1 Content Validation Improvements
Issue
I&T
Level
Priority / Bug Severity
validate#423 Validate does not allow a single-character subdirectory
bug
s.medium
validate#424 Validate does not allow SIP tab file to have lines of differing lengths
bug
s.medium
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
validate#411 Validate repo cannot be checked out on Windows without errors |
|
s.low |
validate#470 Fix validate compilation issues due to removal of veraPDF artifacts from maven central |
|
s.critical |
validate#441 Validate is reporting a ‘String index out of range’ error for a text file |
|
s.high |
validate#435 Array Content Validator is not accepting values at the min/max due to false precision |
|
s.medium |
validate#419 validate 2.2.0-SNAPSHOT warns about a pretty benign bundle + readme.txt |
|
s.medium |
validate#376 Checksums output lowercase and do not accept uppercase checksums |
|
s.low |
validate#461 [SECURITY] Patch log4j library |
|
s.critical |
validate#469 Validate content validation does not handle properly special_constants and field_statistics when they both appear |
|
s.medium |
validate#439 Incorrect Warning for Missing document_standard_id is Stream_Text |
|
s.medium |
validate#349 validate allows absolute path in directory_path_name but shouldn’t |
|
s.medium |
validate#408 Validate 2.1.0-SNAPSHOT skips a collection XML label |
|
s.medium |
validate#447 Validate does not correctly pass PDF/A files that are in a subdirectory |
|
s.high |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
validate#421 Improve warning message for missing_context_reference |
p.must-have |
|
validate#377 Update rule documentation to remove “auto-detect” mention |
unknown |
Wds-react
PDS Web Design System - React Implementation
Planned Updates
wds-react#13 B12.1 Enhancements to DOI Search Component
Issue
I&T
Level
Priority / Bug Severity
wds-react#5 Some findable product do not have links in the search results
bug
s.high
wds-react#9 As a developer, I want to update the DOISearch component backend url in an attribute
requirement
p.should-have
wds-react#10 DOI Search updates per testing
task
unknown
wds-react#12 As a DOI Search user, I want to be able to find a parent data set DOI from a product identifier
requirement
p.must-have
Other Updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
wds-react#28 Hovering Over Status Value Will Crash A Client App |
s.critical |
|
wds-react#27 Hovering Over Status Value Will Crash A Client App |
s.critical |
|
wds-react#29 Fix Search Not Running On First Call For Client App |
s.critical |
|
wds-react#26 Fix Material UI Overriding Client App’s Styling |
s.critical |
Requirements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
wds-react#14 As a PDS.nasa.gov user, I want to search for the DOI for a PDS4 data product from a public facing website (pds.nasa.gov) |
|
p.must-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
|---|---|---|
wds-react#19 Create javascript library for website integration |
|
unknown |
wds-react#17 Combine NPM Package And Embeddable JS Script Toolchains |
unknown |
|
wds-react#4 Add Search DOI Component |
|
unknown |
wds-react#18 Create PDS React Component Library Process For NPM Packages |
|
unknown |
wds-react#8 Create a NPM package |
|
unknown |
wds-react#30 Update NPM Package Documentation |
|
unknown |
wds-react#15 Improve Search UI Behavior For DOI Search Widget |
|
unknown |
wds-react#22 Update DOI Service per user feedback |
unknown |
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#27 Fix issues with app bar dropdown outline on specific browsers / OSes |
s.medium |
Liens
Issue |
Title |
Rationale |
|---|---|---|
pds-swg_15 [CR] B12.1 Defer Registry external source integration task |
[CR] B12.1 Defer Registry external source integration task |
<!– enter rationale for deviation from plan here –> With Product_Metadata_Supplemental and accompanying CSV ingestion supported, a workaround exists for ingesting database data. More use detailed use cases needed for what data needs to be ingested and how we can support it. Additionally, other API tasks have taken precedence ([Staging vs. Operational Data](https://github.com/nasa-pds/pds-registry-app/issues/190), [Handling “deprecated” LIDs and Versions](https://github.com/nasa-pds/pds-registry-app/issues/219)) |
pds-swg_14 [CR] B12.1 Defer Validate Referential Integrity Checking and Logging Improvements |
[CR] B12.1 Defer Validate Referential Integrity Checking and Logging Improvements |
<!– enter rationale for deviation from plan here –> Validate CogE retired in December causing significant delays in content validation improvements and bug fixes (https://github.com/nasa-pds/validate/issues/426). Considering content validation is a critical component ensuring a valid archive, these tasks for improvements to existing capabilities is being tabled to B13.0. |
Engineering Node Software Catalog
The Engineering Node Software resources are listed in the Software Release Summary (B12.1)
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)