# Documents

Supplementary or ancillary reference materials are often included with
archive products to improve their short- and long-term utility. These
documents augment the internal documentation of the product labels and
provide further assistance in understanding the data products and
accompanying materials. Typical archive documents include:

-   Flight project documents

-   Instrument papers

-   Science articles

-   Volume information

-   Software Interface Specifications (SISs)

-   Software user manuals

The PDS criteria for inclusion of a document in the archive are:

1.  Would this information be helpful to a data user?

2.  Is the material necessary?

3.  Is the documentation complete?

In general, the PDS seeks to err on the side of completeness.

Each document to be archived must be prepared and saved in a
PDS-compliant format, including a PDS label. Documents are delivered in
the DOCUMENT directory of an archive volume (see the *Volume
Organization and Naming* chapter of this document).

A flat, human-readable ASCII text version of each document must be
included on the volume, although additional versions may be included in
other supported formats at the option of the data producer. "Flat ASCII
text" means the file may contain only the standard, 7-bit printable
ASCII character set, plus the blank character and the carriage-return
and linefeed characters as record delimiters. A file is "human-readable"
if it is not encoded and if any special markup tags which may be
included do not significantly interfere with an average user's ability
to read the file. So, for example, simple HTML files and TeX/LaTeX files
with relatively little markup embedded in the text are generally
considered human-readable and may, therefore, be used to satisfy the
above ASCII text version requirement.

Note that the PDS takes the requirement for complete documentation very
seriously. Documents that are essential to the understanding of an
archive are considered as important as the data files themselves.
Furthermore, including a document in a PDS archive constitutes
publication (or re-publication) of that document. Consequently,
documents prepared for inclusion in an archive are expected to meet not
only the PDS label and format requirements, but also the structural,
grammatical and lexical requirements of a refereed journal submission.
Documents submitted for archiving which contain spelling errors, poor
grammar or illogical organization will be rejected and may ultimately
lead to the rejection of the submitted data for lack of adequate
documentation.

## PDS Objects for Documents

PDS labels of documentation files must use the TEXT, DOCUMENT, or DOCSET
object, as appropriate. The DOCUMENT object is usually used with
documentation files found in the DOCUMENT directory of an archive
volume. Files described by a DOCUMENT object may be in any of the
formats described in Section 9.2.

The TEXT object may only be used with ASCII text files containing no
markup. TEXT objects are most often used for small text files occurring
anywhere in the archive volume (for example, the AAREADME.TXT file in
the root directory or the DOCINFO.TXT file in the DOCUMENT directory).

### TEXT Objects

TEXT objects are preferred for stand-alone documents with a narrow
focus. For example, the AAREADME.TXT or DOCINFO.TXT files on the archive
volume are usually labeled using a TEXT object. Files described by a
TEXT object must:

a)  Be plain, flat ASCII files without markup tags (i.e., no HTML or TeX
    files), encoded graphics (as in PostScript files), or programmatic
    structures (i.e., no source code files or scripting commands); and

b)  Have a file extension of ".TXT"

### DOCUMENT Objects

DOCUMENT objects are preferred when several versions of the same file
are provided or when there are several component files constituting a
single version of the document - for example, when graphics are included
in separate files from the text. Any file labeled using a DOCUMENT
object must:

a)  Be in one of the PDS-approved formats listed below; and

b)  Use the appropriate object characteristics (listed below) for the
    DOCUMENT object parameters and the file extension.

DOCUMENT labels are combined detached labels, since attaching them to
the formats listed below would make the combined file unusable in its
customary environment (Microsoft *Word*, for example, cannot recognize
".DOC" files with attached PDS labels).

+-----------+---------------+--------+------------------+------------+
| *         | **Object**    | *      | **Document       | **File     |
| *Format** |               | *Inter | Format**         | E          |
|           |               | change |                  | xtension** |
|           |               | Fo     |                  |            |
|           |               | rmat** |                  |            |
+-----------+---------------+--------+------------------+------------+
| Plain     | A             | ASCII  | TEXT             | .ASC       |
| ASCII     | SCII_DOCUMENT |        |                  |            |
| Text      |               |        |                  |            |
+-----------+---------------+--------+------------------+------------+
| HTML      | HTML_DOCUMENT | ASCII  | HTML             | .HTM or    |
|           |               |        |                  | .HTML\*    |
+-----------+---------------+--------+------------------+------------+
| TeX       | TEX_DOCUMENT  | ASCII  | TEX              | .TEX       |
+-----------+---------------+--------+------------------+------------+
| LaTeX     | L             | ASCII  | LATEX            | .TEX       |
|           | ATEX_DOCUMENT |        |                  |            |
+-----------+---------------+--------+------------------+------------+
| Adobe PDF | PDF_DOCUMENT  | BINARY | ADOBE PDF        | .PDF       |
+-----------+---------------+--------+------------------+------------+
| MS Word   | WORD_DOCUMENT | BINARY | MICROSOFT WORD   | .DOC       |
+-----------+---------------+--------+------------------+------------+
| Rich Text | RTF_DOCUMENT  | BINARY | RICH TEXT        | .RTF       |
+-----------+---------------+--------+------------------+------------+
| GIF       | GIF_DOCUMENT  | BINARY | GIF              | .GIF       |
+-----------+---------------+--------+------------------+------------+
| JPG       | JPG_DOCUMENT  | BINARY | JPG              | .JPG       |
+-----------+---------------+--------+------------------+------------+
| Enc       | EPS_DOCUMENT  | BINARY | ENCAPSULATED     | .EPS       |
| apsulated |               |        |                  |            |
|           |               |        | POST­SCRIPT       |            |
| P         |               |        |                  |            |
| ostscript |               |        |                  |            |
+-----------+---------------+--------+------------------+------------+
| PNG       | PNG_DOCUMENT  | BINARY | PNG              | .PNG       |
+-----------+---------------+--------+------------------+------------+
| P         | PS_DOCUMENT   | BINARY | POSTSCRIPT       | .PS        |
| ostscript |               |        |                  |            |
+-----------+---------------+--------+------------------+------------+
| Tagged    | TIFF_DOCUMENT | BINARY | TIFF             | .TIF or    |
| Image     |               |        |                  | .TIFF\*    |
|           |               |        |                  |            |
| File      |               |        |                  |            |
| Format    |               |        |                  |            |
+-----------+---------------+--------+------------------+------------+

\* See chapter *File Specification and Naming* regarding extensions with
more than three characters.

Example: "MYDOC" is a documentation file to be included in the DOCUMENT
directory of an archive volume. Two versions will be supplied: a flat
ASCII version with the graphics in separate TIFF files; and a Microsoft
Word version with in-line graphics in a single file. In the PDS label,
"MYDOC" will be described using a DOCUMENT object for each different
file format provided. The files included in the directory will be:

1.  MYDOC.ASC required ASCII version

2.  MYDOC.DOC optional Microsoft Word version to retain all graphics

3.  MYDOC001.TIF optional scanned TIFF version of selected pages

4.  MYDOC002.TIF optional scanned TIFF version of other selected pages

5.  MYDOC.LBL PDS label defining DOCUMENT object(s) for these files

Optional versions of the document should have the same file name as the
required ASCII version but with different extensions. Optional versions
should be defined as additional DOCUMENT objects in the single PDS
label; the name of the required ASCII file should be indicated in the
text of the DESCRIPTION keyword.

### DOCSET Objects

