<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://digitalprojects.uah.edu/items/browse?output=omeka-xml&amp;page=29&amp;sort_field=added" accessDate="2026-04-06T00:19:57+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>29</pageNumber>
      <perPage>20</perPage>
      <totalResults>8239</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="997" public="1" featured="0">
    <fileContainer>
      <file fileId="838">
        <src>https://digitalprojects.uah.edu/files/original/20/997/spc_stnv_000050.pdf</src>
        <authentication>09a1d1c6d68b9534213e2a76fef3a7b7</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177225">
                    <text>ShTC'rN tI:STORY DOCl_!f.:ENT
L j n l v ~,slty 06 b ,. kens Kc--c- c ! ~institute
,
tlistciy

Science

G l ' e c l , n s i ~Group
~~

----------

Da@
AEROSPACE VEHlCLE SIMULATION AND CHECKOUT

J. W. Moore
Quality &amp; Reliability Assurance Laboratory
Marshall Space Flight Center
Huntsville, Alabama

J. R. Mitchell
Quality &amp; Reliability Aesurance Laboratory
Marshall Space Flight Centat
Huntsville, Alabama

4

H. H. Trauboth
Computation Laboratory
Marshall Space Flight Center
Huntsville, Alabama

The advancement of the space age into increasingly complex and ambitious miesions r e quiring the development and operation of more
sophisticated and intricate 'launch vehicles has
generated numerous problem areas. The purpose
of this paper i s to: define the Aerospace Vehicle
Simulation; discuss the relationship of this simulation to the major problem a r e a s of checkout;
describe the development and implementation of
this simulation system; indicate multiciscipline
applications to present and future programs.
Introduction
The advent of the Apollo missions and the
ever increasing traffic of men and equipment into
the world of space will and i s requiring the development and operation of more sophisticated and
intricate space vehicles. Among the myriad difficulties created by these vehicles i s how to e s tablish knowledge of their existing conditions;
i. e., the checkout of these complex space vehicles. Concepts, techniques and methods for improving checkout of complex systems have and
continue to be the subject of numerous studies
and investigations and considerable progress has
been made in this area. A concept which i s being pursued by National Aeronautics and Space
Administration (NASA)/Marshall Space Flight
Center (MSFC) i s the development of a &amp;ital
simulation of aerospace vehicles. This concept
shows immense promise in the benefits that i t
can offer not only in alleviating the problems a s sociated with aerospace vehicle checkout but also
in a number of other a r e a s of the aerospace program such a s hardware design and analysis,
mission analysis and configuration management.
In order to s e t the stage t o indicate the manner in which an aerospace vehicle simulation can
a s s i s t in the solution of the checkout problems,
it would be appropriate to f i r s t consider just what
a r e the primary a r e a s of difficulties attendant to
a checkout of a present day aerospace vehicle.

The list of checkout problems enumerated and
discussed here is not intended to be all inclueive
but only to show the nature of the problems encountered in performing the checkout operation.
Possibly the f i r s t and foremost difficulty encountered i s that of obtaining a thorough analyeie
of the vehicle's functional systems. Essentially
most of the other problems encountered in checkout a r e based on the lack of an adequate knowledge of how the vehicle's subsystems operate
and/or the operation of the supporting ground
equipment. The present mode of operation in the
checkout field does not always allow the checkout
engineers to become a s intimately knowledgeable
of the performance of the systems a s i s desirable,
Thus a system i s needed that would provide checkout personnel with all the available information on
the system's operation and performance ,and aid
in the actual system and circuit analysie.
One of the major jobs of the checkout engineer i s the establishment of the test requirements
for the vehicle system and subsystems. This
task involves the determination of what system
o r subsystem parameters o r characteristics to
check and when in the checkout sequence they
should be monitored. Also entailed here is how
much testing is necessary to insure the adequacy
of operation of the system; i. e., will end-to-end
testing be sufficient a t some stages in the checkout operation o r i s detailed component or subsystem testing required. This problem relates back
to a thorough analysis of the system o r subsystem
and a determination of its reliability and criticality in relationship to the mission.
The generation and evaluation of test procedures and/or test programs has always been one
of the most tedious and time consuming tasks
faced by the checkout personnel. Once it has
been decided what to test and when to test, we
must then determine how the c i r h i t o r subsystem
will be tested. The selection of the proper

�stimuli and the o p t h u m point to apply it, the s e lection of the t e s t points a t which measurements
will be made, and the proper correlation of the
response to the stimuli and the establishment of
the proper sequence to test, a r e a l l factors which
make the generation of t e s t programs an exacting
science today. It i s required that checkout personnel have a c c e s s to a system which would allow them to vary and evaluate these factors without entailing the buildup of expensive hardware
systems. The debugging of computer programs
is a well known problem and any system that
would aid this operation would present tremendous savings in costs and time.

A corollary to the aforementioned problems
i s that of human e r r o r occurrence in checkout
s y s t e m s and operations. The system analysis
and data reduction a r e often plagued by mistakes
when performed by hand. Such efforts a s the
tracing of signal paths through pages of drawings
and the generation and checking of step-by-step
procedures a r e often fraught with e r r o r s due to
the poor efficiency of humans a t such routine and
often humdrum tasks.
Invariably during the various stages of the
checkout operations, malfunctions o r improper
operations of the vehicle systems a r e discovered.
Generally these malfunctions a r e f i r s t noticed on
the overall o r system level tests which then gives
r i s e to the problem of fault isolation of the malfunctions to a particular component o r replacable
unit. The two categories of techniques for fault
isolation during automated testing a r e logical
analysis and synthesis. The f o r m e r involves
taking all the required measurements on a piece
of equipment; i. e., performing all tests, and
then deducing values of elements of the equipment.
The deduced values of the elements a r e then compared to acceptable tolerance limits to isolate the
fault. Fault isolation by logical synthesis cons i s t s of a comparison of a l l test outputs with all
possible modes of failure. When a match occurs,
the mode of failure i s known, and hence the fault
i s isolated t o a level consistent with the defined
mode of failure. The use of these techniques in
an automated t e s t operation requires detailed
analysis of the systems and circuits to generate
the t e s t routines required to progressively isolate a fault. This problem i s compounded by the
fact that the t e s t points available a r e not always
the optimum ones for troubleshooting a circuit
crr system.
Thus f a r in the space program the completely developed space vehicle has not been built,
t h e r e a r e continuous modifications being made to
each vehicle. The effects of these changes on the
vehicle system's performance must be a s s e s s e d

and the effect on the Ground Support Equipment
(GSE) and the t e s t operations must be evaluated.
Test techniques, programs, procedures, etc.
must be reviewed to determine if they a r e still
adequate t o checkout the system as modified.
This very often requires going back through a detailed analysis of the system and making extensive changes to computer checkout programs, all
of which i s time consuming and costly. Therefore, a major problem in checkout i s how to obtain a faster response t o design changes i n t e r m s
of system performance, effects on GSE and on
checkout aperations. The s a m e comments a r e
t r u e also for determining the effects on the apace
vehicle and i t s checkout of changes in equipment
which interface with the vehicle (e. g.. GSE,
checkout equipment, etc. ).
A prime problem encountered by checkout
personnel i s that of maintaining an up-to-date .
configuration of the space vehicle. Very often.
considerable effort i s expended on the analysis
of circuits, subsystems, and systems; the generation of test procedures, programs, etc. for
the checkout of hardware that has already been
changed but the documentation reflecting the
changes has not filtered through the paper mill
to those who need it. What i s desirable h e r e to
alleviate this problem i s a centralized, up-todate, complete data source with the ability to call
up information based on various criteria.

Objective of Simulation
The problems enumerated in the foregoing
section of this paper represent the types of difficulties encountered in preparing for and conducting the checkout operaticn on an aerospace
vehicle. To relieve this situation, work has been
conducted by MSFC to define and develop a system that would provide checkout engineers, a s
well a s other potential u s e r s , with the information they need and establish a major new tool to
a s s i s t them in the preparation for the checkout
task. The tool envisioned i s the simulation of a
spzre vehicle a ~ its
d GSF, on iarge scale digital computer. This portion of the paper will discuss the objectives of the digital Aerospace Vehicle Simulation and the relationship of this sirnulation t o the aforementioned checkout problem
areas.
The Aerospace Vehicle Simulation i s a part
of the total aerospace vehicle information system,
It i s an engineering type tool, for u s e on a gene r a l purpose digital computer, where a n individual selects the hardware system(s) to be sirnulated and the conditions for their simulation in
various forms which best support the needs of
the user.

�Basically the objectives of the Aerospace Venicle Simulation i s t o a i d in the solution of the
previously mentioned problems a s well a s t o a s s i s t other u s e r s in the solution of t h e i r particul a r problems. In t e r m s of the checkout a r e a
the objectives of the Aerospace Vehicle Simulation a r e to: ( a ) obtain a m o r e refined checkout
of the space vehicle by a n increased depth of
analysis and synthesis of the space vehicle s y s t e m s , (b) generation and evaluation of checkout
procedures, (c) the evaluation of changes in
flight and GSE h a r d w a r e and/or checkout techniques and procedures, (d) and a s a configuration management documentation data center and
control.
Refined Checkout
The establishment of a m o r e refined o r sophisticated checkout of the space vehicle r e q u i r e s that the checkout personnel obtain a n inc r e a s e d knowledge of t h e vehicle system's operation and have the capability to perform an extensive analysis of the system's functional behavior.
The Aerospace Vehicle Simulation through the
functions which i t can perform will provide
checkout personnel with the knowledge and analy s i s capability which i s required. These various functions will be discussed in the subsequent paragraphs.
The backbone of the simulation will be dynamic
o r transient analysis of a selected portion of the
space vehicle and ground support s y s t e m s and
the d i s c r e t e simulation; i. e, , follow signals
through a selected portion of the vehicle on a
d i s c r e t e basis. Generally a l l other engineering
type u s e s of the simulation \\ill use these two
m a j o r functions in some form. The u s e r will
want to be able to simulate different combinations of a variety of configurations. Some may
want a somewhat refined simulation of a r e l a tively s m a l l composite of components while othe r s may want only a c u r s o r y simulation of a
l a r g e network of components. Perhaps, a s i s
the c a s e for an overall s y s t e m checkout, it will
be d e s i r e d to specify a s little a s the input s t i m uli and output nodes a t which the response i s to
be computed, having the simulation construct
the pertinent program system from the program
l i b r a r y and the data base.
The transient analysis simulation use will
s e r v e t o determine the transient operation time
of the elements based on their p a r a m e t e r s , stability c h a r a c t e r i s t i c s for the portion of the syst e m under consideration and transient response
of circuits o r s y s t e m s considered. It will provide outputs such as: plot of transient response,
listing of equipment unstahle i n operation. The

