Operation (PDS3)

This document describes how to operate the Harvest Tool software for use with PDS3 data product registration. The following topics can be found in this document:

Note: The command-line examples in this section have been broken into multiple lines for readability. The commands should be reassembled into a single line prior to execution.

Quick Start

This section is intended to give a quick and easy way to set up the Harvest policy configuration file and how to run the tool. For a more detailed explanation on other ways to set up the policy configuration file as well as other ways of running the tool, go to the Harvest Policy File and Advanced Usage sections.

Setup

Included in the Harvest package is an example policy configuration file for PDS3 data product registration. Go to the examples/ folder, make a copy of the harvest-policy-pds3.xml file and modify it as necessary. The following breaks down the policy file example and indicates what modifications are to be performed.

Registry Package

<registryPackage>
  <name>Harvest Package Example PDS3 Products</name>
  <description>This is a Harvest run of the Example PDS3 products.</description>
</registryPackage>
        

Specify a Registry package name and description. This allows the Registry to associate registered products of a Harvest run to a particular package.

PDS3 Directories

<pds3Directories>
  <path>$HOME/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA</path>
  <fileFilter>
    <include>*.LBL</include>
  </fileFilter>
</pds3Directories>
        

Specify the top level directory for Harvest to crawl for products to register.

Access URLs

<accessUrls registerFileUrls="false">
  <accessUrl>
    <baseUrl>http://starbase.jpl.nasa.gov</baseUrl>
    <offset>$HOME</offset>
  </accessUrl>
</accessUrls>
        

Specify the base URL of where the physical data products are located. This allows Harvest to provide links to the physical data products in the slots of each registered product in the Registry.

Checksums

<checksums generate="true">
  <manifest basePath="$HOME/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/">
    $HOME/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/CHECKSUMS.TXT
  </manifest>
</checksums>
        

Specify a Checksum Manifest file. The basePath attribute is used to resolve relative file references, if found, within a Manifest file. If this attribute is not specified in the policy configuration file, the default behavior is to use the target directory as the base path. If there are multiple target directories specified, then it is required to explicitly specify a base path value in the policy.

With this configuration, Harvest will generate checksums for each file object to be registered and compare against the supplied checksums in the data product label as well as the manifest file.

LID Contents

<lidContents prefix="urn:nasa:pds" appendFilename="true">
  <elementName>DATA_SET_ID</elementName>
</lidContents>
        

Specify any additional elements to use to formulate the LID for each PDS3 data product that will get registered.

Title Contents

<titleContents appendFilename="true">
  <elementName>DATA_SET_ID</elementName>
</titleContents>
        

Specify any additional elements to use to formulate the title for each PDS3 data product that will get registered.

Static Metadata

<staticMetadata>
  <slot name="information_model_version">
    <value>1.2.0.1</value>
  </slot>
  <slot name="product_class">
    <value>Product_Proxy_PDS3</value>
  </slot>
  <slot name="data_set_ref">
    <value>urn:nasa:pds:context_pds3:data_set:data_set.vg2-j-pls-5-summ-ele-mom-96.0sec-v1.0</value>
  </slot>
  <slot name="investigation_ref">
    <value>urn:nasa:pds:context_pds3:investigation:mission.voyager</value>
  </slot>
  <slot name="instrument_host_ref">
    <value>urn:nasa:pds:context_pds3:instrument_host:instrument_host.vg2</value>
  </slot>
  <slot name="instrument_ref">
    <value>urn:nasa:pds:context_pds3:instrument:instrument.pls_vg2</value>
  </slot>
  <slot name="target_ref">
    <value>urn:nasa:pds:context_pds3:target:target.planet.jupiter</value>
  </slot>
</staticMetadata>
        

Specify metadata to go with each PDS3 data product registration.

Ancillary Metadata

<ancillaryMetadata>
  <elementName slotName="observation_start_date_time">
    START_TIME
  </elementName>
  <elementName slotName="observation_stop_date_time">
    STOP_TIME
  </elementName>
  <elementName slotName="product_type">
    PRODUCT_TYPE
  </elementName>
  <elementName slotName="creation_date_time">
    PRODUCT_CREATION_TIME
  </elementName>
  <elementName slotName="encoding_type">
    INTERCHANGE_FORMAT
  </elementName>
</ancillaryMetadata>
        

Specify metadata to extract from each data product label.

Running The Tool

The following command demonstrates the recommended way to run Harvest:

%> harvest -c harvest-policy-pds3.xml -l harvest.log
        

The -c flag option specifies the policy configuration file while the -l flag option specifies the log file for the Harvest output.