DOCSET objects are used for document products that are to be cataloged
and associated with both the archive and the data products that they
describe. Cataloging the DOCSET object aggregates the document product
to the archive and/or data products (i.e., the document product becomes
"linked" with the Volume, Mission, Instrument Host, Instrument, and/or
Dataset) and makes the document product searchable and downloadable.
DOCSET objects are used when there are one or more component files
constituting a single document product - for example, an archivist wants
an EDR SIS to be coupled with the specific data product that it
describes. The SIS consists of multiple text and graphic files and
exists in several formats (TEXT and PDF).

Cataloged document products are labeled at three levels of description:

1.  Archive volume level (e.g., VOLDESC.CAT)

2.  Catalog level (e.g., DOCSET.CAT, DATASET.CAT)

3.  Product level (e.g., EDR_HTM.LBL)

The following examples describe files having keywords and keyword-values
that are representative of what would exist at each of the levels.

> **Archive Level\
> **\
> Directory = ROOT/VOLDESC.CAT\
> \
> OBJECT = CATALOG\
> \^DOCUMENT_CATALOG\
> \
> \
> \
> **Catalog Level\
> **\
> Directory = CATALOG/\*.CAT\
> \
> OBJECT = DOCSET\
> OBJECT = DOCUMENT_INFORMATION\
> OBJECT = DOCUMENT_ONLINE\
> \
> DOCUMENT_ID\
> DOCUMENT_NAME\
> **...**
>
> **Product Level\
> **\
> Directory = DOCUMENT/\*.LBL
>
> DOCUMENT/\*.PDF; \*.TXT; \*.HTM; **...**\
> \
> OBJECT = DOCUMENT_PRODUCT\
> OBJECT = FILE\
> OBJECT = MANIFEST_TABLE\
> \
> DOCUMENT_ID\
> DOCUMENT_PRODUCT_ID
>
> PARENT_FILE_NAME
>
> **...\
> **

Any file labeled using a DOCSET object must:

a)  Be in one of the PDS-approved DOCUMENT formats listed in Section
    9.1.2; and

b)  Use the appropriate object characteristics (listed below) for the
    DOCUMENT object parameters and the file extension.

DOCSET labels must be combined detached labels, since attaching them to
the formats listed below would make the combined file unusable in its
customary environment (Microsoft *Word*, for example, cannot recognize
".DOC" files with attached PDS labels).

#### Labeling Multi-part Document Products

There are two methods for labeling multi-part document products:

1.  Using the FILE object

2.  Using the MANIFEST table object

Both the FILE and MANIFEST objects provide a mechanism for specifying
the properties of a multi-part document product within a single label.
Either a separate FILE object can be used to specify each file that is
part of the document product; or, a single instance of the MANIFEST
table object can be used to specify the files that comprise the document
product.

The set of keywords and objects that are applicable to cataloging
document products are:

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

Document Product using FILE object

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

OBJECT = DOCUMENT_PRODUCT - Required (single instance only)

DOCUMENT_ID - Required

DOCUMENT_PRODUCT_ID - Required

DOCUMENT_VERSION_ID - Required

DOCUMENT_NAME - Optional

PUBLICATION_DATE - Optional

DOCUMENT_TOPIC_TYPE - Optional

DOCUMENT_FORMAT - Required

PARENT_FILE_NAME - Required

FILES - Required

DESCRIPTION - Required

OBJECT = FILE - Required (multiple instances allowed)

FILE_SPECIFICATION_NAME - Required

DOCUMENT_FORMAT - Required

RECORD_TYPE - Required

FILE_RECORDS - Optional (required if RECORD_TYPE \<\> STREAM)

ENCODING_TYPE - Required

MIME_TYPE - Optional

DESCRIPTION - Optional

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

Document Product using MANIFEST_TABLE object

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

\^MANIFEST_TABLE - Required

OBJECT = DOCUMENT_PRODUCT - Required (single instance only)

DOCUMENT_ID - Required

DOCUMENT_PRODUCT_ID - Required

DOCUMENT_VERSION_ID - Required

DOCUMENT_NAME - Required

PUBLICATION_DATE - Optional

DOCUMENT_TOPIC_TYPE - Optional

DOCUMENT_FORMAT - Required

PARENT_FILE_NAME - Required

FILES - Required

DESCRIPTION - Required

OBJECT = MANIFEST_TABLE - Required (multiple instances allowed)

COLUMNS - Required

ROWS - Required

ROW_BYTES - Required

OBJECT = COLUMN - Required (multiple instances allowed)

COLUMN_NUMBER - Required

NAME - Required

START_BYTE - Required

BYTES - Required

FORMAT - Required

DATA_TYPE - Required

DESCRIPTION - Required

The minimum set of columns (COLUMN_NAME) required for using the
MANIFEST_TABLE are:

\- FILE_SPECIFICATION_NAME (required)

\- DOCUMENT_FORMAT (required; must be a value in parent object)

\- RECORD_TYPE (required)

\- ENCODING_TYPE (required)

\- BYTES (required)

Optional columns (COLUMN_NAME) include:

\- CREATION_DATE (optional)

\- DESCRIPTION (optional)

\- ENCODING_TYPE (optional)

\- MIME_DATE (optional)

Note: (1) Each of the above COLUMNs represent the set of information
required when using the FILE object.

> \(2\) The MANIFEST_TABLE object may contain additional COLUMNs for any
> of the optional keywords used in the FILE object or for any valid
> keyword specified in the PDS data dictionary.
>
> \(3\) Each row in the MANIFEST_TABLE is equivalent to a single
> instance of "OBJECT=FILE".

## Document Format Details

### Flat ASCII Text

**Line Length and Delimiters** - PDS recommends plain text files have
line length restricted to 78 characters or fewer, to accommodate
printing and display on standard devices. Each line must be terminated
by the two-character carriage-return/linefeed sequence (ASCII decimal
character codes 13 and 10, respectively).

**Page Length and Breaks -** Block paragraph style is preferred, with
paragraphs being separated by at least one blank line. The form feed
character (ASCII decimal code 12) may be used to indicate page breaks,
in which case pages should contain no more than 60 lines of text. A
formfeed character should be inserted immediately after the END
statement line of an attached PDS label in these files.

### ASCII Text Containing Markup Language

**Line Length and Delimiters -** The 78-character line length
recommendation is dropped for these files. Notwithstanding, the lines
must be delimited by the carriage return/linefeed character combination.

**Page Length and Breaks -** Page breaks are controlled by the markup in
these files. Consequently, there are no specific page length
recommendations.

Note: ASCII files containing extensive markup may not pass the
"human-readable" test. For example, some automatic converters producing
HTML files that might be expected to be human-readable add so many
additional marks and notations that those files are, in fact, not
"human-readable". Consult a PDS data engineer for help in determining
whether a particular file can be considered "human-readable" for archive
purposes.

#### Hyper-Text Markup Language (HTML) Files

PDS archive products must adhere to Version 3.2 of the HTML language, a
standard generalized markup language (SGML) conforming to the ISO 8879
standard. All files are subject to validation against the HTML 3.2 SGML
Declaration and the HTML Document Type Definition.

Note: Constructs not defined in the HTML 3.2 standard (e.g., FRAME,
STYLE, SCRIPT, and FONT FACE tags) are not allowed in PDS documentation
files.

#### Location of Files

PDS strongly recommends that targets of all HTML links be present on the
archive volume. In cases where external links are provided, the link
should lead to supplementary information that is not essential to
understanding or use of the archival data.