analysis will encompass discrete and continuous
operation of electrical, mechanical, hydraulic.
and pneumatic elements.
The object of the discrete simulation is t o
allow a u s e r t o follow the sequence of operations.
on a discrete basis, through a selected portion
of the vehicle and/or ground system. The t i m e
intervals involved either have predefined values
o r a r e the r e s u l t of calculation of the expected
times of operation of the elements based on their
p a r a m e t e r s , which values can be calculated by
the dynamic simulation. Typical of the type outputs which would be generated are: function s e quence, listing of sequence of operation by t i m e ,
listing of component status change, listing f o r
comparison run, etc.
Using the discrete and dynamic simulations
a s the base, various features can be added t o the
simulation system that will permit i t t o be applied in the following a r e a s to improve checkout.
Design Evaluation. The nature of the simulation will be such that the design and operation
of the hardware can be verified on an individual
basis a s well a s an integrated system. The following types of problem a r e a s can be determined
and evaluated: equipment interactions, determination of closely timed operations, check for inconsistencies such a s conflicting signals a n d / o r
component operations which lead to inconsistent
functions, check for redundancies to detect unintentional multiple circuit paths o r operational
modes and the verification of the proper functioning of intentional redundant signal paths o r
modes of operation, and detailed analysis and
evaluation of hardware functioning.
F a i l u r e Effects. Various components o r
combinations of components a r e failed and the
resulting system operation i s compared to the
normal system operation to identify the effect of
the over-all system impact of failures and the
determination if monitoring devices detected the
failure, and if so, how long between time of failu r e and malfunction detection.
Fault Isolation. This i s , in a sense, the r e v e r s e of the failure effects application. Here a
fault i s simulated and i t s effects a r e followed
through the system so that if given a s e t of symptoms the possible malfunction which will cause
the symptoms can be defined.
Test Data Analysis. Transient response
data, discrete events recordings, etc., taken
during a checkout a r e compared to the computed
data in the simulation and a l l marginal o r abnorm a l operations a r e identified. An analysis can

�then be made t o determine if component tolerances should be changed, marginal components
replaced, operation sequences changed, etc.
Reliability Assessment. The simulation prog r a m computes and prints out the number of
t i m e s each component is activated o r cycled and
t i m e during which each was in the active s t a t e
during testing o r a launch countdown. This data
may be obtained on a time basis o r a per t e s t
b a s i s and will be valuable in establishing the operation and maintenance program a s well a s computing reliability numbers for each component
o r system.
T e s t Point Selection. A checkout planning
function is the selection of t e s t points to be used
to m e a s u r e the performance o r troubleshoot a
system. If consulted e a r l y in the design phase,
checkout personnel could select these points from
among a l l locations a t which measurements could
be taken. In practice, the t e s t points have already been allocated, so. the only selection is
which t e s t points should be used for a particular
test. Test point selection must also include consideration of the time available for taking measurements, the confidence required in estimates
of performance, and the level of fault isolation
desired. Given this information the simulation
system can evaluate various combinations of
t e s t points and thus aid in the selection of the
optimum s e t of t e s t points.

debugging s o that other necessary work in the
t e s t system must be interleaved. When problems
appear, their isolation can involve the t e s t program, checkout system or simulator. Additionally the simulation of faults o r marginal responaem
such a s a slow-or-faat acting relay a r e not readily implemented.
With the Aerospace Vehicle Simulation to
simulate the vehicle system and checkout support equipment, i t can provide the checkout computer with s t r e a m s of data i n form of PCM bits.
discrete signals, digitized hardline aignale, etc..
a s they would be received by the checkout computer in an actual checkout operation. Checkout
personnel can then s e t up the conditions which
spell out a proposed o r actual checkout o r countdown and compare the resulting outputs t o determine if the t e s t program functioned a s intended
and verify that each component has been tested.
The simulation provides a convenient media f o r
changing and up-dating the t e s t program. Vehicle system variations, such a s responses over
the full range of tolerances, a s well a s faults
may be entered in the simulation to verify that
the checkout programs will recognize and respond a s intended to these conditions. By these
means, t e s t programs could be checked out m o r e
thoroughly in preliminary stages without verifying hardware simulators and up-dated systems
configurations. It would also provide t e s t personnel training without using o r risking damage
to the vehicle system o r checkout complex.

Checkout Procedure Generation and Evaluation
Design Change Evaluation
The detailed t e s t procedure o r program calls
out the sequence of tests, the stimuli applied,
measurement made, the method of t e s t result
evaluation, and the t e s t result displays. The
fault isolation procedure is similar in nature.
With the subsystem and/or system of the
space vehicle and i t s test system simulated,
various t e s t techniques and t e s t sequences could
b e t r i e d in o r d e r to select the most effective
ones. Rules for generating the t e s t sequence
could be tested on the model and if the model
correctly simulated the subsystem, the t e s t syst e m and their interrelations, these rules could
be used to generate the detailed t e s t procedures.
Similarly, fault isolation t e s t procedures could
be generated by incorporating failures in the
model and using diagnostic rules.
Today, t e s t program debugging i s usually
performed using the checkout system and specially constructed hardware simulators of the vehicle system. This method has the advantage of
checking the total checkout system, however, it
t i e s up the full checkout system during program

This objective of the Aerospace Vehicle
Simulation applies to possible changes which
might be made to the equipment being simulated.
Proposed design changes may be incorporated
into the simulation by simply changing the equations for the hardware affected. Then the design
simulation can be performed, compared with the
prechange operation and a l l differences identified. An evahiation may then be made to determine if the differences comply with the intent of
the design change. This method will thoroughly
a s s e s s the over-all system's impact of a proposed design change before it i s actually incorporated in the hardware.
Typical of the functions of the Design Change
Evaluation objective are:
(a) To check the effect of circuit parameter
changes on delays associated with operations of
elements i n the system portion under consideration.

�(b) To check the effect on operation sequence
of a change in delays, addition o r deletion of alements, addition o r deletion of signals, and r e routing of signals.
(c) To check for conflict in physical location
of connections between elements of the portion
of the system considered.
(d) To check for possible redundancies, inconsistencies, o r questionalbe operation of equipment using the change data.
(e) To perform transient analysis for the
system portion under consideration using the
change data.
Documentation Data Center and Control
The objective of the Aerospace Vehicle Simulation in this a r e a will be to incorporate the existing MSFC Configuration Management Accounting
System and expand this system to include the
functional data of the space vehicle and GSE.
This will bring together the complete documentation of the vehicle/GSE system such that the management type data and the engineering type data
can be easily cross-referenced,
The configuration management data will be
used to support the established formal s e t of procedural concepts by which a uniform system of
configuration identification, control, and accounting i s established and maintained for a l l NASA
systems/equipment and components thereof.Specifically this i s accounting information directed
toward keeping t r a c k of the following information:
(a) Specifications for contract end items
(b) Changes to and maintenance of the specifications
(c) Engineering documentation required f a r
design releases, design changes, design reviews,
and t e s t acceptance and reviews.
This Aerospace Vehicle Simulation System
will allow the engineering functional data to be
closely correlated to the configqration management data such that when design releases o r design changes a r e made, the engineering data can
be immediately flagged and any changes in the engineering data required can be incorporated.
This then will allow u s e r s of the simulation to
have immediate a c c e s s to documentation on the
up-to-date configuration of the space vehicle/
GSE hardware.

Background
The f i r s t steps toward the development of
the Aerospace Vehicle Simulation were undertaken with a feasibility etudy which was conducted
by Brown Engineering Company under the directcognizance of NASAIMSFC, and an in-house
MSFC study effort to apply the computer technology to checkout oriented problems. The primary
a r e a of concern in these feasibility studies was
to e s t a b l i ~ h : (a) a means to provide an automated
method of expressing the detailed functional r e lationships that occur between components as
they interact during operation in a space vehicle,
(b) that the phyeical interconnection data of a
space vehicle system can be converted into a form
that can be processed by a digital computer by
using standard er.@neering data and standard programming techniques. (c) techniques which would
depict the introcomponent relationships, primarily mathematical expressions of tne input and output dynamics.

In effect a Total Systems Definitive Statement was developed based upon a notation system
of mathematical symbology representing
(a) General Functional Relationships
(b) Intercomponent Relationships (physical
interconnections)
(c) Introcomponent Relationships (dynamic
interactions)
These three algorithms were developed to
the point of applying existing vehicle data, in this
case the functional relationships of S-1-8 components were graphically described in a sequence
diagram using a n IBM 7040 computer system.
This preliminary feasibility study established the basic premise for this type of simulation. It emphasized the point that hardware and
sofiware-wise we were capablc of performing
this large scale simulation task. It remained
now to define the requirements and specifications
for an Aerospace Vehicle Simulation. This was
performed under contract (NAS8-20060) with the
General Electric Company. Daytona Beach,
Florida, entitled "Analytical Study of Launch
Vehicle Component Level Simulation". The basic
objectives of this study were to identify and solve
problems dealing with the general nature of the
simulation, formulation, operation, maintenance,
and effectiveness; and to present to MSFC specific recommendations concerning the simulation.
This study encompassed analysis of present data

