PDS4 Data Release: Process Overview
This process details the steps necessary to ingest a PDS4 data delivery locally as well as initiate an associated ingestion of that delivery at the Engineering Node. The flow for this process is as follows:
For this Process, we will assume that the Node has received either a new or updated bundle from a Data Provider and that the bundle is staged in an area on disk that is accessible by the locally installed PDS4 software (including but not limited to the Validate Tool and Harvest Tool). The following topics can be found in this document:
Validate
The first step to perform after receiving new or updated data from a Data Provider is to validate that data. This can be accomplished by executing the Validate Tool. There are a few ways to execute the software depending on the state of development of the data. In this case, we would expect to have a complete bundle with fully resolvable schemaLocation references in the PDS4 labels. The PDS4 Data Release at DN procedure details the steps for this validation. Any errors generated during the run should be corrected prior to moving to the next step. Depending on the error(s) encountered, the Data Provider may need to be involved in the correction.
Ingest at the Discipline Node (DN)
The next step is to ingest the data at the local Discipline Node. Depending on the Node, this ingestion may be preceded by an ingestion into a Node-specific data system or simply copying the data to an online directory for access by the public. The rest of this step focuses on ingesting the data with the locally installed PDS4 software. The PDS4 Data Release at DN procedure details the steps for this ingestion. Any errors generated during ingestion should be corrected prior to moving to the next step. Depending on the error(s) encountered, the Data Provider may need to be involved in the correction.
The final step of this process will notifying Engineering Node that the bundles and collections are ready for ingestion into the central Registry and Search.
Ingest at the Engineering Node (EN)
The next step is for the EN operations staff to ingest the Product_Bundle and Product_Collection products (and their associated inventory files), associated with the PDS4 data release, into the EN-hosted Registry and Search Services. The PDS4 Data Release at EN procedure details the steps for this ingestion.
Release
The next step is for the EN operations staff to send out a data release notification to subscribed PDS users. The PDS4 Data Release at EN procedure details the steps for this notification.