Build 11.1 Plan¶
- Build 11.1 Plan
- Key Dates
- Planned PDS4 Information Model Changes
- Planned Software Changes
- Other Information
The Planetary Data System (PDS) is a long-term archive of digital data products returned from NASA’s planetary missions, and from other kinds of flight and ground-based data acquisitions, including laboratory experiments. But it is more than just a facility - the archive is actively managed by planetary scientists to help ensure its usefulness and usability by the world wide planetary science community.
The following page outlines the planned PDS software enhancements, bug fixes, and impacted requirements for the upcoming Build .
A more detailed breakdown of these tasks by date and priority can be found in our Zenhub Roadmap (login required).
Delivery to I&T
The PDS4 IM and all software updated during this build cycle are delivered to EN I&T.
Test Readiness Review (TRR)
PDS EN internal review to verify readiness to enter I&T phase.
Delivery and Deployment Review (DRR)
PDS internal review with PDS Software Working Group to verify readiness to deploy build system.
PDS4 system is operationally deployed and website is updated accordingly.
For a more detailed schedule, see https://pds-engineering.jpl.nasa.gov/content/schedules.
Planned PDS4 Information Model Changes¶
This section details the planned changes to the PDS4 Information Model for this build. These changes are deliverables by the PDS Data Design Working Group (DDWG) to the Engineering Node for implementation.
pds4-information-model#258 CCB-301: The attribute <name> in the <DD_Attribute> and <DD_Class> classes is not properly constrained
pds4-information-model#256 CCB-312: <ldd_version_id> does not appear to be constrained the way LDDTool expects
pds4-information-model#254 CCB-305: Missing validation constraint on <specified_unit_id>
pds4-information-model#253 CCB-313: Definition of <external_source_product_identifier> refers to non-existent documentation
pds4-information-model#249 CCB-288: Change Internal_Reference reference type to ‘guided’ text
pds4-information-model#257 CCB-302: No <reference_type> values defined in DD_Attribute or DD_Class contexts
pds4-information-model#255 CCB-300: Apparently deprecated units of measure are not actually deprecated
pds4-information-model#251 CCB-303: The definition for <skos_relation_name> is not sufficient.
pds4-information-model#250 CCB-315: “PDS3” is an allowed parsing standard for Bundle documentation file
Planned Software Changes¶
This section details the planned software changes for this build.
Planned tasks for the next release cycle are grouped by software component, and sub-tasks are included where known at the time of this plan generation. Each section also includes additional information, such as:
Link to 🔍 User Guide
Link to 💻 Github Repo
Link to 🚑 Issue Tracking
Link to 📒 Backlog - future work not planned for this release cycle
Don’t see the tool you are looking for? This means there is no active development planned for this build cycle. Head to the PDS Tool Registry to see all possible tools available for PDS data.
Have a new feature or tool you think we should be working on? Create a ticket in the applicable Github repo or in our PDS EN Operations repo and we will see how that can fit into our plans moving forward.
Validates PDS4 product labels, data and PDS3 Volumes
- validate#250 Improvements to meet updated Standards Reference since initial requirements implementation
validate#5 Improve file base name check according to Standards Reference
validate#6 Improve pds4.bundle unlabeled files check to handle files without a file suffix
validate#11 Update allowable field_format values per Standards Reference definition regarding [+|-] characters
validate#81 Validate and throw error when duplicate LIDs are found in Bundle
validate#153 Update validate to throw error when a file has a space in the filename
validate#230 Update validate per SR requirements for collection inventories
validate#240 Unexpected error for data collection in a sub-directory
validate#242 Update LID validation to meet latest PDS4 SR Requirements
- validate#249 Improvements for validating accumulating bundles / collections
validate#51 Provide the capability to specify multiple locations for pds4.bundle validation
validate#231 For accumulating bundles, validate latest version of collections only
validate#238 validate does not perform full bundle validation when using a specific bundle.xml
validate#246 Add output directory flag to validate-bundle tool
validate#256 validate should only do integrity checking on latest version of a collection when referenced by LID
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.
The software tools and data necessary for generating the Information Model including PDS4 ontology, data, and information model.
- pds4-information-model#241 Improvements from Build 11.0 testing
pds4-information-model#104 LDDTool: Enable to ability to set custom namespace base URI in IngestLDD
pds4-information-model#175 LDDTool: Displaying invalid Imaging Discipline Classes
pds4-information-model#186 PDS4_PDS_1E00.sch inconsistent rules for type of Investigation vs Investigation_Area
pds4-information-model#235 Incorrect error messages for DD_Associate_External_Class
PDS Open Archival Information System (OAIS) utilities, including Submission Information Package (SIP) and Archive Information Package (AIP) generators
pds-deep-archive#80 NSSDCA Delivery Onboarding
Service and tools for generating DOIs for PDS bundles, collections, and data sets
- pds-doi-service#52 API Implementation for DOI Service
pds-doi-service#38 Add Status / Query component to API
pds-doi-service#77 Add POST PDS4 or OSTI DOI label to API
pds-doi-service#78 Add POST Reserve xslx/csv DOI function to API
pds-doi-service#79 Add Release DOI function to API
pds-doi-service#80 Develop API specification in SwaggerHub
pds-doi-service#100 Add GET DOI to the API
pds-doi-service#101 Add PUT DOI to the API (for updates)
pds-doi-service#105 Complete get DOIS criterias with the arguments proposed in command line
pds-doi-service#106 Add exception name in the error messages
pds-doi-service#107 allow to post PDS4 labels in the payload (for draft)
pds-doi-service#91 Develop User Access / Management Strategy
pds-doi-service#23 Document how to Deactivate a DOI (with curl command)
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.
pds-registry-app#42 Integrate Registry API into pds-registry-app
- pds-registry-app#27 Manage PDS4 product relationships
pds-registry-app#92 Update Registry API per PDS API v0-beta
- pds-registry-app#91 Deploy Registries in AWS
pds-registry-app#81 Registry Integration component
pds-registry-app#12 Ingest PDS supplemental metadata
- pds-registry-app#53 Improve Attribute Search Component
pds-registry-app#45 Validate Elastic Search index configuration for attribute search
pds-registry-app#61 Update the index schema in ES dynamically when new record are ingested
pds-registry-app#64 Fix the Json data dictionary format
pds-registry-mgr-elastic#5 Create a field-data type lookup table
pds-registry-mgr-elastic#6 Update the field-data type lookup table
pds-registry-app#93 Research tech stack modifications due to large number of search fields in registry
Front-end interface for PDS.nasa.gov data search capability
- PDS.nasa.gov-Search#21 DOI Landing Page Requirements and Design
PDS API Application with client and server integrated into one package
pds-api#31 Streamline testing of API server implementation
- pds-api#17 Response format conventions and parameter definition
pds-api#18 Refine format conventions defined by the API WG
pds-api#19 Define default response fields
pds-api#20 Define required response fields
pds-api#21 Define response formatting for default vs “additional” metadata fields
pds-api#22 Update API Spec with refined response format conventions and field definitions
pds-api#23 Implement response format definition in API Service
pds-api#35 Initial Federated API implementation
pds-api#24 Define PDS handling of enriched / supplemental metadata
pds-api#25 PDS API extension convention for discipline-specific search engines
pds-api#15 Query passing and search integration design
pds-api#14 Define intra-discipline (product-level) search scope
pds-api#12 Initial Query Syntax Lexer Implementation
pds-api#7 Initial discipline/node-specific search parameter definition
*umbrella project to manage the build cycle (continuous integration and stable release) for the PDS EN tools. *
- pdsen-corral#16 Github Action and Documentation Generation Best Practices
nasa-pds.github.io#3 Update nasa-pds.github.io with software documentation best practices
nasa-pds.github.io#4 Update nasa-pds.github.io with github action best practices
pds-template-repo-python#2 Define a PDS standard to manage version in python project
pds-deep-archive#81 Update Github Actions for dev and ops releases
pds-doi-service#94 Update to use pds round-up github action
roundup-action#1 Add Java / Maven support
pdsen-corral#24 Re-evaluate generating requirements for -dev versions
pds-template-repo-python#3 Add the roundup action in the template
validate#255 Retrofit validate CI to use roundup-action
pds4-jparser#30 Retrofit pds4-jparser CI to use roundup-action
pds-registry-app#94 Retrofit pds-registry-app CI to use roundup-action
pdsen-corral#23 AWS Continuous Deployment Implementation
pdsen-corral#22 Integration with Test Rail
pdsen-corral#20 AWS Continuous Deployment Strategy
PDS.nasa.gov User Experience Task Issue and Prototype repository
PDS.nasa.gov-UX#6 Model workflows and initial design directions
- PDS.nasa.gov-UX#47 Design System Documentation
pds-wds#1 Show Text Field component that displays units
pds-wds#2 Add other organizational logos
pds-wds#4 Propagate PDS brand colors across all components in Figma
pds-wds#6 Define types of banner notifications
pds-wds#8 Document UI guidelines and rules
pds-wds#9 Restructure component organization in Figma
PDS.nasa.gov-UX#54 Relay for Figma (continuous delivery)
PDS.nasa.gov-UX#45 WDS Mobile Considerations
- PDS.nasa.gov-UX#31 Formulate PDS Information Architecture
Tickets for the PDSEN Operations Team
Provides functionality for tracking status and other aspects pertaining to PDS products that are not captured in the Registry Service.
pds-tracking-service#1 Open Source Tracking Service
This section details the controlling and applicable documents referenced for this release. The controlling documents are as follows:
PDS Level 1, 2 and 3 Requirements, April 20, 2017.
PDS4 Project Plan, July 17, 2013.
PDS4 System Architecture Specification, Version 1.3, September 1, 2013.
PDS4 Operations Concept, Version 1.0, September 1, 2013.
PDS General System Software Requirements Document (SRD), Version 1.1, September 1, 2013.
PDS Harvest Tool Software Requirements and Design Document (SRD/SDD), Version 1.2, September 1, 2013.
PDS Preparation Tools Software Requirements and Design Document (SRD/SDD), Version 0.3, September 1, 2013.
PDS Registry Service Software Requirements and Design Document (SRD/SDD), Version 1.1, September 1, 2013.
PDS Report Service Software Requirements and Design Document (SRD/SDD), Version 1.1, September 1, 2013.
- PDS Search Service Software Requirements and Design Document (SRD/SDD), Version 1.0, September 1, 2013.
PDS Search Scenarios, Version 1.0, September 1, 2013.
PDS Search Protocol, Version 1.2, March 21, 2014.
PDAP Search Protocol, Version 1.0, March 21, 2014.
PDS Security Service Software Requirements and Design Document (SRD/SDD), Version 1.1, September 1, 2013.
PDS NSSDC Delivery Software Requirements and Design Document (SRD/SDD), Version 0.1, October 29, 2019.
System Requirements, Dependencies, and Assumptions¶
See individual applications for specific dependencies and system requirements.