�organization and 'simulation methods, the available and anticipated computer hardware and the
potential utilizations in o r d e r to select a n optimum combination of equipment, method* and
techniques. This study provided and substantiated the p r e m i s e that the Aerospace Vehicle
Simulation can be developed, i s practical and desirable.
Several other activities which have been conducted by MSFC, which were closely related to
this simulation, have had a significant input into
the program. The Electrical Support Equipment
Discrete Simulation developed for the Astronics
Laboratory of MSFC by General Electric under
the NASw-410 contract provided a building block
f o r the discrete simulation portion of the Aerospace Vehicle Simulation. This effort utilized
the Boolean expression algorithm t o describe the
d i s c r e t e functional relationships. A number of
simulation output programs have been developed
with specific needs in mind and each utilize information provided from the central data base.
One of these output programs f o r the simulated
automatic countdown provides a listing of a l l
changes in status of each component throughout
the launch sequence selected. Tne countdown
time that i s associated with the status change i s
a l s o computed and printed out. Tnis simulation
with i t s associated print out provides information
which is useful in:
(a) Identifying the sequence of occurrence
of discrete events.
(b) Determining those time periods in which
numerous events occur.

( c ) Determining those time periods in which
critical events occur.
(d) Forming a basis for comparison with
actual prelaunch and launch data.
A simulation analysis program was also initiated during this time to evaluate the application
of continuous dynamic analysis methods and techniqnes. This effort included the utilization of a n
existing general purpose Dynamic Systems Analyzer P r o g r a m (DYNASAR), developed by the
General Electric Company. The primary purpose of t h i s effort was to demonstrate and evaluate DYNASAR a s a suitable dynamic simulation
tool. The example selected for this evaluation
was the s t a r t transients of the Saturn F-1 engine
propulsion system. Objectives were to:

(a) Evaluate the capability of DYNASAR for '
simulation of complex dynamic systems.

(b) Determine via a re;llistic example the
relationship between rimulation time and r e a l
time.
( c ) Evaluate the application of DYNASAR
for r e a l t h e test and evaluation of compler
space vehicle systemcl.

The concluaions a r r i v e d a t from thin effort
indicated that:
(a) This method was far from optimurn in
achieving r e a l time response. DYNASAR s a c r i fices time in that it paces itself to the smallest
response time i n the system.

(b) The accuracy of the simulation developed proved exceptionally good and a very c l o r e
correlation between simulation and actual t e s t
data was obtained.
(c) DYNASAR was capable of performing
the sophisticated vehicle systems simulation but
other numerical techniques may be m o r e advantageous.
Another element being evaluated for possible use a s a building block for the Aerospace
Venicle Simulation i s the F a s t Access t o Systems
Technical Information (FASTf) developed by
General Dynamics Convair. This i n essence i s
a computerized analysis program used for pin
pointing malfunctions logically and systematically.
The basic premise of the FASTI System i s that
the actual systems to be simulated operate i n a
logic and t i ~ sequence.
e
This then enables the
variables in discrete networks t o be described
by a s e t of Boolean logic equations. This methodology lends itself readily to the analysis of
Discrete Networks f o r the purpose of:
(a) Generating fault isolation data.
(b) Testing critical timing and sequence
considerations.
(,c) Testing the effects of engineering design changes.
'

This FASTI System is presently being utilized a s
a t e s t bed c a s e on the Saturn S-IC stage a t MSFC
a n a n Automatic Malfunction Analysis P r o g r a m
incorporated into the checkout activity.
Thus a s evidenced by the many fauceted
programs, relating to the Aerospace Vehicle
Simulation, the concept and feasibility of developing this powerful aid to Aerospace Vehicle
Checkout i s aound and built upon a versatile and
modular premise.

�Reauirements of the Simulation
Let us f i r s t summarize some general r e quirements which the users; i. e., checkout personnel, a r e demanding from the simulation eystern.
The u s e r wants t o be able to select any portion of the vehicle and its ground support equipment (GSE) and t o simulate it a t any defined level
of depth. The data he is using should correspond
t o the up-to-date hardware configuration which
he is simulating. Therefore, permanent and
temporary changes of the hardware have t o be
immediately reflected by the data base of the
simulation system. Modifications of the model
by deleting and/or adding subsystems and/or
parameters should be handled easily by the user.
He also wishes freedom in selecting and format-ting the outputs after imposing a variety of predetermined conditions on them. In o r d e r to obtain control of the simulation, the language for
man-machine communications has t o be readily
understood by the practical engineer. The simulatiod system has also to account for the possibility that several u s e r s may want to simulate
simultaneously the same system o r part of the
s a m e system from different locations. In e s sence, the simulation system has to be of a flexible and evolutionary structure.

(e) How does the u s e r operate the sirnulation system?
Thid l a s t question incorporates a number of additional easential questions:
(f) In which language does the uaer communicate with the simulation symtem?
(g) How does he select the portion of the vehicle he is interested in?

(h) What does he want to do with the output
signals which the simulation generates ?
(i) Who maintains and controls the data
base ?
We will t r y to answer the above questionm by
discussing the following a r e a s of the simulation
system:
(a) Modeling the vehicle

(b) Structure of the data base
(c) Processing of the simulation
(d) Language
(e) Control of data base

Some of the requirements demanded by the
u s e r have already led to the selection of the computer hardware system. Basically, what i s r e quired i s a large time-shared digital computer
with rapid access bulk storage capacity and r e mote input/output stations. A hybrid computer
system i s not readily adaptable for this simulation because the analog portion i s not able to be
time-shared and the wiring of i t s patchboard
cannot be changed a s rapidly a s a list in a digital computer.
In order to define m o r e specific requirements of the simulation.we may a s k ourselves
some basic questions t
(a) What do we want to simulate?
(b) How do we break down a system, which
is of the complexity of a space vehicle, into
functional blocks ?
(c) I-Iow do we mathematically represent the
functions of the blocks; i. e. , how do we s e t up
the mathematical model?
(d) How do we solve numerically the mathematical model equations ?

(f) Organization of simulation system
(g) Some special technical and human problem s
Modeling of the Vehicle

In our checkout work we a r e concerned with
the simulation of the internal functions of a space
vehicle; i. e.. we want to generate the time r e sponses of the continuous and discrete dynamics
of the equipment of the space vehicle. Using the
word "vehicle" implies also the ground support
equipment. We do not deal with the dynamics of
the rpechanical structure of the vehicle and the
flight trajectories except in basic form to close
the guidance and control loop of the vehicle.
A space vehicle may be considered a s a
large physical system which consists of a great
number of various types of subsystems and components.

�tion, while for a refined simulation tine continuour
dynamic characteristics have to be considered.

Table 1
Types af Syatema
Encountered in Space Vehicle Simulation

TYE!

Representing

Attitude Control
Systems

Electronic, Mechanical,
Electro-Mechanical

Navigation Systems

Electronic, Mechanical,
Electro-Mechanical

Propulsion Systems

Hydraulic, Electronic,
Mechanical. ElectroMechanical, Pneumatic

Emergency
- Detection
System

Electronic

Power Supply and
Distribution System

Electronic, Mechanical

Tracking Syetems

Electronic, Mechanical

Radio Command Systems

Electronic

In order to checkout a complete vehicle, it
i s broken into a set of rather independent functional system.8; e. g., the Instrument Unit. S-IVBstage,
etc. These systems can be further divided into subsystems; e. g., guidance and control,
propulsion, networks, etc. In checkout each subsystem i s first tested by itself before the interplay of a set of.subsystems, which forms a subsystem of the next higher level. i s tested. This
process of successively breaking down a subsystem into several subsystems of the next lower
level can be carried on until we reach the piecepart level.
Each subsystem may be thought of a s a functional block, which i s defined by its name, the
names of its inputloutput variables and the functional relationships between its input and output
variables. If two functional blocks a r e connected
in series the characteristic of each block must
not change; i. e.. the functional blocks have to be
decoupled and independent of load. This functional
relationship i s mathematically expressed by a set
of characteristic equations, For one hardware
subsystem there may be several functional blocks
defined, depending on the depth of the simulation,
F o r instance, the stabilized platform may be represented a s a first approximation by linear
transfer functions of low order, a more sophisticated model will include nonlinearities and high
order transfer functions. -4 mechanical valve may
be described by its on-off state and a discrete
pick-up and drop-out time for a cursory sirnula-

There a r e many ways to mathematically describe the functional relationships between the
input variables and output variables of a system.
We distinguish between several large categoriem
of systems: colrtinuous, discrete and combined
continuous /discrete systems. The continuow
systems can further be subdivided into linear and
nonlinear systems. Linear systems can be represented by Laplace transfer functions, impulw
responses, ordinary linear differential equation..
and state variables. Non-linear systems can be
described by a combination of Laplace transfer
functions or impulse responses and nonlinear
time-invariant functions, ordinary nonlinear differential equations, and state variables. A discrete system i s understood a s a system which
contains binary variables only; i. e. , on-off states
of relays. valves, switches, etc. The functions
a r e represented by Boolean equations associated
with pick-up and drop-out time, or by time-sequence tables. If a continuous system i s combined with a discrete system, threshold condition8
have to be considered. A change of state of a
discrete variable occurs when a threshold of a
continuous signal i s exceeded.
Depending on the number of variables of a
subsystem we a r e interested in, we might choose
a different mathematical representation of the
same subsystem. Consider for instance a linear
electrical filter. If this filter is part of a larger
system and the user is interested in the input and
output voltage only, he will represent the filter a s
one transfer function or impulse response. But
in the event he needs some test points inside the
filter, he will describe it by a block diagram of
several transfer functions or a set of differential
equations.
The design of an efficient model requires
skill and judgement on the part of the system
analyst and he has to know to what detail the simulation i s to be performed, in order to obtain valid
responses that match with the responses of the
real hardware. He also has to know whicn test
points a r e essential and have to appear a s output
variables of the functional blocks.
Structure of Data Base
The central data base shall contain all data
that a r e necessary to describe a vehicle; i. e..
the location, interconnections and functions of its
subsystems and components. Tinese data a r e
stored in a systematical way in a number of lists.
We distinguish between three basic data bases.

