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

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

<sddl>

<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<!-- -->
<!--  SDDL Name:    DMS_ASN_ID.XML -->
<!-- -->
<!--  Purpose:      This SDDL file defines the DMS_ASN_ID relation.-->
<!-- -->
<!--  Modification History:-->
<!-- -->
<!--    Date       OPR      Who                       Reason-->
<!--  - - - -    - - - -    - -   - - - - - - - - - - - - - - - - - - - - - -->
<!--  08/18/05   48821     Baum   Initial version                     -->
<lm>  07/06/06   56015  MSwam  Add sms_id, creation_date </lm> <!-- last mod -->
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->


    <record name="DMS_ASN_ID_TYPE">

        <description>This relation is used to provide a list of the special
                   DMS associations that wree created without SPSS support.
                   There are no SPSS_DB:qeassociation records for these
                   associations. These associations were created for a project
                   to reprocessing old unassociated datasets into new 
                   associations.</description>


            <field name="association_id">
                    <type>C9</type>

                    <description>This field identifies an OPUS association.   An
                    association is a set of exposures that will be
                    merged into products by OPUS pipeline calibration
                    processing. The full association consists of a
                    list of exposures and products.  

                    This field completely identifies an association. This is 
                    the OPUS value used for the keyword ASN_ID.  It has the
                    following format:

                           IPPPSSAAa

                    where:
                           I = instrument code
                               (e.g., N for NICMOS, O for STIS),
                         PPP = program_id
                          SS = obset_id of the first associated exposure,
                         AAa = the two-character sequence (AA = 01,02,...)
                               is unique within the obset SS;
                               plus the product id (a) that is always
                               0 for associations and primary products.
                    </description>
            </field>

            <field name="sms_id">
                    <type>C9</type>
                    <description><![CDATA[ The C&C list is a major data 
                    structure within SPSS that
                    contains information on 'candidates' and the 'calendar'.

                    The candidate data, often referred to as the candidate
                    pool, are scheduling units and their associated
                    observation set, alignment, and target data.

                    The calendar is a timeline of activities that are laid
                    down by the SPSS scheduling utilities.  Example
                    activities include slews, PCS aquisitions, small angle
                    maneuvers, science, TDRS contacts, tape recordings,
                    science instrument reconfigurations, and others.

                    When a C&C List is saved in SPSS (via the cclist -save
                    comand) it receives an identifier.  The identifier can
                    be up to 9 characters long.  Within operations, the C&C
                    list naming convention is:    yydddnxx

                    where          yy  = last two digits of the year
                                   ddd = day of year of start of calendar
                                     n = length of calendar in days (usually 7)
                                    xx = unique identifier within above info.
                                    ]]> </description>

            </field>

        <field name="creation_date">
                <type>SYBASE_DATETIME</type>
                <description>This field is set to the time at which this
                     dms_asn_id record was entered into the table by the
                     dms_asn_insert.pl tool.  </description>
        </field>

    </record>


    <relation name="dms_asn_id">

        <type>DMS_ASN_ID_TYPE</type>

        <description>DMS association names </description>

        <subsystem_using>OPUS</subsystem_using>

            <index name="dms_asn_id_1">
                    <type>unique clustered</type>
                    <field name="association_id"/>
            </index>

    </relation>
</sddl>