Command-Line Options

The following table describes the command-line options available:

Command-Line OptionDescription
-c, --configSpecify a policy configuration file to set the tool behavior. (This flag is required)
-u, --usernameSpecify a username for authentication with the PDS Security Service.
-p, --passwordSpecify a password associated with the username.
-k, --keystore-passSpecify a keystore password associated with the keystore file being passed into the tool.
-l, --log-fileSpecify a log file name. Default is standard out.
-v, --verboseSpecify the message severity level and above to include in the log (0=Debug, 1=Info, 2=Warning, 3=Error). Default is Info and above (level 1).
-e, --regexpSpecify file patterns to look for when registering products from a target directory. Each pattern must be surrounded by quotes (i.e. -e "*.xml").
-D, --ignore-dirSpecify patterns to look for when traversing a target directory for sub-directories to ignore. Each pattern must be surrounded by quotes (i.e. -D "CATALOG").
-pds3, --is-pds3-dirSpecify to indicate that the target directory is a PDS3 directory. Note that only one PDS3 target directory can be passed into the tool.
-P, --portSpecify a port number to use if running the tool in persistence mode. See the Persistence Mode section for more details.
-w, --waitSpecify the time, in seconds, to wait in between the crawls if running the tool in persistence mode. See the Persistence Mode section for more details.
-V, --versionDisplay the release number and copyright information.
-h, --helpDisplay harvest usage.

Advanced Usage

This section describes more advanced ways to run the tool, as well as its behaviors and caveats.

Tool Execution

The Harvest Tool operates with a policy file to register product metadata. Details on how to create this policy file can be found in the Harvest Policy File section.

This section demonstrates some of the other ways that the tool can be executed:

  • Registering PDS3 Data Products From a Single Target
  • Registering PDS3 Data Products From Multiple Targets
  • Registering PDS3 Data Products From Targets Specified In The Policy File
  • Registering PDS3 Data Products To A Secured Registry Instance
  • Excluding Sub-Directories To Traverse From a Target

Registering PDS3 Products From a Single Target

The following command demonstrates registering PDS3 data products to a non-secured registry instance from a target directory, $HOME/directory, where only files that end with a .LBL file extension, will be processed:

% harvest $HOME/directory -pds3 -e "*.LBL" -c policy.xml
        

Registering PDS3 Products From Multiple Targets

The following command demonstrates how to register PDS3 data products to a non-secured registry instance from two target directories, $HOME/directory1 and $HOME/directory2, using the policy file, policy.xml. Only files that end with a .LBL file extension will be processed. The output will go to a log file, harvest.log:

% harvest $HOME/directory1, $HOME/directory2 -pds3 -e "*.LBL" -c policy.xml -l harvest.log
        

Registering PDS3 Products From Targets Specified In The Policy File

Targets can either be specified on the command-line or in in the policy file. Any targets specified on the command-line will overwrite any targets specified in the policy file. The following command demonstrates registering PDS3 data products based on targets specified in the policy file, policy.xml:

% harvest -c policy.xml
        

Registering Products To A Secured Registry Instance

The following command demonstrates how to register PDS3 data products to a secured registry instance from a target directory, $HOME/directory, using the policy file, policy.xml:

% harvest $HOME/directory -pds3 -c policy.xml -u {username} -p {password} \
  -k {keystorePassword}
        

Excluding Sub-Directories To Traverse From a Target

The following command demonstrates registering PDS3 data products from a target directory, $HOME/directory, where the tool will not traverse the sub-directory CONTEXT:

% harvest $HOME/directory -pds3 -c policy.xml -D "CONTEXT"
        

Persistence Mode

The Harvest Tool can be run in persistence mode through an XML-RPC accessible web service called a daemon. Under this scenario, the Harvest Tool wakes up periodically, inspects a target directory or directories, and registers the latest products. This section details how to set this up.

In order to run the tool through the daemon, the command-line option flags -P and -w need to be used. This tells the Harvest Tool the port number to use and how long to sleep in between crawls, respectively. When the daemon is running, it can be accessed through the following url: http://localhost:{port number}/xmlrpc. The following command demonstrates launching the Harvest Tool through the daemon on port 9001, where it will wait 120 seconds in between crawls:

% harvest -c policy.xml -u {username} -p {password} \
  -k {keystorePassword} -l log.txt -P 9001 -w 120
        

After running the above command, the daemon will be accessible at http://localhost:9001/xmlrpc.

