<?xml version="1.0" encoding="UTF-8"?>

<!-- <!DOCTYPE sddlschema SYSTEM "sddlschema.xsd">-->

<sddl>

<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<!-- -->
<!--  SDDL Name:  PRODUCT_ENG_MAP.SDDL -->
<!-- -->
<!--  Purpose:      This SDDL file defines the PRODUCT_ENG_MAP relation.-->
<!-- -->
<!--  Modification History:-->
<!-- -->
<!--    Date       PR      Who                       Reason-->
<!--  - - - -    - - - -   - -   - - - - - - - - - - - - - - - - - - - - - -->
<!--  01/30/01   44862     Baum  Original implementation-->
<lm>  07/03/03   48821     CTB   Converted to XML format </lm> <!-- last mod -->
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
 

    <record name="PRODUCT_ENG_MAP_TYPE"> 
 
 
        <description>This relation is used to identify the ENG files that may be
                   required for FGS, GSA or AST product generation. It is used
                   to simplify creation and collection of telemetry for 
                   processing.  When a product has no eng_ready = N flags, 
                   then the OSF for the product can be created using the
                   product rootname. </description>


            <field name="product_rootname">
                    <type>C14</type>
                    <description>IPPPSSOOT for jitter or astrometry products;
                         GYYYYDDDHHMMSS for GS acquisition data.</description>
            </field>

            <field name="product_type">
                    <type>C3</type>
                    <description>FGS for jitter, AST for astrometry, or GSA for GS 
                         acqusition data.</description>
            </field>

            <field name="eng_rootname">
                    <type>C12</type>
                    <description>TYYYYDDDHHMM, rootname of the ENG file.</description>
            </field>

            <field name="eng_ready">
                    <type>C1</type>
                <discrete>Y</discrete>
                <discrete>N</discrete>
                    <description>N indicates the telemetry file eng_rootname is not yet
                     recognized as ready for this product_type. Y indicates
                     that the processing for this product type has recognized
                     the presence of eng_rootname. Having separate control for
                     each product type simplifies initiation of processing. </description>
            </field>
    </record>
 
 
 
    <relation name="product_eng_map">
 
        <type>PRODUCT_ENG_MAP_TYPE</type>

        <description>Product to ENG File Mapping Relation</description>

        <subsystem_using>OPUS</subsystem_using>

        <index name="product_eng_map_1">
            <type>unique clustered</type>
            <field name="eng_rootname"/>
            <field name="product_rootname"/>
            <field name="product_type"/>
        </index>

        <index name="product_eng_map_2">
            <type>nonclustered</type>
            <field name="product_rootname"/>
            <field name="product_type"/>
        </index>

    </relation>
</sddl>