PDS recommends that all files comprising an HTML document or series of
documents be located in a single directory. However, locating ancillary
files (e.g., images, common files) in subdirectories may be required
under certain circumstances (e.g., to avoid conflicts in file names or
to minimize replication of common files).

#### Discouraged HTML 3.2 Capabilities

Although the APPLET tag is advertised to be supported by all Java
enabled browsers, not all applets execute on all browsers on all
platforms. Further, some browsers require that the user explicitly
enable use of Java applets before the applet will execute. Consequently,
applets are permitted in PDS document files only when the information
they convey is not essential to understanding or use of the archival
data.

Use of the TAB character is permitted but strongly discouraged because
of variations in implementation among browsers and resulting
misalignments within documents.

Use of animated GIF image files is discouraged.

### Non-ASCII Formats

Wherever possible the specific encoding and version level information
should be included in the label for all non-ASCII documents. The
ENCODING_TYPE keyword is used to indicate the base encoding type (e.g.,
PostScript, GIF, etc.), while the specific version information should be
included in the text of the DESCRIPTION keyword. See the PSDD for a list
of standard encoding types. Additional types may be added at the
discretion of the PDS data engineer.

### Validation

Documentation files prepared to accompany a data set or data set
collection must be validated. Validation consists of checking to ensure
that the files can be copied or transmitted electronically, and can be
read or printed by their target text-processing program. Documentation
files should be spell-checked prior to being submitted to PDS for
validation.

## Examples

### TEXT Object - Attached label (Plain ASCII Text)

The following label could be attached to a plain ASCII text file
describing the content and format of Mars Pathfinder Imager Experiment
Data Records.

> PDS_VERSION_ID = PDS3
>
> RECORD_TYPE = STREAM
>
> OBJECT = TEXT
>
> NOTE = \"Mars Pathfinder Imager Experiment Data Record SIS\"
>
> PUBLICATION_DATE = 1998-06-30
>
> END_OBJECT = TEXT
>
> END

### DOCUMENT Object - Detached Label (Two Document Versions)

If the data producer chose to provide the same document in both plain
ASCII text and as a Microsoft Word document, the detached label would
have the name EDRSIS.LBL and would be as follows:

> PDS_VERSION_ID = PDS3
>
> RECORD_TYPE = UNDEFINED
>
> \^ASCII_DOCUMENT = \"EDRSIS.ASC\"
>
> \^WORD_DOCUMENT = \"EDRSIS.DOC\"
>
> OBJECT = ASCII_DOCUMENT
>
> DOCUMENT_NAME = \"Mars Pathfinder Imager Experiment Data Record\"
>
> PUBLICATION_DATE = 1998-06-30
>
> DOCUMENT_TOPIC_TYPE = \"DATA PRODUCT SIS\"
>
> INTERCHANGE_FORMAT = ASCII
>
> DOCUMENT_FORMAT = TEXT
>
> DESCRIPTION = \"This document contains a textual description of the
> VICAR and PDS formatted Mars Pathfinder IMP Experiment Data Records.
> This is the ASCII text version of the document required by PDS.\"
>
> END_OBJECT = ASCII_DOCUMENT
>
> OBJECT = WORD_DOCUMENT
>
> DOCUMENT_NAME = \"Mars Pathfinder Imager Experiment Data Record\"
>
> PUBLICATION_DATE = 1998-06-30
>
> DOCUMENT_TOPIC_TYPE = \"DATA PRODUCT SIS\"
>
> INTERCHANGE_FORMAT = BINARY
>
> DOCUMENT_FORMAT = \"MICROSOFT WORD\"
>
> DESCRIPTION = \"This document contains a textual description of the
> VICAR and PDS formatted Mars Pathfinder IMP Experiment Data Records.
> The document was created using Microsoft Word 6.0.1 for the
>
> Macintosh.\"
>
> END_OBJECT = WORD_DOCUMENT
>
> END

### DOCUMENT Object - Detached Label (Documents Plus Graphics)

The following label (EDRSIS.LBL) illustrates the use of an HTML document
as the required ASCII document. The same document is also included as a
PDF file, and four PNG images are included separately.