In order to stop the daemon from running, a daemon controller is needed. The bin/ directory of the Harvest Tool release package contains a shell script, harvest-ctrl, and a batch file, harvest-ctrl.bat, which are used to gracefully shut down the daemon service on a UNIX-like and Windows system, respectively. In addition, they can provide a few additional statistics about the crawling.

The following table describes the command-line options available for harvest-ctrl:

Command-Line OptionDescription
--urlSpecify the URL of the daemon service running the Harvest Tool.
--operationSpecify a single operation to perform. List of valid operations can be found in the next table.

The following table describes the operation names available to pass with the --operation command-line option:

Operation OptionDescription
--stopSpecify this operation to shut down the daemon service.
--isRunningGives an indication whether the daemon service is running.
--getNumCrawlsReturns the number of crawls that have occurred.
--getWaitIntervalReturns the time, in seconds, that the crawler has to wait in between crawls.
--getMilisCrawlingReturns the amount of milliseconds spent crawling.
--getAverageCrawlTimeReturns the average amount of time, in milliseconds, spent during each crawl.

The following examples demonstrate how to run harvest-ctrl using a few of the different operations. For demonstration purposes, assume that the daemon service is located at the following url: http://localhost:9001/xmlrpc.

Determine the Status of the Daemon Service

The following command is used to find out if the daemon service is still running:

% harvest-ctrl --url http://localhost:9001/xmlrpc --operation --isRunning
        

Shutdown the Daemon Service

The following command demonstrates shutting down the daemon service:

% harvest-ctrl --url http://localhost:9001/xmlrpc --operation --stop
        

PDS3 Unlabeled File Registration

Normally, the Harvest Tool is used for registering labeled products. However, there may be a use case for wanting to register unlabeled files (browse images, thumbnail images, etc.). This section details how to set up the policy file to do this.

Included in the Harvest package is an example policy configuration file for registering unlabeled PDS3 files. Go to the examples/ folder, make a copy of the harvest-policy-unlabeled-pds3-files.xml file and modify it as necessary. The set up is similar to what is described in the Setup section. The only difference is that the candidates area is configured slightly differently as seen below:

<candidates>
  <pds3ProductMetadata objectType="Product_File_Repository">
    <lidContents prefix="urn:nasa:pds:msl-m-hazcam-5-rdr-v1.0" appendDir="true">
      <offset>$HOME/MSLHAZ_1XXX</offset>
    </lidContents>
    
    <staticMetadata>
      <slot name="product_class">
        <value>Product_File_Repository</value>
      </slot>
      <slot name="file_type">
        <value>Extra</value>
      </slot>
    </staticMetadata>
  </pds3ProductMetadata>
</candidates>
        

The objectType="Product_File_Repository" attribute must be specified in the config file. This tells the tool to perform unlabeled file registration. Each file being processed will be registered as a Product_File_Repository product. As the tool crawls a directory, it first checks that each file about to be processed does not have an associated label file in the same directory. If it does, it will skip this file.

For the lidContents area, the full path to the target file being registered will be appended to the prefix value. Specify an offset to trim off of the path. In this example, $HOME/MSHLHAZ_1XXX will be trimmed off the file path before appending to the prefix.

Once the policy file has been modified, run the tool as you normally would:

%> harvest -c harvest-policy-unlabeled-pds3-files.xml -l harvest-unlabeled-pds3-files.log
        

Harvest Policy File

The Harvest policy file is an XML-based configuration file that the tool uses to find products and register their metadata. The schema for the policy file can be found in the Harvest Policy Schema section. This section describes the valid elements that are available to setup the policy file to do PDS3 data product registration.

PDS3 Data Product Registration

By default, the tool registers discovered PDS3 products under the Product_Proxy_PDS3 objectType in the registry. Additionally, the tool has to dynamically create certain metadata in order to support ingestion of PDS3 data products into the registry. The following is an example of a policy file to perform product registration of PDS3 data products:

