Release Description Document (Build B13.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 B13.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-350: Adopt more rigorous / stringent rules for leap seconds and use of “24:00:00” in datetimes |
|
CCB-360: Add new permissible value to Units_of_Misc |
|
CCB-361: Add a permissible value for microradians to Units_of_Angle |
|
CCB-362: Add a permissible value of nm/mm to Units_of_Misc |
|
CCB-354: Add new permissible values to Header/parsing_standard_id to support new versions of CDF |
|
CCB-355: Add Funding_Acknowledgement class to Citation_Information Class |
|
CCB-325: Support for video and audio as product observational |
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.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, 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.
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#24 Re-imagine and Implement New Registry Architecture in AWS
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
cloud-tasks#34 Phase 1: Plan and Architect SBN-PSI Catalina Sky Survey Migration
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
cloud-tasks#40 NGAP Onboarding
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
cloud-tasks#57 Prototype and Adapt ESDIS Thin Egresss App (TEA) for PDS
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
cloud-tasks#60 Develop initial PDS Cloud Cost Model
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
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#145 Canonical path is not processed correctly (‘/../ in path) |
🟡 |
s.critical |
deep-archive#134 Cannot connect to any PDS API endpoints for pds-deep-archive-registry |
🟡 |
s.high |
deep-archive#137 Pagination handling does not appear to work properly for pds-deep-registry-archive |
🟡 |
s.high |
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#377 DOI Service does not accurately parse <author_list> and <editor_list> in XML labels |
🟢 |
s.medium |
doi-service#403 CICD: build does not work because of dependency conflicts |
🔵 |
s.high |
doi-service#398 Still – Unable to generate / export json report of DOI metadata |
🟡 |
s.medium |
Requirements
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
doi-service#283 As a publisher, I want to be notified when a new DOI has been minted or significant update to the metadata |
🟢 |
p.could-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 |
Enhancements
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
doi-service#363 Enhance weekly reporting to push to ADS SFTP server |
🔵 |
p.must-have |
Doi-ui
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
doi-ui#153 Develop DOI Editor and Service Documentation
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
Other Updates
Bugs
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
doi-ui#167 doi-editor release ui inoperable under Firefox |
🟡 |
s.high |
doi-ui#130 Remove vulnerabilities from the package per npm audit |
🟡 |
s.high |
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 Status |
Priority / Bug Severity |
|---|---|---|
harvest#112 –overwrite flag is not respected for <bundles> elements in harvest config |
🟡 |
s.high |
harvest#102 Harvest skips path that is the root of a soft link |
🟢 |
s.high |
Enhancements
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
harvest#106 Improve skipped product INFO message |
🟡 |
p.should-have |
Nucleus
None
Planned Updates
nucleus#2 Initial Implementation and Operationalize Nucleus
Issue |
I&T Status |
Level |
Priority / Bug Severity |
|---|---|---|---|
nucleus#29 As a user, I want to know the baseline architecture and deployment |
🟡 |
requirement |
p.must-have |
nucleus#14 B13.1 Technology Selection and Internal Review
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
nucleus#16 Develop Cost Model
Issue |
I&T Status |
Level |
Priority / Bug Severity |
|---|---|---|---|
nucleus#37 Prepare cost model for Nucleus - Considering Amazon Managed Airflow (Amazon MWAA) |
🟡 |
task |
unknown |
nucleus#18 Develop Detailed Technical Architecture
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
Operations
Tickets for the PDSEN Operations Team
Planned Updates
operations#309 Initial Wordpress migration for pds-engineering website
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
operations#369 B13.1 Prep and Stage IM and Tools for I&T
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
Pds-api
PDS web APIs specifications and user’s manual
Planned Updates
pds-api#181 Initial PDS Keyword Search Design
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
pds-api#230 Support latest product search from API
Issue |
I&T Status |
Level |
Priority / Bug Severity |
|---|---|---|---|
pds-api#220 Past versions are being returned by API, by default |
🟡 |
bug |
s.high |
pds-api#221 As a user, I want to query only the latest versions of products unless explicitly requested |
🟡 |
requirement |
p.must-have |
pds-api#235 Enable Swagger Interface on pds.nasa.gov
Issue |
I&T Status |
Level |
Priority / Bug Severity |
|---|---|---|---|
pds-api#193 As a user, I want to be able to access the Search API Swagger interface from pds.nasa.gov |
🟡 |
requirement |
p.must-have |
pds-api#239 As a user, I want to get application/json response format by default if I request an API url in my browser |
🟡 |
requirement |
p.should-have |
Other Updates
Bugs
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
pds-api#215 vnd.nasa.pds.pds4+xml format does not return information |
🟢 |
s.medium |
pds-api#257 Search API documentation seems outdated? |
🔵 |
s.medium |
pds-api#196 Swagger API page does not show the expected deployed API version |
🟡 |
s.low |
pds-api#214 vnd.nasa.pds.pds4+json format does return information |
🟡 |
s.medium |
pds-api#240 API Client cannot connect to current deployed API |
🟡 |
s.high |
pds-api#213 Accept header of text/csv returns blank lines |
🟡 |
s.medium |
pds-api#251 link to registry-api documentation from registry page is incorrect |
🔵 |
s.low |
pds-api#200 API performance degradation from B12.1 release |
🟡 |
s.high |
pds-api#199 hits appears to be showing the current page count, not the overall number of its |
🟡 |
s.medium |
Requirements
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
pds-api#198 As a user, I want query responses for empty results to be clearly documented |
🟢 |
p.should-have |
pds-api#175 As a user, I want to know how to query observational data only |
🟡 |
p.must-have |
Enhancements
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
pds-api#194 Develop NASA/PDS Skin for Search API Swagger interface |
🟢 |
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#513 B13.1 Prep IM and LDDTool for new IM Version
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
pds4-information-model#544 Test and Validate Term Mapping Implementation
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
pds4-information-model#546 B13.1 Continue Refactoring the IMTool/LDDTool Code
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
pds4-information-model#547 B13.1 Updates per CCB-Approved SCRs
Issue |
I&T Status |
Level |
Priority / Bug Severity |
|---|---|---|---|
pds4-information-model#599 CCB-360: Add new permissible value to Units_of_Misc |
🟢 |
requirement |
p.must-have |
pds4-information-model#602 CCB-361: Add a permissible value for microradians to Units_of_Angle |
🟢 |
requirement |
p.must-have |
pds4-information-model#603 CCB-362: Add a permissible value of nm/mm to Units_of_Misc |
🟢 |
requirement |
p.must-have |
pds4-information-model#608 CCB-354: Add new permissible values to Header/parsing_standard_id to support new versions of CDF |
🟢 |
requirement |
p.must-have |
pds4-information-model#611 CCB-355: Add Funding_Acknowledgement class to Citation_Information Class |
🟢 |
requirement |
p.must-have |
pds4-information-model#616 CCB-325: Support for video and audio as product observational |
🟢 |
requirement |
p.must-have |
pds4-information-model#548 B13.1 Expand Support for SKOSS Terminological Entry Mapping
Issue |
I&T Status |
Level |
Priority / Bug Severity |
|---|---|---|---|
pds4-information-model#544 Test and Validate Term Mapping Implementation |
🔵 |
theme |
unknown |
pds4-information-model#549 B13.1 Initial Support for Target Ontology Project
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
pds4-information-model#625 B13.1 Document Updates
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
Other Updates
Bugs
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
pds4-information-model#506 hyb2 has incorrect namespace for IM v1.14 |
🔵 |
s.medium |
pds4-information-model#507 Bug generating BepiColombo SERENA dictionary |
🔵 |
s.medium |
pds4-information-model#606 LDDTool does not write a DocBook file for the Common Dictionary |
🔵 |
s.medium |
pds4-information-model#648 Revert date format change from #641 in Product_XML_Schema |
🟡 |
s.high |
pds4-information-model#618 Information Model does not have Product_External included in Identification_Area.product_class |
🟢 |
s.critical |
Requirements
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
pds4-information-model#458 As a developer I want to have the PDS4 Information Model expressed in the RDF/OWL/TTL format. |
🔵 |
p.should-have |
pds4-information-model#473 As a user, I want to describe a relationship between an attribute in the model and the column of a table |
🟢 |
p.should-have |
pds4-information-model#502 CCB-350: Adopt more rigorous / stringent rules for leap seconds and use of “24:00:00” in datetimes |
🟢 |
p.must-have |
pds4-information-model#620 As a user I want to export the IM in the RDF/OWL format in RDF format |
🔵 |
p.could-have |
Enhancements
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
pds4-information-model#641 Update date format to be timezone aware |
🔵 |
unknown |
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
Bugs
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
pds4-jparser#57 Parse failure for table fields of type ASCII_Numeric_Base16 |
🟡 |
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#56 SQL permission on data-search |
🔵 |
s.critical |
portal-tasks#69 Freedom of Information Act link is sending users to an Access Denied page. |
🟡 |
s.low |
portal-tasks#31 Data release manager pages missing login session check |
🟡 |
s.medium |
portal-tasks#8 URL Encoding errors from Subscription Service pages |
🟡 |
s.medium |
portal-tasks#68 Links returning 404 |
🟡 |
s.low |
portal-tasks#54 Possible XSS vulnerability on data set view pages |
🟡 |
s.critical |
portal-tasks#47 [SECURITY] JQuery upgrade needed to avoid possible injection |
🟡 |
s.high |
portal-tasks#55 dataset status needs to be updated to better handle potential security vulnerability |
🟡 |
s.critical |
Enhancements
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
portal-tasks#57 Add new MILabel video and presentation to training site |
🔵 |
p.must-have |
portal-tasks#49 Update DataSet View to display DOI from label if there is no DOI for the product in our database |
🟢 |
p.should-have |
portal-tasks#58 Update PDS4 data dictionary links to be more consistent between Common and Local DD links |
🔵 |
unknown |
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#148 Develop Simple Dashboard for Node Monitoring
Issue |
I&T Status |
Level |
Priority / Bug Severity |
|---|---|---|---|
registry#130 As a user, I want to view dashboard report of bundles with archive status and other tracking information |
🟢 |
requirement |
p.should-have |
Other Updates
Bugs
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
registry#136 follow on to #118, registry-manager still unable to change archive status on bundle contents |
🟡 |
s.high |
registry#159 ref_collection_lidvid field in some node registries populated using older versions of registry loader tools create string fields in the schema vs. the expected list types |
🟢 |
s.medium |
registry#120 Continuous Delivery not working with OpenSearch |
🔵 |
s.medium |
registry#97 registry-manager won’t set archive-status on some collections |
🟢 |
s.high |
registry#118 archive status value was not changed on bundle’s contents |
🟡 |
s.high |
registry#146 OpenSearch service of Registry won’t start on Linux |
🟡 |
s.high |
registry#150 TLS termination listening on wrong port |
🟡 |
s.medium |
Requirements
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
registry#52 As a user, I want to indicate a product has been superseded |
🟢 |
p.should-have |
registry#100 Update documentation to include explicit example of how to query staged data |
🟢 |
p.must-have |
registry#153 As a user, I want to all metadata attributes to be searchable |
🟡 |
p.must-have |
Enhancements
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
registry#100 Update documentation to include explicit example of how to query staged data |
🟢 |
p.must-have |
registry#139 Update docs to be more clear that there is a required next step after data ingestion |
🔵 |
unknown |
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#257 B13.1 Fix must-have bugs for Registry API
Issue |
I&T Status |
Level |
Priority / Bug Severity |
|---|---|---|---|
registry-api#241 requests with bad q= syntax should return 400 error |
🟡 |
bug |
s.medium |
registry-api#258 not found lidvid does not return 404 error |
🟡 |
bug |
s.medium |
registry-api#260 api does not return 400 error when q parameter value cannot be parsed |
🟡 |
bug |
s.medium |
registry-api#261 The members of a bundle can not be requested |
🟡 |
bug |
s.high |
registry-api#287 Search criteria not producing expected matches |
🟢 |
task |
unknown |
Other Updates
Bugs
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
registry-api#196 documents / members returns an error |
🟡 |
s.high |
registry-api#211 swaggger ui error in production |
🟢 |
s.high |
registry-api#207 lidvid not found raises 500 error |
🟡 |
s.high |
registry-api#121 Fix vulnerabilities raised by sonalift |
🟡 |
s.high |
registry-api#240 Pagination not working as expected with /collections/{identifier}/products |
🟡 |
s.high |
registry-api#200 /classes endpoint does not work in a browser |
🟡 |
s.medium |
registry-api#227 Keyword search does not work on registry-api deployed on pds.nasa.gov |
🟡 |
s.medium |
registry-api#234 registry-api does not respect VID when a LIDVID is used as an id, instead returns latest version |
🟡 |
s.high |
registry-api#231 /classes/collections/<lidvid>/members (and deprecated equivalent) hangs |
🟡 |
s.high |
registry-api#191 version number are treated as floats |
🟡 |
s.medium |
registry-api#206 When q=”” the returned status is 500 instead of 400 |
🟡 |
s.low |
registry-api#148 Critical OSS Vulnerability: spring-web@5.3.20 |
🟡 |
s.low |
registry-api#202 observational end-point returns collections |
🟢 |
s.high |
registry-api#190 /all suffix returns a message which I don’t understand |
🟢 |
s.high |
registry-api#224 registry-api does not return latest version of product metadata when multiple versions are harvested |
🟢 |
s.high |
registry-api#293 Requests with Accept:application/vnd.nasa.gds.pds4+json fail for products with no ops:Label_File_Info/ops:file_name |
🔵 |
s.high |
Requirements
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
registry-api#223 As a user, I want to know the members of a bundle product |
🟢 |
p.must-have |
registry-api#212 As a user, I want the API to support redundant / in the url |
🟢 |
p.should-have |
registry-api#248 Suggest: Return Content-Type application/json by default |
🟡 |
unknown |
registry-api#208 As a registry-tool/registry-user I want to ensure leading multiple forward-slashes in request paths are stripped out |
🟢 |
p.should-have |
registry-api#282 As a user, I want to search by any metadata attribute |
🟢 |
p.must-have |
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#32 JSON BLOB performs undesirable conversion of floating-point types with int-like values |
🟡 |
s.high |
registry-common#31 Registry manager fails with updates to LDDTool to support ISO Formatted dates |
🟡 |
s.high |
Registry-crawler-service
Server application providing the functionality for crawling PDS4 products. It has to be used with other components, such as RabbitMQ message broker, Harvest Server and Harvest Client to enable performant ingestion of large data sets into PDS Registry (https://github.com/NASA-PDS/registry).
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
registry-crawler-service#24 Stable Roundup can no longer trigger Imaging workflow |
🔵 |
unknown |
Registry-harvest-cli
Client application providing the functionality for capturing and indexing product metadata into the PDS Registry system (https://github.com/NASA-PDS/registry). Different from the standalone Harvest Tool, this goes along with Crawler and Harvest Server to enable performant ingestion of large data sets.
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
registry-harvest-cli#16 Stable Roundup can no longer trigger Imaging workflow |
🔵 |
unknown |
Registry-harvest-service
Server application providing the functionality for capturing and indexing product metadata into the PDS Registry system (https://github.com/NASA-PDS/registry). Different from the standalone Harvest Tool, this goes along with Crawler and Harvest Client to enable performant ingestion of large data sets.
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
registry-harvest-service#25 Harvest service sometimes skips collection inventory files |
🟢 |
s.high |
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#57 ref_lid_collection error when ingesting data sets |
🟡 |
s.medium |
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#103 unstable build failed |
🔵 |
s.medium |
roundup-action#98 git push in roundup action failing w/ remote ahead of local |
🔵 |
s.low |
roundup-action#105 Roundup broken for python repos |
🔵 |
s.medium |
roundup-action#96 Roundup failing on unstable build |
🔵 |
s.medium |
roundup-action#104 Versions in CHANGELOG off a bit since we moved to release tagging scheme on Java projects |
🔵 |
s.medium |
Software-issues-repo
Issue tracking repository as a centralized entry point for general PDS software bugs and feature requests.
Planned Updates
software-issues-repo#52 B13.1 Planning
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
Template-repo-python
*template repository for PDS python developments *
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Bugs
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
template-repo-python#67 Local pre-commit checks pass, but in branch workflow fails |
🔵 |
s.medium |
Validate
Validates PDS4 product labels, data and PDS3 Volumes
Planned Updates
validate#414 Referential Integrity Checking with the Registry+API
Issue |
I&T Status |
Level |
Priority / Bug Severity |
|---|---|---|---|
validate#415 As a user, I want to validate all internal references to products in the PDS archive are valid |
🟡 |
requirement |
p.must-have |
validate#601 Create command-line script to wrap the new registry referential integrity checker |
🔵 |
enhancement |
p.must-have |
validate#481 B13.1 Content Validation Improvements: Intermingled Headers
Issue |
I&T Status |
Level |
Priority / Bug Severity |
|---|---|---|---|
validate#425 Refactor content validation to more robustly handle intermingled Headers |
🟢 |
enhancement |
p.must-have |
validate#480 Validate does not calculate overlaps correctly when Header is not first object in file |
🟢 |
bug |
s.medium |
validate#498 Improve Content Validation Performance through Spot Checking
Issue |
I&T Status |
Level |
Priority / Bug Severity |
|---|---|---|---|
validate#1 As a user, I want to execute content validation against every nth file |
🟢 |
requirement |
p.could-have |
validate#557 Dockerize Validate
Issue |
I&T Status |
Level |
Priority / Bug Severity |
|---|---|---|---|
validate#556 As a user, I want to be able to use validate from a docker container |
🟢 |
requirement |
p.should-have |
validate#578 B13.1 Fix Must-Have Priority Bugs
Issue |
I&T Status |
Level |
Priority / Bug Severity |
|---|---|---|---|
validate#444 pds4.bundle option seems to not travel through enough subdirectories |
🟢 |
bug |
p.must-have |
validate#453 Validate should not check PDF/A validity if content validation is disabled |
🟢 |
bug |
p.must-have |
validate#474 Validate can’t find files in directory specified by <directory_path_name> |
🟢 |
bug |
p.must-have |
validate#499 validate doesn’t flag a data file with only LF |
🟢 |
bug |
p.must-have |
validate#503 validate passes confusing message to the command window |
🟢 |
bug |
p.must-have |
validate#511 Table_Character not accurately checking field formats |
🟢 |
bug |
p.must-have |
validate#514 Validate does not catch NaNs in Binary Tables |
🟢 |
bug |
s.medium |
validate#519 Validate should throw record length error when record delimiter does not occur in correct location |
🟢 |
bug |
p.must-have |
validate#529 ERROR [error.array.value_out_of_min_max_range] evaluation is not correct |
🟢 |
bug |
p.must-have |
validate#531 ERROR [error.table.bad_file_read] incorrectly reports that GroupFieldBinary group_length is larger than size of contained fields |
🟢 |
bug |
p.must-have |
validate#544 validate gives a error.table.bad_field_read error |
🟢 |
bug |
p.must-have |
validate#554 –spot-check-data flag throws IOException |
🟢 |
bug |
p.must-have |
validate#564 Array object validation regression in v3.0.3 |
🟢 |
bug |
p.must-have |
validate#576 validate does not correctly handle field format checks for hex values |
🟢 |
bug |
p.must-have |
validate#597 Validate does not maintain history of other versions it comes across as it traverses directories causing erroneous WARNING messages |
🟢 |
bug |
s.medium |
Other Updates
Bugs
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
validate#593 Regression in validate no longer enabling CRLF to be embedded within a Table_Character record |
🟢 |
s.high |
validate#155 Fix uncaught exception error when validating an array object |
🟢 |
s.low |
validate#551 Validate fails regression test on issue 188 |
🟢 |
s.medium |
validate#616 validate does not correctly validate byte offsets to data objects |
🟢 |
s.high |
validate#614 invalid_object_definition occurs upon out-of-order data objects |
🟡 |
s.medium |
validate#620 verbosity flag does not appear to output INFO messages |
🔵 |
s.medium |
validate#473 NullPointerException when Table_Delimited is missing records attribute |
🟢 |
s.low |
Requirements
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
validate#596 As a user, I want to validate all products referenced from a collection exist within the archive |
🟢 |
p.must-have |
validate#595 As a user, I want to validate all collections referenced from a bundle exist within the archive |
🟢 |
p.must-have |
validate#316 As a user, I want to validate all internal references from one product to another exist within the archive |
🟢 |
p.must-have |
Enhancements
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
validate#436 Improve error messages for overlapping objects in a label |
🟢 |
p.should-have |
validate#569 Improve error message when file is truncated and cannot be read |
🟢 |
p.could-have |
validate#537 Refactor getMessageCountBasedOnProblemType function using introspection |
🔵 |
unknown |
validate#434 Scaled value min/max error does not display scaled value |
🔵 |
p.should-have |
Wds-implementation
PDS Web Design System
Planned Updates
wds-implementation#22 Initial Data Search Journey Prototype
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
Web-analytics
None
Planned Updates
No planned updates realized for this build in this repository.
Other Updates
Requirements
Issue |
I&T Status |
Priority / Bug Severity |
|---|---|---|
web-analytics#2 As a data engineer, I want to sync logs from PDS website in an automated fashion |
🟡 |
p.should-have |
Web-modernization
PDS.nasa.gov Web Modernization repo for managing the overall design process and user testing for modernizing the PDS web experience.
Planned Updates
web-modernization#161 B13.1 User Journey Figma Prototyping: Homepage & Search
No requirements, significant enhancements, or bug fixes identified for this Build. See theme for more details.
Liens
Issue |
Title |
Rationale |
|---|---|---|
pds-swg_21 [CR] Defer Validate Content Validation Improvements |
[CR] Defer Validate Content Validation Improvements |
Numerous bug fixes added onto the front half of the build implementation pushed out all other higher priority improvements. This will move onto B14.0 stack. Additionally, a lot of these tickets may have been fixed or improved from some of the bug fixes from B13.1, but we have not had the time to come up with sufficient test data to test all the table types. |
Engineering Node Software Catalog
The Engineering Node Software resources are listed in the Software Release Summary (B13.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)