> PDS_VERSION_ID = PDS3
>
> RECORD_TYPE = UNDEFINED
>
> \^HTML_DOCUMENT = \"EDRSIS.HTM\"
>
> \^PDF_DOCUMENT = \"EDRSIS.PDF\"
>
> \^PNG_DOCUMENT = (\"FIG1.PNG\",\"FIG2.PNG\",\"TAB1.PNG\",\"TAB2.PNG\")
>
> OBJECT = HTML_DOCUMENT
>
> DOCUMENT_NAME = \"Mars Pathfinder Imager Experiment Data Record\"
>
> PUBLICATION_DATE = 1998-06-30
>
> DOCUMENT_TOPIC_TYPE = \"DATA PRODUCT SIS\"
>
> INTERCHANGE_FORMAT = ASCII
>
> DOCUMENT_FORMAT = HTML
>
> DESCRIPTION = \"This document contains a description
>
> of the VICAR and PDS formatted Mars Pathfinder IMP Experiment Data
> Records. This is an HTML version of the document.\"
>
> END_OBJECT = HTML_DOCUMENT
>
> OBJECT = PDF_DOCUMENT
>
> DOCUMENT_NAME = \"Mars Pathfinder Imager Experiment Data Record\"
>
> PUBLICATION_DATE = 1998-06-30
>
> DOCUMENT_TOPIC_TYPE = \"DATA PRODUCT SIS\"
>
> ENCODING_TYPE = \"PDS-ADOBE-1.1\"
>
> INTERCHANGE_FORMAT = BINARY
>
> DOCUMENT_FORMAT = \"ADOBE PDF\"
>
> DESCRIPTION = \"This document contains a description
>
> of the VICAR and PDS formatted Mars Pathfinder IMP Experiment Data
> Records. This is a PDF version of the document.\"
>
> END_OBJECT = PDF_DOCUMENT
>
> OBJECT = PNG_DOCUMENT
>
> DOCUMENT_NAME = \"Mars Pathfinder Imager Experiment Data Record\"
>
> PUBLICATION_DATE = 1998-06-30
>
> DOCUMENT_TOPIC_TYPE = \"DATA PRODUCT SIS\"
>
> FILES = 4
>
> ENCODING_TYPE = \"PNG1.0\"
>
> INTERCHANGE_FORMAT = BINARY
>
> DOCUMENT_FORMAT = PNG
>
> DESCRIPTION = \"This document is a PNG representation of two figures
> and two tables from the Mars
>
> Pathfinder IMP Experiment Data Record SIS.\"
>
> END_OBJECT = PNG_DOCUMENT
>
> END

### DOCSET Object - Detached Label (using FILE object)

The following sets of labels illustrate the method whereby a document
product is cataloged using the FILE object. The example illustrates four
document products to be cataloged:

1.  AAREADME -- a document that describes the archive volume

2.  ERRATA -- a document that describes the archive volume

3.  GBATMSN -- a set of documents that describe a mission

4.  GEDRSIS -- a set of files that describe a dataset

#### Archive Volume Level

The following example illustrates the method whereby a document product
is cataloged at the Archive Level using the FILE object. The
DOCUMENT_CATALOG object is used to construct a list of the DOCUMENTs
that are to be aggregated to the archive product. The
VOLUME_REFERENCE_INFO object is used to construct a list of those
DOCUMENTs that are descriptive of the archive volume, as opposed to the
mission which uses MISSION_REFERENCE_INFORMATION, or instrument which
uses INSTRUMENT_REFERENCE_INFO, etc. The DOCUMENT_ID keyword is the
unique identifier for the archived document.

Note: The method whereby a document product is cataloged at the Archive
Level is the same for using the FILE object or the MANIFEST_TABLE
object.

**[(a) ROOT/VOLDESC.CAT]{.underline}**

PDS_VERSION_ID = PDS3

RECORD_TYPE = STREAM

OBJECT = VOLUME

VOLUME_SERIES_NAME = \"GROUND BASED ATMOSPHERIC OBSERVATIONS\"

VOLUME_SET_NAME = \"GROUND BASED ATMOSPHERIC OBSERVATIONS\"

VOLUME_SET_ID = \"USA_NASA_PDS_GBAT_0001\"

VOLUMES = 1

VOLUME_NAME = \"Spectrophotometry of the Jovian

Planets and Titan at 300- to 1000-nm\"

VOLUME_ID = \"GBAT_0001\"

VOLUME_FORMAT = \"ISO-9660\"

VOLUME_VERSION_ID = \"VERSION 2\"

MEDIUM_TYPE = \"CD-WO\"

DATA_SET_ID = \"ESO-J/S/N/U-SPECTROPHOTOMETER-4-V2.0\"

PUBLICATION_DATE = 1998-12-17

DESCRIPTION = \"

This volume contains archival data produced from ground based

observations of the Jovian planets and Titan tabulating the methane
absorption coefficient and the full disk albedos of the Jovian planets
and Titan at wavelengths from 300 nm to 1000 nm. \"

OBJECT = CATALOG

\^MISSION_CATALOG = \"MISSION.CAT\"

\^INSTRUMENT_HOST_CATALOG = \"ESOHOST.CAT\"

\^INSTRUMENT_CATALOG = \"ESOSPINS.CAT\"

\^DATA_SET_CATALOG = \"DATASET.CAT\"

\^DOCUMENT_CATALOG = {\"GBATMSN.CAT\",

\"GEDRSIS.CAT\",

\"AAREADME.CAT\",

\"ERRATA.CAT\"}

END_OBJECT = CATALOG

OBJECT = VOLUME_REFERENCE_INFO

DOCUMENT_ID = { \"GBAT_0001-AAREADME_DOC-V1.0\",

\"GBAT_0001-ERRATA_DOC-V1.0\" }

END_OBJECT = VOLUME_REFERENCE_INFO

END_OBJECT = VOLUME

END

#### Catalog Level 

The following examples illustrate the method whereby document products
are cataloged at the Catalog Level using the FILE object. The DOCSET
object is used to describe the attributes associated with the archive
document. The DOCSET object and its associated keywords and subobjects
are more fully described in Appendix A.

Note: The method whereby a document product is cataloged at the Catalog
Level is the same for using the FILE object or the MANIFEST_TABLE
object.

**[(a) CATALOG/GBATMSN.CAT]{.underline}**

PDS_VERSION_ID = PDS3

OBJECT = DOCSET

DOCUMENT_ID = \"GBAT_0001-MISSION_DOC-V1.0\"

REFERENCE_KEY_ID = \"N/A\"

OBJECT = DOCUMENT_INFORMATION

DOCUMENT_NAME = \"GBAT MISSION DOCUMENT\"

DOCUMENT_VERSION_ID = \"V1.0\"

DOCUMENT_TOPIC_TYPE = \"MISSION DISCRIPTION\"

AUTHOR_FULL_NAME = \"A.J. SMITH\"

PUBLICATION_DATE = 2000-02-12

COPYRIGHT_HOLDER = \"CALIFORNIA INSTITUTE OF TECHNOLOGY\"

NODE_ID = \"IMAGING-JPL\"

DOCUMENT_DESC = \"

Document Overview

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

This document is a description of the GBAT mission.

Document Purpose

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

Provides a full set of mission information.

Source Format

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

The original document was written in Microsoft Word97.

Available Formats

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

Text and HTML.\"

END_OBJECT = DOCUMENT_INFORMATION

OBJECT = DOCUMENT_ONLINE

ON_LINE_IDENTIFICATION =
\"HTTP://WWW.IMG.JPL.NASA.GOV/PDS/MISSION.HTML\"

ON_LINE_NAME = \"GBATMSN\"

NODE_ID = \"IMAGING-JPL\"

PROTOCOL_TYPE = URL

DISTRIBUTION_FORMAT = { HTML, PDF }

END_OBJECT = DOCUMENT_ONLINE

END_OBJECT = DOCSET

END

**[(b) CATALOG/GEDRSIS.CAT]{.underline}**

PDS_VERSION_ID = PDS3

OBJECT = DOCSET

DOCUMENT_ID = \"GBAT_0001-EDRSIS1997-V1.0\"

REFERENCE_KEY_ID = \"SMITH&WESSON1997A\"

OBJECT = DOCUMENT_INFORMATION

DOCUMENT_NAME = \"IMAGER FOR MARS PATHFINDER (IMP)

EXPERIMENT DATA RECORD (EDR)\"

DOCUMENT_VERSION_ID = \"V1.0\"

DOCUMENT_TOPIC_TYPE = \"SOFTWARE INTERFACE SPECIFICATION (SIS)\"

AUTHOR_FULL_NAME = \"A.J. SMITH\"

PUBLICATION_DATE = 2000-02-12

COPYRIGHT_HOLDER = \"CALIFORNIA INSTITUTE OF TECHNOLOGY\"

NODE_ID = \"IMAGING-JPL\"

DOCUMENT_DESC = \"

Document Overview

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

This document is a Software Interface Specification (SIS)

describing the format of the IMP Experiment Data Records.

Document Purpose

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

System Interface Specification (SIS)

Source Format

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

The original document was written in Microsoft Word97.

Available Formats

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

Text, Adobe PDF, and HTML.\"

END_OBJECT = DOCUMENT_INFORMATION

OBJECT = DOCUMENT_ONLINE

ON_LINE_IDENTIFICATION = \"HTTP://WWW-IMG.JPL.NASA.GOV/PDS/EDRSIS.HTML\"

ON_LINE_NAME = \"EDR SIS\"

NODE_ID = \"IMAGING-JPL\"

PROTOCOL_TYPE = URL

DISTRIBUTION_FORMAT = { HTML, PDF }

END_OBJECT = DOCUMENT_ONLINE

END_OBJECT = DOCSET

END

**[(c) CATALOG/AAREADME.CAT]{.underline}**

PDS_VERSION_ID = PDS3

OBJECT = DOCSET

DOCUMENT_ID = \"GBAT_0001-AAREADME_DOC-V1.0\"

REFERENCE_KEY_ID = \"N/A\"

OBJECT = DOCUMENT_INFORMATION

DOCUMENT_NAME = \"GBAT_0001-AAREADME Volume Description\"

DOCUMENT_VERSION_ID = \"V1.0\"

DOCUMENT_TOPIC_TYPE = \"VOLUME CONTENTS\"

AUTHOR_FULL_NAME = \"A.J. SMITH\"

PUBLICATION_DATE = 2000-02-12

COPYRIGHT_HOLDER = \"CALIFORNIA INSTITUTE OF TECHNOLOGY\"

NODE_ID = \"IMAGING-JPL\"

DOCUMENT_DESC = \"

Document Overview

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

This document is a description of the GBAT volume.

Document Purpose

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

Volume Description

Source Format

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

The original document was a TEXT object.

Available Formats

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

Text\"

END_OBJECT = DOCUMENT_INFORMATION

OBJECT = DOCUMENT_ONLINE

ON_LINE_IDENTIFICATION =
\"HTTP://WWW-IMG.JPL.NASA.GOV/PDS/AAREADME.HTML\"

ON_LINE_NAME = \"AAREADME.TXT\"

NODE_ID = \"IMAGING-JPL\"

PROTOCOL_TYPE = URL

DISTRIBUTION_FORMAT = HTML

END_OBJECT = DOCUMENT_ONLINE

END_OBJECT = DOCSET

END

**[(d) CATALOG/ERRATA.CAT]{.underline}**

PDS_VERSION_ID = PDS3

OBJECT = DOCSET

DOCUMENT_ID = \"GBAT_0001-ERRATA_DOC-V1.0\"

REFERENCE_KEY_ID = \"N/A\"

OBJECT = DOCUMENT_INFORMATION

DOCUMENT_NAME = \"GBAT_0001-ERRATA Volume Description\"

DOCUMENT_VERSION_ID = \"V1.0\"

DOCUMENT_TOPIC_TYPE = \"VOLUME CONTENTS\"

AUTHOR_FULL_NAME = \"A.J. SMITH\"

PUBLICATION_DATE = 2000-02-12

COPYRIGHT_HOLDER = \"CALIFORNIA INSTITUTE OF TECHNOLOGY\"

NODE_ID = \"IMAGING-JPL\"

DOCUMENT_DESC = \"

Document Overview

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

This document is a description of the errata associated with

the GBAT_0001 volume.

Document Purpose

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

Volume Contents

Source Format

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

The original document was a TEXT object.

Available Formats

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

Text\"

END_OBJECT = DOCUMENT_INFORMATION

OBJECT = DOCUMENT_ONLINE

ON_LINE_IDENTIFICATION = \"HTTP://WWW-IMG.JPL.NASA.GOV/PDS/ERRATA.HTML\"

ON_LINE_NAME = \"ERRATA.TXT\"

NODE_ID = \"IMAGING-JPL\"

PROTOCOL_TYPE = URL

DISTRIBUTION_FORMAT = HTML

END_OBJECT = DOCUMENT_ONLINE

END_OBJECT = DOCSET

END

**[(e) CATALOG/MISSION.CAT]{.underline}**

PDS_VERSION_ID = PDS3

LABEL_REVISION_NOTE = \"Lyle Huber, 1999-01-29\"

RECORD_TYPE = FIXED_LENGTH

RECORD_BYTES = 80

OBJECT = MISSION

MISSION_NAME = \"GROUND BASED ATMOSPHERIC OBSERVATIONS\"

OBJECT = MISSION_INFORMATION

MISSION_START_DATE = 1993

MISSION_STOP_DATE = 1995

MISSION_ALIAS_NAME = \"UNK\"

MISSION_DESC = \"

Mission Overview

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

From \[KARKOSCHKA1994\]

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

Full-disk albedo spectra of the jovian planets and Titan were derived

from observations at the European Southern Observatory in July 1993. The

spectra extend from 300- to 1000-nm wavelength at 1-nm resolution. The

signal-to-noise ratio is approximately 1000 in the visible. The accuracy
is 2

percent for relative and 4 percent for absolute albedos. Colors and
magnitudes

were also determined. Some 40-60 Raman scattering features are visible
in the

spectrum of each jovian planet. A Raman scattering model with five
parameters

adjusted for each planet can explain these features. A methane
absorption

spectrum is given which fits methane features in the spectra of the
jovian

planets and Titan. It differs from room-temperature laboratory spectra
but it

is consistent with some limited laboratory data at cold temperatures.
Three

new, weak methane bands were detected in the spectra of Uranus and
Neptune. A

strong absorption band in Jupiter\'s spectrum is possibly due to water,

confirming a strong depletion of oxygen in the probed part of Jupiter\'s

atmosphere.

From \[KARKOSCHKA1998\]

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

Full-disk albedo spectra of the jovian planets and Titan were derived
from

observations at the European Southern Observatory in July 1995. The
spectra

extend from 300 to 1050 nm wavelength. The spectral resolution is 0.4 nm

between 520 and 995 nm, and 1 nm elsewhere. The accuracy of the albedo

calibration is 4 percent. UBV magnitudes were also determined. Raman

scattering was quantified for each planet. Methane and ammonia bands are
shown

at 0.4 nm spectral resolution, including a new band at 930 nm wavelength
which

is probably due to ammonia. Maps of the variation of these absorptions
across

the disks of Jupiter and Saturn are displayed. Saturn\'s spectrum is

undisturbed by light from its rings due to the edge-on geometry during
the

observations. The albedo of Uranus near 1 micro-m wavelength has dropped

almost 10 percent between 1993 and 1995, while there has been no change
in the

ultraviolet. The signature of light from Titan\'s surface yielded a path
length

of 4 km-am of methane in Titan\'s atmosphere. The temperature dependence
of the

width of the 890-nm methane band was used to measure temperature
variations at

three altitude levels, resulting in the first temperature maps of
Jupiter and

Saturn based on reflected sunlight. Jupiter displays a banded
temperature

structure with some discrete features of a few Kelvin amplitude.
Saturn\'s

> north-south temperature asymmetry has reversed since the Voyager
> observations. \"

MISSION_OBJECTIVES_SUMMARY = \"UNK\"

END_OBJECT = MISSION_INFORMATION

OBJECT = MISSION_HOST

INSTRUMENT_HOST_ID = ESO

OBJECT = MISSION_TARGET

TARGET_NAME = JUPITER

END_OBJECT = MISSION_TARGET

END_OBJECT = MISSION_HOST

OBJECT = MISSION_HOST

INSTRUMENT_HOST_ID = ESO

OBJECT = MISSION_TARGET

TARGET_NAME = SATURN

END_OBJECT = MISSION_TARGET

END_OBJECT = MISSION_HOST

OBJECT = MISSION_HOST

INSTRUMENT_HOST_ID = ESO

OBJECT = MISSION_TARGET

TARGET_NAME = URANUS

END_OBJECT = MISSION_TARGET

END_OBJECT = MISSION_HOST

OBJECT = MISSION_HOST

INSTRUMENT_HOST_ID = ESO

OBJECT = MISSION_TARGET

TARGET_NAME = NEPTUNE

END_OBJECT = MISSION_TARGET

END_OBJECT = MISSION_HOST

OBJECT = MISSION_HOST

INSTRUMENT_HOST_ID = ESO

OBJECT = MISSION_TARGET

TARGET_NAME = TITAN

END_OBJECT = MISSION_TARGET

END_OBJECT = MISSION_HOST

OBJECT = MISSION_REFERENCE_INFORMATION

REFERENCE_KEY_ID = { \"KARKOSCHKA1994\",

\"KARKOSCHKA1998\" }

DOCUMENT_ID = \"GBAT_0001-MISSION_DOC-V1.0\"

END_OBJECT = MISSION_REFERENCE_INFORMATION

END_OBJECT = MISSION

END

**[(f) CATALOG/DATASET.CAT]{.underline}**

PDS_VERSION_ID = PDS3

RECORD_TYPE = STREAM

LABEL_REVISION_NOTE = \"Lyle Huber, 1998-12-17\"

OBJECT = DATA_SET

DATA_SET_ID = \"ESO-J/S/N/U-SPECTROPHOTOMETER-4-V2.0\"

OBJECT = DATA_SET_INFORMATION

DATA_SET_NAME = \"Spectrophotometry of the Jovian

Planets and Titan at 300- to 1000-nm\"

DATA_SET_COLLECTION_MEMBER_FLG = \"N\"

DATA_OBJECT_TYPE = TABLE

START_TIME = 1993

STOP_TIME = 1995

DATA_SET_RELEASE_DATE = 1998-09-01

PRODUCER_FULL_NAME = \"ERICH KARKOSCHKA\"

DETAILED_CATALOG_FLAG = \"N\"

DATA_SET_DESC = \"

Data Set Overview

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

The best description of this data set is \[KARKOSCHKA1998\] which

can be found in ASCII form in /DOCUMENT/ICARUS98.ASC on this

volume. Some of the text in this DATASET.CAT file is quoted

from this reference. Additionally, the previous version (1993)

of this data set is included as well. The reference for that

portion of the data set is \[KARKOSCHKA1994\] and can be found in

/DOCUMENT/ICARUS94.ASC.

Full-disk albedo spectra of the jovian planets and Titan were

derived from observations at the European Southern Observatory

in July 1995. The spectra extend from 300 to 1050 nm

wavelength. The spectral resolution is 0.4 nm between 520 and

995 nm, and 1 nm elsewhere. The accuracy of the albedo

calibration is 4 percent. UBV magnitudes were also determined.

Raman scattering was quantified for each planet. Methane and

ammonia bands are shown at 0.4 nm spectral resolution,

including a new band at 930 nm wavelength which is probably due

to ammonia. Maps of the variation of these absorptions across

the disks of Jupiter and Saturn are displayed. Saturn\'s

spectrum is undisturbed by light from its rings due to the

edge-on geometry during the observations. The albedo of Uranus

near 1 micro-m wavelength has dropped almost 10 percent between

1993 and 1995, while there has been no change in the

ultraviolet. The signature of light from Titan\'s surface

yielded a path length of 4 km-am of methane in Titan\'s

atmosphere. The temperature dependence of the width of the

890-nm methane band was used to measure temperature variations

at three altitude levels, resulting in the first temperature

maps of Jupiter and Saturn based on reflected sunlight.

Jupiter displays a banded temperature structure with some

discrete features of a few Kelvin amplitude. Saturn\'s

north-south temperature asymmetry has reversed since the

Voyager observations.

Data

====

The tables present the methane absorption coefficient and

albedos of Jupiter, Saturn, Uranus, Neptune and Titan at 1 nm

resolution and 0.4 nm sampling from 300-1050 nm and at 0.4 nm

resolution and 0.1 nm sampling from 520-995 nm. \"

CONFIDENCE_LEVEL_NOTE = \"

Confidence Level Overview

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

Table II in \[KARKOSCHKA1998\] summarizes the UBV magnitudes,

calculated from the albedo spectra by the same method as

\[KARKOSCHKA1994\]. Note that for Jupiter, Saturn, and Titan,

their full-disk albedos shown are not geometric albedos and the

listed magnitudes are not opposition magnitudes due to their

finite phase angles during the observation. Geometric albedos

of Jupiter and Saturn are probably some 5 percent larger than

the given albedos. Accordingly, their opposition magnitudes

are about 0.05 more negative than the listed magnitudes.

As stated in \[KARKOSCHKA1994\], relative albedos are good to 2

percent and absolute albedos are good to 4 percent, mostly due

to the uncertainty in the solar-to-stellar flux ratio. The 2

percent accuracy applies also to the 2-year variations which

are not influenced by solar or stellar flux errors since the

same comparison stars were used in both years.

Review

======

This data set is currently scheduled to undergo PDS peer review

in January 1999.

Data Coverage and Quality

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

This section should probably be added to by Karkoschka or

others during the peer review. \"

END_OBJECT = DATA_SET_INFORMATION

OBJECT = DATA_SET_TARGET

TARGET_NAME = JUPITER

END_OBJECT = DATA_SET_TARGET

OBJECT = DATA_SET_TARGET

TARGET_NAME = SATURN

END_OBJECT = DATA_SET_TARGET

OBJECT = DATA_SET_TARGET

TARGET_NAME = URANUS

END_OBJECT = DATA_SET_TARGET

OBJECT = DATA_SET_TARGET

TARGET_NAME = NEPTUNE

END_OBJECT = DATA_SET_TARGET

OBJECT = DATA_SET_TARGET

TARGET_NAME = TITAN

END_OBJECT = DATA_SET_TARGET

OBJECT = DATA_SET_HOST

INSTRUMENT_HOST_ID = \"EOS\"

INSTRUMENT_ID = \"B&C\"

END_OBJECT = DATA_SET_HOST

OBJECT = DATA_SET_REFERENCE_INFORMATION

REFERENCE_KEY_ID = { \"KARKOSCHKA1994\",

\"KARKOSCHKA1998\" }

DOCUMENT_ID = \"GBAT_0001-EDRSIS1997-V1.0\"

END_OBJECT = DATA_SET_REFERENCE_INFORMATION

END_OBJECT = DATA_SET

END

#### Product Level 

The following examples illustrate the method whereby document products
are cataloged at the Product Level using the FILE object. The
DOCUMENT_PRODUCT object is used to specify the attributes associated
with each instance of the archive document. The DOCUMENT_PRODUCT object
and its associated keywords are more fully described in Appendix A.

**[(a) DOCUMENT/AAREADME.LBL]{.underline}**

OBJECT = DOCUMENT_PRODUCT

DOCUMENT_ID = \"GBAT_0001-AAREADME_DOC-V1.0\"

DOCUMENT_PRODUCT_ID = \"GBAT_0001-AAREADME_TXT-V1.0\"

DOCUMENT_VERSION_ID = \"V1.0\"

DOCUMENT_FORMAT = TEXT

PARENT_FILE_NAME = AAREADME.TXT

FILES = 1

DESCRIPTION = \"Archived version of AAREADME.TXT\"

OBJECT = FILE

FILE_SPECIFICATION_NAME = \"/DOCUMENT/AAREADME.TXT\"

DOCUMENT_FORMAT = TEXT

RECORD_TYPE = STREAM

ENCODING_TYPE = ASCII

MIME_TYPE = \"N/A\"

DESCRIPTION = \"

Volume GBAT_0001

Spectrophotometry of the Jovian Planets and Titan

at 300- to 1050-nm Wavelength: the Methane Spectrum\"

END_OBJECT = FILE

END_OBJECT = DOCUMENT_PRODUCT

END

**[(b) DOCUMENT/ERRATA.LBL]{.underline}**

OBJECT = DOCUMENT_PRODUCT

DOCUMENT_ID = \"GBAT_0001-ERRATA_DOC-V1.0\"

DOCUMENT_PRODUCT_ID = \"GBAT_0001-ERRATA_TXT-V1.0\"

DOCUMENT_VERSION_ID = \"V1.0\"

DOCUMENT_FORMAT = TEXT

PARENT_FILE_NAME = ERRATA.TXT

FILES = 1

DESCRIPTION = \"Archived version of ERRATA.TXT\"

OBJECT = FILE

FILE_SPECIFICATION_NAME = \"/DOCUMENT/ERRATA.TXT\"

DOCUMENT_FORMAT = TEXT

RECORD_TYPE = STREAM

ENCODING_TYPE = ASCII

MIME_TYPE = \"N/A\"

DESCRIPTION = \"

No errors or anomalies were noted in creating this volume.\"

END_OBJECT = FILE

END_OBJECT = DOCUMENT_PRODUCT

END

**[(c) DOCUMENT/GBATMSN.LBL]{.underline}**

OBJECT = DOCUMENT_PRODUCT

DOCUMENT_ID = \"GBAT_0001-MISSION_DOC-V1.0\"

DOCUMENT_PRODUCT_ID = \"GBAT_0001-MISSION_TXT-V1.0\"

DOCUMENT_VERSION_ID = \"V1.0\"

DOCUMENT_FORMAT = TEXT

PARENT_FILE_NAME = MISSION.TXT

FILES = 1

DESCRIPTION = \"Archived version of MISSION.CAT\"

OBJECT = FILE

FILE_SPECIFICATION_NAME = \"/DOCUMENT/MISSION.TXT\"

DOCUMENT_FORMAT = TEXT

RECORD_TYPE = STREAM

ENCODING_TYPE = ASCII

MIME_TYPE = \"N/A\"

DESCRIPTION = \"

Text equivalent of MISSION.CAT.\"

END_OBJECT = FILE

END_OBJECT = DOCUMENT_PRODUCT

OBJECT = DOCUMENT_PRODUCT

DOCUMENT_ID = \"GBAT_0001-MISSION_DOC-V1.0\"

DOCUMENT_PRODUCT_ID = \"GBAT_0001-MISSION_HTML-V1.0\"

DOCUMENT_VERSION_ID = \"V1.0\"

DOCUMENT_FORMAT = HTML

PARENT_FILE_NAME = MISSION.HTML

FILES = 2

DESCRIPTION = \"Archived version of MISSION.CAT\"

OBJECT = FILE

FILE_SPECIFICATION_NAME = \"/DOCUMENT/MISSION.HTML\"

DOCUMENT_FORMAT = TEXT

RECORD_TYPE = STREAM

ENCODING_TYPE = ASCII

MIME_TYPE = \"N/A\"

DESCRIPTION = \"

HTML equivalent of MISSION.CAT.\"

END_OBJECT = FILE

OBJECT = FILE

FILE_SPECIFICATION_NAME = \"/DOCUMENT/MSN_GIFS/MSNGIF1.GIF\"

DOCUMENT_FORMAT = GIF

RECORD_TYPE = UNDEFINED

ENCODING_TYPE = \"GIF87A\"

MIME_TYPE = \"IMAGE/GIF\"

DESCRIPTION = \"

Only figure in MISSION.HTML.\"

END_OBJECT = DOCUMENT_PRODUCT

END

**[(d) DOCUMENT/GEDRSIS.LBL]{.underline}**

OBJECT = DOCUMENT_PRODUCT

DOCUMENT_ID = \"GBAT_0001-EDRSIS1997-V2.0\"

DOCUMENT_PRODUCT_ID = \"GBAT_0001-EDRSIS_TXT-V1.0\"

DOCUMENT_VERSION_ID = \"V1.0\"

DOCUMENT_FORMAT = TEXT

PARENT_FILE_NAME = EDRSIS.TXT

FILES = 1

DESCRIPTION = \"Archived version of MISSION.CAT\"

OBJECT = FILE

FILE_SPECIFICATION_NAME = \"/DOCUMENT/EDRSIS.TXT\"

DOCUMENT_FORMAT = TEXT

RECORD_TYPE = STREAM

ENCODING_TYPE = ASCII

MIME_TYPE = \"N/A\"

DESCRIPTION = \"

The EDR SIS in TEXT format.\"

END_OBJECT = FILE

END_OBJECT = DOCUMENT_PRODUCT

OBJECT = DOCUMENT_PRODUCT

DOCUMENT_ID = \"GBAT_0001-EDRSIS1997-V2.0\"

DOCUMENT_PRODUCT_ID = \"GBAT_0001-EDRSIS_HTML-V2.0\"

DOCUMENT_VERSION_ID = \"V2.0\"

DOCUMENT_FORMAT = HTML

PARENT_FILE_NAME = EDRSIS.HTML

FILES = 1

DESCRIPTION = \"Archived version of the EDR SIS\"

OBJECT = FILE

FILE_SPECIFICATION_NAME = \"/DOCUMENT/EDRSIS.HTML\"

DOCUMENT_FORMAT = TEXT

RECORD_TYPE = STREAM

ENCODING_TYPE = ASCII

MIME_TYPE = \"N/A\"

DESCRIPTION = \"

The EDR SIS in HTML format.\"

END_OBJECT = FILE

END_OBJECT = DOCUMENT_PRODUCT

OBJECT = DOCUMENT_PRODUCT

DOCUMENT_ID = \"GBAT_0001-EDRSIS1997-V2.0\"

DOCUMENT_PRODUCT_ID = \"GBAT_0001-EDRSIS_PDF-V1.5\"

DOCUMENT_VERSION_ID = \"V1.5\"

DOCUMENT_FORMAT = PDF

PARENT_FILE_NAME = EDRSIS.PDF

FILES = 1

DESCRIPTION = \"Archived version of the EDR SIS\"

OBJECT = FILE

FILE_SPECIFICATION_NAME = \"/DOCUMENT/EDRSIS.PDF\"

DOCUMENT_FORMAT = \"ADOBE PDF\"

RECORD_TYPE = UNDEFINED

ENCODING_TYPE = BINARY

MIME_TYPE = \"N/A\"

DESCRIPTION = \"

The EDR SIS in PDF format.\"

END_OBJECT = FILE

END_OBJECT = DOCUMENT_PRODUCT

**[(e) DOCUMENT/EDR_HTM.LBL]{.underline}**

PDS_VERSION_ID = PDS3

OBJECT = DOCUMENT_PRODUCT

DOCUMENT_ID = \"EDRSIS1997-V1.5\"

DOCUMENT_PRODUCT_ID = \"EDRSIS1997_HTML-V1.5\"

DOCUMENT_VERSION_ID = \"V1.5\"

DOCUMENT_FORMAT = {HTML, GIF}

INTERCHANGE_FORMAT = {ASCII, BINARY}

PARENT_FILE_NAME = \"EDRSIS.HTM\"

FILES = 6

DESCRIPTION = \"

These files contain the HTML version of the Software Interface

Specification (SIS) for the IMP EDRs.\"

OBJECT = FILE

FILE_SPECIFICATION_NAME = \"INDEX.HTML\"

DOCUMENT_FORMAT = HTML

INTERCHANGE_FORMAT = ASCII

RECORD_TYPE = STREAM

ENCODING_TYPE = \"HTML-2.0\"

MIME_TYPE = \"TEXT/HTML\"

BYTES = 116000

END_OBJECT = FILE

OBJECT = FILE

FILE_SPECIFICATION_NAME = \"HTM_GIFS/EDRSIS1.GIF\"

DOCUMENT_FORMAT = GIF

INTERCHANGE_FORMAT = BINARY

RECORD_TYPE = UNDEFINED

ENCODING_TYPE = \"GIF87A\"

MIME_TYPE = \"IMAGE/GIF\"

BYTES = 16000

END_OBJECT = FILE

OBJECT = FILE

FILE_SPECIFICATION_NAME = \"HTM_GIFS/EDRSIS2.GIF\"

DOCUMENT_FORMAT = GIF

INTERCHANGE_FORMAT = BINARY

RECORD_TYPE = UNDEFINED

ENCODING_TYPE = \"GIF87A\"

MIME_TYPE = \"IMAGE/GIF\"

BYTES = 4000

END_OBJECT = FILE

OBJECT = FILE

FILE_SPECIFICATION_NAME = \"HTM_GIFS/EDRSIS3.GIF\"

DOCUMENT_FORMAT = GIF

INTERCHANGE_FORMAT = BINARY

RECORD_TYPE = UNDEFINED

ENCODING_TYPE = \"GIF87A\"

MIME_TYPE = \"IMAGE/GIF\"

BYTES = 3000

END_OBJECT = FILE

OBJECT = FILE

FILE_SPECIFICATION_NAME = \"HTM_GIFS/EDRSIS4.GIF\"

DOCUMENT_FORMAT = GIF

INTERCHANGE_FORMAT = BINARY

RECORD_TYPE = UNDEFINED

ENCODING_TYPE = \"GIF87A\"

MIME_TYPE = \"IMAGE/GIF\"

BYTES = 4000

END_OBJECT = FILE

OBJECT = FILE

FILE_SPECIFICATION_NAME = \"HTM_GIFS/EDRSIS5.GIF\"

DOCUMENT_FORMAT = GIF

INTERCHANGE_FORMAT = BINARY

RECORD_TYPE = UNDEFINED

ENCODING_TYPE = \"GIF87A\"

MIME_TYPE = \"IMAGE/GIF\"

BYTES = 3000

END_OBJECT = FILE

END_OBJECT = DOCUMENT_PRODUCT

END

### DOCSET Object - Detached Label (using MANIFEST object)

The following sets of labels illustrate the method whereby a document
product is cataloged using the MANIFEST_TABLE object. The example
illustrates four document products to be cataloged:

1.  AAREADME -- a document that describes the archive volume

2.  ERRATA -- a document that describes the archive volume

3.  GBATMSN -- a set of documents that describe a mission

4.  GEDRSIS -- a set of files that describe a dataset

#### Archive Volume Level

The method whereby a document product is cataloged at the Archive Level
is the same for using the FILE object or the MANIFEST_TABLE object (see
9.3.4.1 for an example).

#### Catalog Level 

The method whereby a document product is cataloged at the Catalog Level
is the same for using the FILE object or the MANIFEST_TABLE object (see
9.3.4.2 for an example).

#### Product Level 

The following examples illustrate the method whereby multi-part document
products are cataloged at the Product Level using the MANIFEST_TABLE
object.

Note: For single-part document products or document products having a
relatively small number of parts, the FILE object is recommended as the
MANIFEST_TABLE object is more appropriate for describing document
products containing a large number of parts.

**[(a) DOCUMENT/EDR_HTM.LBL]{.underline}**

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

EDR_HTM.LBL - using MANIFEST_TABLE objects to catalog (multi-part)

document products

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

PDS_VERSION_ID = PDS3

\^MANIFEST_TABLE = \"EDR_HTM.TAB\"

OBJECT = DOCUMENT_PRODUCT

DOCUMENT_ID = \"EDRSIS1997-V1.0\"

DOCUMENT_PRODUCT_ID = \"EDRSIS1997_HTML-V1.0\"

DOCUMENT_VERSION_ID = \"1.5\"

DOCUMENT_FORMAT = {HTML, GIF}

INTERCHANGE_FORMAT = {ASCII, BINARY}

PARENT_FILE_NAME = \"EDRSIS.HTM\"

FILES = 6

DESCRIPTION = \"

These files contain the HTML version of the Software Interface

Specification (SIS) for the IMP EDRs.\"

OBJECT = MANIFEST_TABLE

COLUMNS = 7

ROWS = 6

ROW_BYTES = 86

OBJECT = COLUMN

COLUMN_NUMBER = 1

NAME = FILE_SPECIFICATION_NAME

START_BYTE = 2

BYTES = 21

FORMAT = \"A21\"

DATA_TYPE = CHARACTER

DESCRIPTION = \"The path and file name with extension,

relative to the DOCUMENT directory, of the named file. When

the file is located at the top level directory, this field

only contains the name of the file.

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 2

NAME = DOCUMENT_FORMAT

START_BYTE = 26

BYTES = 10

FORMAT = \"A10\"

DATA_TYPE = CHARACTER

DESCRIPTION = \"The document_format element represents the

manner in which documents are stored, such as TEX, POSTSCRIPT,

TIFF, etc.\"

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 3

NAME = INTERCHANGE_FORMAT

START_BYTE = 41

BYTES = 6

FORMAT = \"A6\"

DATA_TYPE = CHARACTER

DESCRIPTION = \"Either ASCII or BINARY.\"

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 4

NAME = RECORD_TYPE

START_BYTE = 50

BYTES = 20

FORMAT = \"A20\"

DATA_TYPE = CHARACTER

DESCRIPTION = \"The record format of the file.\"

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 5

NAME = ENCODING_TYPE

START_BYTE = 73

BYTES = 30

FORMAT = \"A30\"

DATA_TYPE = CHARACTER

DESCRIPTION = \"The type of compression or encryption

used for data storage..\"

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 6

NAME = DESCRIPTION

START_BYTE = 106

BYTES = 30

FORMAT = \"A30\"

DATA_TYPE = CHARACTER

DESCRIPTION = \"The description of the EDR.\"

END_OBJECT = COLUMN

OBJECT = COLUMN

COLUMN_NUMBER = 7

NAME = BYTES

START_BYTE = 139

BYTES = 8

FORMAT = \"I8\"

DATA_TYPE = ASCII_INTEGER

UNITS = BYTES

DESCRIPTION = \"The size of the file, in bytes\"

END_OBJECT = COLUMN

END_OBJECT = MANIFEST_TABLE

END_OBJECT = DOCUMENT_PRODUCT

END

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

EDR_HTM.TAB - The manifest table defined above

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

1 2 3 4 5 6 7 8 9

123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890

\"123456789012345678901\",\"12345\",\"123456\",\"1234567890\",\"123456789\",\"123456789\",12345678

\"EDRSIS.HTM \",\"HTML \",\"ASCII \",\"STREAM \",\"NONE
\",\"TEXT/HTML\",116000

\"INDEX.HTML \",\"HTML \",\"ASCII \",\"STREAM \",\"HTML-2.0
\",\"TEXT/HTML\",116000

\"HTM_GIFS/EDRSIS1.GIF \",\"GIF \",\"BINARY\",\"UNDEFINED \",\"GIF87A
\",\"GIF \",16000

\"HTM_GIFS/EDRSIS2.GIF \",\"GIF \",\"BINARY\",\"UNDEFINED \",\"GIF87A
\",\"GIF \",4000

\"HTM_GIFS/EDRSIS3.GIF \",\"GIF \",\"BINARY\",\"UNDEFINED \",\"GIF87A
\",\"GIF \",3000

\"HTM_GIFS/EDRSIS4.GIF \",\"GIF \",\"BINARY\",\"UNDEFINED \",\"GIF87A
\",\"GIF \",4000

\"HTM_GIFS/EDRSIS5.GIF \",\"GIF \",\"BINARY\",\"UNDEFINED \",\"GIF87A
\",\"GIF \",3000

AAREADME.TXT, 9-2

ASCII files

containing markup, 9-4

format, 9-3

DOCINFO.TXT, 9-2

DOCUMENT, 9-2

DOCUMENT objects, 9-2

documentation, 9-1

ASCII file format, 9-3

criteria for inclusion, 9-1

example

attached TEXT, 9-5

detached, 9-5

with graphics, 9-6

format, 9-1

HTML, 9-1, 9-4

labels for, 9-2

markup files, 9-4

non-ASCII files, 9-5

required ASCII format, 9-1

TeX/LaTeX, 9-1

validation, 9-5

ENCODING_TYPE, 9-5

extensions

table of, 9-3

TEXT, 9-2

TEXT objects, 9-2