<policy>
  <!-- Specify a single directory containing the PDS3 data products to register. -->
  <pds3Directory>
    <path>/Users/mcayanan/pds3</path>
    <fileFilter>
      <include>*.LBL</include>
    </fileFilter>
  </pds3Directory>
  <candidates>
    <!--
      Harvest will register PDS3 data products under the objectType
      'Product_Proxy_PDS3'.
    -->
    <pds3ProductMetadata>
      <!-- Tells Harvest what element values to use to create the LID. -->
      <lidContents prefix="urn:nasa:pds">
        <elementName>DATA_SET_ID</elementName>
        <elementName>INSTRUMENT_ID</elementName>
        <elementName>PRODUCT_ID</elementName>
      </lidContents>
      <titleContents>
        <elementName>DATA_SET_ID</elementName>
        <elementName>PRODUCT_ID</elementName>
      </titleContents>
      <staticMetadata>
        <slot name="information_model_version">
          <value>0.8.0.0.k</value>
        </slot>
        <slot name="target_ref">
          <value>urn:nasa:pds:target:MARS::1.0</value>
        </slot>
        <slot name="mission_ref">
          <value>urn:nasa:pds:mission.MER</value>
        </slot>
      </staticMetadata>
      <!-- Register any additional metadata. Default is to
        register metadata defined in the identification area of the
        Product_Proxy_PDS3 schema. -->
      <ancillaryMetadata>
        <elementName slotName="start_time">
          START_TIME
        </elementName>
        <elementName slotName="stop_time">
          STOP_TIME
        </elementName>
      </ancillaryMetadata>
      <includePaths>
        <path>/data/pds3/label</path>
      </includePaths>
    </pds3ProductMetadata>
  </candidates>
</policy>
      

This policy file is made up of the following complex type elements: pds3Directory, pds3ProductMetadata, lidContents, titleContents, staticMetadata, ancillaryMetadata, and includePaths.

pds3Directory

Specify this element to tell the Harvest Tool the directory location to crawl. The following table describes the elements that are allowed:

Element NameDescription
pathSpecify a directory location containing the PDS3 data products to register. Multiple tags can be specified to point to other directories to crawl.
fileFilterSpecify one or more include elements, where each element value contains a pattern to look for when crawling a target directory for files to register. If omitted, the default is to get all files within a directory.
directoryFilterSpecify one or more exclude elements, where each element value contains a pattern to look for when crawling a target directory for sub-directories to ignore.

In the example above, the Harvest Tool will crawl for PDS3 data products starting at the location /data/pds3/dataset, looking for files with a .LBL file extension.

pds3ProductMetadata

Specify this element to tell the Harvest Tool what metadata to ingest into the registry when registering PDS3 data products. This element must be specified within the candidates tag as shown in the example. The following table describes the elements that are allowed:

Element NameDescription
lidContentsTells the Harvest Tool what fields to use to form the logical identifier.
staticMetadataSpecify static metadata to add as slots for every discovered PDS3 data product.
ancillaryMetadataSpecify ancillary metadata to add as slots for every discovered PDS3 data product.

lidContents

Specify this element to tell the Harvest Tool how to generate the logical identifier. The prefix attribute specifies what to prepend to the logical identifier. This is a required attribute. In the example above, the logical identifiers of every discovered PDS3 data product will be prefixed with urn:nasa:pds.

The following table describes the optional attributes that are allowed:

Attribute NameDescription
appendFilenameWhen set to true, the tool will append the product label filename (minus the extension) to the end of the logical identifier.

The following table describes the elements that are allowed:

Element NameDescription
elementNameSpecify an element name whose value will be used in creating the logical identifier. Can be specified more than once.

In the policy example above, the logical identifier will be formed using the following contents: prefix + DATA_SET_ID + ":" + INSTRUMENT_ID + ":" + PRODUCT_ID.

titleContents

Specify this element to tell the Harvest Tool how to generate the title of the registered PDS3 product.

There is an optional attribute that can be specified called appendFilename. When this attribute is specified and set to true, the Harvest Tool will append the product label filename (minus the extension) to the end of the title.

The following table describes the elements that are allowed:

Element NameDescription
elementNameSpecify an element name whose value will be used in creating the title of the registered product. Can be specified more than once.

In the policy example above, the title contents will be formed using the following contents: DATA_SET_ID + " " + PRODUCT_ID.

staticMetadata

Specify this element to tell the Harvest Tool to register a set of static metadata with the discovered PDS3 data products. The following table describes the elements that are allowed:

Element NameDescription
slotThe slot element contains a name attribute to specify what slot name to use in the registry. The value tag specifies the slot value.

In the policy example above, it specifies that for every PDS3 data product that is registered, the following metadata will be added as slots: information_model_version, target_ref, and mission_ref.

ancillaryMetadata

Specify this element to tell the Harvest tool what additional metadata to register. The following table describes the elements that are allowed:

Element NameDescription
elementNameSpecify an element name found in the PDS3 data product label. An optional slotName attribute can be used to set the slot name for this element. If slotName is not set, the tool will use the element name in lowercase form as the slot name. In addition, a slotType attribute can be used to define units to go along with an extracted value. The units will be registered as the slotType in the registry.

In the example above, the values from the following elements will be extracted from a PDS3 product label: START_DATE_TIME and STOP_DATE_TIME.