�namely the tlphysical data base", the "parameter
data base" and the "functional data base" (Fig. 1).
The "physical data base (PHDB)" is part of
the Configuration Management Accounting System,
which i s already partly in operation. and contains
the data that a r e necessary to manufacture the
hardware of a vehicle. It contains in generic o r der the Contract End Item (CEI) number, part
numbers. the location of parts within the equipment, wiring connections, physical dimensionr,
etc. It also includes "technological data"; e. g.,
the inductance of a coil, the elasticity of a spring,
etc.
The "functional data base (FDB)" contains
the characteristic equations which describe the
functions of components and subsystems. It constitutes the mathematical model of the hardware to
be simulated. Each functional block i s described
by a list of several items: name of block, input
and output variables, type of mathematical model,
characteristic equations andlor names and interconnections of functional blocks within this block.
Hence, a functiorial block might be expressed by
a s e r i e s of other functional blocks, which a r e inside this single biock and of successively lower
level. This scheme allo-vs the representation of
a system o r subsystem a s a single functional
block of any predetermined level of depth and with
any desired output variables. Also, for one hardware subsystem, there may exist several different
functional blocks to represent this subsystem.
Fig. 2 shows the various types of functional data
for continuous and discrete systems. There is
a string of lists of functional blocks o r only one
block to describe a system.
The "parameter data base (PDB)" contains
the algebraic equations which generate from the
technological data of the PHDB the functional
parameters of the characteristic equations of
the FDB.
In some cases there might be a close correspondence bet~veenthe technological parameters
and the parameters of the characteristic equations
describing the dynamics of the subsystem. For
instance, consider again the linear electrical filter. If this filter is represented by a set of first
o r d e r differential equations, the coefficients a r e
equal t o the values of the piece-parts (resistors.
coils, condensers). The configuration of the network i s expressed by the location of the coefficients within the system of differential equations.
Hence, there i s a one-to-one correspondence between the physical network and the elements of
the mathematical model. In this form the mathematical model might be quite readily generated
from the physical and technological data of the

system by the computer. But, if we represent
the same filter by a transfer function, the poles
and zeros of this function a r e obtained by arithmetic calculations between the vaiuer of the pieceparts. If one piece-part changes i t s value. ssve r a l poles and zeros have to 5s recalculated.
The three permanent basic data bases are of
extensive size and will be stored a s m a s t e r file
on magnetic disks.
P r o c e s sing of Simulation
During the processing of the simulation, 8eve r a l basic tasks have t o be performed which may
be classified as:
(a) Preparation of the simulation (pre-simulation)
(b) Numerical solution of the. mathematical
equations (airnulation run)
(c) Utilization of tne output signale (postsimulation)
Before the u s e r can s t a r t his simulation, he
has to select the system(s) he wants t o simulate.
There a r e two options to select the model which
represents the hardware system. The user may
call up only one functional block which may have
the same name a s the hardware system and contains a l l information about the system to the detail required and the inputlout put variables he i s
interested in. Thus, he i s not concerned with the
interconnections of internal functional blocks. In
case the user wants to build his own model, he
simply tells the computer whicn functional blocks
he wishes to use and how they a r e to be interconnected. The computer stores a list of a l l functional blocks versus the physical equipment. If
the user wants to know whicn functional blocks
a r e available, he specifies the equipment and r e ceives a print-out of all functional blocks, which
have been set up for the simulation of that particuIar equipment for several ievels of detail. He
tnen initiates an extraction of the lists of a l l functional blocks which a r e required for the simulation from the "master file" to an intern-ledlate
file, the "temporary filett. If he wants to make
some temporary changes for his simulation run
he can modify this file. He also specifies initial
conditions. Tine functional data a r e then compiled
and transferred to a "data working file", wnicil
serves a s data base for the subroutines t o solve
the mathematical equations.
Several subroutines for the numerical solution of the mathematical equations will be available. F o r the solution of differential equations;

�e. g. , Runge-Kutta, predictor-corrector and
power s e r i e s methods can be used. If the model
consists of a block diagram of transfer functions
of any order, subroutines a r e provided to reduce
these interconnected transfer functions to one
overall t r a n s f e r function and t o calculate the corresponding time function. Another subroutine
making u s e of the convolution works directly on
the block diagram after the transfer functions
have been transformed into weightirig functions.
The simulation of discrete dynamic systems r e quires the evaluations of Boolean equations for
which s e v e r a l approaches a r e kno~m.
Certain c r i t e r i a will be established upon
which a selection can be made a s to what type
of mathematical model will be solved by what
optimal numerical method. These crite,ria include stability of solution, computation speed,
accuracy, algebraic loops, handling of discontinuities, handling of systems with extremely
different time-constants and of specific types of
nonlinearities, storage requirements, etc. Each
functional block will have a designator attached,
which tells which numerical method i s recommended. Unless the u s e r overrides this bignator through a control statement and chooses
another mathematical method from the library,
the designated method will be used automatically.
During the actual simulation run; i. e. , wheri
the desired output signals a r e generated a t successive time steps; o r immediately after the
the output signals can further
simulation run;
be processed to generate the outputs a s outlined
previously. F o r exan~ple,the output signal may
he printed only if certain conditions a r e being
met (e. g.. certain voltage limits a r e exceeded).
Additional calculations on the output variables
may be performed (e. g., power consumption,
mean square e r r o r ) . Comparisons may be made
-.=iithpre-established values (e. g.. measured
values at t e s t points). The output values may be
o r d e r e d together with other items in listings.
F o r the output of data various types of peripheral
equipment may be selected (e. g. , printer, magnetic tape, graphical display). If the simulation
i s f a s t enough, the output signals may be sent
directly to hardware a s stimuli, o r hardware r e sponses may be compared in real-time.

Lf the u s e r wants to know the current status
of a subsystem without going through a simulation
run, he just calls up the natne of tne data base,
the names of the functional blocks and the statements ne i s interested in, and specifies the output format and output equipment.

Language
Sirice the system t o be simulated is specified
in t e r m s of functional blocks, a block-diagramoriented language which u s e s engineering type of
expression6 is to be strived for. Thereby. a
close correspondence between the model and the
computer input is guaranteed. Similar t o analog
simulation languages a s D S ~ f 9 0 MIMIC
,
etc.
the input format is divided into.independent segments; i. e.,
Connection statement*,
Data s tatementa

.

Procedural statements,
Control statements.
F o r setting up and changing the functional data
base a l l four types of statement8 will be used,
To prepare and execute h simulation run the
"procedural statements1' can be omitted.
The "connection statements" describe how
the functional blocks a r e to be connected with one
another to form the block diagram which r e p r e sents the model. The "data statements" specify
the values of the parameters and initial conditions.
The "procedural statements" describe the functional relationships between the input and output
variables. The "control statementsI1 contain a l l
the information to control the l a r g e variety of
inputs and outputs of the simulation and allow
some influence on the internal processing. F o r
ifistance, the u s e r can override certain automatic
control schemes for the selection of the numerical method.
All variables and parameters may be designated by any symbolic names, which can coincide
with those in engineering documentation. The
equations a r e written in their original mathematic a l form. No programming knowledge i s necesaary for the u s e r , a l l data a r e written in f r e e
form and only a few simple rules have t o be observed.
The language can easily be expanded by c r e a t i p of new functional blocks and new statements.
If the u s e r violates any of the simple formal rules
and/or if inconsistencies occur, the computer
will tell the u s e r where and what mistake has been
made.

�Control of Data Base
Before the simulation system can be put to
work, the permanent "functional data base" for
those physical systems, which a r e to be simulated, has t o be established. As the f i r s t step i n
the development of this data base, the documentation in form of schematics, characteristic charts,
reports etc., has to be studied by checkout and
design personnel to derive valid mathematical
models of-the desired different levels of depth
f o r the physical system considered. Through
this process the various functional blocks will be
determined. The functions of these blocks a r e
described by "procedural statements8' and/or
"connection statements".
Special control statements will initiate prog r a m s which aid the preparation of the functional
data base; e. g., an overall transfer function of
a block diagram of several t r a n s f e r functions
may be computed, o r the inverse -place transf o r m is determined, if the weighting function i s
desired.
The algebraic equations for the parameters
of the parameter data base a r e described by procedural statements which a r e headed by the names
of the functional blocks to which they belong. The
nomenclature of the technological parameters
must correspond to that of the physical data base,
and thk nomenclature of the functional parameters
to that of the data statements of the functional
data base.
After the validity of the models has been approved the statements which describe the various
functional blocks will be t r a n s f e r r e d to the permanent m a s t e r file of the functional data base by
u s e of control statements. To a s s u r e that only
approved data, which contain no e r r o r s a r e stored
in the m a s t e r file, special control schemes have
to be applied. T'he s a m e statements will be used
for the temporary file. In the same way the
parameter data base i s filled.

If a permanent design change occurs, i t is
located by i t s Contract End Item (CEI) number
and part number and initiated in the physical
data base. Along with the data statements of the
different data bases special control designators
a r e used, which allow a routing of changes from
the physical data base to the functional and parame t e r data bases. Hence, a change in the physical
data base i s immediately reflected to the other
data bases. If only the values of parameters
change the data statements in the functional data
base may be up-dated via tKe parameter data
base. However, if the configuration of the mathematical model i s modified the u s e r i s notified

by a flag, which tells him what has been changed
in the physical data base and he can then manually
rearrange his model. If the u s e r wants to improve his model he effects the functional and
parameter data bases only. '

