**Planetary Data System**

**Validation Matrix**

**DRAFT**

March 15, 2004

Version 1.0

![](media/image1.png){width="2.5125in" height="2.5125in"}

![](media/image2.wmf){width="1.1722222222222223in"
height="0.4486111111111111in"}

Jet Propulsion Laboratory

Pasadena, California

JPL D-xxxxx

**CHANGE LOG**

  ---------------- ------------ ----------------------------- ------------
  **Revision**     **Date**     **Description**               **Author**

  Start Draft      2004-02-01   Initial outline               R. Joyner

  Draft Release 1  2004-03-15   First Draft                   R. Joyner
  ---------------- ------------ ----------------------------- ------------

**TABLE OF CONTENTS**

**Section Title Page**

[1. INTRODUCTION 5](#introduction)

[1.1. Document Purpose 5](#document-purpose)

[1.2. Document Scope 5](#document-scope)

[1.3. Applicable Documents 6](#applicable-documents)

[2. Validation Checklist - Inspection
7](#validation-checklist---inspection)

[3. Detailed Checklist - Inspection
10](#detailed-checklist---inspection)

[3.1 Read the Top Level files 10](#read-the-top-level-files)

[3.1.1 AAREADME.TXT 10](#aareadme.txt)

[3.1.2 VOLDESC.CAT 12](#voldesc.cat)

[3.1.3 ERRATA.TXT 13](#errata.txt)

[3.1.4 EXTRANEOUS Files 13](#extraneous-files)

[3.2 Inspect the files in the CATALOG directory
13](#inspect-the-files-in-the-catalog-directory)

[3.2.1 MISSION.CAT 14](#mission.cat)

[3.2.2 DATASET.CAT 15](#dataset.cat)

[3.3 Inspect the files in the DOCUMENT directory
16](#inspect-the-files-in-the-document-directory)

[3.4 Inspect the files in the INDEX directory
16](#inspect-the-files-in-the-index-directory)

[3.5 Inspect the files in the LABEL directory
18](#inspect-the-files-in-the-label-directory)

[3.6 Inspect the files in the BROWSE directory
18](#inspect-the-files-in-the-browse-directory)

[3.7 Inspect the files in the CALIB directory
19](#inspect-the-files-in-the-calib-directory)

[3.8 Inspect the files in the GEOM directory
19](#inspect-the-files-in-the-geom-directory)

[3.9 Inspect the files in the GAZETTER directory
20](#inspect-the-files-in-the-gazetter-directory)

[3.10 Inspect the files in the SOFTWARE directory
20](#inspect-the-files-in-the-software-directory)

[3.11 Inspect the files in the EXTRAS directory
21](#inspect-the-files-in-the-extras-directory)

[3.12 Inspect the files in the DATA directory
21](#inspect-the-files-in-the-data-directory)

[4. Validation Checklist -- Tool Suite
23](#validation-checklist-tool-suite)

[5. Detailed Checklist -- Tool Suite 24](#detailed-checklist-tool-suite)

[5.1 Verify ISO 9660 Compliance 24](#verify-iso-9660-compliance)

[5.2 Verify Syntax and Semantics of PDS Labels
25](#verify-syntax-and-semantics-of-pds-labels)

[5.3 Verify Keyword and Keyword-value pairs
25](#verify-keyword-and-keyword-value-pairs)

[5.4 Verify Record Structure of PDS Labels
26](#verify-record-structure-of-pds-labels)

[5.5 Verify Reference Citations 30](#verify-reference-citations)

[5.6 Verify the Structure of the INDEX files
31](#verify-the-structure-of-the-index-files)

[5.7 Verify Data Products 31](#verify-data-products)

[5.7 Test Referential Integrity 32](#test-referential-integrity)

[appendix a Online Resources 33](#appendix-a-online-resources)

[appendix B PDS Data SET Types 34](#appendix-b-pds-data-set-types)

[appendix c isocheck parameters 36](#appendix-c-isocheck-parameters)

[appendix d LVTOOL parameters 38](#appendix-d-lvtool-parameters)

[appendix e kwvTOOL parameters 40](#appendix-e-kwvtool-parameters)

[appendix f NEWLINE parameters 42](#appendix-f-newline-parameters)

[appendix g reffind parameters 44](#appendix-g-reffind-parameters)

#  

##### INTRODUCTION

The Planetary Data System (PDS) ensures the quality of archive data
volumes submitted to it by two primary methods:

-   Validation

-   Peer-review

The first method, validation, is a qualitative assessment or an archive
volume, where the emphasis is on the overall quality of the product and
its conformance to PDS Standards. Validation addresses "How well does
the product fit the PDS Model ?" This document addresses the validation
process. A brief step-by-step checklist is presented followed by a more
detailed discussion of each step involved in a complete and exhaustive
validation of an archive volume.

The second method, Peer-review, addresses "How well does the product
serve its scientific users ?" The Peer-review process is not addressed
in this document.

##### Document Purpose

This document presents the validation checklist. The checklist should:

-   Make the practice of validation more consistent

-   Improve understanding of the validation process

-   Enable PDS discipline nodes to perform as many validation checks as
    possible

-   Provide guidelines for writing software that assists in validation

##### Document Scope

The validation checklist shows how to apply the standards. It is not a
substitute for the standards, themselves. The [PDS Standards
Reference]{.underline} is still the canonical source of standards
information. When there is a conflict between the checklist and the [PDS
Standards]{.underline}, it is the checklist that should be modified.

The validation checklist describes *what* to test. For the most part, it
does not discuss the tools to use for testing. Think of it as providing
the requirements for such tools.

There are two parts to the checklist. The first part summarizes the
checklist as a table. This gives a high-level view of the validation
process. It also makes it easy to \"check off\" each step as it is
performed in an actual validation. The second part describes each step
in detail.

##### Applicable Documents

\[1\] Planetary Data System Standards Reference, October 15, 2002,

> Version 3.5, JPL D-7669, Part 2. (<http://pds.jpl.nasa.gov/stdref>)

\[2\] Planetary Science Data Dictionary Document, August 28, 2002,

JPL D-7116, Rev. E. (<http://pds.jpl.nasa.gov/psdd.pdf>)

\[3\] PDS Toolbox Overview, Toolbox Release 4, JPL D-10263, November 16,
1992. - An overview of PDS supported software libraries and utilities
and available User's Guides. These are optional documents that may help
the data producer in a variety of steps during the overall data
preparation process.

-   PDS Label Verifier User\'s Guide, Version 1.2, JPL D-8923, November
    9, 1992.

-   User\'s Guide for the PDS Label Generators, JPL D-10265, November 2,
    1992.

-   User\'s Guide for the PDS Simple Label Editor, Release 2.4, JPL
    D-9436, November 1, 1992.

-   PDS Table Browser User\'s Guide, JPL D-10264, October 15, 1992.

-   PDS Toolbox Utilities User\'s Guide, Version 1.1, JPL D-9420,
    October 28, 1992.

-   PDS Label Library User\'s Guide, Version 1.1, JPL D-8922, March
    31,1992.

##### Validation Checklist - Inspection

The following steps are taken to "manually" inspect / examine a PDS
archive volume to ensure PDS compliance. Whenever possible, the steps
are linked to an appropriate section of the [PDS Standards
Reference]{.underline}. Some steps fall under the category of general
quality assurance, and these are labeled \"General QA\" in the list:

+---+--------------------------------------------------------+---------+
| * |                                                        |         |
| * |                                                        |         |
| V |                                                        |         |
| a |                                                        |         |
| l |                                                        |         |
| i |                                                        |         |
| d |                                                        |         |
| a |                                                        |         |
| t |                                                        |         |
| i |                                                        |         |
| o |                                                        |         |
| n |                                                        |         |
| C |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| k |                                                        |         |
| l |                                                        |         |
| i |                                                        |         |
| s |                                                        |         |
| t |                                                        |         |
| \ |                                                        |         |
| " |                                                        |         |
| I |                                                        |         |
| n |                                                        |         |
| s |                                                        |         |
| p |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| i |                                                        |         |
| o |                                                        |         |
| n |                                                        |         |
| / |                                                        |         |
| E |                                                        |         |
| x |                                                        |         |
| a |                                                        |         |
| m |                                                        |         |
| i |                                                        |         |
| n |                                                        |         |
| a |                                                        |         |
| t |                                                        |         |
| i |                                                        |         |
| o |                                                        |         |
| n |                                                        |         |
| " |                                                        |         |
| * |                                                        |         |
| * |                                                        |         |
+---+--------------------------------------------------------+---------+
| * | **Action**                                             | **Stan  |
| * |                                                        | dards** |
| S |                                                        |         |
| t |                                                        |         |
| e |                                                        |         |
| p |                                                        |         |
| * |                                                        |         |
| * |                                                        |         |
+---+--------------------------------------------------------+---------+
| P |                                                        |         |
| a |                                                        |         |
| r |                                                        |         |
| t |                                                        |         |
| I |                                                        |         |
| : |                                                        |         |
| G |                                                        |         |
| e |                                                        |         |
| t |                                                        |         |
| a |                                                        |         |
| n |                                                        |         |
| O |                                                        |         |
| v |                                                        |         |
| e |                                                        |         |
| r |                                                        |         |
| v |                                                        |         |
| i |                                                        |         |
| e |                                                        |         |
| w |                                                        |         |
| o |                                                        |         |
| f |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| V |                                                        |         |
| o |                                                        |         |
| l |                                                        |         |
| u |                                                        |         |
| m |                                                        |         |
| e |                                                        |         |
+---+--------------------------------------------------------+---------+
| 1 | Read the top level files for a general understanding   | General |
| . | of the volume.                                         | QA      |
| 1 |                                                        |         |
+---+--------------------------------------------------------+---------+
| 1 | AAREADME.TXT                                           | General |
| . |                                                        | QA      |
| 2 | A well written AAREADME.TXT will contain an overview   |         |
|   | of the contents and organization of the associated     |         |
|   | volume and the science data within the volume, general |         |
|   | instructions for its use, and the person(s) who may be |         |
|   | contacted for additional information, questions, or    |         |
|   | anomalies.                                             |         |
+---+--------------------------------------------------------+---------+
| 1 | VOLDESC.CAT                                            |         |
| . |                                                        |         |
| 3 | The VOLDESC.CAT uses the VOLUME object to provide a    |         |
|   | high-level description of the contents of the archive  |         |
|   | volume. Attention to the naming convention used for    |         |
|   | the VOLUME keywords is critical and must conform to    |         |
|   | "legacy" values. Inspect the Standard Values for each  |         |
|   | keyword to assure compatibility (i.e., make sure the   |         |
|   | new value "fits").                                     |         |
+---+--------------------------------------------------------+---------+
| 1 | ERRATA.TXT                                             |         |
| . |                                                        |         |
| 4 | A well written ERRATA.TXT will provide a complete and  |         |
|   | thorough description of all errors and anomalies that  |         |
|   | are known to exist on the archive volume, and possibly |         |
|   | in previous volumes of a volume set. All known errors  |         |
|   | / anomalies must be described within this file. Any    |         |
|   | waivers against the archive volume must be described   |         |
|   | within this file. Any non-compliant properties or      |         |
|   | practices must be described in a                       |         |
|   | "not-suitable-as-a-model-for-future-archives" caveat.  |         |
+---+--------------------------------------------------------+---------+
| 1 | Ensure there are no more than 100 files in any         | General |
| . | directory.                                             | QA      |
| 5 |                                                        |         |
+---+--------------------------------------------------------+---------+
| 1 | Ensure that the directory structure does not span more | General |
| . | than 8 levels deep.                                    | QA      |
| 6 |                                                        |         |
+---+--------------------------------------------------------+---------+
| 1 | Ensure the ROOT directory is clear of any extraneous   | General |
| . | files (e.g., html navigation files).                   | QA      |
| 7 |                                                        |         |
+---+--------------------------------------------------------+---------+
| 1 | Ensure the archive volume is clear of any              | General |
| . | \"advertising\" or \"endorsements\".                   | QA      |
| 8 |                                                        |         |
|   | Example Disclaimer:                                    |         |
|   |                                                        |         |
|   | The Jet Propulsion Laboratory, the California          |         |
|   | Institute of Technology, and the National Aeronautics  |         |
|   | and Space Administration does not recommend or endorse |         |
|   | any Commercial product mentioned on this PDS archive   |         |
|   | volume.                                                |         |
+---+--------------------------------------------------------+---------+
| 1 | Ensure that any proprietary formats and/or articles    | General |
| . | have been cleared with the institution producing and   | QA      |
| 9 | distributing the archive volumes (e.g., GIF, AGU,      |         |
|   | ICARUS, IEEE, Space Science Reviews).                  |         |
+---+--------------------------------------------------------+---------+
| P |                                                        |         |
| a |                                                        |         |
| r |                                                        |         |
| t |                                                        |         |
| I |                                                        |         |
| I |                                                        |         |
| : |                                                        |         |
| I |                                                        |         |
| n |                                                        |         |
| s |                                                        |         |
| p |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| f |                                                        |         |
| i |                                                        |         |
| l |                                                        |         |
| e |                                                        |         |
| i |                                                        |         |
| n |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| C |                                                        |         |
| A |                                                        |         |
| T |                                                        |         |
| A |                                                        |         |
| L |                                                        |         |
| O |                                                        |         |
| G |                                                        |         |
| d |                                                        |         |
| i |                                                        |         |
| r |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| o |                                                        |         |
| r |                                                        |         |
| y |                                                        |         |
+---+--------------------------------------------------------+---------+
| 2 | Ensure that the CATINFO.TXT file identifies and        | Section |
| . | describes the function of each file in the CATALOG     | 1       |
| 1 | directory.                                             | 9.3.2.1 |
+---+--------------------------------------------------------+---------+
| 2 | 1.  Read each catalog file for content and structure.  | General |
| . |     The files must contain information essential to    | QA      |
| 2 |     understanding the science data and the overall     |         |
|   |     structure of the archive. The documents should     |         |
|   |     impart sufficient detail so that future users will |         |
|   |     be able to "use" the data long after the corporate |         |
|   |     knowledge has disappeared.                         |         |
+---+--------------------------------------------------------+---------+
| 2 | Ensure each catalog file will pass the Referential     |         |
| . | Integrity check                                        |         |
| 3 |                                                        |         |
+---+--------------------------------------------------------+---------+
| P |                                                        |         |
| a |                                                        |         |
| r |                                                        |         |
| t |                                                        |         |
| I |                                                        |         |
| I |                                                        |         |
| I |                                                        |         |
| : |                                                        |         |
| I |                                                        |         |
| n |                                                        |         |
| s |                                                        |         |
| p |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| f |                                                        |         |
| i |                                                        |         |
| l |                                                        |         |
| e |                                                        |         |
| s |                                                        |         |
| i |                                                        |         |
| n |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| D |                                                        |         |
| O |                                                        |         |
| C |                                                        |         |
| U |                                                        |         |
| M |                                                        |         |
| E |                                                        |         |
| N |                                                        |         |
| T |                                                        |         |
| d |                                                        |         |
| i |                                                        |         |
| r |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| o |                                                        |         |
| r |                                                        |         |
| y |                                                        |         |
+---+--------------------------------------------------------+---------+
| 3 | Ensure that the DOCINFO.TXT file identifies and        | Section |
| . | describes the function of each file in the DOCUMENT    | 1       |
| 1 | directory.                                             | 9.3.3.2 |
+---+--------------------------------------------------------+---------+
| 3 | Ensure that each DOCUMENT, at a minimum, is described  | Section |
| . | by human-readable ASCII text (additional versions may  | 9       |
| 2 | be included)                                           |         |
+---+--------------------------------------------------------+---------+
| 3 | Ensure that each DOCUMENT is described using the       | Section |
| . | correct set of object characteristics (e.g., TEXT vs   | 9.1     |
| 3 | DOCUMENT object)                                       |         |
+---+--------------------------------------------------------+---------+
| 3 | If the archive product uses                            | Section |
| . | locally-defined-data-elements (i.e., a local           | 1       |
| 4 | data-dictionary), ensure that the Data Dictionary      | 9.3.3.2 |
|   | files are present (e.g., PDSDD.FUL and PDSDD.IDX).     |         |
+---+--------------------------------------------------------+---------+
| P |                                                        |         |
| a |                                                        |         |
| r |                                                        |         |
| t |                                                        |         |
| I |                                                        |         |
| V |                                                        |         |
| : |                                                        |         |
| I |                                                        |         |
| n |                                                        |         |
| s |                                                        |         |
| p |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| f |                                                        |         |
| i |                                                        |         |
| l |                                                        |         |
| e |                                                        |         |
| s |                                                        |         |
| i |                                                        |         |
| n |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| I |                                                        |         |
| N |                                                        |         |
| D |                                                        |         |
| E |                                                        |         |
| X |                                                        |         |
| d |                                                        |         |
| i |                                                        |         |
| r |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| o |                                                        |         |
| r |                                                        |         |
| y |                                                        |         |
+---+--------------------------------------------------------+---------+
| 4 | Ensure that the INDXINFO.TXT file identifies and       | Section |
| . | describes the function of each file in the INDEX       | 1       |
| 1 | directory.                                             | 9.3.2.3 |
+---+--------------------------------------------------------+---------+
| 4 | Ensure that the required columns of data exist in the  | A       |
| . | INDEX.LBL and INDEX.TAB.                               | ppendix |
| 2 |                                                        | A       |
|   |                                                        | .21.4.1 |
+---+--------------------------------------------------------+---------+
| 4 | Ensure that only data-labels are listed in the         | A       |
| . | INDEX.TAB.                                             | ppendix |
| 3 |                                                        | A.21    |
+---+--------------------------------------------------------+---------+
| 4 | Ensure that columns of data in the INDEX.TAB that have | Section |
| . | a DATA_TYPE = CHAR are double quoted.                  | 12      |
| 4 |                                                        |         |
+---+--------------------------------------------------------+---------+
| 4 | Ensure that columns of data in the INDEX.TAB that have | Section |
| . | a DATA_TYPE \<\> CHAR are not double quoted (e.g.,     | 12      |
| 5 | DATA_TYPE = TIME or DATE or INTEGER, or REAL, etc.)    |         |
+---+--------------------------------------------------------+---------+
| 4 | Ensure that if VOLUMES \> 1 (in VOLDESC.CAT), that a   | Section |
| . | CUMINDEX.LBL and CUMINDEX.TAB exist.                   | 1       |
| 6 |                                                        | 9.3.2.3 |
+---+--------------------------------------------------------+---------+
| 4 | Ensure that if VOLUMES = 1 (in VOLDESC.CAT), that a    | Section |
| . | CUMINDEX.LBL and CUMINDEX.TAB are present.             | 1       |
| 7 |                                                        | 9.3.2.3 |
+---+--------------------------------------------------------+---------+
| P |                                                        |         |
| a |                                                        |         |
| r |                                                        |         |
| t |                                                        |         |
| V |                                                        |         |
| : |                                                        |         |
| I |                                                        |         |
| n |                                                        |         |
| s |                                                        |         |
| p |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| f |                                                        |         |
| i |                                                        |         |
| l |                                                        |         |
| e |                                                        |         |
| s |                                                        |         |
| i |                                                        |         |
| n |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| L |                                                        |         |
| A |                                                        |         |
| B |                                                        |         |
| E |                                                        |         |
| L |                                                        |         |
| d |                                                        |         |
| i |                                                        |         |
| r |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| o |                                                        |         |
| r |                                                        |         |
| y |                                                        |         |
+---+--------------------------------------------------------+---------+
| 5 | Ensure that the LABINFO.TXT file identifies and        | Section |
| . | describes the function of each file in the LABEL       | 1       |
| 1 | directory.                                             | 9.3.3.6 |
+---+--------------------------------------------------------+---------+
| 5 | Ensure that each Format file ("label snippet") is not  | General |
| . | terminated with an "END" statement.                    | QA      |
| 2 |                                                        |         |
+---+--------------------------------------------------------+---------+
| 5 | Ensure that each Format file ("label snippet") is not  | General |
| . | labeled (with a separate label file).                  | QA      |
| 3 |                                                        |         |
+---+--------------------------------------------------------+---------+
| P |                                                        |         |
| a |                                                        |         |
| r |                                                        |         |
| t |                                                        |         |
| V |                                                        |         |
| I |                                                        |         |
| : |                                                        |         |
| I |                                                        |         |
| n |                                                        |         |
| s |                                                        |         |
| p |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| f |                                                        |         |
| i |                                                        |         |
| l |                                                        |         |
| e |                                                        |         |
| s |                                                        |         |
| i |                                                        |         |
| n |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| B |                                                        |         |
| R |                                                        |         |
| O |                                                        |         |
| W |                                                        |         |
| S |                                                        |         |
| E |                                                        |         |
| d |                                                        |         |
| i |                                                        |         |
| r |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| o |                                                        |         |
| r |                                                        |         |
| y |                                                        |         |
+---+--------------------------------------------------------+---------+
| 6 | Ensure that the BROWINFO.TXT file identifies and       | Section |
| . | describes the function of each file in the BROWSE      | 1       |
| 1 | directory.                                             | 9.3.3.x |
+---+--------------------------------------------------------+---------+
| 6 | Ensure that the browse files use an approved image     | General |
| . | format -- PNG.                                         | QA      |
| 2 |                                                        |         |
+---+--------------------------------------------------------+---------+
| P |                                                        |         |
| a |                                                        |         |
| r |                                                        |         |
| t |                                                        |         |
| V |                                                        |         |
| I |                                                        |         |
| I |                                                        |         |
| : |                                                        |         |
| I |                                                        |         |
| n |                                                        |         |
| s |                                                        |         |
| p |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| f |                                                        |         |
| i |                                                        |         |
| l |                                                        |         |
| e |                                                        |         |
| s |                                                        |         |
| i |                                                        |         |
| n |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| C |                                                        |         |
| A |                                                        |         |
| L |                                                        |         |
| I |                                                        |         |
| B |                                                        |         |
| d |                                                        |         |
| i |                                                        |         |
| r |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| o |                                                        |         |
| r |                                                        |         |
| y |                                                        |         |
+---+--------------------------------------------------------+---------+
| 7 | Ensure that the CALINFO.TXT file identifies and        | Section |
| . | describes the function of each file in the CALIB       | 1       |
| 1 | directory.                                             | 9.3.3.1 |
+---+--------------------------------------------------------+---------+
| 7 | Ensure, at a minimum, that the calibration             | Section |
| . | algorithm(s), programs / routines, and sample files    | 8.1     |
| 2 | are present and are usable to the point where the user |         |
|   | community could (re)process the data independent of    |         |
|   | input from the data producer(s).                       |         |
+---+--------------------------------------------------------+---------+
| P |                                                        |         |
| a |                                                        |         |
| r |                                                        |         |
| t |                                                        |         |
| V |                                                        |         |
| I |                                                        |         |
| I |                                                        |         |
| I |                                                        |         |
| : |                                                        |         |
| I |                                                        |         |
| n |                                                        |         |
| s |                                                        |         |
| p |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| f |                                                        |         |
| i |                                                        |         |
| l |                                                        |         |
| e |                                                        |         |
| s |                                                        |         |
| i |                                                        |         |
| n |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| G |                                                        |         |
| E |                                                        |         |
| O |                                                        |         |
| M |                                                        |         |
| E |                                                        |         |
| T |                                                        |         |
| R |                                                        |         |
| Y |                                                        |         |
| d |                                                        |         |
| i |                                                        |         |
| r |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| o |                                                        |         |
| r |                                                        |         |
| y |                                                        |         |
+---+--------------------------------------------------------+---------+
| 8 | Ensure that the GEOMINFO.TXT file identifies and       | Section |
| . | describes the function of each file in the GEOMETRY    | 1       |
| 1 | directory.                                             | 9.3.3.5 |
+---+--------------------------------------------------------+---------+
| 8 | Ensure, at a minimum, that the files describe the      | Section |
| . | observational geometry of the data products (e.g.,     | 8.2     |
| 2 | SEDRs, SPICE kernels).                                 |         |
+---+--------------------------------------------------------+---------+
| P |                                                        |         |
| a |                                                        |         |
| r |                                                        |         |
| t |                                                        |         |
| I |                                                        |         |
| X |                                                        |         |
| : |                                                        |         |
| I |                                                        |         |
| n |                                                        |         |
| s |                                                        |         |
| p |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| f |                                                        |         |
| i |                                                        |         |
| l |                                                        |         |
| e |                                                        |         |
| s |                                                        |         |
| i |                                                        |         |
| n |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| G |                                                        |         |
| A |                                                        |         |
| Z |                                                        |         |
| E |                                                        |         |
| T |                                                        |         |
| T |                                                        |         |
| E |                                                        |         |
| R |                                                        |         |
| d |                                                        |         |
| i |                                                        |         |
| r |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| o |                                                        |         |
| r |                                                        |         |
| y |                                                        |         |
+---+--------------------------------------------------------+---------+
| 9 | Ensure that the GAZINFO.TXT file identifies and        | Section |
| . | describes the function of each file in the GAZETTER    | 1       |
| 1 | directory.                                             | 9.3.3.4 |
+---+--------------------------------------------------------+---------+
| 9 | Ensure, at a minimum, that the GAZETTER_TABLE(s) of    | Section |
| . | information adequately and accurately describe the     | 8.1     |
| 2 | detailed information about all the named features      |         |
|   | associated with the target(s) under investigation.     |         |
+---+--------------------------------------------------------+---------+
| P |                                                        |         |
| a |                                                        |         |
| r |                                                        |         |
| t |                                                        |         |
| X |                                                        |         |
| : |                                                        |         |
| I |                                                        |         |
| n |                                                        |         |
| s |                                                        |         |
| p |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| f |                                                        |         |
| i |                                                        |         |
| l |                                                        |         |
| e |                                                        |         |
| s |                                                        |         |
| i |                                                        |         |
| n |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| S |                                                        |         |
| O |                                                        |         |
| F |                                                        |         |
| T |                                                        |         |
| W |                                                        |         |
| A |                                                        |         |
| R |                                                        |         |
| E |                                                        |         |
| d |                                                        |         |
| i |                                                        |         |
| r |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| o |                                                        |         |
| r |                                                        |         |
| y |                                                        |         |
+---+--------------------------------------------------------+---------+
| 1 | Ensure that the SOFTINFO.TXT file identifies and       | Section |
| 0 | describes the function of each file in the SOFTWARE    | 1       |
| . | directory.                                             | 9.3.3.7 |
| 1 |                                                        |         |
+---+--------------------------------------------------------+---------+
| 1 | Ensure, at a minimum, the descriptions of the          | Section |
| 0 | processing algorithms are adequately and accurately    | 1       |
| . | described. The software libraries and application      | 9.3.3.7 |
| 2 | programs for accessing or processing the data may also |         |
|   | be included.                                           |         |
+---+--------------------------------------------------------+---------+
| 1 | Ensure that ONLY public domain software is included on | Section |
| 0 | the archive volume.                                    | 1       |
| . |                                                        | 9.3.3.7 |
| 3 |                                                        |         |
+---+--------------------------------------------------------+---------+
| P |                                                        |         |
| a |                                                        |         |
| r |                                                        |         |
| t |                                                        |         |
| X |                                                        |         |
| I |                                                        |         |
| : |                                                        |         |
| I |                                                        |         |
| n |                                                        |         |
| s |                                                        |         |
| p |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| f |                                                        |         |
| i |                                                        |         |
| l |                                                        |         |
| e |                                                        |         |
| s |                                                        |         |
| i |                                                        |         |
| n |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| E |                                                        |         |
| X |                                                        |         |
| T |                                                        |         |
| R |                                                        |         |
| A |                                                        |         |
| S |                                                        |         |
| d |                                                        |         |
| i |                                                        |         |
| r |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| o |                                                        |         |
| r |                                                        |         |
| y |                                                        |         |
+---+--------------------------------------------------------+---------+
| 1 | Ensure that the EXTRINFO.TXT file identifies and       | Section |
| 1 | describes the function of each file in the EXTRAS      | 1       |
| . | directory.                                             | 9.3.3.3 |
| 1 |                                                        |         |
+---+--------------------------------------------------------+---------+
| P |                                                        |         |
| a |                                                        |         |
| r |                                                        |         |
| t |                                                        |         |
| X |                                                        |         |
| I |                                                        |         |
| I |                                                        |         |
| : |                                                        |         |
| I |                                                        |         |
| n |                                                        |         |
| s |                                                        |         |
| p |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| f |                                                        |         |
| i |                                                        |         |
| l |                                                        |         |
| e |                                                        |         |
| s |                                                        |         |
| i |                                                        |         |
| n |                                                        |         |
| t |                                                        |         |
| h |                                                        |         |
| e |                                                        |         |
| D |                                                        |         |
| A |                                                        |         |
| T |                                                        |         |
| A |                                                        |         |
| d |                                                        |         |
| i |                                                        |         |
| r |                                                        |         |
| e |                                                        |         |
| c |                                                        |         |
| t |                                                        |         |
| o |                                                        |         |
| r |                                                        |         |
| y |                                                        |         |
+---+--------------------------------------------------------+---------+
| 1 | Ensure that the "specific object definition" defined   | Section |
| 2 | to describe the data products is identical across the  | 13      |
| . | data set.                                              |         |
| 1 |                                                        |         |
+---+--------------------------------------------------------+---------+
| 1 | Ensure that the "data product identification elements" | Section |
| 2 | (i.e., data product keywords) used within a data       | 5.3.4   |
| . | product label meet the minimum set required by the PDS |         |
| 2 | Standards.                                             |         |
+---+--------------------------------------------------------+---------+

### 

##### Detailed Checklist - Inspection

The following describes each step of the "inspection / examination"
checklist in more detail:

##### Read the Top Level files

Read the AAREADME.TXT, VOLDESC.CAT, ERRATA.TXT for a general
understanding of the volume. Check that the descriptions are written
clearly. If done correctly, these files provide a good overview of the
volume and will form the basis for much of the "manual" validation on
the remaining files in the archive volume.

Both the AAREADME.TXT and VOLDESC.CAT files are required. The ERRATA.TXT
file is optional.

##### 3.1.1 AAREADME.TXT

1.  The INTRODUCTION should describe the data product processing level
    (RAW, REDUCED, etc).

-   Ensure the CODMAC number in the dataset_id corresponds with the
    above description.

2.  The INTRODUCTION should describe the type of data product (EDR,
    REDR, SPECTRAL, etc).

-   Ensure that the dataset_id and dataset_name reference the specific
    type(s) and ensure the Primary Data Object is appropriate for the
    type of data (e.g., SPECTRAL data should use the SPECTRAL object and
    not the TABLE object).

3.  The INTRODUCTION should include a list of TARGET(s).

-   Ensure each TARGET is reflected in the MISSION.CAT and the
    DATASET.CAT.

4.  The INTRODUCTION should provide a thorough description of the unique
    aspects of the dataset.

-   Ensure that this dataset is unique amongst the other datasets
    (within the Mission and the other datasets in the catalog).

5.  The INTRODUCTION section should provide a description of the period
    over which the data was acquired.

-   Ensure the time period is accurately reflected in the INDEX.TAB and
    the use of START_TIME and END_TIME in data labels.

6.  Ensure that the directory tree drawn in AAREADME.TXT matches the
    actual volume.

7.  There should be a thorough description of the Volume structure and
    naming conventions (formation rules) used for naming files in the
    DATA, BROWSE, and GEOMetry, and CALIBration (sub)directories.

> Section 19 of the Standards describes the acceptable types of volume
> organization. Each type requires a certain directory structure. You
> should determine which type of organization is used by the current
> volume, and then verify that the required directories and files are
> present.

8.  If the data has been calibrated, there should be a comprehensive and
    easily understood description of how the data was calibrated.

-   Ensure the CODMAC number reflects the level (or absence) of
    calibration.

-   The INTRODUCTION should include a brief description of the
    calibration algorithm(s) and how the user would use the files to
    calibrate the data.

9.  The ERRATA section should provide a complete description of all
    anomalies associated with the (single) archive volume being
    validated.

-   This information may be supplemented / duplicated in the ERRATA.TXT
    which will have descriptions of all anomalies associated with all
    volumes in the volume set.

10. The DISK FORMAT section should describe whether the archive volume
    is ISO_LEVEL_1 or ISO_LEVEL_2 compliant.

-   The filenames and directory names should comply with this statement.

11. The ACKNOWLEDGEMENTS section should acknowledge the various teams /
    persons and their level of involvement / participation (e.g., the
    members of the peer-review committee).

12. The RELATED PDS PRODUCTS section should list any other PDS products
    (future or current) that are related.

13. The COGNIZANT PERSONNEL section should list contact information for
    the person most directly responsible for construction and release of
    the data products / volume. Additionally, contact information should
    be provided for others who contributed / participated in the
    preparation of the data or volume.

##### 3.1.2 VOLDESC.CAT

1.  VOLUME_SERIES_NAME - the keyword-value remains static for every
    volume produced within the mission / campaign.

-   Ensure all products being produced by the mission are using the same
    keyword-value. The VOLUME_SERIES_NAME typically includes the
    target(s) that are under investigation. Check the list of standard
    values to assure compatibility.

2.  VOLUME_SET_NAME - volume sets are considered to be a single
    orderable set (i.e., a single volume within the set is not useful
    without the other volumes in the set).

-   Check the list of standard values to assure compatibility.

3.  VOLUME_SET_ID -- identifies a volume or a set of volumes (e.g.,
    "USA_NASA_PDS_VG_23xx" reserves 100 IDs for a contiguous production
    run of archive volumes).

-   Check the list of standard values to assure compatibility and the
    uniqueness of the ID.

-   Ensure the VOLUME_SET_ID uses "PDS" (and not "JPL") as the
    institution for all NASA funded missions.

-   For non-NASA funded missions, ensure the VOLUME_SET_ID uses a
    standardized acronym such as "ESA" (e.g., EU_ESA_DSCI_GEM_0001).

4.  VOLUMES -- the number of archive volumes to be produced.

-   UNK or NULL is not an acceptable keyword-value for an archive
    volume.

5.  MEDIUM_TYPE - identifies the physical storage medium for an archive
    volume. The appropriate set of values in include: CD-ROM, CD-WO,
    DVD-R, DVD-ROM.

-   Check the list of standard values to assure compatibility.

-   This set of standard values is static.

6.  VOLUME_FORMAT -- identifies the logical format used in writing the
    physical volume (e.g., ISO-9660, ISO-9660_LEVEL1, ISO-9660_LEVEL2,
    UDF_ISO-9660_BRIDGE.

-   Check the list of standard values to assure compatibility.

-   This set of standard values is static.

7.  VOLUME_ID - provides a unique identifier for a data volume. (e.g.,
    VG_2307)

-   Check the list of standard values to assure compatibility and the
    uniqueness of the ID.

-   The keyword has a set of standard values that are of type
    "IDENTIFIER"

8.  VOLUME_VERSION_ID - identifies the version of an archive volume.

-   All original volumes should use have a keyword-value of \'Version
    1\'.

9.  VOLUME_NAME - contains the unique name of an archive volume (e.g.,
    \"VOLUME 2307: RECORDER A 23:01:40 to 23:13:20 \").

-   Ensure the keyword-value describes the contents of the volume in
    terms that a user can understand and find useful in locating the
    data of interest.

-   Ensure the keyword-value is related to and more specific than the
    VOLUME_SET_NAME.

##### 3.1.3 ERRATA.TXT

1.  Ensure that the items described within this file closely match those
    described in the ERRATA section of the AAREADME.TXT.

2.  Ensure that the complete set of errors, anomalies, waivers,
    non-compliant properties / practices (i.e., any and all deviations
    from PDS Standards) are thoroughly documented.

##### 3.1.4 EXTRANEOUS Files

1.  HTML based navigation should be discouraged where the files are
    co-located with the science data (i.e., disk clutter). The use of an
    AUTORUN.INF to automatically launch html-navigation is not permitted
    (i.e., including the AUTORUN.INF file in the ROOT directory is not
    allowed). The preferred method, for incorporating HTML based
    navigation into an archive volume, is to include the HTML files in
    the EXTRAS directory.

2.  Ensure there are no hidden or system files.

##### 3.2 Inspect the files in the CATALOG directory

Read the DATASET.CAT, INST.CAT, INSTHOST.CAT, and MISSION.CAT for a
general understanding of the mission, spacecraft, instrument, and type
of science data under investigation. Check that the descriptions are
written clearly. If done correctly, these files will form the basis for
much of the "manual" validation on the remaining files in the archive
volume.

1.  This is an REQUIRED directory.

2.  Ensure that the content and structure within each catalog file
    adheres to PDS standards.

3.  Ensure each catalog file will pass the Referential Integrity check.

4.  Check the catalog files, against those in that have been ingested,
    to determine if they are new or have been modified. Do not rely on
    the LABEL_REVISION_NOTE as the sole indicator of changes having been
    made.

5.  Ensure that the level of documentation within the catalog files is
    appropriate to the ARCHIVE_STATUS (i.e., it is entirely appropriate
    for skeleton-like content to be submitted for an ARCHIVE_STATUS =
    "IN QUEUE"). As the mission progresses, and while the data products
    are being released for distribution, the catalog files are augmented
    with more and more content to the point where they merit a
    peer-review - ARCHIVE_STATUS = "PRE PEER REVIEW". The full
    complement of catalog files must have passed peer-review prior to
    when the data products that they describe are ready for archive --
    ARCHIVE_STATUS = "ARCHIVED".

6.  Ensure that the ARCHIVE_STATUS is appropriate with respect to
    whether the data is in the distribution phase (ARCHIVE_STATUS = "IN
    QUEUE") or the preservation phase (ARCHIVE_STATUS = "ARCHIVED")

##### 3.2.1 MISSION.CAT

1.  Ensure that the MISSION_ALIAS_NAME value is the official designation
    given to the mission during design. The keyword accepts multiple
    values:

> MISSION_ALIAS_NAME = { "VRM", "SP-18" }

2.  Ensure values for MISSION_START_DATE and MISSION_STOP_DATE
    represents the dates when the Mission started and stoped.

-   UNK or NULL is not an acceptable keyword-value for an archive
    volume.

3.  Ensure that all of the TARGET(s) are listed in the MISSION_TARGET
    object. Multiple targets may be listed as either:

> OBJECT = MISSION_TARGET
>
> TARGET_NAME = \"MARS\"
>
> END_OBJECT = MISSION_TARGET
>
> OBJECT = MISSION_TARGET
>
> TARGET_NAME = \"PHOBOS\"
>
> END_OBJECT = MISSION_TARGET

OR

> OBJECT = MISSION_TARGET
>
> TARGET_NAME = { \"MARS\", \"PHOBOS\" }
>
> END_OBJECT = MISSION_TARGET

4.  Ensure the keyword-values associated with MISSION_START_DATE and
    MISSION_STOP_DATE are inclusive of the values stated in the
    AAREADME.TXT and the values listed in the INDEX.TAB file.

5.  Ensure the Mission Phase Names and descriptions are well organized.
    There may be MISSION_PHASE_NAME and MISSION_PHASE_DESC keywords
    present in the data-labels. These keyword-values should correspond
    with the Mission Phase Name headings in the MISSION.CAT:

> CRUISE
>
> \-\-\-\-\--
>
> The Cruise Phase extended from injection into the Earth-Mars
>
> trajectory until 10 days before Mars orbit insertion. During
>
> the Inner Cruise sub-phase, MGS aimed its solar panels toward
>
> the Sun and communicated through its low-gain antenna; during
>
> the Outer Cruise sub-phase, the high-gain antenna could be
>
> used while the solar panels generated acceptable levels of
>
> power. The transition occurred on 1997-01-09.
>
> Mission Phase Start Time : 1996-11-07
>
> Mission Phase Stop Time : 1997-09-02

6.  Ensure the Mission Phase Start Time and Stop Time keyword-values are
    inclusive of the values stated in the MISSION_START_DATE and
    MISSION_STOP_DATE values.

##### DATASET.CAT

1.  Ensure that the DATA_SET_ID adheres to the rigorous set of
    formulation rules stipulated in the Standards Reference, including
    the version_number.

2.  Ensure the each element in the DATA_SET_ID is reflected in the
    DATA_SET_NAME, including the version_number.

3.  Ensure DATA_OBJECT_TYPE reflects the type of primary object used in
    the data labels. If the data is described by more than one type of
    data object, the keyword-value should reflect the principal data
    object. The use of set or series notation is not permitted (e.g.,
    DATA_OBJECT_TYPE = { TABLE, SERIES } is not compliant).

4.  Ensure the keyword-values associated with START_TIME and STOP_TIME
    are inclusive of the values stated in the AAREADME.TXT, the
    keyword-values associated with MISSION_START_DATE and
    MISSION_STOP_DATE in the MISSION.CAT, and the values listed in the
    INDEX.TAB file.

5.  Ensure that the CONFIDENCE_LEVEL_NOTE section describes, in
    sufficient detail, all the nuances associated with the reliability,
    accuracy, and (un)certainty of the data.

-   UNK or NULL is not an acceptable keyword-value for an archive
    volume.

6.  Ensure the keyword-values associated with DATA_SET_TARGET are a
    proper subset of the values listed in the MISSION_TARGET object(s).

##### 3.3 Inspect the files in the DOCUMENT directory

1.  This is an OPTIONAL directory.

2.  Ensure that the LABEL for each DOCUMENT uses the appropriate Object
    and Object parameters:

-   TEXT Objects are used for stand-alone documents with a narrow focus
    (e.g., AAREADME.TXT, DOCINFO.TXT)

-   DOCUMENT Objects are used principally for documents in the DOCUMENT
    directory where there are multiple instances of the document (e.g.,
    MISSION.DOC, MISSION.HTM).

```{=html}
<!-- -->
```
-   Object (e.g., ASCII_DOCUMENT, HTML_DOCUMENT, etc)

-   Interchange format (e.g., ASCII or BINARY)

-   Document format (e.g., TEXT, HTML, JPG, etc)

3.  Ensure that each DOCUMENT has the correct file extension for the
    type of Object used in the DOCUMENT label (e.g., OBJECT =
    JPG_DOCUMENT would use a file extension of ".JPG").

4.  If the DOCUMENT is described by HTML, ensure the document adheres to
    Version 3.2 of the HTML language standard.

5.  Ensure that non-ASCII documents are readable (i.e., whenever
    feasible, review the PDF, MS-WORD, and other non-ASCII documents in
    the DOCUMENT directory. Make sure the text is readable and the
    illustrations legible. This is especially important for legacy
    documents that were scanned into digital form.

6.  Check spelling in text files (i.e., ideally, you should check the
    spelling in all files that contain descriptive text. At very least,
    key files such as AAREADME.TXT, VOLDESC.CAT, ERRATA.TXT, and the
    CATALOG files should be checked. If time allows, also look at the
    xxxxINFO.TXT files and key files in the DOCUMENT directory).

##### 3.4 Inspect the files in the INDEX directory

1.  This is an REQUIRED directory.

2.  Ensure that the INDXINFO.TXT file identifies and describes the
    function of each file in the INDEX directory.

3.  Ensure that the following required COLUMN objects exist in the
    INDEX_TABLE object in the INDEX.LBL file:

-   FILE_SPECIFICATION_NAME, or PATH_NAME and FILE_NAME (i.e., either a
    single column indicating the complete path to the data files; or two
    columns which when combined form the path to the data files).

-   PRODUCT_ID - if the PRODUCT_ID and the FILE_NAME values are
    identical or if the PRODUCT_ID and the FILE_SPECIFICATION_NAME
    values are identical, then this COLUMN is not required (as it would
    be a duplicate set of information).

-   VOLUME_ID -- if the value is identical across all data in the
    INDEX.TAB, then this COLUMN is not required. However, if it is not
    represented as a COLUMN of data, then the VOLUME_ID must be present
    in the LABEL as a keyword and keyword-value pair (i.e., If the
    VOLUME_ID value for each product listed in the INDEX.TAB varies,
    then values must be listed as a COLUMN. If the VOLUME_ID is static
    across all products listed in the INDEX.TAB, then the single value
    may exist as either a COLUMN or as a keyword and keyword-value
    pair).

-   DATA_SET_ID -- if the value is identical across all data in the
    INDEX.TAB, then this COLUMN is not required. However, if it is not
    represented as a COLUMN of data, then the DATA_SET_ID must be
    present in the LABEL as a keyword and keyword-value pair (i.e., If
    the DATA_SET_ID value for each product listed in the INDEX.TAB
    varies, then values must be listed as a COLUMN. If the DATA_SET_ID
    is static across all products listed in the INDEX.TAB, then the
    single value may exist as either a COLUMN or as a keyword and
    keyword-value pair).

-   PRODUCT_CREATION_TIME - if the value is identical across all data in
    the INDEX.TAB, then this COLUMN is not required. However, if it is
    not represented as a COLUMN of data, then the PRODUCT_CREATION_TIME
    must be present in the LABEL as a keyword and keyword-value pair
    (i.e., If the PRODUCT_CREATION_TIME value for each product listed in
    the INDEX.TAB varies, then values must be listed as a COLUMN. If the
    PRODUCT_CREATION_TIME is static across all products listed in the
    INDEX.TAB, then the single value may exist as either a COLUMN or as
    a keyword and keyword-value pair).

-   LOGICAL_VOLUME_PATH_NAME -- this COLUMN is only required for archive
    volumes that conform to the LOGICAL volume construct (see Section
    19.1 for more information). This COLUMN must be used in conjunction
    with the PATH_NAME and FILE_NAME columns (i.e., not used in
    conjunction with the FILE_SPECIFICATION_NAME column).

> If the value is identical across all data in the INDEX.TAB, then this
> COLUMN is not required. However, if it is not represented as a COLUMN
> of data, then the LOGICAL_VOLUME_PATH_NAME must be present in the
> LABEL as a keyword and keyword-value pair (i.e., If the
> LOGICAL_VOLUME_PATH_NAME value for each product listed in the
> INDEX.TAB varies, then values must be listed as a COLUMN. If the
> LOGICAL_VOLUME_PATH_NAME is static across all products listed in the
> INDEX.TAB, then the single value may exist as either a COLUMN or as a
> keyword and keyword-value pair).

4.  Ensure that at a minimum all data-labels are present in the
    INDEX.TAB. (i.e., all files having an extension of LBL if the data
    products are labeled with detached labels). If the data products are
    labeled with attached labels, then the data product files are
    listed). The data files include those files in the DATA directory
    and subdirectories, and any calibration files in the CALIB
    directory. If the INDEX.TAB contains files other than data-labels,
    this should be discouraged. The principal function of the INDEX.TAB
    is to provide a machine readable method for locating data of
    interest (i.e., not any files of interest). The user always has the
    option of including additional INDEX files which can contain
    additional sets of "indexed" information.

5.  Ensure that the INDEX_TYPE keyword-value is SINGLE for INDEX.TAB and
    CUMULATIVE for CUMINDEX.TAB. The two allowable values for INDEX_TYPE
    are SINGLE, meaning that every row in the index table describes a
    file on the current volume; or CUMULATIVE, meaning that every row in
    the index table describes a file residing on the current volume or a
    previous volume in the volume set.

6.  Ensure that the START_BYTE and BYTES keyword values are set such
    that the column values do not include the double quotes (i.e., for
    columns having DATA_TYPE = CHAR, the column values when displayed in
    NASAVIEW or TBTOOL are displayed without double quotes.

7.  Ensure that if there are column values of type TIME or DATE or
    numeric, and if those values are double quoted in INDEX.TAB, that
    the DATA_TYPE = CHAR. This practice should be discouraged. All
    column values should have a DATA_TYPE representative of their
    respective data type.

##### 3.5 Inspect the files in the LABEL directory

1.  This is an OPTIONAL directory.

2.  The files in this directory are referred to as Format files. These
    files are functionally "label-snippets" which allow a data preparer
    to "write once -- use many times". By embedding a STRUCTURE pointer
    in a label, the data preparer can reference the "label-snippet" in
    data files that span multiple directories.

3.  Ensure that the Format files have an extension of .FMT.

4.  Ensure that the Format files are referenced via a STRUCTURE pointer.

5.  Ensure that the Format files only exist in the LABEL directory (or
    are co-located with the data file).

##### 3.6 Inspect the files in the BROWSE directory

1.  This is an OPTIONAL directory.

2.  Ensure that the files in this directory are used solely as "reduced
    resolution versions" of the data products (i.e., the precision of
    the science quality image has been reprocessed to "thumbnail" size
    and stored in a low-resolution (lossy) format; such as, GIF, TIFF,
    or PNG).

> Note that PNG is the preferred format in which to store browse images.
> GIF is a proprietary format and requires a "release" to distribute GIF
> images. The TIFF format is not supported by most html-browsers.

3.  As these files are used as a vehicle for quickly locating the
    science data of interest, ensure that there is a "link" between the
    browse image and the data product it describes.

##### 3.7 Inspect the files in the CALIB directory

1.  This is an OPTIONAL directory.

2.  Ensure that the algorithm(s) provided by the data producer(s)
    adequately and accurately explain the method(s) by which the user
    community would produce calibrated products. Sample products should
    be included to serve as a baseline (against which products produced
    by users can be compared).

3.  The PDS relies on feedback from the science users to ascertain the
    usability of the calibration files.

##### 3.8 Inspect the files in the GEOM directory

1.  This is an OPTIONAL directory.

2.  Ensure each SPICE Kernel is described using the SPICE_KERNEL object
    and in accordance with the attributes described in Section A.26.

3.  At a minimum, three sets of information should be described:

-   Spacecraft ephemeris (spk).

-   Target body ephemeris (pck).

-   Spacecraft orientation, including the orientation of the platform to
    which the instrument is attached (ck).

4.  The above information is provided in the form of SPICE kernels which
    are specific to the spacecraft (instrument host), the instrument,
    and the targets under observation (see the SPICE tutorial for the
    definition of each type SPICE kernel).

> Summary of Kernel types:
>
> ik \-- instrument orientation to spacecraft.
>
> ck \-- attitude information for spacecraft and instrument platforms.
>
> ek \-- EROS shape model kernels.
>
> fk \-- frames kernel directory.
>
> lsk \-- information to convert between UTC times and any other time
> systems.
>
> pck \-- Models used for rotations of solar system bodies and shapes
> (constants and matrices of planets and satellites).
>
> sclk \-- Spacecraft clock kernel modeled against the time system TDT
> (Terrestrial Dynamical Time).
>
> spk \-- NAIF ephemeris system - planet and spacecraft positions.
>
> plt \-- SPICE plate model.
>
> grav \-- gravity data.

##### 3.9 Inspect the files in the GAZETTER directory

1.  This is an OPTIONAL directory.

2.  Ensure the GAZETTER directory contains detailed information about
    the named features on a target body associated with the data set(s)
    on the volume. "Named features" are those that the International
    Astronomical Union (IAU) has named and approved. Note that, unlike
    large-scale planetary features viewed from orbit, some of the
    features may not have been approved by the International
    Astronomical Union (IAU) (i.e., the names may be transitory and are
    subject to change).

3.  The IMG-USGS node is the only data producer of GAZETTER_TABLEs.

4.  The kinds of features described include a gazetteer of the names
    informally assigned to many of the rocks and other local small
    features visible near the landing site.

5.  Ensure each feature is described as a row in the GAZETTER_TABLE
    object, in accordance with the attributes described in Section A.16

##### 3.10 Inspect the files in the SOFTWARE directory

1.  This is an OPTIONAL directory.

2.  Ensure the algorithm(s), that the user community would use to
    process or access the data, are adequately and accurately
    documented. The documentation should reside in the DOC subdirectory.

> Notes:

a)  The most critical set of information is the set of documentation
    describing the algorithms that the user community would use to
    process or access the data products on the archive volume.

b)  The software libraries, utilities, and application programs are
    secondary to the algorithms in terms of long term usability (i.e.,
    the language in which the application is coded will (eventually)
    evolve making the code unusable; but, a well documented algorithm
    should be useful irrespective of how the language matures).

```{=html}
<!-- -->
```
3.  Ensure that if software is included, the software is organized and
    resides in directories appropriate to the hardware platform /
    operating system under which it operates.

4.  Ensure, if multiple versions of the software are supplied to support
    different platforms and operating systems, the semi-rigid naming
    schema for the directories in which the software resides is adhered
    to.

5.  Ensure that software included on the volume compiles and executes as
    described in the /SOFTWARE/SOFTINFO.TXT file. If source code is
    included on the volume, try to build and execute it on the specified
    platforms. Likewise, if binary code is included, try to run it on
    the specified platforms.

6.  Ensure PUBLIC domain software is accompanied by appropriate software
    releases / disclaimers.

##### 3.11 Inspect the files in the EXTRAS directory

1.  This is an OPTIONAL directory.

2.  The EXTRAS directory is the designated area for housing additional
    elements provided by data preparers outside the scope of any PDS
    (levied) requirements.

##### 3.12 Inspect the files in the DATA directory

1.  The DATA directory is OPTIONAL. But, if this directory does not
    exist at the root, there should be a whole slew of other
    functionally equivalent directories.

2.  Ensure the data products are being produced in accordance with
    Tables 3.1 and 3.2 of the Standards Reference.

3.  Ensure that the "specific data object definition" does not vary
    across the data set (i.e., the structure of the individual data
    product labels does not vary by the addition or removal of keyword
    elements and/or objects, or by their order).

4.  Ensure the primary data type, as defined by the DATA_OBJECT_TYPE
    keyword, reflects the primary data type of the data products being
    produced. For example, if DATA_OBJECT_TYPE = TABLE, then the main
    data files should use TABLE objects, and have a file extension of
    either '.TAB' or '.DAT'. In the case of images, DATA_TYPE = IMAGE
    implies that the data files are using the IMAGE object and have
    extensions of '.IMG', '.IBG', or '.IMQ'.

5.  For data products using Standard Data Types having varying numbers
    of bytes, ensure the BYTES keyword-value accurately reflects the
    precision of the data product (e.g., 1-byte, 2-byte, 4-byte, 8-byte,
    16-byte, 20-byte integer, real, complex, etc). Variations to the
    number of bytes noted in the Standards is not permitted (i.e., For
    DATA_TYPE = IBM_REAL, the data can only be produced as BYTES = 4 or
    BYTES = 8. For DATA_TYPE = LSB_INTEGER, the data can only be
    produced as BYTES = 1, 2, or 4).

##### Validation Checklist -- Tool Suite

The following steps are taken to "use the PDS Tool suite" to inspect /
examine a PDS archive volume to ensure PDS compliance. Whenever
possible, the steps are linked to an appropriate section of the [PDS
Standards Reference]{.underline}. Some steps fall under the category of
general quality assurance, and these are labeled \"General QA\" in the
list:

  ---------------- --------------------------------------------------------- ---------------
  **Validation                                                               
  Checklist\                                                                 
  Step-by-Step**                                                             

  **Step**         **Action**                                                **Standards**

  Part I: ISO                                                                
  Checker Tool                                                               
  (ISOCHECK)                                                                 

  1.1              Execute ISOCHECK which will analyze either a CD or DVD    General QA
                   and report any deviations from the ISO standards.         

  1.2              Analyze the ISOCHECK report                               General QA

  Part II: Label                                                             
  Verifier Tool                                                              
  (LVTOOL)                                                                   

  2.1              Execute LVTOOL which will analyze each file in the        General QA
                   archive volume and generate a report of potentially       
                   non-compliant items. LVTOOL checks the syntax and         
                   semantics of PDS labels by comparing them to the Toolbox  
                   Data Dictionary.                                          

  2.2              Execute ListErr which will analyze the LVTOOL report file General QA
                   and generate a report listing a "filtered output"         

  2.3              Analyze the "filtered output" report                      General QA

  Part III:                                                                  
  Keyword Value                                                              
  Tool (KWVTOOL)                                                             

  3.1              Execute KWVTOOL which will analyze each label file and    General QA
                   generate a report listing the unique set of keywords and  
                   keyword-values pairs.                                     

  3.2              Analyze the KWVTOOL report                                General QA

  Part IV: NewLine                                                           
  Tool (NEWLINE)                                                             

  4.1              Execute NEWLINE which will analyze each data label and    General QA
                   the associated data file(s) to generate a report listing  
                   the principle data product attributes.                    

  4.2              Analyze the NEWLINE report                                General QA

  Part V: AllRefs                                                            
  Tools (ALLREFS)                                                            

  5.1              Execute ALLREFS which will analyze the REFS.CAT file and  General QA
                   the associated CATALOG files to generate a report listing 
                   the references cited within the archive volume.           

  5..2             Analyze the ALLREFS report                                General QA

  Part VI: Index                                                             
  Tool (INDEX)                                                               

  6.1              Execute INDEX which will analyze the INDEX and CUMINDEX   General QA
                   files and generate a report of potentially non-compliant  
                   items.                                                    

  6.2              Analyze the INDEX report                                  General QA

  Part VII: Table                                                            
  Browser Tool                                                               
  (TBTOOL)                                                                   

  6.1              Execute TBTOOL against the INDEX file(s) in the INDEX     General QA
                   directory to ensure the columns of data are appropriate   
                   with respect to the label descriptors. TBTOOL             
                   interactively examines PDS labeled ASCII and BINARY data  
                   described by TABLE, SERIES, and SPECTRUM objects, in      
                   order to verify the columns of data.                      

  6.2              Execute TBTOOL against the data products which are        General QA
                   described using the either the TABLE, SERIES, or SPECTRUM 
                   object to ensure the columns of data are appropriate with 
                   respect to the label descriptors.                         

  Part VIII:                                                                 
  NasaView Tool                                                              

  6.1              Execute NasaView against the data products which are      General QA
                   described using any of the approved PDS objects (except   
                   the SPREADSHEET object) to ensure the data are            
                   appropriate with respect to the label descriptors.        
  ---------------- --------------------------------------------------------- ---------------

##### Detailed Checklist -- Tool Suite

The following describes each step of the "Tool Suite" checklist in more
detail:

##### 5.1 Verify ISO 9660 Compliance

The following criteria can be verified by analyzing the report generated
by ISCHECK.

1.  All PDS volumes must be ISO 9660 level-1 or level-2 compliant. These
    standards require the following:

-   All directory and filenames must be uppercase.

-   For ISO 9660 level-1 compliance, filenames must adhere to the
    \"8.3\" standard: a one to eight-character base name, followed by a
    dot (.), followed by a one to three-character extension. Directory
    names are not greater than eight characters.

-   For ISO 9660 level-2 compliance, filenames can be up to thirty
    characters in length. The filenames consist of a base name, followed
    by a dot (.), followed by an extension of one or more characters.

-   Directories should not be nested more than eight levels deep.

##### 5.2 Verify Syntax and Semantics of PDS Labels

The following criteria can be verified by analyzing the report generated
from either LVTOOL or the "filtered report" generated from LISTERR.

2.  Every file on the volume should either contain a label itself or be
    pointed to by a label. It is important to ensure that there are no
    zero-length files. These often indicate an error writing the data to
    physical media (e.g., CD or DVD).

3.  A formation rule is a method for constructing a value, usually a
    name or ID string. Adhering to formation rules keeps names and IDs
    consistent. In PDS, keywords that use formation rules include
    DATA_SET_ID, VOLUME_SET_ID, VOLUME_ID, and DATA_OBJECT_TYPE.

4.  All labels on the volume must be validated against the current Data
    Dictionary. All pointers in a label must be checked to ensure that
    they point to a valid object.

5.  In order for labels to be valid, all their keywords and standard
    values must be in the data dictionary. When a keyword or standard
    value is missing from the data dictionary, it could mean any one of
    the following:

-   The keyword or standard value should be ingested

-   The keyword or standard value needs to be approved

-   There has been a syntax or typographical error

##### 5.3 Verify Keyword and Keyword-value pairs

The following criteria can be verified by analyzing the report generated
by KWVTOOL.

1.  The first section of the report lists the set of keywords that are
    not present in the Data Dictionary. There are a couple of
    possibilities as to why the keyword is listed as not being found in
    the Data Dictionary:

    -   The value is not actually a keyword. If KWVTOOL is not properly
        configured to "ignore" certain types of files (e.g., HTML, C,
        etc), KWVTOOL will wrongly identify lines in the file as ODL
        statements. An example of this would be setting a local variable
        in HelloWorld.C or HelloWorld.HTM:

> myVariable = 1

"myVariable" will be identified as the keyword, "1" will be identified
as the keyword-value, and the keyword / keyword-value pair will be
reported as a non-existent keyword in the Data Dictionary. If you adjust
the file-extension parameters to "ignore" files having extensions of
".C" and ".HTM", this will alleviate the problem.

-   The value is a keyword. But, the keyword does not exist in the Data
    Dictionary. When a keyword or standard value is missing from the
    data dictionary, it could mean any one of the following:

```{=html}
<!-- -->
```
-   The keyword or standard value should be ingested

-   The keyword or standard value needs to be approved

-   There has been a syntax or typographical error

2.  The second section of the report lists the unique keyword /
    keyword-value pairs. The unique list of keyword / keyword-value
    pairs is a quick method for locating potentially anomalous pairings.
    This list should be examined very closely for possible discrepancies
    / anomalies. For example:

-   If the archive volume consists of a single data set, then the report
    should only list a single instance of:

> DATA_SET_ID CO-J-CIRS-2/3/4-TSDR-V1.0
>
> If the above keyword is listed more than once, then a file (or files)
> exists on the archive volume having the anomalous keyword /
> keyword-value pair. To locate the file(s) re-execute KWVTOOL in
> "verbose" mode.

3.  Check keyword/value pairs for consistency. Examine the \"KEYWORD =
    VALUE\" pairs on the volume to find those that are technically legal
    but \"make no sense.\" For example, INSTRUMENT_HOST_ID = VG2 is a
    legal value, but is out of place on a Voyager I volume.

4.  There are other cases where a value must be checked against
    \"outside information.\" For example: VOLUMES = 8 seems valid. But
    if you are checking the ninth volume in a set, it is incorrect. In
    fact, experience has shown it worth checking the VOLUMES keyword,
    since errors occasionally occur, just like the one in the example.

##### 5.4 Verify Record Structure of PDS Labels

The following criteria can be verified by analyzing the report generated
by NEWLINE.

1.  Ensure that the file characteristics and record structure of each
    file on the archive volume are appropriate and are in compliance
    with Table 5.1 of the Standards Reference.

2.  Based on the type of file, which is most easily discerned from the
    file extension, the set of file characteristics and record structure
    are to be validated.

    a.  Example #1 - the AAREADME.TXT file is expected to:

-   Not have any illegal characters

-   Have line-terminators (for each line in the file)

-   Have a RECORD_TYPE of STREAM (but may be FIXED_LENGTH)

-   Have an INTERCHANGE_FORMAT of ASCII

-   Have FILE_RECORDS, RECORD_BYTES, and ROW_BYTES of N/A

-   Have a MIN line length of 1 character and MAX line length of 80

-   The TOTAL_BYTES column represents the number of bytes in the file.

    a.  Example #2 - the CATALOG files (.CAT) are expected to:

-   Not have any illegal characters

-   Have line-terminators (for each line in the file)

-   Have a RECORD_TYPE of STREAM (but may be FIXED_LENGTH)

-   Have an INTERCHANGE_FORMAT of ASCII

-   Have FILE_RECORDS, RECORD_BYTES, and ROW_BYTES of N/A

-   Have a MIN line length of 1 character and MAX line length of 75

-   The TOTAL_BYTES column represents the number of bytes in the file.

    a.  Example #3 - the data product label files (.LBL) are expected
        to:

-   Not have any illegal characters

-   Have line-terminators (for each line in the file)

-   Have a RECORD_TYPE of STREAM or FIXED_LENGTH)

-   Have an INTERCHANGE_FORMAT of ASCII or BINARY

-   Have FILE_RECORDS, RECORD_BYTES, and ROW_BYTES that are appropriate
    to the type of OBJECT being used to describe the data product

-   Have a MIN line length of 1 character and MAX line length not
    exceeding RECORD_BYTES

-   The TOTAL_BYTES column represents the number of bytes in the file.

-   The FILE_PTR_LENGTH column is the arithmetic product of RECORD_BYTES
    \* ROW_BYTES and represents the predicted number of bytes in the
    data product file that the data product label describes (i.e.,
    HSK01010100.LBL describes the data product file, HSK01010100.DAT,
    and because the data product file is FIXED_LENGTH, the label
    attributes can be used to predict the size (in bytes) of the data
    product file -- 31356). The FILE_PTR_LENGTH value of the LBL file
    should match the TOTAL_BYTES value of the DAT file.

    a.  Example #4 - the data product files (.DAT) are expected to:

-   May have illegal characters (if the file is BINARY)

-   May or may not have line-terminators (for each line in the file)

-   Have a RECORD_TYPE , INTERCHANGE_FORMAT , FILE_RECORDS,
    RECORD_BYTES, and ROW_BYTES of N/A

-   Have a MIN line length of 1 character and MAX line length not
    exceeding RECORD_BYTES

-   The TOTAL_BYTES column represents the number of bytes in the file.
    This value should match the FILE_PTR_LENGTH value for the associated
    LBL file.

    a.  Example #5 - INDEX.LBL is expected to:

-   Not have illegal characters

-   Have line-terminators (for each line in the file)

-   Have a RECORD_TYPE of FIXED_LENGTH

-   Have an INTERCHANGE_FORMAT of ASCII

-   Have FILE_RECORDS, RECORD_BYTES, and ROW_BYTES that are appropriate
    to the type of OBJECT being used to describe the data product

-   Have a MIN line length of 1 character and MAX line length not
    exceeding RECORD_BYTES

-   The FILE_PTR_LENGTH column is the arithmetic product of RECORD_BYTES
    \* ROW_BYTES and represents the predicted number of bytes in the
    data product file that the data product label describes (i.e.,
    HSK01010100.LBL describes the data product file, HSK01010100.DAT,
    and because the data product file is FIXED_LENGTH, the label
    attributes can be used to predict the size (in bytes) of the data
    product file -- 31356). The FILE_PTR_LENGTH value of the LBL file
    should match the TOTAL_BYTES value of the DAT file.

    a.  Example #6 - INDEX.TAB is expected to:

-   Not have illegal characters

-   Have line-terminators (for each line in the file)

-   Have a RECORD_TYPE , INTERCHANGE_FORMAT , FILE_RECORDS,
    RECORD_BYTES, and ROW_BYTES of N/A

-   Have a MIN line length and MAX line length equal to RECORD_BYTES.

-   The TOTAL_BYTES column represents the number of bytes in the file.
    This value should match the FILE_PTR_LENGTH value for the associated
    LBL file.

Ill. Line RECORD INTER. FILE REC. ROW TOTAL FILE PTR

File Name Char Term TYPE FORMAT RECORDS BYTES BYTES Min Max BYTES LENGTH

\-\-\-\-\-\-\-\-\-\-\-- \-\-\-- \-\-\-- \-\-\-\-\-\-\-- \-\-\-\-\-\-\--
\-\-\-\-\-\-- \-\-\-\-- \-\-\-\-\-\-\-\-- \-\-\-\-- \-\-\-\--
\-\-\-\-\-\-\-\-\-- \-\-\-\-\-\-\-\-\--

g:\\

AAREADME.TXT STREAM - - 80 - 2 80 8049 -

ERRATA.LBL STREAM ASCII - - - 5 79 769 -

ERRATA.TXT - - - - 2 74 263 -

VOLDESC.CAT - - - - 2 78 2339 -

G:\\CATALOG\\

CATINFO.LBL STREAM ASCII - - - 5 79 831 -

CATINFO.TXT - - - - 2 70 467 -

DATASET.CAT STREAM - - - - 2 80 30582 -

INST.CAT STREAM - - - - 2 78 8831 -

INSTHOST.CAT STREAM - - - - 2 79 40217 -

MISSION.CAT STREAM - - - - 2 80 52237 -

PERSON.CAT STREAM - - - - 2 76 6015 -

PROJREF.CAT STREAM - - - - 2 64 785 -

TARGET.CAT STREAM - - - - 2 77 6954 -

G:\\DATA\\HSK_DATA\\

DATASET.LBL STREAM ASCII - - - 5 55 471 -

DATASET.TXT - - - - 5 5 5 -

HSK01010100.DAT Bad Bad - - - - 7 112 31356 -

HSK01010100.LBL FIXED BINARY 78 402 402 5 76 1784 31356

HSK01010104.DAT Bad Bad - - - - 1 118 88440 -

HSK01010104.LBL FIXED BINARY 220 402 402 5 76 1786 88440

HSK01010108.DAT Bad Bad - - - - 1 127 90852 -

HSK01010108.LBL FIXED BINARY 226 402 402 5 76 1786 90852

G:\\INDEX\\

INDEX.LBL FIXED ASCII 99 171 171 2 80 7152 16929

INDEX.TAB - - - - 171 171 16929 -

INDXINFO.LBL STREAM ASCII - - - 5 75 491 -

INDXINFO.TXT - - - - 2 72 373 -

3.  For attached labels, ensure that RECORD_TYPE, RECORD_BYTES, and
    related keywords are correct. These tests are performed to ensure
    consistency between the label and the data. There are several errors
    that commonly occur when attached labels are used with RECORD_TYPE =
    FIXED. Check the following:

-   Every line in the label should be padded to the length specified in
    RECORD_BYTES (unless LABEL_RECORDS = 1, where the length of the
    whole label should be RECORD_BYTES)

-   The pointer should point correctly to the first data record

-   The number of FILE_RECORDS should be correctly given

For .TXT and .CAT files, also note:

-   The RECORD_TYPE must be \"STREAM\" or \"FIXED\"

-   If RECORD_TYPE = STREAM, then the RECORD_BYTES keyword is not
    allowed

-   INTERCHANGE_FORMAT = ASCII

-   For .TXT files, RECORD_BYTES must be less than or equal to 80

-   For .CAT files, the line lengths in the description fields must be
    less than or equal to 72

4.  Ensure all filenames have the proper extension, according to the
    data in the file. File extensions should be used to identify the
    data type of a file. Section 10.2.3 lists the required file
    extensions for key PDS data types. Section 10.2.4 lists the file
    extensions reserved for other types of data. A filename has the
    proper extension when:

-   A file with a required or reserved extension contains the type of
    data assigned to that extension.

-   A file with an assigned type of data has the appropriate extension.

> For example, a file with an .LBL extension should be a PDS label file.
> Conversely, a PDS label file should not have the extension .LAB.

5.  Ensure that the following is true for all labels, .TXT, and .ASC
    files:

-   Line terminators are pairs.

-   There are no embedded .

-   There are no embedded characters, other than line terminators with
    an ASCII value less than 32 (decimal).

-   There are no embedded characters with an ASCII value greater than
    127 (decimal).

-   The line lengths are not greater than 80 characters, including line
    terminators.

> With the exception of the line length limit, all these tests should
> also hold true for HTML files.

##### 5.5 Verify Reference Citations

The following criteria can be verified by analyzing the report generated
by REFFIND.

1.  Ensure that the references and accompanying citations are correct
    and comply with the American Geophysical Union (AGU) reference
    citation formats (see B.31.5).

2.  The reference file (REF.CAT) should be properly formed. It should
    contain citations made in other CATALOG/\*.CAT files and be
    consistent with the reference database.

Check for the following consistency errors:

-   Duplicate citations in REF.CAT

-   Citations referenced in a CATALOG/.CAT file that do not appear in
    REF.CAT

-   Citations in REF.CAT that do not appear in the reference database

-   Citations in REF.CAT that appear differently in the reference
    database.

> Note: Sometimes, when citations in REF.CAT differ from those in the
> database, it is the database citation that needs to be changed.

3.  Also check the syntax of REFKEYID within text descriptions. It
    should be uppercase, enclosed in square brackets, and take the form:

-   \[Primary Author(ETAL)Citation Date\] - e.g., \[SMITHETAL1993\]

-   Primary Author should match the first name in the citation

-   Citation Date should match the date in the citation

> In the case of multiple citations, the REFKEYIDs should be separated
> by a semicolon, not a comma, e.g., \[SMITHETAL1993; SMITHETAL1994\].

##### 5.6 Verify the Structure of the INDEX files

The following criteria can be verified by analyzing the report generated
by INDEXCHECK.

1.  Validate the structure of INDEX.TAB and ensure that each entry
    points to a data file:

2.  Check the syntax of INDEX.TAB:

-   Values must comma separated (CSV)

-   If the values are not date/time, enclose the entire column in
    quotes, including whitespace (e.g., \"325.098 \")

-   If the values are date/time, do not enclose them in double quotes
    (e.g., 1980-11-12T23:59:59Z)

-   Values should be checked for proper syntax, according to their data
    type

3.  Check that every entry in INDEX.TAB points to the label for a data
    file. Note: the entries point to the label, not to the data
    directly.

4.  Ensure that every data file is pointed to in INDEX.TAB and that
    every data file must have an attached or detached label. Make sure
    that every one of these labels is pointed to by an entry in the
    INDEX.TAB.

5.  Ensure that CUMINDEX.TAB contains all the INDEX.TAB files for the
    volume set.

6.  Check whether a CUMINDEX.TAB is required. If VOLUMES = 1, it is not
    required. Otherwise, it must be present.

7.  As a volume set is assembled, make sure each CUMINDEX.TAB file
    contains the INDEX.TAB files for all previously published volume.

##### 5.7 Verify Data Products

1.  NasaView and TBTOOL provide a visual interface for browsing TABLE,
    SPECTRUM, and SERIES Objects. Both applications parse the data
    product label and report any syntax errors. Then the applications
    display the individual table(s), columns, bit_columns, and items. It
    is worth checking the columns against the data type prescribed in
    the label. Examine as large a sampling of tables as feasible.

2.  Use NASAView to view IMAGE files. Check the quality of the image. It
    is also worth checking the image against its description in the
    label. Examine as large a sampling of images as feasible.

##### 5.7 Test Referential Integrity

1.  Test referential integrity with a test ingestion.

2.  PDS volumes provide information, mostly through the .CAT files, for
    the high-level PDS catalog. The catalog is a relational database,
    and it is important that it maintain referential integrity (RI) as
    new information is added.

3.  Currently, there is only one way to make certain of this. That is:
    ingest the new information on a copy of the database, then run the
    test for referential integrity.

4.  Once the referential integrity test has succeeded, information from
    the volume can be ingested into the real catalog. At this point, the
    volume should be consistent with PDS standards and the PDS data
    model, and should be accepted as valid.

###### appendix a Online Resources 

The following resources may be of interest during the validation process
and are available electronically at the designated URL:

###### appendix B PDS Data SET Types 

The following are the standard set of PDS approved Data Set Types. Other
types exist and are in use in PDS approved archive products, but this
list represents the "core" types of data sets and are included here as a
guide for future data producers.

**AEDR** (Aggregated Experiment Data Record)

**Calib**

\- May be either Calibration Data or Calibrated Data.

\- Calibration data are those that are collected with the science
instrument or

in conjunction with a specific set of measurements, and which are used
to

translate raw data numbers generated by the instrument into meaningful

units.

\- Calibrated data are science data generated by the instrument which
have been

corrected so that the values are expressed in or are proportional to
some

physical unit such as radiance. These data have not been resampled, so
the

edited data can still be reconstructed.

**DDR** (Derived Data Record)

\- a product that has been derived from EDRs or RDRs by averaging,
binning,

sampling, etc.

**DIM** (Digital Imaging Model)

**DSDP** (Decompressed Standard Data Product)

**DTM** (Digital Terrain Model)

**EDR** (Experiment Data Record)

\- Space science data that may have been corrected for

telemetry errors and split or decommutated into a data set for a given

instrument. Data may be tagged with time and location of acquisition.

This data usually corresponds to CODMAC level 2 or NASA level 0
products.

**GTDR** (Global Sinusoidal Topography Data Record)

**GREDR** (Global Radar Reflectivity Data Record)

**GSDR** (Global Surface Slope Data Record)

**GEDR** (Global Emissivity Data Record)

MDR (Master Data Record)

\- All telemetry ordered by time. Occasionally MDRs are broken into
video

MDRs, science MDRs, and engineering MDRs.

**MIDR** (Mosaicked Image Data Record)

\- created by combining multiple EDRs; may also be geometrically and/or

radiometrically corrected.

**ODR** (Original Data Record)

\- Telemetry data with space science data embedded. ODRs are often
recycled

during processing and not retained.

\- For Magellan, the ODR came out of the telemetry system. Magellan
retained

the ODRs.

**PEDR** (Precision Experiment Data Record)

**QUBE**

\- a multi-dimensional array of sample values

**RDR** (Reduced Data Record)

\- a product that has been converted from the raw data counts returned
from

the spacecraft into units like degrees or meters.

**REDR** (Raw Experiment Data Record)

**SAMPLER**

\- Sample data from a data set (as opposed to sub-sampled data).

**SEDR** (Supplementary Experiment Data Record)

\- Non-science data associated with a data set; it is useful in
interpreting

data and consists of instrument gains, offset, pointing information for

scan platforms, etc.

**SHGADR**

**TDR**

**TUBE**

###### appendix c isocheck parameters 

The following are useful for configuring ISOCHECK to analyze the archive
volume for ISO-9660 compliance.

1.  The ISOCHECK tool is one of the checks performed by the Validation
    Tool Suite and can only be executed if Perl has been installed.

![](media/image3.jpeg){width="3.4375in" height="6.041666666666667in"}

2.  Sample report from the ISOCHECK tool:

###### 

> \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--
>
> CD-ROM ISO Checker (BETA) version 0.2.2
>
> Last Modified : 03.08.2000
>
> Author(s) : Akos Czikmantory \[JoeyCz@jpl.nasa.gov\]
>
> \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--
>
> Displaying Volume Results:
>
> ==========================
>
> Volume Identifier : VG_2802
>
> WARNING !! Volume Identifier is more than 9 characters.
>
> ID : CD001
>
> Number of Volume Descriptor Records:
>
> ====================================
>
> Primary 1
>
> Boot 0
>
> Supplementary 0
>
> Partition 0
>
> Terminator 1
>
> Number of Files and Directories on disk :
>
> ==\> Files : 775
>
> ==\> Dirs : 55
>
> Total Errors counted :
>
> ==\> 2
>
> Frequency of Error :
>
> ==\> Filename is more than 8 characters : 0
>
> ==\> Extention is more than 3 characters : 0
>
> ==\> Filename contains Illegal character(s) : 0
>
> ==\> Extention contains Illegal character(s) : 0
>
> ==\> Missing Extention : 2
>
> ==\> Directory Depth is more than 8 levels : 0
>
> CD-ROM Validation Results :
>
> ==========================
>
> SORTING BY ERRORS
>
> =================
>
> Filename is more than 8 characters
>
> ==================================
>
> None.
>
> Extention is more than 3 characters
>
> ===================================
>
> None.
>
> Filename has an illegal character
>
> =================================
>
> None.
>
> Extention has an illegal character
>
> ==================================
>
> None.
>
> Missing extention
>
> =================
>
> ==\> l:\\SOFTWARE\\OAL\\IDL\\IDLMAKE
>
> NAME : IDLMAKE
>
> PATH : \\SOFTWARE\\OAL\\IDL
>
> ==\> l:\\SOFTWARE\\OAL\\SOURCE\\MAKEFILE
>
> NAME : MAKEFILE
>
> PATH : \\SOFTWARE\\OAL\\SOURCE
>
> Directory depth is more than 8 levels
>
> =====================================
>
> None.
>
> Errors detected on disk.
>
> ==\> ISO Check FAILED !

###### appendix d LVTOOL parameters 

The following are useful for configuring LVTOOL to analyze only the
files of interest.

3.  LVTOOL command file

LVTOOL -a

-v

-e

-nw

-d c:\\util\\pdsdd.idx

-f f:\\\*.\*

-r lvtool.out

-ivf c:\\util\\lvtool.in

-ivd c:\\util\\lvtool-dir.txt

> Note: For LVTOOL to produce a report suitable for LISTER, the \"-nw\"
> parameter must be used.

4.  File Extension settings

The "ivf" parameter is used to reference a file -- the contents of which
is a CSV list of file extensions that LVTOOL should "ignore" (i.e., any
file having an extension in the list will not be processed by LVTOOL).
There a number of file types that are inappropriate for LVTOOL to
process because the particular type of file does not contain a PDS label
(e.g., EXE or PDF, PS) or contains text that is structured similarly to
a label file but is not ODL (e.g., HTML, C, TEX). The following is the
recommended set of file extensions that should not be processed:

**EXE,HTM,TIFF,PNG,EPS,PS,JPG,GIF,PDF,STY,PDS,INF,INV,HLP,DLL,FOR,C,H,MAK,HED,DES,ABS,INI,ZIP,DSP,TEX**

Note: Each value must be delimited by comma and the set of values must
reside within a single line (i.e., only a single CRLF should be present
at the end of the line).

Note: The above set of values should be "tailored to fit" the archive
products under investigation (e.g., if detached labels are used, then
adding TAB, DAT, IMG, and/or IMQ to the list of file extensions would
increase the speed with which LVTOOL will process the volume and also
greatly reduce the size of the report file).

5.  Directory settings

The "ivd" parameter is used to reference a file -- the contents of which
is a CSV list of directories that LVTOOL should "ignore" (i.e., any
directory in the list will not be processed by LVTOOL). There are a
number of directories (that may exist on an archive volume) that are
inappropriate for LVTOOL to process because the directory does not
contain any PDS label files). The following is the recommended set of
directories that should not be processed:

G:\\SOFTWARE

G:\\EXTRAS

Note: The above file must list each directory on a single line and each
entry must designate the full directory path (including the root
directory). Each entry must be terminated with a CRLF.

###### appendix e kwvTOOL parameters 

The following are useful for configuring KWVTOOL to analyze only the
files of interest.

1.  KWVTOOL command file

KWVTOOL -a

-v

-d c:\\util\\pdsdd.idx

-f f:\\\*.\*

-r kwvtool.out

-ivf c:\\util\\lvtool.in

-ivd c:\\util\\kwvtool-dir.txt

-lef c:\\util\\kwv-skipped.out

-sf c:\\util\\kwvtool-kwords.txt

2.  File Extension settings

The "ivf" parameter is used to reference a file -- the contents of which
is a CSV list of file extensions that LVTOOL should "ignore" (i.e., any
file having an extension in the list will not be processed by LVTOOL).
There a number of file types that are inappropriate for LVTOOL to
process because the particular type of file does not contain a PDS label
(e.g., EXE or PDF, PS) or contains text that is structured similarly to
a label file but is not ODL (e.g., HTML, C, TEX). The following is the
recommended set of file extensions that should not be processed:

**EXE,HTM,TIFF,PNG,EPS,PS,JPG,GIF,PDF,STY,PDS,INF,INV,HLP,DLL,FOR,C,H,MAK,HED,DES,ABS,INI,ZIP,DSP,TEX**

Note: Each value must be delimited by comma and the set of values must
reside within a single line (i.e., only a single CRLF should be present
at the end of the line).

Note: The above set of values should be "tailored to fit" the archive
products under investigation (e.g., if detached labels are used, then
adding TAB, DAT, IMG, and/or IMQ to the list of file extensions would
increase the speed with which LVTOOL will process the volume and also
greatly reduce the size of the report file).

3.  Directory settings

The "ivd" parameter is used to reference a file -- the contents of which
is a CSV list of directories that LVTOOL should "ignore" (i.e., any
directory in the list will not be processed by LVTOOL). There are a
number of directories (that may exist on an archive volume) that are
inappropriate for LVTOOL to process because the directory does not
contain any PDS label files). The following is the recommended set of
directories that should not be processed:

> G:\\SOFTWARE
>
> G:\\EXTRAS

Note: The above file must list each directory on a single line and each
entry must designate the full directory path (including the root
directory). Each entry must be terminated with a CRLF.

4.  Keyword settings

The "sf" parameter is used to reference a file -- the contents of which
is a CSV list of keywords that KWVTOOL should "ignore" (i.e., any
keyword in the list will not be processed by KWVTOOL). There are a
number of keywords that are inappropriate for KWVTOOL to process because
the associated keyword-values are not of interest (i.e., keyword-values
of type DESCRIPTION or TEXT are probably not of interest because the
descriptions will almost certainly not be unique within the archive
volume). The following is the recommended set of file extensions that
should not be processed:

**FILE_NAME,DESCRIPTION,FILE_RECORDS,NAME,NOTE,PUBLICATION_DATE,RECORD_BYTES,ROWS,ROW_BYTES,BYTES,FORMAT,START_BYTE**

Note: Each value must be delimited by comma and the set of values must
reside within a single line (i.e., only a single CRLF should be present
at the end of the line).

Note: The above set of values should be "tailored to fit" the archive
products under investigation (e.g., if a keyword / keyword-value pair is
being used to impart a critical set of information, then adjust the
value appropriately).

###### appendix f NEWLINE parameters 

The following are useful for configuring NEWLINE to analyze only the
files of interest.

1.  NEWLINE command file

NEWLINE -nd

-if f:\\\*.\*

-of newline.out

-bd f:

The above configuration will execute NEWLINE against all files on the
archive volume and will generate a non-verbose report.

Ill. Line RECORD INTER. FILE REC. ROW TOTAL FILE PTR

File Name Char Term TYPE FORMAT RECORDS BYTES BYTES Min Max BYTES LENGTH

\-\-\-\-\-\-\-\-\-\-\-- \-\-\-- \-\-\-- \-\-\-\-\-\-\-- \-\-\-\-\-\-\--
\-\-\-\-\-\-- \-\-\-\-- \-\-\-\-\-\-\-\-- \-\-\-\-- \-\-\-\--
\-\-\-\-\-\-\-\-\-- \-\-\-\-\-\-\-\-\--

g:\\

AAREADME.TXT STREAM - - 80 - 2 80 8049 -

ERRATA.LBL STREAM ASCII - - - 5 79 769 -

ERRATA.TXT - - - - 2 74 263 -

VOLDESC.CAT - - - - 2 78 2339 -

G:\\CATALOG\\

CATINFO.LBL STREAM ASCII - - - 5 79 831 -

CATINFO.TXT - - - - 2 70 467 -

DATASET.CAT STREAM - - - - 2 80 30582 -

INST.CAT STREAM - - - - 2 78 8831 -

INSTHOST.CAT STREAM - - - - 2 79 40217 -

MISSION.CAT STREAM - - - - 2 80 52237 -

PERSON.CAT STREAM - - - - 2 76 6015 -

PROJREF.CAT STREAM - - - - 2 64 785 -

TARGET.CAT STREAM - - - - 2 77 6954 -

G:\\DATA\\HSK_DATA\\

DATASET.LBL STREAM ASCII - - - 5 55 471 -

DATASET.TXT - - - - 5 5 5 -

HSK01010100.DAT Bad Bad - - - - 7 112 31356 -

HSK01010100.LBL FIXED BINARY 78 402 402 5 76 1784 31356

HSK01010104.DAT Bad Bad - - - - 1 118 88440 -

HSK01010104.LBL FIXED BINARY 220 402 402 5 76 1786 88440

HSK01010108.DAT Bad Bad - - - - 1 127 90852 -

HSK01010108.LBL FIXED BINARY 226 402 402 5 76 1786 90852

G:\\INDEX\\

INDEX.LBL FIXED ASCII 99 171 171 2 80 7152 16929

INDEX.TAB - - - - 171 171 16929 -

INDXINFO.LBL STREAM ASCII - - - 5 75 491 -

INDXINFO.TXT - - - - 2 72 373 -

A more detailed version of the report can be generated by removing the
"-nd" parameter. Note that this option is useful for locating the exact
placement of illegal characters in a single file.

===== PDS - Line Counter Program =====

Thu Mar 11 09:31:47 2004

Input file: g:\\catalog\\CRSDS.CAT

================================================

\(1\) Checking for illegal characters, such as TABs

\-\--\>\> No illegal characters were detected

\(2\) Checking record type and line lengths

================================================

\(3\) Checking Max and Min line lengths

\-\--\>\> Line length (minimum): 80 (inclusive of line terminator(s))

\-\--\>\> Line length (maximum): 80 (inclusive of line terminator(s))

================================================

\(5\) Checking line terminator sequences (\<CR\>\<LF\>)

\-\--\>\> Lines detected: 324 (in input file)

\-\--\>\> of which: 0 (were not terminated with \<CR\>\<LF\>

)

================================================

\(6\) Checking Object structure(s)

\[ 1, 80, 25920\] PDS_VERSION_ID = PDS3

\[ 2, 80, 25920\] LABEL_REVISION_NOTE = \"J. MAFI (PPI),

\[ 3, 80, 25920\] RECORD_TYPE = STREAM

\[ 4, 80, 25920\]

\[ 5, 80, 25920\] +-OBJECT = DATA_SET

\[ 6, 80, 25920\] \| DATA_SET_ID = \"VG2-J-CRS-5-SUM

\[ 7, 80, 25920\] \|

\[ 8, 80, 25920\] \|+- OBJECT = DATA_SET_INFORMA

\[ 9, 80, 25920\] \|\| DATA_SET_NAME = \"VG2 JUP CRS DER

\[ 10, 80, 25920\] \|\|PROTON/ION/ELECTRON FLUX BROWSE V1.0\"

\[ 11, 80, 25920\] \|\| DATA_SET_COLLECTION_MEMBER_FLG = N

\[ 12, 80, 25920\] \|\| START_TIME = 1979-07-03T00:00

\[ 13, 80, 25920\] \|\| STOP_TIME = 1979-08-03T23:45

\[ 14, 80, 25920\] \|\| DATA_SET_RELEASE_DATE = 1997-12-01

\[ 15, 80, 25920\] \|\| PRODUCER_FULL_NAME = \"NATIONAL SPACE

\[ 16, 80, 25920\] \|\| DETAILED_CATALOG_FLAG = N

\[ 17, 80, 25920\] \|\| DATA_OBJECT_TYPE = \"TIME SERIES\"

\[ 18, 80, 25920\] \|\| DATA_SET_DESC = \"

\[ 19, 80, 25920\] \|\|

\[ 20, 80, 25920\] \|\| Data Set Overview

\[ 21, 80, 25920\] \|\| =================

\[ 22, 80, 25920\] \|\| Instrument P.I. : Rochus E. Vogt

\[ 23, 80, 25920\] \|\| Data Supplier : National Space Science

\[ 24, 80, 25920\] \|\| Data sampling rate : variable (1 hr for FPHA

\[ 25, 80, 25920\] \|\| for all others)

\[ 26, 80, 25920\] \|\| Data Set Start Time : 1979-07-03T00:00:00.000

\[ 27, 80, 25920\] \|\| Data Set Stop Time : 1979-08-03T23:45:00.000

\[ 28, 80, 25920\] \|\|

\[ 29, 80, 25920\] \|\| (The following description has been excerpted f

\[ 30, 80, 25920\] \|\| \[NSSDCCRS1979\])

\[ 31, 80, 25920\] \|\|

\[ 32, 80, 25920\] \|\| As its name implies, the Cosmic Ray Subsystem (

\[ 33, 80, 25920\] \|\| designed for cosmic ray studies \[STONEETAL1977B

###### appendix g reffind parameters 

The following are useful for configuring REFFIND to analyze only the
files of interest.

1.  REFFIND is a WINDOWS based application and can only be executed on
    PCs.

![](media/image4.jpeg){width="6.40625in" height="5.354166666666667in"}

2.  Sample REFFIND report:

8/6/2003

========================================

Input FileName: E:\\AAvalidation\\Atmos-CIRS_0001\\CATALOG\\REF.CAT

REFKEYID matches 1st Author Unique within

REFERENCE_KEY_ID citation date matches the file

========================================

Input FileName: E:\\AAvalidation\\Atmos-CIRS_0001\\CATALOG\\DATASET.CAT

Is cited within Unique within

REFERENCE_KEY_ID description(s) the File

KUNDE ET AL -\> False True

========================================

Input FileName: E:\\AAvalidation\\Atmos-CIRS_0001\\CATALOG\\INST.CAT

Is cited within Unique within

REFERENCE_KEY_ID description(s) the File

KUNDE ET AL -\> False True

========================================

Input FileName: E:\\AAvalidation\\Atmos-CIRS_0001\\CATALOG\\INSTHOST.CAT

Is cited within Unique within

REFERENCE_KEY_ID description(s) the File

ASMAR&RENZETTI1993 True True

DAMARIOETAL1992 -\> False True

ONEIL1991 -\> False True

ONEIL1995 -\> False True

ONEIL1996 -\> False True

YEATESETAL1985 -\> False True

========================================

Input FileName: E:\\AAvalidation\\Atmos-CIRS_0001\\CATALOG\\MISSION.CAT

Is cited within Unique within

REFERENCE_KEY_ID description(s) the File

JPLD-5564 -\> False True

PD699-004 True True

========================================

Input FileName: E:\\AAvalidation\\Atmos-CIRS_0001\\CATALOG\\PERSON.CAT

Is cited within Unique within

REFERENCE_KEY_ID description(s) the File

========================================

Input FileName: E:\\AAvalidation\\Atmos-CIRS_0001\\CATALOG\\TARGET.CAT

Is cited within Unique within

REFERENCE_KEY_ID description(s) the File

========================================

Column 1 - REFERENCE_KEY_ID is derived from all catalog templates

(REF.CAT and the user selected \*.CAT files).

Column 2 - TRUE indicates that the REFKEYID exists in the REF.CAT file.

FALSE indicates that the REFKEYID is not in the REF.CAT file.

Column 3 - TRUE indicates that the REFKEYID exists in at least 1 of the

\*.CAT files and may or may not exist in the REF.CAT

file (see Column 2).

FALSE indicates that the REFKEYID exists in the REF.CAT file

but is not in any other file.

Column 4 - TRUE indicates that the REFKEYID exists in the AllRef.CAT

file (i.e., already exists in the catalog).

FALSE indicates that the REFKEYID is not in the AllRef.CAT

file (i.e., must be ingested into the catalog).

Column 5 - TRUE indicates that the citation in the REF.CAT file

matches the citation in the AllRefs.txt file.

FALSE indicates that the citation in the REF.CAT file

does not match that found in the AllRefs.txt file.

In Citation

REFS.CAT Is Cited In matches

REFERENCE_KEY_ID as REFKEYID as Reference AllRefs.txt AllRefs.txt

ASMAR&RENZETTI1993 -\> False True True -\> False

DAMARIOETAL1992 -\> False True True -\> False

JPLD-5564 -\> False True True -\> False

KUNDE ET AL -\> False True -\> False -

KUNDE ET AL -\> False True -\> False -

ONEIL1991 -\> False True True -\> False

ONEIL1995 -\> False True True -\> False

ONEIL1996 -\> False True True -\> False

PD699-004 -\> False True -\> False -

YEATESETAL1985 -\> False True True -\> False

========================================

The following lists the non-matching Ref.Cat and the AllRef.txt
citations.

NONE