includePaths

Specify this element to tell the Harvest tool the locations of where to find file references specified in a label. By default, the tool will look for the file reference in the location of the label file. The following table describes the elements that are allowed:

Element NameDescription
pathSpecify the directory location of where to find the file references in a label. This element can be specified more than once to specify multiple search paths.

In the example above, the tool will look at the /data/pds3/label directory for file references if they cannot be found in the same location as the label file.

Report Format

This section describes the contents of the Harvest Tool report. At this time, the Harvest Tool only outputs a series of log messages. The log will report the success or failure of a discovered product attempting to be registered. Additionally, any syntactical errors in a discovered product are reported. A log consists of a severity level, file name, and a message. The following is an example of some of the log messages that can be expected from the Harvest Tool:

PDS Harvest Tool Log

Version                     Version 1.7.0-dev
Time                        Thu, Sep 18 2014 at 05:41:08 PM
Target(s)                   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA]
Target Type                 PDS3
File Inclusions             [*.LBL]
Severity Level              INFO
Registry Location           http://localhost:8080/registry
Registry Package Name       Harvest Package Example PDS3 Products
Registration Package GUID   urn:uuid:f6ac9627-aa58-43f2-b07a-fd2f66237fd7

INFO:   XML extractor set to the following default namespace: http://pds.nasa.gov/pds4/pds/v1
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/CHECKSUMS.TXT] \
Processing checksum manifest.
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Begin processing.
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Creating logical identifier.
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Created the following logical identifier: urn:nasa:pds:vg2-j-pls-5-summ-ele-mom-96.0sec-v1.0:ele_mom
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Created title: VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0 ELE_MOM
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL]
Created access url: http://starbase.jpl.nasa.gov/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL
SUCCESS:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Successfully registered product: urn:nasa:pds:vg2-j-pls-5-summ-ele-mom-96.0sec-v1.0:ele_mom::1.0
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Product has the following GUID: urn:uuid:3a2da8de-72f4-4ca9-a9e7-7db6405daf18
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Capturing file object metadata for ELE_MOM.LBL
WARNING:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Generated checksum 'c63f0c34641c60a786edad1dea542c72' does not match supplied checksum 'c5a1215ba4a2d1287f3bd855dd62dc17' in the manifest for file object \
'/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL'.
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Capturing file object metadata for ELE_MOM.TAB
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Generated checksum '2b555c42a7e7b4981407c9a824237f4a' matches the supplied checksum '2b555c42a7e7b4981407c9a824237f4a' in the manifest for file object \
'/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.TAB'.
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Created access url: http://starbase.jpl.nasa.gov/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL
SUCCESS:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Successfully registered product: urn:nasa:pds:vg2-j-pls-5-summ-ele-mom-96.0sec-v1.0:ele_mom:ele_mom.lbl::1.0
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Product has the following GUID: urn:uuid:92e68631-f0f6-4a05-ac77-1d3f0c2f2aa8
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Created access url: http://starbase.jpl.nasa.gov/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.TAB
SUCCESS:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Successfully registered product: urn:nasa:pds:vg2-j-pls-5-summ-ele-mom-96.0sec-v1.0:ele_mom:ele_mom.tab::1.0
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Product has the following GUID: urn:uuid:7a98092a-2f8e-480d-b884-15311b8cff77
SUCCESS:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Successfully registered association to urn:nasa:pds:vg2-j-pls-5-summ-ele-mom-96.0sec-v1.0:ele_mom:ele_mom.lbl::1.0
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Association has the following GUID: urn:uuid:785fb3fe-1520-4608-8464-4ad53cf5571e
SUCCESS:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Successfully registered association to urn:nasa:pds:vg2-j-pls-5-summ-ele-mom-96.0sec-v1.0:ele_mom:ele_mom.tab::1.0
INFO:   [/Users/mcayanan/pds3/VG2-J-PLS-5-SUMM-ELE-MOM-96.0SEC-V1.0/DATA/ELE_MOM.LBL] \
Association has the following GUID: urn:uuid:87a037e3-f4c7-42a2-9a8f-d435a0c0e51d

Summary:

1 of 1 file(s) processed, 0 other file(s) skipped
0 error(s), 1 warning(s)

1 of 1 products registered.
2 of 2 ancillary products registered.

Product Types Registered:
2 Product_File_Repository
1 Product_Proxy_PDS3

1 of 2 generated checksums matched their supplied value in the manifest, 0 value(s) not checked.

2 of 2 associations registered.


End of Log



     

Common Errors

At this time, there are no common errors to report.