A distinction i s made between permanent and
temporary changes. Permanent changes effect
the permanent data base in the m a s t e r file and
occur only, if a CEI engineering change has been
approved. The m a s t e r file has to be protected
against ertbneous changes by a system of controls.
These controls may be obtained by allowing only
one NASA office a t MSFC to write into the comput e r ' s m a s t e r file via a n individual transmission
line. All other u s e r s of the simulation system
would be able to read only from the m a s t e r file.
A record i s kept of a l l design changes together
with the name of the responsible official and the
date of change.
The temporary file i s not critical and needs
no permanent protection However, temporary
storage might be provided on magnetic tape o r on
cards.
The functional data in the bulk storage of the
magnetic disk will be grouped with respect to the
functional blocks. Each functions1 block will be
stored dynamically a t random in order to save
storage space and time. A f i i e d storage sequence
cannot be applied becatise the data base will be
continuously changing. An address book of the
functional block names versus their current s t o r age location can speed up the s e a r c h for a particulax b l o c k
Organization of Simulation System
In order to be able to expand the software
system a t any given phase of its development
and to modify i t easily, s o that it can meet the
most recent requirements, the simulation system
i's constructed of a number of operational building
blocks, called program modules. The interplay
of these program modules i s controlled by seve r a l monitors and an overall executive monitor.
The program modules perform specific processing functions; e. g., each input and output
function i s executed by a program module. F o r
each numerical method one module i s available
which can handle any size of the particular type
of equation for which the numerical algorithm i s
designed. Before the actual simulation run s t a r t s
the statements of the functional blocks and program modules for the computations a r e taken from
the m a s t e r file and temporary file, respectively,

�and compiled into tne "working file1*in c o r e memory, During the simulation r u n the wotking file
only is being used.
Already existing programs;e. g., the prog r a m s t o s i m u l a t e the d i s c r e t e dynamics of the
E l e c t r i c a l Support Equipment (ESZ-simulation of
GE), c a n be incorporated a s p r o g r a m modules.
a f t e r t h e f o r m a t of tineir data b a s e has been modified t o m e e t t h e specifications f o r the functional
d a t a base. The interfaces of t h e s e p r o g r a m s
have t o be a l t e r e d , s o tinat they c a n work with
t h e i r modified data b a s e and c a n be controlled by
t h e monitor.
Zach monitor is responsible f o r the control
of one m a j o r processing task: the input, tine output, t h e preparation of the simulation, the 8 imulation r u n and t h e maintenance of the data base
(Fig. 3). The executive monitor provides the
p r o p e r sequence of operations of tinese monitors.
Fig. 4 depicts a block d i a g r a m of the information
flow.
Special P r o b l e m A r e a s
During t h e development, a number of difficult but not insolvable problems will a r i s e .
Some of the outstanding problems s h a l l be outlined.
F o r the establishing of the functional data
base a tremendous amount of documentation nas
t o be reviewed and i t s status compared against
tne actual manufactured nardware. Many r e p o r t s
and s c h e m a t i c s a r e noT.vkept a t s e v e r a l laborat o r i e s and offices. Tney nave to be made a c c e s s i b l e to the personnel which s e t up tne mathem a t i c a l models. This means, tnat personnel from
outside a laboratory o r office a r e searching for
m a t e r i a l wnich normally is kept within tnat a r e a
of r e s p o ~ s i b i l i t yand 2ot readily available t o
outsiders. This imposes tne question, wno a r e
tne best men t o put tneir noses into other peo? l e t s business ? Tnis i s a human problem,
wnicn the C e n t e r ' s management ilas t o solve.
A group of s y s t e m analysists and checkout
e x p e r t s i n cooperation witn d e s i g n e r s must ext r a c t f r o m t ~ l epile of documentation tine information which is n e c e s s a r y to construct valid
mathematical models. During tnis p r o c e s s a l s o
tile functional blocks a r e specified. Theoretically, a model is valid i f it r e a c t s like the '
nardware wnicn is being simulated under the
s a m e environmental conditions; nowever, the
m e a s u r e d data a r e not always tne exact data.
i t is often subject t o noise, d r i f t and tolerances
of components inside t ~ equipment
e
and a r e
sonletirnes t h e r e s p o n s e s of a sligntly modified

configuration of hardware. Tinus. tne cornpariron
of tne responses of tne model witn the response.
of the actual hardware involves Some judgement
upon which not all p a r t i e s will always agree.
Often various factors a r e neglected i n o r d e r t o
obtain a model of reasonable c l e a r n e s l . Tnc deg r e e of such a simplification may cause disputer
among the experts.
The human problem of "wno is responsible
f o r tine control of changes within the permanent
data base1', nas been mdntioned already. But
t n e r e is a l s o a technical problem of now t o r e t r i e v e data from the bulk s t o r a g e devices with
reasonable speed and a t t h e s a m e t i m e have tire
ability to change tne configuration of t n e d a t a
bases continuously and rapidly. Tne g r e a t variety of possible outputs of the simulation. the
linking togetner of the t h r e e data bases, tne
insertion of new functional blocks into the data
base etc.. a l l t h e s e many scnemes which m a k e
tine s y s t e m s o flexible. c r e a t e on the otner nand
requirements f o r intricate sorting routines,
control indicators and control l i s t s (e. g. a d d r e s s
lists, c r o s s reference lists, etc. ).

.

F o r the n a m e r i c s l solution of differential
equations and t r a n s f e r function block d i a g r a m s
a variety of methods have been published, but no
clear-cut explanation is given a s t o wnich d i s tinctive s y s t e m of matnematical equations each
method might be applied favorably. There a r e
s e v e r a l c r i t e r i a (e. g. , computational speed,
storage requirements, stability, etc. ) upon
which a metnod has to be judged. The quality
of a metnod depends a l s o on the type of input signals (discontinuous, oscillatory signals, etc. )
used. Kevertheless, s o m e kind of catalogue has
to be establisned which tells qualitatively t h e
trade-offs of the different methods for tne various
types of s y s t e m s of equations. Tnis evaluation
has to be done in cooperation with numerical
mathematicians.
The simulation system witn its c e n t r a l data
bank will be in operation on a l a r g e time-shared
digital computer. When s e v e r a l u s e r s want t o
r u n a simulation a n d / o r tne c e n t r a l p r o c e s s o r is
already occupied witn otner programs, s e v e r a l
o r a l l simulation runs may be interrupted and,
nence, the simulation may be intolerably delayed.
In o r d e r to give precedence t o urgent simulations.
a priority scneme nas t o be worked into the simulation system. Tnpse simulations wnich a r e connected to hardware for real-time operation o r
which use on-line graphical displays have a
higher priority tnan tnose simulations wnicn a r e
lengtny and u s e a printer o r c a r d punch as output
equipment. If the r e s u l t s of a lengtny simulation
a r e t o be displayed on a n on-line r e m o t e graphical

�console tne r e s u l t s have to be buffered in a memory. 'Vhen the simulation i s finished, a rignal
from the p r o c e s s o r t o the console i s sent, to tell
the u s e r that he may c a l l the r e r u l t s for display.
This scheme prevents the u s e r from staring a t
the TV tube and waiting nervously for the end of
the simulation run.
The present digital computers a r e already
s o fast a s t o allow real-time simulations in many
c a s e s , where the time constants a r e not too small.
Tne appearance of even f a s t e r digital computers
on the m a r k e t in the near future lead us to believe,
that much m o r e real-time applicatians of the
simulation will be seen. Since the computation
t h e of the processor during a simulation run
never a g r e e s precisely with r e a l time the results
nave to be s t o r e d in a buffer before they a r e r e leased by a clock a t the exact time. If several
real-time simulations a r e allowed, the priority
and clock control scneme gets quite sopnisticated.
Semi-real-time simulation may be performed by
storing the output signals of a simulation run on
magnetic tape. This tape may tnen be run in
synchronous with the hardware and the r e a l time
responses compared with tne results on the tape.
The signals on the tape may a l s o be used a s realtime stimuli to the hardware.
The development and implementation of the
simulation system requires quite a large amount
of effort for a team of skilled people, who a r e
experts in different but related fields such a s syst e m s engineering, electrical and mecnanical
engineering, numerical matr,err.atics and computations, and s y s t e m s programming. This effort
s e e m s to be justified already solely by the impact on the inlprovement of checkout of space
vehicles, nowever, a m o r e wide-spread usage
by design engineers and management of several
other laboratories and offices can be foreseen,
which would make the need of the simulation system even more oivious. In o r d e r to familiarize
then1 witn tne advantages of the digital simulation, tile differelit t&gt;-pes of future users nave to
be educated 5). \\el1 prepared seminars and
smoot~llyreadable docurrient2ltion. Tine u s e r nas
to be convinced tnat the simulation system i s a
powerful tool, by ivhicn laborious and tedious
routine work can be eliminated and tnus, f r e e
him for creative engiceeriny activities. He.
thereby, can abandon his f e a r tnat the computer
mignt s t e a l away work for wnicn he was trained.
As outlined prei-ious1;-, the simulation system
i s constructed of n:any ratner self-contained
p a r t s ; i. e.. program r~:odules. monitors and
lists. .\ judicious decision *as to be made.
which partE nave,to be designed first, in o r d e r
to obtain a functioning, ti~ocgn,limited simula-

tion system, Thore parts, wnicn a r e moat easential to perform the pilot implementation will
be selected. Several operation. wnicn may be
handled automatically in a later pnase, will be
done manually a t the beginning. F o r instance.
the parameter data J a r e may be omitted a t firat.
The parameters for the data statements in tne
functional blocks may be derived manually from
the documentation. Thus, the simulation system
can evolve gradually from a relatively simple
to a more and more sophisticated tool.
Implementation

In order to develop and produce tae Aerospace Vehicle Simulation, to provide management, operations planners. design engineers
and naturally the checkout specialists with t n i s
powerful, versatile, computerized simulation
tool---a pilot implementation program was inaugurated.
This pilot implementation program will produce the modular simulation programs a s previously discussed capable of performing both
dynamic and discrete simulation functions for
selected systems of the Saturn V Instrument
Unit and tne Saturn S-IVB Stage a s related to
post manufacturing cneckout. The operational
computer programs, methods and tecnniques
developed in tnis pilot implementation will be
part of the fully developed Aerospace Venicle
Simulation. This pilot implementation will be
designed and programmed to include: a matnematical model of tne selected portions of tne
Kavigation and Control systems; tne simulation
data base, and the computer programs to provide a realistic simulation of tne selected IU and
S-IVB systems and related GSE. Tne system of
primary interest in the pilot implementation will
be the Guidance and Control system, since tnis
will cover a l l major types of simulation c a s e s
desired in any type vehicle; i. e. guidance,
control, propulsion. etc. whicn will be simulated in sufficient detail to accurately describe:
navigation signal sensing, propulsion system
sensing. J-2 engine positioning, engine(s) s t a r t stop. Elements such a s communications, command systems, Launcn Control Computer. engine dynamics and missile dynamics wilI be included in simplified form to close a l l loops but ,
only to the extent tney affect guidance and control.

