Release Description Document (build B12.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 B12.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-283: Add reference_type value document_to_data |
|
CCB-329 - Broaden Definition of Attribute aperture |
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’ which are defined at the planing phase (see plan B12.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…)
The deliveries are validated by the development team and most of time, when relevant, also go through an additional Integration & Test process as indicated by a specific icon in the following tables.
archive-analytics
Processes, tools, and configuration for managing PDS archive analytics software and reports
Planned Updates
No planned update realised in the build in this repository.
Other updates
Requirements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
archive-analytics#7 As a PDS Project Office, I want to know the historical total volume of PDS holdings over time |
p.must-have |
|
archive-analytics#2 As a manager, I want to know the current total volume of PDS holdings |
p.must-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
archive-analytics#16 Develop procedure and export of Kibana config |
unknown |
cloud-strategy
PDS Cloud Migration documentation, issue, tracking and simple tools for assisting in the PDS hybrid cloud study and migration efforts.
Planned Updates
cloud-strategy#2 B12.0 Refine AWS Registry Deployment Strategy (no
epic in this repository)
devops
Parent repo for PDS DevOps activities
Planned Updates
devops#4 Refine Continuous Integration processes
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
devops#5 As an EN developer, I want to make sure I have access to all PDS repos. |
requirement |
p.could-have |
|
devops#6 As a developer, I want to make sure I have access to all our Python PyPi package repos. |
requirement |
p.could-have |
devops#3 Develop and implement PDS CD Strategy (no epic in this
repository)
devops#9 Improvements per JPL-PDS Open Source Policy (no epic in
this repository)
Other updates
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 update realised in the build in this repository.
Other updates
Requirements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
harvest#60 As a user, I want to ingest the PDS4 label as JSON in a binary blob form |
p.should-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
harvest#58 Enable blob ingestion by default |
p.must-have |
|
harvest#55 Quick fix to support date/time conversion to “ISO instant” format |
p.must-have |
operations
Tickets for the PDSEN Operations Team
Planned Updates
No planned update realised in the build in this repository.
Other updates
Enhancements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
operations#141 Forward old proposing pages to new web page |
unknown |
pds-api
PDS API Application with client and server integrated into one package
Planned Updates
pds-api#24 [registry] Handle PDS Supplemental Metadata
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
pds-api#67 As an API user, I want to access supplemental metadata from Product_Metadata_Supplemental. |
requirement |
p.must-have |
pds-api#76 [pds-api] Improve API Performance
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
pds-api#80 As a developer, I never want the label blob to be returned |
requirement |
p.must-have |
pds-api#75 [pds-api] B12.0 API Response Improvements
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
pds-api#91 Disable XML and HTML responses from current registry-api-service implementation |
enhancement |
p.should-have |
|
pds-api#101 As a user, I want to receive a JSON response that contains the PDS4 label metadata in JSON format (application/pds4+json) |
requirement |
p.must-have |
|
pds-api#105 As an API user, I want to know how long a request took to complete |
requirement |
p.should-have |
pds-api#77 [pds-api] PDS4 Product Relationships
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
pds-api#56 As an API user, I want to know the children and ancestors of bundle, collections, and products |
requirement |
p.must-have |
|
pds-api#59 As an API user, I want to know the Product(s) that belong to a given Bundle. |
requirement |
p.must-have |
|
pds-api#60 As an API user, I want to know the Bundle for a given Product. |
requirement |
p.must-have |
|
pds-api#61 As an API user, I want to know the Collection(s) for a given Product. |
requirement |
p.must-have |
|
pds-api#62 As an API user, I want to know the Bundle for a given Collection. |
requirement |
p.must-have |
pds-api#79 [pds-api] PDS Core Registry (no epic in this repository)
pds-api#81 [pds-api] B12.0 Improve API query handling
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
pds-api#83 As an API user, I want to search using URL parameters |
requirement |
p.must-have |
pds-api#84 [pds-api] Initial Google-like Search
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
pds-api#99 As an API user, I want to be able to use the API for free text search |
requirement |
p.must-have |
Other updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-api#73 As a n00b paginator, there might be an off-by-1 error in the limit parameter |
s.medium |
Requirements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-api#68 As an API user, I want to know in the response how many hits are returned for an API query. |
p.must-have |
|
pds-api#96 As an API user, I want to get the latest version of a product, by default |
p.must-have |
|
pds-api#107 As an API user, I want to explicitly request the latest version of a product |
p.could-have |
|
pds-api#95 As a user, I want to query for all versions of a product |
unknown |
pds-api-client
PDS API Client
Planned Updates
No planned update realised in the build in this repository.
Other updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-api-client#6 Stack trace when calling BundlesApi.bundle_by_lidvid |
s.medium |
pds-deep-archive
PDS Open Archival Information System (OAIS) utilities, including Submission Information Package (SIP) and Archive Information Package (AIP) generators
Planned Updates
pds-deep-archive#105 Integrate PDS Deep Archive with Registry
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
pds-deep-archive#7 As a user, I want to generate AIPs and SIPs using Registry |
requirement |
p.should-have |
|
pds-deep-archive#106 Improvements per API updates to remove workarounds from code |
enhancement |
p.must-have |
Other updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-deep-archive#116 deep archive misses products that specify primary products using lower case ‘p’ |
s.low |
pds-doi-service
Service and tools for generating DOIs for PDS bundles, collections, and data sets
Planned Updates
pds-doi-service#86 Deploy DOI API and UI
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
pds-doi-service#87 Dev beta testing with API |
task |
unknown |
|
pds-doi-service#90 Deploy point build of DOI service and UI |
task |
unknown |
|
pds-doi-service#145 review the full doi workflow and make it smooth for eng operators/users |
enhancement |
unknown |
|
pds-doi-service#187 As a SA, I want the operational deployment of the service to be secure |
requirement |
p.must-have |
pds-doi-service#178 B12.0 Refinements to DOI Service and UI for
Initial Release
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
pds-doi-service#163 Dockerize API Service |
enhancement |
p.should-have |
|
pds-doi-service#177 As an API user I want to filter on lidvids with wildcards |
requirement |
p.must-have |
|
pds-doi-service#180 As an API user I want to filter on PDS3 Data Set IDs with wildcards |
requirement |
p.must-have |
|
pds-doi-service#188 As a user, I want to make sure I can not override existing DOI with new LIDVID |
bug |
s.medium |
|
pds-doi-service#192 As a user, I want the application to support the history of PDS’s DOIs, especially the one created for PDS3 products |
requirement |
p.must-have |
pds-doi-service#179 Develop DataCite Interface
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
pds-doi-service#103 As the PDS, I want to mint DOIs through DataCite |
requirement |
p.must-have |
Other updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-doi-service#220 CI does not work on main branch for dev release |
unknown |
|
pds-doi-service#247 Fix test failure with flask_testing module |
s.medium |
|
pds-doi-service#191 API accepts Reserve submissions with invalid LIDVIDs |
s.medium |
Requirements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-doi-service#174 As an operator, I want to release a DOI through DataCite |
p.must-have |
|
pds-doi-service#175 As an operator, I want to update DOI metadata through DataCite |
p.must-have |
|
pds-doi-service#198 As a user, I want to use the API with ids containing a slash (/) |
p.should-have |
|
pds-doi-service#167 As a user, I want to see the lidvid of my DOIs in the email report |
p.should-have |
|
pds-doi-service#228 As an admistrator of the application, I want to restrict access to API by specific referrer |
p.must-have |
|
pds-doi-service#171 As an operator, I want to reserve a DOI through DataCite |
p.must-have |
|
pds-doi-service#184 As an API user, I want to always have an update date for the DOIs |
p.could-have |
|
pds-doi-service#183 As a user of the API, I want to see the DOI’s title when I go GET /dois request |
unknown |
|
pds-doi-service#172 As an operator, I want query for one or more minted DOIs from DataCite |
p.must-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-doi-service#227 Update DOI service for handling existing DOIs acceptance criteria per #175 |
unknown |
|
pds-doi-service#165 Add service to API for update of the status of records with OSTI (check sub command) |
unknown |
|
pds-doi-service#162 Implement Application Server to wrap Flask service |
p.should-have |
|
pds-doi-service#242 Port from pystache to jinja2 |
unknown |
|
pds-doi-service#229 As a user, I want to see the PDS3 ids as they originally are |
unknown |
pds-doi-ui
web UI for pds-doi-service
Planned Updates
No planned update realised in the build in this repository.
Other updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-doi-ui#70 navigation issue when using the app bar |
s.high |
|
pds-doi-ui#35 As a SA, I don’t want security vulnerabilities in the public UI |
s.medium |
|
pds-doi-ui#22 After reserve one file successfully, resubmit a new file |
s.low |
Requirements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-doi-ui#71 As a user, I want to have a dedicated favicon for the service |
p.should-have |
|
pds-doi-ui#65 As a user, I want my search criteria to persist in the URL |
p.could-have |
|
pds-doi-ui#42 As a user, I want to acquire a DOI for a PDS4 product that has been registered and is publicly accessible |
p.must-have |
|
pds-doi-ui#25 As a user, I want to search for a DOI and associated metadata by LID/LIDVID |
p.must-have |
|
pds-doi-ui#41 As a user, I want to acquire a DOI for a PDS4 product prior to it’s public release of the data |
p.must-have |
|
pds-doi-ui#34 As a user, I want to see the error/warnings messages on the same page from where they were raised |
p.could-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-doi-ui#9 Return API error message in UI |
unknown |
|
pds-doi-ui#10 Provide a mean to come back to release action when on reserve screen |
p.must-have |
|
pds-doi-ui#48 Enhancements per initial implementation of mockups |
unknown |
|
pds-doi-ui#49 Add Feedback Widget to DOI UI |
unknown |
|
pds-doi-ui#79 Create javascript library for website integration |
unknown |
|
pds-doi-ui#82 Create PDS React Component Library Process For NPM Packages |
unknown |
|
pds-doi-ui#1 Reserve DOI UI forms |
unknown |
|
pds-doi-ui#50 Add additional help information throughout DOI UI |
unknown |
|
pds-doi-ui#75 Add link to landing page from Identifier column in search results |
unknown |
|
pds-doi-ui#54 Update Release and Update DOI pages to follow similar design as Create DOI page |
unknown |
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.
Planned Updates
pds-registry-app#26 Manage duplicate products (no epic in this
repository)
pds-registry-app#152 Pilot DN Registry + API AWS Deployments (no
epic in this repository)
pds-registry-app#155 [registry] Registry Regression Test and
Documentation
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
pds-registry-app#153 As a developer, I want to extend the registry-mgr and harvest using the Java API |
requirement |
p.must-have |
|
pds-registry-app#154 As a manager, I want the registry to have regression tests included in CI |
requirement |
p.should-have |
Other updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-registry-app#163 docker instructions in README.md are not working |
s.medium |
Requirements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-registry-app#130 As a node operator, I want to harvest and ingest a subset of a bundle based on existing registered data. |
p.must-have |
|
pds-registry-app#185 As a user, I want to know the version of all registry app components via the command-line |
p.must-have |
|
pds-registry-app#12 As a registry user, I want to ingest supplemental metadata from Product_Metadata_Supplemental. |
p.must-have |
|
pds-registry-app#147 As a node operator, I want to be able to tag ingested data with the node it is ingested by. |
p.must-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-registry-app#173 Upgrade API on AWS with latest version 0.3.1 |
unknown |
|
pds-registry-app#150 Develop plan for instituting AWS ES Cross Cluster Search |
p.must-have |
|
pds-registry-app#165 Initial deployment of API on AWS - Fargate solution |
unknown |
pds-registry-mgr-elastic
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 update realised in the build in this repository.
Other updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-registry-mgr-elastic#33 registry-mgr cannot handle updated JSON files output from LDDTool |
s.medium |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-registry-mgr-elastic#27 Update registry-mgr-elastic to support new LDD JSON version information |
unknown |
pds-wds-web
PDS Web Design System - Basic web implementation
Planned Updates
No planned update realised in the build in this repository.
Other updates
Enhancements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds-wds-web#25 Review and merge App Bar Updates |
unknown |
PDS.nasa.gov-Search
Front-end interface for PDS.nasa.gov data search capability
Planned Updates
No planned update realised in the build in this repository.
Other updates
Enhancements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
PDS.nasa.gov-Search#33 Initial investigation for Search UI utilizing PDS API and identify new API user stories |
unknown |
PDS.nasa.gov-UX
PDS.nasa.gov User Experience Task Issue and Prototype repository
Planned Updates
PDS.nasa.gov-UX#74 Plan and Kick-off PDS WMWG
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
PDS.nasa.gov-UX#73 Rev 3 of milestones to breakdown of notional goals and deliverables |
enhancement |
p.must-have |
PDS.nasa.gov-UX#75 User Testing for NASA CMS Trade Study (no epic
in this repository)
PDS.nasa.gov-UX#79 Initial Visual Design (no epic in this
repository)
Other updates
Enhancements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
PDS.nasa.gov-UX#59 Rollout PDS App Bar to Discipline Nodes |
unknown |
|
PDS.nasa.gov-UX#85 Update user personas for PDS WMWG |
unknown |
|
PDS.nasa.gov-UX#86 [Training] incorporate changes from June pow-wow |
p.must-have |
|
PDS.nasa.gov-UX#82 Develop kickoff meeting slides |
p.must-have |
|
PDS.nasa.gov-UX#81 [Training] incorporate new materials - misc videos and ancillary files for TBD video |
p.must-have |
|
PDS.nasa.gov-UX#88 [Training] incorporate changes from first iteration of feedback |
p.must-have |
|
PDS.nasa.gov-UX#80 Create new Training page |
p.must-have |
|
PDS.nasa.gov-UX#92 Synthesize Workshop Feedback |
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#349 Establish LDD Management Teams and
Processes (no epic in this repository)
pds4-information-model#326 B12.0 LDDTool Improvements
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
pds4-information-model#240 Improve argument handling using argument parsing library |
task |
p.must-have |
|
pds4-information-model#330 As a user I want to know the output of the tool after it completes execution. |
requirement |
p.should-have |
|
pds4-information-model#338 As a developer, I want to know the dLDD version from the output JSON data |
requirement |
p.should-have |
pds4-information-model#350 B12.0 PDS4 Information Model SCR
Implementation (no epic in this repository)
pds4-information-model#368 B12.0 Evolution of
DD_Associate_External_Class
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
pds4-information-model#324 An LDD developer desires to inherit a class/attribute defined using DD_Associate_External_Class |
requirement |
p.must-have |
|
pds4-information-model#369 Evolution of CCB-256: Need method for providing permissible value definitions for external namespaces in Ingest_LDD. |
enhancement |
unknown |
|
pds4-information-model#391 Issue with DD_Associate_External_Class when trying to reference pds:Internal_Reference and pds:Local_Internal_Reference |
bug |
s.high |
Other updates
Requirements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds4-information-model#403 CCB-329 - Broaden Definition of Attribute aperture |
p.must-have |
|
pds4-information-model#387 As an operator, I want to be able to convert from XML to RDF using the PDS4 Information Model |
p.must-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds4-information-model#344 [namespace-registry] add new namespace “ctli” |
p.must-have |
|
pds4-information-model#353 [namespace-registry] add new namespace “ml” |
p.must-have |
|
pds4-information-model#352 [namespace-registry] add new namespace “m2020” |
p.must-have |
|
pds4-information-model#374 [namespace-registry] add new namespace “clipper” |
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 update realised in the build in this repository.
Other updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
pds4-jparser#40 SNAPSHOT dependencies in 2.0.0 release |
s.low |
|
pds4-jparser#42 Software does not build in Java11 on Windows |
s.medium |
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 update realised in the build in this repository.
Other updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
PLAID#25 All products are assumed to be Product_Observational by PLAID |
s.high |
|
PLAID#21 Discipline LDD workflow page is missing new discipline LDDs added to config |
s.medium |
Requirements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
PLAID#15 As a PDS Operator, I want to update PLAID to the latest PDS4 Information Model |
unknown |
registry-api-service
PDS Registry API service. Complies with PDS API specification
Planned Updates
No planned update realised in the build in this repository.
Other updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
registry-api-service#36 The end point /bundles/{lidvid}/products does not fully work |
s.medium |
|
registry-api-service#69 As a paginator, I want endpoints to consistently return no results when I page to the end of results |
s.high |
|
registry-api-service#16 API server crashes with OutOfMemoryError if invalid query is used |
s.high |
|
registry-api-service#62 API unable to handle products with multiple file areas |
s.high |
|
registry-api-service#27 XML and PDS4+XML Response Formats are invalid |
s.high |
|
registry-api-service#51 blob is returned in product results if fields to return are not specified |
unknown |
|
registry-api-service#43 As an API caller, I expect MD5s and file reference URLs to have real values and not the string “null” |
s.high |
|
registry-api-service#17 error 500 on GET /collections/:lidvid:/products |
s.high |
|
registry-api-service#53 If Elasticsearch is down on API server startup, it starts, but doesn’t accept connections |
s.medium |
Requirements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
registry-api-service#47 As a user, I want to have a complete default fields (for now at least) |
unknown |
|
registry-api-service#13 As a developer, I want to utilize ElasticSearch performance robustness for API response time requirements. |
p.must-have |
|
registry-api-service#33 As a user, I want to get a 404 error when I attempt to request a resource which does not exists |
unknown |
|
registry-api-service#14 As a node operators, I want to deploy the Registry API Service with the PDS Registry. |
p.must-have |
|
registry-api-service#10 As a SA, I want to deploy the API behind a proxy |
p.must-have |
registry-ci
Continuous Integration framework and regression tests for different Registry components, such as Harvest, Registry Manager and API.
Planned Updates
No planned update realised in the build in this repository.
Other updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
registry-ci#2 Maven build step of “Run CI” GitHub action could not handle source branches with ‘/’ in the name |
unknown |
validate
Validates PDS4 product labels, data and PDS3 Volumes
Planned Updates
validate#317 B12.0 Referential Integrity Improvements
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
validate#69 As a user, I want to validate that all context objects specified in observational products are referenced in the parent bundle/collection Reference_List |
requirement |
p.should-have |
|
validate#308 As a user, I want to check that all Internal References are valid references to other PDS4 products within the current validating bundle |
requirement |
p.must-have |
|
validate#358 Improve validate performance by removing unnecessary file IO |
enhancement |
p.should-have |
|
validate#368 Product referential integrity check throws invalid WARNINGs |
bug |
s.medium |
|
validate#372 Issues with logic for reading latest version of collections, and file read logging lost with v2.* of validate |
bug |
s.medium |
validate#318 B12.0 Content Validation Improvements
Issue |
I&T |
Level |
Priority / Bug Severity |
---|---|---|---|
validate#57 As a user, I want to be warned when there are alphanumeric characters between fields in Table_Character |
requirement |
p.could-have |
|
validate#164 As a user, I want to validate PDF files are PDF/A |
requirement |
p.should-have |
|
validate#303 As a user, I want to the raise a WARNING if the object-defined size in the label does not match the file_size value |
requirement |
p.should-have |
Other updates
Bugs
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
validate#361 validate does not check Header of a File_Area_Ancillary nor does not provide a meaningful error message for an incorrect Table_Character offset |
s.medium |
|
validate#310 Validate missing collections in bundle after CCB-282 updates |
s.medium |
|
validate#325 Validate Incorrectly Throws Error When Embedded Field_Character Contains <CR><LF> |
s.medium |
|
validate#357 Validate allows CRLF within a Table_Delimited field |
s.medium |
|
validate#392 Validate throws incorrect overlap error when first Field_Bit has length 1 |
s.medium |
|
validate#379 FileService:printStackTraceToFile:ERROR when validating a product with overlapping fields |
unknown |
|
validate#381 validate does not work correctly when the path name contains a space |
s.medium |
|
validate#360 validate does not parse colon in Windows path |
s.high |
|
validate#364 validate does not allow “.XML” as an extension for a label file |
s.medium |
|
validate#326 File-size check fails for large data files |
s.medium |
|
validate#327 validate fails to process large data file |
s.medium |
|
validate#366 validate should not check if file is PDF/A if –skip-content-validation is enabled |
s.low |
|
validate#380 stack trace being created during successful validate execution |
s.high |
|
validate#375 validate halts if label has name “collection” embedded |
s.medium |
Requirements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
validate#367 As a user, I want to validate all files referenced by a Product_Document |
p.must-have |
Enhancements
Issue |
I&T |
Priority / Bug Severity |
---|---|---|
validate#373 Update pds4 version mismatch warning message and problem type |
unknown |
|
validate#374 Refactor PDF/A check handling to match with similar product checks |
unknown |
Liens
Issue |
Title |
Rationale |
---|---|---|
pds-swg_12 [CR] Defer Validate Configuration Improvements from B12.0 |
[CR] Defer Validate Configuration Improvements from B12.0 |
_enter rationale for deviation from plan here_ Depending on triaged priority of bug fixes, the tend to move towards the top of validate dev queue as they are often blockers to allowing a user to successfully validate their archives. |
pds-swg_11 [CR] B12.0 Add Information Model Tasks to Release Plan |
[CR] B12.0 Add Information Model Tasks to Release Plan |
The GEOM LDD split effort is fully underway and we have pretty much dug the hole too deep at this point. Pulling back on that effort is most likely a non-starter, so we have to pivot to support that. The “B12.0 Refactoring of IMTool” effort is not critical and should not impact LDDTool for the near-term. |
Engineering Node Software Catalog
The Engineering Node Software resources are listed in the software release summary (B12.0)
Installation and operation
PDS Engineering node software are meant to be deployed in 3 contexts: standalone, discipline nodes or engineering node 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 Sotware Requirements and Design Document (SRD/SDD)