========================================== 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: .. toctree:: :glob: :maxdepth: 3 rdd.rst 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 | +================================+=====================================================+ |`pds4-information-model#164`_ |CCB-283: Add reference_type value document_to_data | +--------------------------------+-----------------------------------------------------+ |`pds4-information-model#403`_ |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* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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.* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ Planned Updates ~~~~~~~~~~~~~~~ - `cloud-strategy#2`_ B12.0 Refine AWS Registry Deployment Strategy (no epic in this repository) -------- devops ------ *Parent repo for PDS DevOps activities* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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)* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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 ||iandt| |p.should-have | +-----------------------------------------------------------------------------------------+----------+--------------------------+ Enhancements ++++++++++++ +----------------------------------------------------------------------------------+----------+--------------------------+ |Issue |I&T |Priority / Bug Severity | +==================================================================================+==========+==========================+ |`harvest#58`_ Enable blob ingestion by default ||iandt| |p.must-have | +----------------------------------------------------------------------------------+----------+--------------------------+ |`harvest#55`_ Quick fix to support date/time conversion to "ISO instant" format ||iandt| |p.must-have | +----------------------------------------------------------------------------------+----------+--------------------------+ -------- operations ---------- *Tickets for the PDSEN Operations Team* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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 ||iandt| |unknown | +----------------------------------------------------------------+----------+--------------------------+ -------- pds-api ------- *PDS API Application with client and server integrated into one package* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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. ||iandt| |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 ||iandt| |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 ||iandt| |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) ||iandt| |requirement |p.must-have | +-------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------+--------------------------+ |`pds-api#105`_ As an API user, I want to know how long a request took to complete ||iandt| |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 ||iandt| |requirement |p.must-have | +---------------------------------------------------------------------------------------------------------------+----------+--------------+--------------------------+ |`pds-api#59`_ As an API user, I want to know the Product(s) that belong to a given Bundle. ||iandt| |requirement |p.must-have | +---------------------------------------------------------------------------------------------------------------+----------+--------------+--------------------------+ |`pds-api#60`_ As an API user, I want to know the Bundle for a given Product. ||iandt| |requirement |p.must-have | +---------------------------------------------------------------------------------------------------------------+----------+--------------+--------------------------+ |`pds-api#61`_ As an API user, I want to know the Collection(s) for a given Product. ||iandt| |requirement |p.must-have | +---------------------------------------------------------------------------------------------------------------+----------+--------------+--------------------------+ |`pds-api#62`_ As an API user, I want to know the Bundle for a given Collection. ||iandt| |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 ||iandt| |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 ||iandt| |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 ||iandt| |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. ||iandt| |p.must-have | +------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-api#96`_ As an API user, I want to get the latest version of a product, by default ||iandt| |p.must-have | +------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-api#107`_ As an API user, I want to explicitly request the latest version of a product ||iandt| |p.could-have | +------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-api#95`_ As a user, I want to query for all versions of a product ||iandt| |unknown | +------------------------------------------------------------------------------------------------------------+----------+--------------------------+ -------- pds-api-client -------------- *PDS API Client* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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` ||iandt| |s.medium | +-----------------------------------------------------------------------------+----------+--------------------------+ -------- pds-deep-archive ---------------- *PDS Open Archival Information System (OAIS) utilities, including Submission Information Package (SIP) and Archive Information Package (AIP) generators* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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 ||iandt| |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' ||iandt| |s.low | +----------------------------------------------------------------------------------------------------------+----------+--------------------------+ -------- pds-doi-service --------------- *Service and tools for generating DOIs for PDS bundles, collections, and data sets* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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 ||iandt| |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 ||iandt| |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 ||iandt| |enhancement |p.should-have | +----------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------+--------------------------+ |`pds-doi-service#177`_ As an API user I want to filter on lidvids with wildcards ||iandt| |requirement |p.must-have | +----------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------+--------------------------+ |`pds-doi-service#180`_ As an API user I want to filter on PDS3 Data Set IDs with wildcards ||iandt| |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 ||iandt| |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 ||iandt| |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 ||iandt| |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 ||iandt| |unknown | +------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-service#247`_ Fix test failure with flask_testing module ||iandt| |s.medium | +------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-service#191`_ API accepts Reserve submissions with invalid LIDVIDs ||iandt| |s.medium | +------------------------------------------------------------------------------+----------+--------------------------+ Requirements ++++++++++++ +----------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |Issue |I&T |Priority / Bug Severity | +======================================================================================================================+==========+==========================+ |`pds-doi-service#174`_ As an operator, I want to release a DOI through DataCite ||iandt| |p.must-have | +----------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-service#175`_ As an operator, I want to update DOI metadata through DataCite ||iandt| |p.must-have | +----------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-service#198`_ As a user, I want to use the API with ids containing a slash (/) ||iandt| |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 ||iandt| |p.must-have | +----------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-service#171`_ As an operator, I want to reserve a DOI through DataCite ||iandt| |p.must-have | +----------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-service#184`_ As an API user, I want to always have an update date for the DOIs ||iandt| |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 ||iandt| |unknown | +----------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-service#172`_ As an operator, I want query for one or more minted DOIs from DataCite ||iandt| |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 ||iandt| |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 ||iandt| |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 ||iandt| |unknown | +--------------------------------------------------------------------------------------------------------------+----------+--------------------------+ -------- pds-doi-ui ---------- *web UI for pds-doi-service* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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 ||iandt| |s.high | +-----------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-ui#35`_ As a SA, I don't want security vulnerabilities in the public UI ||iandt| |s.medium | +-----------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-ui#22`_ After reserve one file successfully, resubmit a new file ||iandt| |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 ||iandt| |p.should-have | +-----------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-ui#65`_ As a user, I want my search criteria to persist in the URL ||iandt| |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 ||iandt| |p.must-have | +-----------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-ui#25`_ As a user, I want to search for a DOI and associated metadata by LID/LIDVID ||iandt| |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 ||iandt| |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 ||iandt| |p.could-have | +-----------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ Enhancements ++++++++++++ +---------------------------------------------------------------------------------------------------+----------+--------------------------+ |Issue |I&T |Priority / Bug Severity | +===================================================================================================+==========+==========================+ |`pds-doi-ui#9`_ Return API error message in UI ||iandt| |unknown | +---------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-ui#10`_ Provide a mean to come back to release action when on reserve screen ||iandt| |p.must-have | +---------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-ui#48`_ Enhancements per initial implementation of mockups ||iandt| |unknown | +---------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-ui#49`_ Add Feedback Widget to DOI UI ||iandt| |unknown | +---------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-ui#79`_ Create javascript library for website integration ||iandt| |unknown | +---------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-ui#82`_ Create PDS React Component Library Process For NPM Packages ||iandt| |unknown | +---------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-ui#1`_ Reserve DOI UI forms ||iandt| |unknown | +---------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-ui#50`_ Add additional help information throughout DOI UI ||iandt| |unknown | +---------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-ui#75`_ Add link to landing page from `Identifier` column in search results ||iandt| |unknown | +---------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-doi-ui#54`_ Update Release and Update DOI pages to follow similar design as Create DOI page ||iandt| |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.* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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 ||iandt| |requirement |p.must-have | +-----------------------------------------------------------------------------------------------------------+----------+--------------+--------------------------+ |`pds-registry-app#154`_ As a manager, I want the registry to have regression tests included in CI ||iandt| |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 ||iandt| |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. ||iandt| |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 ||iandt| |p.must-have | +-----------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-registry-app#12`_ As a registry user, I want to ingest supplemental metadata from Product_Metadata_Supplemental. ||iandt| |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. ||iandt| |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 ||iandt| |p.must-have | +------------------------------------------------------------------------------------+----------+--------------------------+ |`pds-registry-app#165`_ Initial deployment of API on AWS - Fargate solution ||iandt| |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)* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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 ||iandt| |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* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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 ||iandt| |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 ||iandt| |p.must-have | +-------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`PDS.nasa.gov-UX#88`_ [Training] incorporate changes from first iteration of feedback ||iandt| |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.* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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 ||iandt| |task |p.must-have | +--------------------------------------------------------------------------------------------------------------+----------+--------------+--------------------------+ |`pds4-information-model#330`_ As a user I want to know the output of the tool after it completes execution. ||iandt| |requirement |p.should-have | +--------------------------------------------------------------------------------------------------------------+----------+--------------+--------------------------+ |`pds4-information-model#338`_ As a developer, I want to know the dLDD version from the output JSON data ||iandt| |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 ||iandt| |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. ||iandt| |enhancement |unknown | +--------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------+--------------------------+ |`pds4-information-model#391`_ Issue with DD_Associate_External_Class when trying to reference pds:Internal_Reference and pds:Local_Internal_Reference ||iandt| |bug |s.high | +--------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------+--------------------------+ Other updates ~~~~~~~~~~~~~ Requirements ++++++++++++ +------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |Issue |I&T |Priority / Bug Severity | +==============================================================================================================================+==========+==========================+ |`pds4-information-model#403`_ CCB-329 - Broaden Definition of Attribute aperture ||iandt| |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 ||iandt| |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.* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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 ||iandt| |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* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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 ||iandt| |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 ||iandt| |s.high | +-----------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`registry-api-service#16`_ API server crashes with OutOfMemoryError if invalid query is used ||iandt| |s.high | +-----------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`registry-api-service#62`_ API unable to handle products with multiple file areas ||iandt| |s.high | +-----------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`registry-api-service#27`_ XML and PDS4+XML Response Formats are invalid ||iandt| |s.high | +-----------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`registry-api-service#51`_ blob is returned in product results if fields to return are not specified ||iandt| |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" ||iandt| |s.high | +-----------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`registry-api-service#17`_ error 500 on GET /collections/:lidvid:/products ||iandt| |s.high | +-----------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`registry-api-service#53`_ If Elasticsearch is down on API server startup, it starts, but doesn't accept connections ||iandt| |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) ||iandt| |unknown | +----------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`registry-api-service#13`_ As a developer, I want to utilize ElasticSearch performance robustness for API response time requirements. ||iandt| |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 ||iandt| |unknown | +----------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`registry-api-service#14`_ As a node operators, I want to deploy the Registry API Service with the PDS Registry. ||iandt| |p.must-have | +----------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`registry-api-service#10`_ As a SA, I want to deploy the API behind a proxy ||iandt| |p.must-have | +----------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ -------- registry-ci ----------- *Continuous Integration framework and regression tests for different Registry components, such as Harvest, Registry Manager and API.* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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* .. list-table:: :widths: 15 15 15 15 15 15 * - `User Guide `_ - `Github Repo `_ - `Issue Tracking `_ - `Backlog `_ - `Stable Release `_ - `Dev Release `_ 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 ||iandt| |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 ||iandt| |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 ||iandt| |bug |s.medium | +--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------+--------------------------+ |`validate#372`_ Issues with logic for reading latest version of collections, and file read logging lost with v2.* of validate ||iandt| |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 ||iandt| |requirement |p.could-have | +--------------------------------------------------------------------------------------------------------------------------------------+----------+--------------+--------------------------+ |`validate#164`_ As a user, I want to validate PDF files are PDF/A ||iandt| |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 ||iandt| |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 ||iandt| |s.medium | +------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`validate#310`_ Validate missing collections in bundle after CCB-282 updates ||iandt| |s.medium | +------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`validate#325`_ Validate Incorrectly Throws Error When Embedded Field_Character Contains ||iandt| |s.medium | +------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`validate#357`_ Validate allows CRLF within a Table_Delimited field ||iandt| |s.medium | +------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`validate#392`_ Validate throws incorrect overlap error when first Field_Bit has length 1 ||iandt| |s.medium | +------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`validate#379`_ FileService:printStackTraceToFile:ERROR when validating a product with overlapping fields ||iandt| |unknown | +------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`validate#381`_ validate does not work correctly when the path name contains a space ||iandt| |s.medium | +------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`validate#360`_ validate does not parse colon in Windows path ||iandt| |s.high | +------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`validate#364`_ validate does not allow ".XML" as an extension for a label file ||iandt| |s.medium | +------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`validate#326`_ File-size check fails for large data files ||iandt| |s.medium | +------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`validate#327`_ validate fails to process large data file ||iandt| |s.medium | +------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`validate#366`_ validate should not check if file is PDF/A if --skip-content-validation is enabled ||iandt| |s.low | +------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`validate#380`_ stack trace being created during successful validate execution ||iandt| |s.high | +------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+--------------------------+ |`validate#375`_ validate halts if label has name "collection" embedded ||iandt| |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 ||iandt| |p.must-have | +-------------------------------------------------------------------------------------------+----------+--------------------------+ Enhancements ++++++++++++ +-------------------------------------------------------------------------------------+----------+--------------------------+ |Issue |I&T |Priority / Bug Severity | +=====================================================================================+==========+==========================+ |`validate#373`_ Update pds4 version mismatch warning message and problem type ||iandt| |unknown | +-------------------------------------------------------------------------------------+----------+--------------------------+ |`validate#374`_ Refactor PDF/A check handling to match with similar product checks ||iandt| |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: - `PDS Standalone`_ - `PDS Discipline Nodes`_ - `PDS Engineering Node only`_ 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)`_ - `PDS DOI Service Requirements and Design Document (SRD/SDD)`_ .. _plan B12.0: https://nasa-pds.github.io/releases/12.0/plan.html .. _pds4-information-model#164: https://github.com/NASA-PDS/pds4-information-model/issues/164 .. _pds4-information-model#403: https://github.com/NASA-PDS/pds4-information-model/issues/403 .. |iandt| image:: https://nasa-pds.github.io/_static/images/noun_certified_18093.png :alt: I&T :width: 20 .. _archive-analytics#7: https://github.com/NASA-PDS/archive-analytics/issues/7 .. _archive-analytics#2: https://github.com/NASA-PDS/archive-analytics/issues/2 .. _archive-analytics#16: https://github.com/NASA-PDS/archive-analytics/issues/16 .. _cloud-strategy#2: https://github.com/NASA-PDS/cloud-strategy/issues/2 .. _devops#4: https://github.com/NASA-PDS/devops/issues/4 .. _devops#5: https://github.com/NASA-PDS/devops/issues/5 .. _devops#6: https://github.com/NASA-PDS/devops/issues/6 .. _devops#3: https://github.com/NASA-PDS/devops/issues/3 .. _devops#9: https://github.com/NASA-PDS/devops/issues/9 .. _harvest#60: https://github.com/NASA-PDS/harvest/issues/60 .. _harvest#58: https://github.com/NASA-PDS/harvest/issues/58 .. _harvest#55: https://github.com/NASA-PDS/harvest/issues/55 .. _operations#141: https://github.com/NASA-PDS/operations/issues/141 .. _pds-api#24: https://github.com/NASA-PDS/pds-api/issues/24 .. _pds-api#67: https://github.com/NASA-PDS/pds-api/issues/67 .. _pds-api#76: https://github.com/NASA-PDS/pds-api/issues/76 .. _pds-api#80: https://github.com/NASA-PDS/pds-api/issues/80 .. _pds-api#75: https://github.com/NASA-PDS/pds-api/issues/75 .. _pds-api#91: https://github.com/NASA-PDS/pds-api/issues/91 .. _pds-api#101: https://github.com/NASA-PDS/pds-api/issues/101 .. _pds-api#105: https://github.com/NASA-PDS/pds-api/issues/105 .. _pds-api#77: https://github.com/NASA-PDS/pds-api/issues/77 .. _pds-api#56: https://github.com/NASA-PDS/pds-api/issues/56 .. _pds-api#59: https://github.com/NASA-PDS/pds-api/issues/59 .. _pds-api#60: https://github.com/NASA-PDS/pds-api/issues/60 .. _pds-api#61: https://github.com/NASA-PDS/pds-api/issues/61 .. _pds-api#62: https://github.com/NASA-PDS/pds-api/issues/62 .. _pds-api#79: https://github.com/NASA-PDS/pds-api/issues/79 .. _pds-api#81: https://github.com/NASA-PDS/pds-api/issues/81 .. _pds-api#83: https://github.com/NASA-PDS/pds-api/issues/83 .. _pds-api#84: https://github.com/NASA-PDS/pds-api/issues/84 .. _pds-api#99: https://github.com/NASA-PDS/pds-api/issues/99 .. _pds-api#73: https://github.com/NASA-PDS/pds-api/issues/73 .. _pds-api#68: https://github.com/NASA-PDS/pds-api/issues/68 .. _pds-api#96: https://github.com/NASA-PDS/pds-api/issues/96 .. _pds-api#107: https://github.com/NASA-PDS/pds-api/issues/107 .. _pds-api#95: https://github.com/NASA-PDS/pds-api/issues/95 .. _pds-api-client#6: https://github.com/NASA-PDS/pds-api-client/issues/6 .. _pds-deep-archive#105: https://github.com/NASA-PDS/pds-deep-archive/issues/105 .. _pds-deep-archive#7: https://github.com/NASA-PDS/pds-deep-archive/issues/7 .. _pds-deep-archive#106: https://github.com/NASA-PDS/pds-deep-archive/issues/106 .. _pds-deep-archive#116: https://github.com/NASA-PDS/pds-deep-archive/issues/116 .. _pds-doi-service#86: https://github.com/NASA-PDS/pds-doi-service/issues/86 .. _pds-doi-service#87: https://github.com/NASA-PDS/pds-doi-service/issues/87 .. _pds-doi-service#90: https://github.com/NASA-PDS/pds-doi-service/issues/90 .. _pds-doi-service#145: https://github.com/NASA-PDS/pds-doi-service/issues/145 .. _pds-doi-service#187: https://github.com/NASA-PDS/pds-doi-service/issues/187 .. _pds-doi-service#178: https://github.com/NASA-PDS/pds-doi-service/issues/178 .. _pds-doi-service#163: https://github.com/NASA-PDS/pds-doi-service/issues/163 .. _pds-doi-service#177: https://github.com/NASA-PDS/pds-doi-service/issues/177 .. _pds-doi-service#180: https://github.com/NASA-PDS/pds-doi-service/issues/180 .. _pds-doi-service#188: https://github.com/NASA-PDS/pds-doi-service/issues/188 .. _pds-doi-service#192: https://github.com/NASA-PDS/pds-doi-service/issues/192 .. _pds-doi-service#179: https://github.com/NASA-PDS/pds-doi-service/issues/179 .. _pds-doi-service#103: https://github.com/NASA-PDS/pds-doi-service/issues/103 .. _pds-doi-service#220: https://github.com/NASA-PDS/pds-doi-service/issues/220 .. _pds-doi-service#247: https://github.com/NASA-PDS/pds-doi-service/issues/247 .. _pds-doi-service#191: https://github.com/NASA-PDS/pds-doi-service/issues/191 .. _pds-doi-service#174: https://github.com/NASA-PDS/pds-doi-service/issues/174 .. _pds-doi-service#175: https://github.com/NASA-PDS/pds-doi-service/issues/175 .. _pds-doi-service#198: https://github.com/NASA-PDS/pds-doi-service/issues/198 .. _pds-doi-service#167: https://github.com/NASA-PDS/pds-doi-service/issues/167 .. _pds-doi-service#228: https://github.com/NASA-PDS/pds-doi-service/issues/228 .. _pds-doi-service#171: https://github.com/NASA-PDS/pds-doi-service/issues/171 .. _pds-doi-service#184: https://github.com/NASA-PDS/pds-doi-service/issues/184 .. _pds-doi-service#183: https://github.com/NASA-PDS/pds-doi-service/issues/183 .. _pds-doi-service#172: https://github.com/NASA-PDS/pds-doi-service/issues/172 .. _pds-doi-service#227: https://github.com/NASA-PDS/pds-doi-service/issues/227 .. _pds-doi-service#165: https://github.com/NASA-PDS/pds-doi-service/issues/165 .. _pds-doi-service#162: https://github.com/NASA-PDS/pds-doi-service/issues/162 .. _pds-doi-service#242: https://github.com/NASA-PDS/pds-doi-service/issues/242 .. _pds-doi-service#229: https://github.com/NASA-PDS/pds-doi-service/issues/229 .. _pds-doi-ui#70: https://github.com/NASA-PDS/pds-doi-ui/issues/70 .. _pds-doi-ui#35: https://github.com/NASA-PDS/pds-doi-ui/issues/35 .. _pds-doi-ui#22: https://github.com/NASA-PDS/pds-doi-ui/issues/22 .. _pds-doi-ui#71: https://github.com/NASA-PDS/pds-doi-ui/issues/71 .. _pds-doi-ui#65: https://github.com/NASA-PDS/pds-doi-ui/issues/65 .. _pds-doi-ui#42: https://github.com/NASA-PDS/pds-doi-ui/issues/42 .. _pds-doi-ui#25: https://github.com/NASA-PDS/pds-doi-ui/issues/25 .. _pds-doi-ui#41: https://github.com/NASA-PDS/pds-doi-ui/issues/41 .. _pds-doi-ui#34: https://github.com/NASA-PDS/pds-doi-ui/issues/34 .. _pds-doi-ui#9: https://github.com/NASA-PDS/pds-doi-ui/issues/9 .. _pds-doi-ui#10: https://github.com/NASA-PDS/pds-doi-ui/issues/10 .. _pds-doi-ui#48: https://github.com/NASA-PDS/pds-doi-ui/issues/48 .. _pds-doi-ui#49: https://github.com/NASA-PDS/pds-doi-ui/issues/49 .. _pds-doi-ui#79: https://github.com/NASA-PDS/pds-doi-ui/issues/79 .. _pds-doi-ui#82: https://github.com/NASA-PDS/pds-doi-ui/issues/82 .. _pds-doi-ui#1: https://github.com/NASA-PDS/pds-doi-ui/issues/1 .. _pds-doi-ui#50: https://github.com/NASA-PDS/pds-doi-ui/issues/50 .. _pds-doi-ui#75: https://github.com/NASA-PDS/pds-doi-ui/issues/75 .. _pds-doi-ui#54: https://github.com/NASA-PDS/pds-doi-ui/issues/54 .. _pds-registry-app#26: https://github.com/NASA-PDS/pds-registry-app/issues/26 .. _pds-registry-app#152: https://github.com/NASA-PDS/pds-registry-app/issues/152 .. _pds-registry-app#155: https://github.com/NASA-PDS/pds-registry-app/issues/155 .. _pds-registry-app#153: https://github.com/NASA-PDS/pds-registry-app/issues/153 .. _pds-registry-app#154: https://github.com/NASA-PDS/pds-registry-app/issues/154 .. _pds-registry-app#163: https://github.com/NASA-PDS/pds-registry-app/issues/163 .. _pds-registry-app#130: https://github.com/NASA-PDS/pds-registry-app/issues/130 .. _pds-registry-app#185: https://github.com/NASA-PDS/pds-registry-app/issues/185 .. _pds-registry-app#12: https://github.com/NASA-PDS/pds-registry-app/issues/12 .. _pds-registry-app#147: https://github.com/NASA-PDS/pds-registry-app/issues/147 .. _pds-registry-app#173: https://github.com/NASA-PDS/pds-registry-app/issues/173 .. _pds-registry-app#150: https://github.com/NASA-PDS/pds-registry-app/issues/150 .. _pds-registry-app#165: https://github.com/NASA-PDS/pds-registry-app/issues/165 .. _pds-registry-mgr-elastic#33: https://github.com/NASA-PDS/pds-registry-mgr-elastic/issues/33 .. _pds-registry-mgr-elastic#27: https://github.com/NASA-PDS/pds-registry-mgr-elastic/issues/27 .. _pds-wds-web#25: https://github.com/NASA-PDS/pds-wds-web/issues/25 .. _PDS.nasa.gov-Search#33: https://github.com/NASA-PDS/PDS.nasa.gov-Search/issues/33 .. _PDS.nasa.gov-UX#74: https://github.com/NASA-PDS/PDS.nasa.gov-UX/issues/74 .. _PDS.nasa.gov-UX#73: https://github.com/NASA-PDS/PDS.nasa.gov-UX/issues/73 .. _PDS.nasa.gov-UX#75: https://github.com/NASA-PDS/PDS.nasa.gov-UX/issues/75 .. _PDS.nasa.gov-UX#79: https://github.com/NASA-PDS/PDS.nasa.gov-UX/issues/79 .. _PDS.nasa.gov-UX#59: https://github.com/NASA-PDS/PDS.nasa.gov-UX/issues/59 .. _PDS.nasa.gov-UX#85: https://github.com/NASA-PDS/PDS.nasa.gov-UX/issues/85 .. _PDS.nasa.gov-UX#86: https://github.com/NASA-PDS/PDS.nasa.gov-UX/issues/86 .. _PDS.nasa.gov-UX#82: https://github.com/NASA-PDS/PDS.nasa.gov-UX/issues/82 .. _PDS.nasa.gov-UX#81: https://github.com/NASA-PDS/PDS.nasa.gov-UX/issues/81 .. _PDS.nasa.gov-UX#88: https://github.com/NASA-PDS/PDS.nasa.gov-UX/issues/88 .. _PDS.nasa.gov-UX#80: https://github.com/NASA-PDS/PDS.nasa.gov-UX/issues/80 .. _PDS.nasa.gov-UX#92: https://github.com/NASA-PDS/PDS.nasa.gov-UX/issues/92 .. _pds4-information-model#349: https://github.com/NASA-PDS/pds4-information-model/issues/349 .. _pds4-information-model#326: https://github.com/NASA-PDS/pds4-information-model/issues/326 .. _pds4-information-model#240: https://github.com/NASA-PDS/pds4-information-model/issues/240 .. _pds4-information-model#330: https://github.com/NASA-PDS/pds4-information-model/issues/330 .. _pds4-information-model#338: https://github.com/NASA-PDS/pds4-information-model/issues/338 .. _pds4-information-model#350: https://github.com/NASA-PDS/pds4-information-model/issues/350 .. _pds4-information-model#368: https://github.com/NASA-PDS/pds4-information-model/issues/368 .. _pds4-information-model#324: https://github.com/NASA-PDS/pds4-information-model/issues/324 .. _pds4-information-model#369: https://github.com/NASA-PDS/pds4-information-model/issues/369 .. _pds4-information-model#391: https://github.com/NASA-PDS/pds4-information-model/issues/391 .. _pds4-information-model#403: https://github.com/NASA-PDS/pds4-information-model/issues/403 .. _pds4-information-model#387: https://github.com/NASA-PDS/pds4-information-model/issues/387 .. _pds4-information-model#344: https://github.com/NASA-PDS/pds4-information-model/issues/344 .. _pds4-information-model#353: https://github.com/NASA-PDS/pds4-information-model/issues/353 .. _pds4-information-model#352: https://github.com/NASA-PDS/pds4-information-model/issues/352 .. _pds4-information-model#374: https://github.com/NASA-PDS/pds4-information-model/issues/374 .. _pds4-jparser#40: https://github.com/NASA-PDS/pds4-jparser/issues/40 .. _pds4-jparser#42: https://github.com/NASA-PDS/pds4-jparser/issues/42 .. _PLAID#25: https://github.com/NASA-PDS/PLAID/issues/25 .. _PLAID#21: https://github.com/NASA-PDS/PLAID/issues/21 .. _PLAID#15: https://github.com/NASA-PDS/PLAID/issues/15 .. _registry-api-service#36: https://github.com/NASA-PDS/registry-api-service/issues/36 .. _registry-api-service#69: https://github.com/NASA-PDS/registry-api-service/issues/69 .. _registry-api-service#16: https://github.com/NASA-PDS/registry-api-service/issues/16 .. _registry-api-service#62: https://github.com/NASA-PDS/registry-api-service/issues/62 .. _registry-api-service#27: https://github.com/NASA-PDS/registry-api-service/issues/27 .. _registry-api-service#51: https://github.com/NASA-PDS/registry-api-service/issues/51 .. _registry-api-service#43: https://github.com/NASA-PDS/registry-api-service/issues/43 .. _registry-api-service#17: https://github.com/NASA-PDS/registry-api-service/issues/17 .. _registry-api-service#53: https://github.com/NASA-PDS/registry-api-service/issues/53 .. _registry-api-service#47: https://github.com/NASA-PDS/registry-api-service/issues/47 .. _registry-api-service#13: https://github.com/NASA-PDS/registry-api-service/issues/13 .. _registry-api-service#33: https://github.com/NASA-PDS/registry-api-service/issues/33 .. _registry-api-service#14: https://github.com/NASA-PDS/registry-api-service/issues/14 .. _registry-api-service#10: https://github.com/NASA-PDS/registry-api-service/issues/10 .. _registry-ci#2: https://github.com/NASA-PDS/registry-ci/issues/2 .. _validate#317: https://github.com/NASA-PDS/validate/issues/317 .. _validate#69: https://github.com/NASA-PDS/validate/issues/69 .. _validate#308: https://github.com/NASA-PDS/validate/issues/308 .. _validate#358: https://github.com/NASA-PDS/validate/issues/358 .. _validate#368: https://github.com/NASA-PDS/validate/issues/368 .. _validate#372: https://github.com/NASA-PDS/validate/issues/372 .. _validate#318: https://github.com/NASA-PDS/validate/issues/318 .. _validate#57: https://github.com/NASA-PDS/validate/issues/57 .. _validate#164: https://github.com/NASA-PDS/validate/issues/164 .. _validate#303: https://github.com/NASA-PDS/validate/issues/303 .. _validate#361: https://github.com/NASA-PDS/validate/issues/361 .. _validate#310: https://github.com/NASA-PDS/validate/issues/310 .. _validate#325: https://github.com/NASA-PDS/validate/issues/325 .. _validate#357: https://github.com/NASA-PDS/validate/issues/357 .. _validate#392: https://github.com/NASA-PDS/validate/issues/392 .. _validate#379: https://github.com/NASA-PDS/validate/issues/379 .. _validate#381: https://github.com/NASA-PDS/validate/issues/381 .. _validate#360: https://github.com/NASA-PDS/validate/issues/360 .. _validate#364: https://github.com/NASA-PDS/validate/issues/364 .. _validate#326: https://github.com/NASA-PDS/validate/issues/326 .. _validate#327: https://github.com/NASA-PDS/validate/issues/327 .. _validate#366: https://github.com/NASA-PDS/validate/issues/366 .. _validate#380: https://github.com/NASA-PDS/validate/issues/380 .. _validate#375: https://github.com/NASA-PDS/validate/issues/375 .. _validate#367: https://github.com/NASA-PDS/validate/issues/367 .. _validate#373: https://github.com/NASA-PDS/validate/issues/373 .. _validate#374: https://github.com/NASA-PDS/validate/issues/374 .. _pds-swg_12: https://github.com/NASA-PDS/pds-swg/issues/12 .. _pds-swg_11: https://github.com/NASA-PDS/pds-swg/issues/11 .. _software release summary (B12.0): https://nasa-pds.github.io/releases/B12.0/index.html .. _PDS Standalone: https://nasa-pds.github.io/releases/11.1/index.html#standalone-tools-and-libraries .. _PDS Discipline Nodes: https://nasa-pds.github.io/releases/11.1/index.html#discipline-node-services .. _PDS Engineering Node only: https://nasa-pds.github.io/releases/11.1/index.html#enineering-node-services .. _PDS Deep Archive Sotware Requirements and Design Document (SRD/SDD): https://github.com/NASA-PDS/pds-deep-archive/blob/master/docs/pds4_nssdca_delivery_design_20191219.docx .. _PDS DOI Service Requirements and Design Document (SRD/SDD): https://github.com/NASA-PDS/pds-doi-service/blob/master/docs/design/pds-doi-service-srd.md