.

This pilot implementation will provide tnree
basic levels of deptn, wnicn can naturally be
expanded later. These levels of deptn of simulation are:

�.

(a) The overall system; e. g. Guidance
and Control System considered a s a single
functional block.
(b) The subsystem, described a s an individual definable subsystem of the overall Guidance
and Control System; e. g.. Inertial Stabilizer.
Flight Control Computer, etc.

a r e met. F o r example, the upcoming Saturn
Apollo Application Program. tinis simulation
system could be used by experimenters and designers to select, design and evaluate the experiments t o be flown: to tne integration personnel it
would provide them with the information and ass i s t them in the job of integrating and checking
out these experiments in the modified space venicle.

(c) Functional loops withitl a specified subsystem, t o the amplifier level; e. g., X, Y, o r 2.
gyro loop. P, Y, o r R loop.
The space vehicle systems included in tnis
pilot implementation provide linear and non-.
linear differential equations, transfer functions
and d i s c r e t e functions of sufficient complexity
and variety t o properly t e s t computer programs,
methods and techniques.
The Vehicle Systems Checkout Division of
Quality and Reliability Assurance Laboratory, i n
cooperation with the Computation Laboratory of
IGSFC have been jointly developing the Aerospace
Vehicle Simulation Program. Marshall Space
Flight Center i s in tne process of obtaiding third
generation computer equipment and plans to nave
i t in operation before the end of 1967 with the intent of consolidating tne e n t e r ' s computer r e s o u r c e s into a centralized time sharing system
with remote input/output terminals. Tnis third
generation corr.puter system will provide the
.\erospace Venicle Simulation Program with the
necessary hardware equipment in regards: to
memory capacity, speed of operation, peripneral
equipment, remote stations to expand the pilot
i~xplernentationof the Saturn's-IVE and Instrument Unit Stages to tke simulation of the Total
Saturn l p o l l o Vehicle and associated GSE. Tnis
would include a l l vehicle systems to tne levels
of sophistication o r degree of simulation a s previously 6iscussed in this paper. This system
then wrould not only be available to one laboratory
but throughout the Center for designers, experimenters, planners, configuration managers,
checkout specialists, etc. a l l elements working
f r o m the s a m e central data storage area; i. e..
many types of updated data bases, and times n a r e d for the many and d r i e d simulation.
management o r monitor functions c a r r i e d out by
?..ISFC.

.

Xlti?ough the full in~plementationof the Aerospace 1-ehicle Simulation i s directed towards the
Saturn -L.pollo Vehicle, the logic o r programs
will 5e capable of processing otner configurations
provided tnat tnese configurations a r e described
by a properly structured data base. The simulation Can directly apply t o any and every prog r a m provided data base formats and information

Concluoion
As a natural fall-out of this program, tne
Aerospace Vehicle Simulation could become tne
conceptual stahdard tinrough which any new s y s tern o r innovation must be demonstrated. This
tinen would enable NASA, and any contractor o r ganization, t o determine the a ~ c e p t a b i l i ~ i a n d i i ~ d
limitations of any proposed system and/or innovation prior to actual hardware development. The
extension of tinis concept into future aerospace
programs such a s the AAP (Apollo Applications
Program). the S-IVB Workshop, the Mars Fly-by
Missions, etc. will provide the most consolidated
source of reliable information and the means t o
evaluate and determine optimum systems functional criteria. Tinus a s outlined in this brief the
eventual use of this Aerospace Vehicle Simulation
will greatly benefit a l l d)sciplines and will be
limited only by the imagination of the u s e r s and
the foresight of its designers.
References
1. "Tie General Functional Relationsilip
Langdage System" Report. June. 1964. p r e p a r e d
under h;SFC contract liAS8-11027 hy Brown Engineering Company. Huntsville, Alabama and R. W.
Foster, R-QUAL, MSFC. NASA.
2. "A(iode1ing of Space Venicle Component
Dynamics Using a Digital Differential Analyzer
;.r:etnod", MTP-QUAL-63-2. October, 1963.
Prepared by Richard W. Foster and C a r l Webster.

MSFC. NASA.

le
3. "Analytical Study of Launcn V e ~ ~ i cComponent Level Simulation" Final Report, Decem5er.
1965. Prepared under LMSFCcontract N A S ~ - ~ O O ~ D ,
h , i S ~ cby ~ ~ 0 1 Support
10
Department. General
Electric Co. , Daytona Beach, Florida.
4. "Requirement Specification P a r t I and
Analysis of Dynamic Siinulation Methods f o r
Launcn Ve nicle Component Level Simulation"
Final Report, h:arcn, 1966. P r e p a r e d under
:,:SFC contract j~AS8-ZO060mod 1 by Apollo
Support Department. General Electric Company.
Daytona Beach. Florida.

�5. "Simulation of Selected Discrete Networks" Phase I Final Report, 3 volumes. October,
1965. P r e p a r e d under XSFC contract NASS20016 by General Dynamics Convair Division,
Huntsville. Alabama.

6. "ESE Simulation" Tecnnical Report,
h:ay. 1965. P r e p a r e d under NASA contract
KASw-410 by Apollo Support Department. General
Zlectric Company. Daytona Beach. Florida.
7. "DYNASAR Simdl3tion of the Saturn F-1
Engine Propulsion System: July, 1965. P r e p a r e d under NASA contract NASw-410 by Apolla
Support Department. General Electric Company.
Huntsville. Alabama.

-

8. I1DSL/9O A Digital Simulation P r o g r a m
for Continuous System '.;odeling. " by W. M. Syn
and R. N. Linebarger Proceedings of Spring
Joint Computer Conference, 1966, Vol. 28,
Spartan Books, Washington, D. C. pages 165187.

-

.

- Digital Simulator Program"
9. "%.E.;IMIC
by F. T. Sansom and H. E. Petersen. SESCA
Internal bIemo 65-12, Wright-Patterson Air
Force Base. Ohio, Kay. 1965.
10. "The :.:onitoring Task in Automated
Checkout of Space Vehicles". September. 1965.
P r e p a r e d under KAS-1 contract X-4Sr-21 by
L. Chesler and R. Y'ur~'. iiand Corporation,
Santa Xonica. California.
11. "Growth of Automation in Apollo P r e launch Checkout: Vol. 11. Added Roles". July,
1964. P r e p a r e d under K-XSX contract NASr-21
by L. T. L a s t , L. D. Amdahl. 0. T. C-atto.
a r d A. A. B. F r i t s k e r . Xand Corporation.
Santa \ Ionica. California.
12. "Computer-Assisted Countdown: P r e l i minary Report on a Test of Zarly Capability".
ay 1965. F r e p a r e d urder S I S A contract
?&lt;ASr-Zl b)- 3 . :
Orezner a:ld 0.T. Gatto.
Xand Corporation. Santa :.onica. California.

..

�m

W

.

Pig. 1

.

..

Al~cilwniccr,~mtions
rc1nt:ng t c c ! \ n o l o ~ i c n l
cia:a of Pi!l)!'l with paramrtcrs of c h n r a c t c r i s t i c
equ:i t i 0ns of I:l)I;, e g
polcs am1 zcros of
tmnsfcr fclction i n
t e r n oi \ r a l ~ c sof conponcnts

.

L i s t of f u n c t i o n ~ l
i~locks, i c., f o r each
functionnl 1)lock
connection s t a t c m n t s ,
ciaTa s t n t c ~ c n t s ,
y r o c ~ ~ l u r c ststcncnts
il
,
control s t n t c m n t s .

Types of d a t a i n t h c tllrec b a s i c d a t a bases.

Technological &amp;tn, c . ~ .
values o f comonents,
p r o p c r t i c s of l i q u i d s ,

Intcrconncctions (wiriny,)
of c o v o n e n t s and equipmnt.

Location of p a r t s a d
components \r'i t h i n LXI

Part Nmbers w i t f l i l l
Contract End Itcm (CEI)

etc.

or

Fig. 2 Various types o f frmctional data for continuous and
d i s c r e t e systems.

Uoalcan equations, p i c k - u p / d t g - o u t time, t l ~ r c s h a l dlimits

number s e r i e s o f impulsc rcspanse
or
or

type .and c o e f f i c i e n t s of impulse response

polcs, zcros, r u l t i p l i c i t v and gain f a c t o r o f t r a n s f e r
f~mction

dcgrcc and c o e f f i c i e n t s of d i f f e r e n t i a l equations

or

or

or

d i s c r e t e s i g n a l s f o r DSB)

(continuous and/or d i s c r e t e sign&amp;
*Yq ( c o n t i n u o ~ ss i g n n l s f o r CSB,

0%

D I S C E n SIGNAL BLOCK

n a m s and i n t e r c o n n c c t i m s o f functional blocks

TYPE of mathematical model

xZ\ES of output v a r i a b l e s Y,

XVES of input v a r i a b l e s X,

NR'E OF block

CC)N'TNUnUS SIGNAL DLCCK

�I
i

I

OUI'I'UT :'it1 O!&lt;I'iY COS'l'ltnl,LIiR

b

r

I

1:xccutcs tllc nutnuts on
tlic various output cqiiipment

Prcpnrcs tlic f o m t f o r
various o~~t!lurson:
crwpl~icnldisplay, p r i n t c r ,
t c l c t ) ~ c r ,ync!i cards,
mqpctic t a p

I

I

i

.

I

I.SI'R\CT I OI! :'ROCI:SSnR

I n s e r t s i n i t i a l conditions
i n t o work in^ f i l e

Conpilcs functional data
nnd p-o,clrarn rradulcs from
tcnporary f i l e t o working'
filc

1:xtracts proflam modules f o r
t!lc c o r ~ u t n t i o n sfrom m s t c r
f i l e t o :c~porary f i l c

I

1 : x t n c t s functional I&gt;locks
from m s t c r f i l c t o tcmporar)f f i l c

!ltVI'~'i

Scnds rcol- time signals t o
hardware

Accepts r e a l - t i n t s i g n a l s
o f hardware

Fig. 3 Schenatic anmgcmcnt o f t h c s t r u c t u r e of t l ~ csimulation systcm

OUTPUT STGSr\I. PROCIISSOI1

INPUT SI(;NIIL PROCCSSOR

I

alccks f o r f o m n l e r r o r s
and inconsistcncics ,in uscrk
langungc

ERROR LUCCI PIOCESSOI1

~Zcccptsand dccodcs u s e r ' s
rcqucst mcl d a t a f o r sinulat i m , t c v o r a r y ,md 7crr.ancnt chnngcs of f u n c t i o ~ l a l
d a t a hase

I

b

. E l e c t s inputt c h w n c l s with ,
S c l c c t s output chnnncls
regard t o t h e i r p r i o r i t y
with rcqnrcl t o t h e i r
priority

1 5 ~ f PRIOIII'IY
l
COSI'L~OI.~.T.R

coorJi:lation of
r!oni t o r s

Supplies data f o r l i s t i n z s
and p l o t s , i,c., a d d i t i o n a l
computations with output
s i m a l s and/or e x t r a c t ion
of non-functional data from
d a t a base

OUTPUT SIGVAL COhTIIOLLER

I

Imposes conclitions ( l i m i t s )
and/or comparisons on output s i g n a l s

Gcncratcs output s i g n a l s of
mrithcnatical nodel

RUN
, \ION I'I'OR

. SIfULATInN

I

I

I
Transfers d a t a f o r combarison with simulation
butputs t o temporary data
file

I

I
1

Supplies data f o r output
l i s t i n s s o f d a t a chances

I

I

~COFPARISOKDATA PROCESSOR

I

I

functions f o r functional
blocks

I n s e r t s tcmpornry changes
i n t o tcmpornry r i l e

'ff i'lPOIMRY CI IAYGI! PROCESSOR

II

I n s e r t s p c m n e n t cliangcs
i n t o master f i l c

Checks t h e ,authorization
for pCmncnt data changes

DATA RASE
SKXVIrnR

�FIG. 4

BLOCKDIAGRAM OF INFORMATION FLOW IN SIMULATION SYSTEM.

----CONTROL

FLOW

DATA FLOW FROM AND TO MEMORY
OTHER DATA FLOW

-

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="17963">
                <text>spc_stnv_000050</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17964">
                <text>"Aerospace Vehicle Simulation and Checkout."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17965">
                <text>Paper by J. W. Moore and  J. R. Mitchell, Quality &amp; Reliability Assurance Laboratory, Marshall Space Flight Center, and H. H. Trauboth, Computation Laboratory, Marshall Space Flight Center. The paper summary notes, "The advancement of the space age into increasingly complex and ambitious missions requiring the development and operation of more sophisticated and intricate launch vehicles has generated numerous problem areas. The purpose of this paper is to define the Aerospace Vehicle Simulation; discuss the relationship of this simulation to the major problem areas of checkout; describe the development and implementation of this simulation system; indicate multidiscipline applications to present and future programs."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17966">
                <text>Mitchell, J. R.</text>
              </elementText>
              <elementText elementTextId="17967">
                <text>Moore, J. W.</text>
              </elementText>
              <elementText elementTextId="17968">
                <text>Trauboth, H. H. </text>
              </elementText>
              <elementText elementTextId="17969">
                <text>George C. Marshall Space Flight Center</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17970">
                <text>1966-04-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="17971">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17972">
                <text>Saturn Project (U.S.)   </text>
              </elementText>
              <elementText elementTextId="17973">
                <text>Space vehicles--Testing--Computer simulation</text>
              </elementText>
              <elementText elementTextId="17974">
                <text>Space vehicle checkout program  </text>
              </elementText>
              <elementText elementTextId="17975">
                <text>Computerized simulation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17977">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="17978">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="17979">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="17980">
                <text>Box 17, Folder 9</text>
              </elementText>
              <elementText elementTextId="205759">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17982">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17983">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="17984">
                <text>spc_stnv_000027_000050</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1014" public="1" featured="0">
    <fileContainer>
      <file fileId="855">
        <src>https://digitalprojects.uah.edu/files/original/40/1014/uah_uahp_000362.pdf</src>
        <authentication>35650b051428a6474ae506504bceb71a</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177226">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18202">
                <text>uah_uahp_000362</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18203">
                <text>1992 Pi Kappa Alpha homecoming float.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18204">
                <text>The float is parked on the side of Ben Graves Drive.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18205">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18206">
                <text>1992-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18207">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18208">
                <text>College students</text>
              </elementText>
              <elementText elementTextId="18209">
                <text>Greek letter societies</text>
              </elementText>
              <elementText elementTextId="18210">
                <text>Student activities</text>
              </elementText>
              <elementText elementTextId="18211">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31380">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31920">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18212">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18213">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18214">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18215">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205760">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18217">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18218">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18219">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1015" public="1" featured="0">
    <fileContainer>
      <file fileId="856">
        <src>https://digitalprojects.uah.edu/files/original/40/1015/uah_uahp_000363.pdf</src>
        <authentication>112ada0e24f008e338b5b4d8594b6630</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177227">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18220">
                <text>uah_uahp_000363</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18221">
                <text>UAH spirit display at 1992 Homecoming festivities.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18222">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18223">
                <text>1992-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18224">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18225">
                <text>College campuses</text>
              </elementText>
              <elementText elementTextId="18226">
                <text>Student activities</text>
              </elementText>
              <elementText elementTextId="18227">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31381">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31921">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18228">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18229">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18230">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18231">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205761">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18233">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18234">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18235">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1016" public="1" featured="0">
    <fileContainer>
      <file fileId="857">
        <src>https://digitalprojects.uah.edu/files/original/40/1016/uah_uahp_000364.pdf</src>
        <authentication>0a4e23d1fcaa83977cb81486abc5eb83</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177228">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18236">
                <text>uah_uahp_000364</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18237">
                <text>1992 Pi Kappa Alpha homecoming float at Spragins Hall.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18238">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18239">
                <text>1992-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18240">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18241">
                <text>College campuses</text>
              </elementText>
              <elementText elementTextId="18242">
                <text>College students</text>
              </elementText>
              <elementText elementTextId="18243">
                <text>Greek letter societies</text>
              </elementText>
              <elementText elementTextId="18244">
                <text>Student activities</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18245">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18246">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18247">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18248">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205762">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18250">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18251">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18252">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1017" public="1" featured="0">
    <fileContainer>
      <file fileId="858">
        <src>https://digitalprojects.uah.edu/files/original/40/1017/uah_uahp_000365.pdf</src>
        <authentication>ad987d4c3630d8aa5e0e81ca82c03247</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177229">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18253">
                <text>uah_uahp_000365</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18254">
                <text>UAH mascot interacting with fans at the 1992 Homecoming bonfire.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18255">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18256">
                <text>1992-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18257">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18258">
                <text>College students</text>
              </elementText>
              <elementText elementTextId="18259">
                <text>School mascots</text>
              </elementText>
              <elementText elementTextId="18260">
                <text>Student activities</text>
              </elementText>
              <elementText elementTextId="18261">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31382">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31922">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18262">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18263">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18264">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18265">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205763">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18267">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18268">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18269">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1018" public="1" featured="0">
    <fileContainer>
      <file fileId="859">
        <src>https://digitalprojects.uah.edu/files/original/40/1018/uah_uahp_000366.pdf</src>
        <authentication>8e92f1e51663eeb6b886958641987b90</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177230">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18270">
                <text>uah_uahp_000366</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18271">
                <text>Matt Iley is crowned 1990 Homecoming King.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18272">
                <text>Iley was crowned at a UAH hockey game against the University of Alaska at Fairbanks. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18273">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18274">
                <text>1990-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18275">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18276">
                <text>Iley, Matt</text>
              </elementText>
              <elementText elementTextId="18277">
                <text>College students</text>
              </elementText>
              <elementText elementTextId="18278">
                <text>Student activities</text>
              </elementText>
              <elementText elementTextId="18279">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31383">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31923">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18280">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18281">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18282">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18283">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205764">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18285">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18286">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18287">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1019" public="1" featured="0">
    <fileContainer>
      <file fileId="860">
        <src>https://digitalprojects.uah.edu/files/original/40/1019/uah_uahp_000367.pdf</src>
        <authentication>d9f1fb16f610af9e1fc9a405afce62b7</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177231">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18288">
                <text>uah_uahp_000367</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18289">
                <text>1990 Homecoming King Matt Iley and Queen Julie Preston.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18290">
                <text>Preston and Iley were crowned at a UAH hockey game against the University of Alaska Fairbanks. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18291">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18292">
                <text>1990-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18293">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18294">
                <text>Iley, Matt</text>
              </elementText>
              <elementText elementTextId="18295">
                <text>Preston, Julie</text>
              </elementText>
              <elementText elementTextId="18296">
                <text>College students</text>
              </elementText>
              <elementText elementTextId="18297">
                <text>Student activities</text>
              </elementText>
              <elementText elementTextId="18298">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31384">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31924">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18299">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18300">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18301">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18302">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205765">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18304">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18305">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18306">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1020" public="1" featured="0">
    <fileContainer>
      <file fileId="861">
        <src>https://digitalprojects.uah.edu/files/original/40/1020/uah_uahp_000368.pdf</src>
        <authentication>9102e3e740155d1b0a6cbf8315e14dd7</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177232">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18307">
                <text>uah_uahp_000368</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18308">
                <text>1990 Homecoming court posing with interim president Joe Moquin.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18309">
                <text>Moquin is shown at left. Homecoming King Matt Iley and Queen Julie Preston are shown at center. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18310">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18311">
                <text>1990-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18312">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18313">
                <text>Iley, Matt</text>
              </elementText>
              <elementText elementTextId="18314">
                <text>Moquin, Joseph C. </text>
              </elementText>
              <elementText elementTextId="18315">
                <text>Preston, Julie</text>
              </elementText>
              <elementText elementTextId="18316">
                <text>College students</text>
              </elementText>
              <elementText elementTextId="18317">
                <text>Student activities</text>
              </elementText>
              <elementText elementTextId="18318">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31385">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31925">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18319">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18320">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18321">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18322">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205766">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18324">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18325">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18326">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1021" public="1" featured="0">
    <fileContainer>
      <file fileId="862">
        <src>https://digitalprojects.uah.edu/files/original/40/1021/uah_uahp_000369.pdf</src>
        <authentication>8eb92bd2b984e947c697f19a8309acc9</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177233">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18327">
                <text>uah_uahp_000369</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18328">
                <text>Members of 1991 Homecoming court.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18329">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18330">
                <text>1991-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18331">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18332">
                <text>College students</text>
              </elementText>
              <elementText elementTextId="18333">
                <text>Student activities</text>
              </elementText>
              <elementText elementTextId="18334">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31386">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31926">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18335">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18336">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18337">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18338">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205767">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18340">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18341">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18342">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1022" public="1" featured="0">
    <fileContainer>
      <file fileId="863">
        <src>https://digitalprojects.uah.edu/files/original/40/1022/uah_uahp_000370.pdf</src>
        <authentication>42ea3034e8aa78ee7572d27205e52175</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177234">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18343">
                <text>uah_uahp_000370</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18344">
                <text>1991 Homecoming King and Queen.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18345">
                <text>1990 Homecoming King Matt Iley is seen in the background. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18346">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18347">
                <text>1991-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18348">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18349">
                <text>Iley, Matt</text>
              </elementText>
              <elementText elementTextId="18350">
                <text>College students</text>
              </elementText>
              <elementText elementTextId="18351">
                <text>Student activities</text>
              </elementText>
              <elementText elementTextId="18352">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31387">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31927">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18353">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18354">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18355">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18356">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205768">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18358">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18359">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18360">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1023" public="1" featured="0">
    <fileContainer>
      <file fileId="864">
        <src>https://digitalprojects.uah.edu/files/original/40/1023/uah_uahp_000371.pdf</src>
        <authentication>3e5b857b3da5266d8b15107f1e941412</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177235">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18361">
                <text>uah_uahp_000371</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18362">
                <text>UAH mascot interacting with fans at the 1987 Homecoming hockey game against Ohio University.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18363">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18364">
                <text>1987-02-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18365">
                <text>1980-1989</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18366">
                <text>College sports</text>
              </elementText>
              <elementText elementTextId="18367">
                <text>College students</text>
              </elementText>
              <elementText elementTextId="18368">
                <text>School mascots</text>
              </elementText>
              <elementText elementTextId="18369">
                <text>Student activities</text>
              </elementText>
              <elementText elementTextId="18370">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31388">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31928">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18371">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18372">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18373">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18374">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205769">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18376">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18377">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18378">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1024" public="1" featured="0">
    <fileContainer>
      <file fileId="865">
        <src>https://digitalprojects.uah.edu/files/original/40/1024/uah_uahp_000372.pdf</src>
        <authentication>d0c0f34845496405b3fdffbe049c0f97</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177236">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18379">
                <text>uah_uahp_000372</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18380">
                <text>Hockey referee initiating the 1987 Homecoming game against Ohio University.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18381">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18382">
                <text>1987-02-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18383">
                <text>1980-1989</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18384">
                <text>College sports</text>
              </elementText>
              <elementText elementTextId="18385">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31389">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31929">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18386">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18387">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18388">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18389">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205770">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18391">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18392">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18393">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1025" public="1" featured="0">
    <fileContainer>
      <file fileId="866">
        <src>https://digitalprojects.uah.edu/files/original/40/1025/uah_uahp_000373.pdf</src>
        <authentication>a69a16ede78faa346816166d4c7f9d73</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177237">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18394">
                <text>uah_uahp_000373</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18395">
                <text>1987 Homecoming hockey game against Ohio University.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18396">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18397">
                <text>1987-02-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18398">
                <text>1980-1989</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18399">
                <text>College sports</text>
              </elementText>
              <elementText elementTextId="18400">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31390">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31930">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18401">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18402">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18403">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18404">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205771">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18406">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18407">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18408">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1026" public="1" featured="0">
    <fileContainer>
      <file fileId="867">
        <src>https://digitalprojects.uah.edu/files/original/40/1026/uah_uahp_000374.pdf</src>
        <authentication>138350bd46ef0b957df721659383c761</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177238">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18409">
                <text>uah_uahp_000374</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18410">
                <text>Fans at the 1987 Homecoming hockey game against Ohio University.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18411">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18412">
                <text>1987-02-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18413">
                <text>1980-1989</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18414">
                <text>College sports</text>
              </elementText>
              <elementText elementTextId="18415">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31391">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31931">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18416">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18417">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18418">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18419">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205772">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18421">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18422">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18423">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1027" public="1" featured="0">
    <fileContainer>
      <file fileId="868">
        <src>https://digitalprojects.uah.edu/files/original/40/1027/uah_uahp_000375.pdf</src>
        <authentication>67d896f0c9bf7bcc74e58ade665c0b53</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177239">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18424">
                <text>uah_uahp_000375</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18425">
                <text>Fans at the 1987 Homecoming hockey game against Ohio University.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18426">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18427">
                <text>1987-02-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18428">
                <text>1980-1989</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18429">
                <text>College sports</text>
              </elementText>
              <elementText elementTextId="18430">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31392">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31932">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18431">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18432">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18433">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18434">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205773">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18436">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18437">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18438">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1028" public="1" featured="0">
    <fileContainer>
      <file fileId="869">
        <src>https://digitalprojects.uah.edu/files/original/40/1028/uah_uahp_000376.pdf</src>
        <authentication>ec4d24ea4e7c84d66c7e4663f377a5cc</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177240">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18439">
                <text>uah_uahp_000376</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18440">
                <text>1987 Homecoming reception.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18441">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18442">
                <text>1987</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18443">
                <text>1980-1989</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18444">
                <text>College students</text>
              </elementText>
              <elementText elementTextId="18445">
                <text>Student activities</text>
              </elementText>
              <elementText elementTextId="18446">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31393">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31933">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18447">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18448">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18449">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18450">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205774">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18452">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18453">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18454">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1029" public="1" featured="0">
    <fileContainer>
      <file fileId="870">
        <src>https://digitalprojects.uah.edu/files/original/40/1029/uah_uahp_000377.pdf</src>
        <authentication>36638f0b497c2473de19a94ac37d3a8b</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177241">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18455">
                <text>uah_uahp_000377</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18456">
                <text>Band playing at 1987 Homecoming reception.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18457">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18458">
                <text>1987</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18459">
                <text>1980-1989</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18460">
                <text>College students</text>
              </elementText>
              <elementText elementTextId="18461">
                <text>Student activities</text>
              </elementText>
              <elementText elementTextId="18462">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31394">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31934">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18463">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18464">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18465">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18466">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205775">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18468">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18469">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18470">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1030" public="1" featured="0">
    <fileContainer>
      <file fileId="871">
        <src>https://digitalprojects.uah.edu/files/original/40/1030/uah_uahp_000378.pdf</src>
        <authentication>c16c3f503d4bea285b25335fce54f557</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177242">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18471">
                <text>uah_uahp_000378</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18472">
                <text>Couple at the 1987 Homecoming reception.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18473">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18474">
                <text>1987</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18475">
                <text>1980-1989</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18476">
                <text>College students</text>
              </elementText>
              <elementText elementTextId="18477">
                <text>Student activities</text>
              </elementText>
              <elementText elementTextId="18478">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31395">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31935">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18479">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18480">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18481">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18482">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205776">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18484">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18485">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18486">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1031" public="1" featured="0">
    <fileContainer>
      <file fileId="872">
        <src>https://digitalprojects.uah.edu/files/original/40/1031/uah_uahp_000379.pdf</src>
        <authentication>ef48af44538551aeac415e41daeed9f0</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177243">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18487">
                <text>uah_uahp_000379</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18488">
                <text>Group of students at the 1987 Homecoming reception.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18489">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18490">
                <text>1987</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18491">
                <text>1980-1989</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18492">
                <text>College students</text>
              </elementText>
              <elementText elementTextId="18493">
                <text>Student activities</text>
              </elementText>
              <elementText elementTextId="18494">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31396">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31936">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18495">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18496">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18497">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18498">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205777">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18500">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18501">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18502">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1032" public="1" featured="0">
    <fileContainer>
      <file fileId="873">
        <src>https://digitalprojects.uah.edu/files/original/40/1032/uah_uahp_000380.pdf</src>
        <authentication>291e5d8384a3b7c8650b86830d3cc89e</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177244">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="40">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="9549">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17129">
                  <text>UAH Photograph Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="18503">
                <text>uah_uahp_000380</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18504">
                <text>Attendees enjoying the 1987 Homecoming reception.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18505">
                <text>University of Alabama in Huntsville</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18506">
                <text>1987</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="18507">
                <text>1980-1989</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18508">
                <text>College students</text>
              </elementText>
              <elementText elementTextId="18509">
                <text>Student activities</text>
              </elementText>
              <elementText elementTextId="18510">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="31397">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="31937">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18511">
                <text>Film negatives</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18512">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="18513">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="18514">
                <text>UAH Photograph Collection</text>
              </elementText>
              <elementText elementTextId="205778">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18516">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="18517">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="18518">
                <text>uah_photos_2019_10</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
