SOD

Standardized Osteological Database

by Bob Harris, Jerome C.Rose, and Courtney Waugh

Contents

Objectives

Installation and Setup

Software Overview

Adding New Data

Updating Data

Editing Data

Reports

Maintenance

Bone Code List

Table Structures

SOD OBJECTIVES

In 1990 the Field Museum of Natural History in Chicagoreceived support from the National Science Foundation to convene a seminar/workshoporganized by Jonathan Haas to develop standards for collecting data fromhuman skeletal remains scheduled to b e repatriated. The deliberation ofthe participants resulted in a set of recommendations published as StandardsFor Data Collection From Human Skeletal Remains, edited Jane E. Buikstraand Douglas H. Ubelaker. Realizing that collection and managementof these osteological data from potentially large collections of skeletonsrequires computerization, The Center for Advanced Spatial Technologies,with support from the National Science Foundation Grant DBS-9121552, developeda database application called SOD from these recommended standards withthe ultimate goal of stimulating a national osteological data archive andresearch resource.

This manual is intended as instruction using the SOD(Standardized Osteological Database) software, but is not intended to dictatestandards on the collection of osteological data. SOD was developed usingthe Standards For Data Collection From H uman Skeletal Remains. All of SOD'sdatabase tables and fields are derived from the data recording forms recommendedin the above publication. SOD was not developed with the intent to meetthe Native American Graves Protection and Repatriation Act (NAGPRA) c ompliance.Any data fields associated with the collection affiliations are solelythe opinion of the recorder and are not intended to be in compliance withNAGPRA regulations.

SOD is free-standing relational database applicationdeveloped using Microsoft FoxPro Relational Database Management System™.Microsoft FoxPro was used as the development software for several reasons.Foxpro software runs on both IBM compa tible and Apple Macintosh computers.FoxPro has a distribution kit which allows developers to distribute free-standing applications without the end-user having to own a copy ofFoxPro software. FoxPro creates "DBF" type files which can be importeddirec tly into most spreadsheet and statistical software packages.

One of the primary design objectives of a databaseapplication of this size is ease of use. With this in mind the SOD softwarewas designed with a point and click interface like Microsoft-Windows/AppleMacintosh. The software can be used with a mous e or a standard keyboard.A mouse is recommended but not required.

The SOD database application consists of one generalinformation table, twelve tables of skeletal information and eleven tablesof dental information. The application has one main menu with pull-downmenu options. The data entry and edit windows hav e pop-up lists with descriptivetext for all data fields that require alphabetical or numeric codes. Asingle key "Esc" functions as the "exit without change" thoughout the application.The reporting options consist of standardized report formats with the sa megeneral layout as the data entry screens, with point and click query generationand a customized reports option which allows the user to enter standardSQL statements to generate an unlimited number and variety of output.

Another primary design objective was data integrity.Every field on the data entry and edit windows that requires a code ischecked against a list of possible codes for that field. The dental informationdata entry windows only allow data entered in fields that has been recordedas teeth present in the dental inventory tables.

SOD INSTALLATION AND SETUP

System Requirements:

1) DOS version 3.20 or higher.
2) High density 3.5" or 5.25" disk drive.
3) Hard disk drive with 7 megabytes or more offree disk space.
4) 286 CPU but recommend a 386 CPU or better.
5) 520K of free memory.
6) The line "FILES=" in your config.sys file mustbe "FILES=43" or greater. Installation: 1) Insert diskette number 1 in your floppy diskdrive.
2) Make the disk drive with the SOD diskette thecurrent drive.
3) Type install and press enter.
4) Follow the instructions on the screen (you will be prompted to insert diskette 2). Example of installation from floppy drive A:    Insert in drive A:
   A:[Enter]
   install[Enter] The default drive and directory is C:\SOD. If you specifya different drive and/or directory in the installation program, you willneed to change the line "DEFAULT=C:\SOD" and "PATH=C\SOD\DATA;C:\SOD\RPTS"in the file config.fp which is located in t he new drive and/or directoryto reflect the change in the drive and/or directory.
The default file contains the follow lines: TALK = OFF
BELL = OFF
DEFAULT = C:\SOD
PATH = C:\SOD\DATA;C:\SOD\RPTS
MVCOUNT = 512
COMMAND = CLEAR
COMMAND = SET PROCEDURE TO boneproc.prg To run the SOD software, change directory to the directorycontaining the software and type sod then press enter.
Example with SOD in the directory C:\SOD cd \sod[Enter]
sod[Enter] Setup:
The first time you run the SOD software you willneed to activate the Maintenance option on the Main Menu and run Setupand enter the range of Key Numbers that you received with your software.If your computer is connected to a printer, yo u will also need to run thePrinter Setup option under the Maintenance option. See the Setup and PrintSetup options in the "Maintenance" section of this manual, p. 27

SOFTWARE OVERVIEW

The SOD software is designed to operate in different"modes". Each mode is represented by an option on the Main Menu. Thesemenu options are displayed at the top of the screen and can be accessedby clicking the left mouse button on an op tion or by pressing the "F10"function key, then using the arrow keys to navigate the menu bar. The menuoptions cause the software to take immediate action or display pull downmenus with multiple options.

MAIN MENU

Add_data Update_data Edit_data Browse Reports Maintenance Quit

________________________

_ _

_ Standardized _

_ Osteological _

_ Database _

_ _

________________________

Add_data: This option is used to add new data froma collection that had no previous entry in the general information table.Every new entry must have a minimum of one entry in the general informationtable and, in addition one en try in the inventory for complete remainstable or one or more entries in the inventory for commingled remains table.After the skeletal inventory information has been entered, the user ispresented with a supplemental menu with options to add additional inf ormationabout the current collection or to exit the "add new data" mode.
Update_date: This option is used to add new datato the supplemental database tables where data already exist for the collectionin the general information and inventory tables.
Edit_data: When you choose this option you arepresented with a pull down menu which lists all of the tables in SOD. Fromthis menu you may edit, delete or view data from any table.
Browse: This option also displays a pull downmenu of all the tables from which you can open a browse window. The browsewindow displays your data in a tabular form so that you may scroll throughboth records and fields to view your data.
Reports: The reports option gives the user theoption to run "Standard reports" or "Custom reports" options. The "Standardreports" option generates queries from a push button interface. The queriesare generated on fields in the general information table, producing outputfrom any of the database tables in text files format or in a format likethe data entry forms. The "Custom report" option allows the user to writestandard SQL queries producing an unlimited variety of output.
Maintenance: This option displays a pull downmenu with options to run the setup screen, printer setup screens, deleteand pack groups of data and import and export groups of data.
Quit: Use this option to exit from the software.

Adding New Data

When "Add_data" is chosen, the Main Menu is removed from the screen and replaced with the general information data entry screen below.
General Add/Edit screen functionality: All data entry and edit screens have a common functionality. You can use the mouse, arrow keys, or tab key to move to different fields on the screens. For screens with multiple windows you may move to the next or previous window by using the mouse, by clicking on the desired window,"page up" key, "page down" key, or by simply pressing "enter" when your cursor is in the last field on a window. The escape key allows you to exit from the current window or screen.

General Information Screen

+---------- General Information <----------+

| Key Number: __________ Catalog #: ________________|

| Individual: _ Sex Code: _ Age Code: __ |

| Mean Age: ____ Observer: ___ Date: |

|------------Site Information------------|

| #1 Name/#: &nb sp;/ |

| #2 Name/#: &nb sp;/ |

| Feature #: Site Location &n bsp; |

| Burial #: St/Cnty FIPS: / & nbsp; |

| Skeleton #: UTM E/N/ZONE: / / |

|Coord.(X/Y): / Lat./Lon.: : : / : : |

|-----------Collection Location------------|

| Organization: |

| Street/PO Box: ; |

| City,State Zip: , &nb sp; |

|----------Collection Affiliation-----------|

|Tribal Affil.: +-----+|

| Period: | < Save ||

| Culture: ; | ||

| Phase: &n bsp; | «Cancel» ||

| Variant: ; +-----+|

| &n bsp; |

+----F2 for code list / F3 to Save / Escto Cancel------+

Key Number: The "Key Number" is generatedautomatically. It is computed by adding the number one to the largest valueof the keyno field in the general information (main) table. This valuemust be in the range of key n umbers assigned when the software was distributed.The key number is used as an unique identifier code of each collectionand ties the information in other database tables back to the main table.The user can not add or edit the key number field.
Catalog #: The "Catalog Number" is a valuegenerated by the local user. It is used to identify the unique collections.This value may be any combination of letters or numbers up to 16 characters.After the catalog number is saved in the main table, the Catalog Numbercan not be changed.
Warning: "Please confirm #"; if yousave with wrong number, record must be deleted by keyno (maintenance, seebelow).
Individual: The data entry field "Individual:"must be coded as "S" for single individual (complete remains) or "M" formultiple individuals (commingled remains). The entry in this field determinesthe skeletal inventory data entry screen that will be displayed after savingthe general information screen.
Site Name #1: site number (be consistent); #2other name/number
Sex/Age Code: Press the function key "F2"when the cursor is in the age or sex field for codes.
St/Cnty FIPS: The state and county FIPScodes consist of a two digit code for each state and a three digit codefrom each county in the state. A list of these code may be found in theappendix. Press the function key "F2" when the c ursor is in the state fieldfor a list the states. After a valid state code has been entered, press"F2" to list the counties for that state.
The remaining fields on the general information screenare self explanatory. The collection location fields default to thevalues in the setup table. The Collection affiliation fields are not intendedto comply with the NAGPRA regulations and are the opinions of the observer.
Save/ Cancel: The user can save or cancel the dataentered by highlighting one of these buttons and pressing enter or by clickingthe left mouse button. The data on the screen can also be saved by pressingthe function key "F3" or canceled by pressing the "Esc" key.
If the user entered "S" for Complete Remains or"M" for Commingled Remains in the "Individual" field, the two inventorydata entry screens will be displayed.

NOTE: ALL ENTRIES IN THE GENERAL INFORMATION TABLEMUST HAVE AN ENTRY IN ONE OF THE INVENTORY TABLES. IF YOU CANCEL YOUR ENTRYIN THE INVENTORY TABLE, THE ENTRY FOR THAT KEY NUMBER WILL BE DELETED FROMTHE GENERAL INFORMATION TABLE.
INVENTORY FOR COMPLETE REMAINS
The data entry screen for this table will appearas six windows stacked like cards. This stacked design is used with alldata entry and edit screens that need additional room to display theirfields. As data is entered and the cursor is mo ved from the last fieldin one window to the first field on the next window, the stack of windowswill "shuffle", moving the current window to the top of the stack. Youmay also move new windows to the top of the stack by pressing the "PageDown"and "PageUP" keys or by clicking the left mouse button in the window.
The Inventory field values in windows 1-5 are representedby the bones codes listed (F2).
Window#1: Cranial, Shoulder, Sternum
The inventory field values for this window are representedby the bone codes listed (F2)
Note: There are various elements that appear on the databasebut are not on the Standards recording form. For example: SOD screen1 includes fields for mandibular condyle, hyoid and hyoid body, and xiphoidprocess which are found in the co mments sections of the Standards recordingform (Standards pp. 5-14, Attachment 1).
Similarly, there are skeletal elements which exist onthe Standards form like a field for sphenoid bone, not on SOD screen. These data should be recorded in the comments section of screen 6 of theInventory for Complete Remains.

Inventory for Complete Remains window #1:

+-------- BONE FRAGMENTS/COMMENTS --------+

| +---------- HAND/FOOT -----------+

| | +----------- LONG BONES -----------+

| | | +---------- RIBS/OS COXAE ----------+

| |H| |-+---------- VERTEBRAE -----------+

| | | | | +-------- CRANIAL/SHOULDER/STERNUM--------+

| | Key Number: 7 Catalog#: CAT7 |

| | | | | |-----------Cranial Bones------------|

| | Left Right Left Right |

| | Frontal: 0 0 Maxilla:0 0 |

| | Parietal: 0 0 Palatine:0 0 |

| | Occipital: 0 0 Mandible:0 0 |

| | Temporal: 0 0 Condyle:0 0 |

| | TMJ: 0 0 Hyoid: 0 0 |

| | Zygomatic: 0 0 Hyoid Body: 0 |

+-| |L| |-----------Shoulder/Sternum-----------|

| | Clavicle: 0 0 Sternum Manubrium: 0 |

| | Scapula: 0 0 Body: 0 ;|

| | Glenoid: 0 0 Xiphoid: 0 |

| +--F2 for list of Codes / F3 to Save / Escto Cancel---+

Window #2: Vertebra
The inventory values in this window are represented bythe bone codes listed (F2), with the exception of vertebrae C2-C6 and t1-t9which require counts.

Inventory for Complete Remain window #2:

+-------- CRANIAL/SHOULDER/STERNUM --------+

| +-------- BONE FRAGMENTS/COMMENTS --------+

|-| +---------- HAND/FOOT -----------+

| | | +----------- LONG BONES -----------+

| | | | +---------- RIBS/OS COXAE ----------+

| | |H| |-+---------- VERTEBRAE -----------+

| | Vertebrae (individual) Vertebrae (grouped) |

| | Number Complete |

| | Centrum Neural Arch Centrum Neural Arch |

| | C1: 0 0 ; |

| | C2: 0 0 ; |

| C3-C6: 0 0 0 &nb sp; 0 |

| C7: 0 0 & nbsp; |

| T1-T9: 0 0 0 &nb sp; 0 |

| T10: 0 0 |

| T11: 0 0 |

| T12: 0 0 |

| L1: 0 0 & nbsp; |

| L2: 0 0 & nbsp; |

| L3: 0 0 & nbsp; |

| L4: 0 0 & nbsp; |

| L5: 0 0 & nbsp; |

| Sacrum: 0 0 &nb sp; |

+--F2 for list of Codes / F3 to Save /Esc to Cancel---+

Window #3: Ribs
The inventory values in this window are represented bythe bone codes listed (F2), with the exception of Ribs 3-10 which requirecounts.
Note: No field exists for recording unsided rib fragments. Any unidentified fragments should be weighted and recorded in the commentssection at the bottom of Screen 6.

Inventory for Complete Remainwindow #3:

+---------- VERTEBRAE -----------+

| +-------- CRANIAL/SHOULDER/STERNUM --------+

| | +-------- BONE FRAGMENTS/COMMENTS --------+

| |-| +---------- HAND/FOOT -----------+

| | | | +----------- LONG BONES -----------+

| | | | | +---------- RIBS/OS COXAE ----------+

| | | |H| |-------------Ribs--------------|

| Ribs (individual) Ribs (grouped) |

| Number Complete ; |

| Left Right Left Right |

| 1st: 0 0 |

| 2nd: 0 0 |

|3-10: 0 0 0 0 &nb sp; |

|11th: 0 0 |

|12th: 0 0 |

| +-| | | |-------------Os Coxae-------------|

| Ilium Ischium Pubis Acetabulum Auricular Surface|

|Left 0 0 0 0 0 &nb sp; |

|Right 0 0 0 0 0 &n bsp; |

| +--F2 for list of Codes / F3 to Save / Escto Cancel---+

Window #4: Long Bones
The inentory field values are represented by the bonecodes listed (F2).
Note: Long bone data are entered beginning with the leftside of each bone. Note: earlier versionsof Standards form had L/R reversed.

Inventory for Complete Remain window #4:

+---------- RIBS/OS COXAE ----------+

|-+---------- VERTEBRAE -----------+

| | +-------- CRANIAL/SHOULDER/STERNUM --------+

| | | +-------- BONE FRAGMENTS/COMMENTS --------+

| | |-| +---------- HAND/FOOT -----------+

| | | | | +----------- LONG BONES -----------+

| | | | | | -----Diaphysis---- |

| Proximal Proximal Middle Distal Distal |

| Epiphysis Third Third Third Epiphysis |

|Humerus: 0 0 0 0 0 Left |

| 0 0 0 0 0& nbsp; Right |

|Radius: 0 0 0 0 0 Left |

| 0 0 0 0 0& nbsp; Right |

|Ulna: 0 0 0 0 0 Left&n bsp;|

| 0 0 0 0 0& nbsp; Right |

|Femur: 0 0 0 0 0 Left |

| 0 0 0 0 0& nbsp; Right |

|Tibia: 0 0 0 0 0 Left |

| 0 0 0 0 0& nbsp; Right |

|Fibula: 0 0 0 0 0 Left |

| 0 0 0 0 0& nbsp; Right |

+--F2 for list of Codes / F3 to Save / Esc to Cancel---+

Window#5: Hand/Foot
The inventory field values in Window 5 are representedby the bone codes listed (F2), with the exception of the carpals, metacarpals,tarsals (other than talus and calcaneus), metatarsals, and phalanges whichrequire counts.
This screen also includes fields for recording the presenceof the patellae. These data can be found on page one of the InventoryRecording Form (Standards, Chapter 2, Attachment 2). Standards includesfields for recording the presence of the hand/foot bones and the completenessof them. The database, however, does not include a field for recordingthe completeness of the hands and feet. We suggest entering the totalnumber present for each field, barring completeness .
Record the presence of sesamoid bones in the commentssection of screen 6 of the Inventory for Complete Remains.

Inventory for Complete Remain window #5:

+----------- LONG BONES -----------+

| +---------- RIBS/OS COXAE ----------+

| |-+---------- VERTEBRAE -----------+

| | | +-------- CRANIAL/SHOULDER/STERNUM --------+

| | | +-------- BONE FRAGMENTS/COMMENTS --------+

| | | |-| +---------- HAND/FOOT -----------+

| Left Right Unsided &nb sp; |

| Patella: 0 0 &nb sp; |

|Hand:----------------------------------------------------|

| # Carpals: 0 0 & nbsp; 0 |

| # Metacarpals: 0 0 0 |

| # Phalanges: & nbsp; 0 |

|Foot:----------------------------------------------------|

| Talus: 0 0 ; |

| Calcaneus: 0 0 & nbsp; |

| # Tarsals: 0 0 & nbsp; 0 |

| # Metatarsals: 0 0 0 |

| # Phalanges: & nbsp; 0 |

| &n bsp; |

F2 for list of Codes / F3 to Save / Esc to Cancel---+

Window #6 Bone Fragments/Comments
The bone fragment field on window 6 are for counts and/orweights. The comments area is a "memo" field and can contain unlimitedfree text. This field and similar fields on other data entry screens allowthe user to enter unlimited amount s of text by simply continuing to type.As you reach the end of the visable area, the field scrolls to a new line.To Exit a "memo" field, press the control and the tab keys simultaneously.
Note: Comments sections do not exist for the dental andpathology screens. Check records carefully and record all miscellaneousinformation in the comments section on screen 6 of the Skeletal Inventory.

Inventory for Complete Remain window #6:

+---------- HAND/FOOT -----------+

| +----------- LONG BONES -----------+

| | +---------- RIBS/OS COXAE ----------+

|-+---------- VERTEBRAE -----------+

| +-------- CRANIAL/SHOULDER/STERNUM --------+

| +-------- BONE FRAGMENTS/COMMENTS --------+

| Count Weight&n bsp; |

| Skull Fragments: 0 0.000 |

| Limb Long Bone Fragments: 0 0.000 |

| Vertebrae Fragments: 0 0.000 |

| Hand/Feet Fragments: 0 0.000 |

| Clavicle/Scapula Fragments: 0 0.000 |

| Os Coxae Fragments: 0 0.000 |

| Postcranial Misc. Fragments: 0 0.000 |

| Unidentifiable Fragments: 0 0.000 |

|Comments:-(Ctrl+Tab to exit)---------------|

| _ +---------+|

| _ |< Save &la quo;Cancel»||

| +-| &nb sp; _ +---------+|

| L+--F2for list of Codes / F3 to Save / Esc to Cancel---+

INVENTORY FOR COMMINGLED REMAINS
The commingled inventory table (inv_mult) may have asmany entries as needed to inventory the collection.
Bone Code: This field requires one of the bonecodes listed in the appendix for the bone being recorded. These codesare descriptive abbreviations of 8 characters or less. There is abone code for each bone listed on th e inventory for the complete remainsdata entry screen.
Menu #1
You may press F2 and [Enter] to display Pull DownMenu #1 on the Bone Code Look Up screen. This menu requires the user toselect a category of bones. Click on your selection or use the upand down arrows to cursor to the desir ed category.

+------ INVENTORY FOR COMMINGLED REMAINS ------+

| Key Number: 7 Catalog #:CAT7 |

| &n bsp; |

|Bone Code-Compl-MNI--Count--Weight--Age Code-SexCode-|

| 0 0 0 0.000 &nbs p; |

|-----------------------------|

| &n bsp; |

+F2 for list of Codes

+------------BONE CODE LOOK UP------------+

| Category Bone Name Side Segment |

|+-------++-------++----++---------+ |

||LONG LIMB BONE||

|+-------++-------++----++---------+ |

| &n bsp; |

+--------------------------------+

Menu #2
Press [Enter] twice to display Pull Down Menu #2. This menu requires the user to choose a specific bone.

+------ INVENTORY FOR COMMINGLED REMAINS ------+

| Key Number: 7 Catalog #:CAT7 |

| &n bsp; |

|Bone Code-Compl-MNI--Count--Weight--Age Code-SexCode-|

| 0 0 0 0.000 &nbs p; |

|-----------------------------|

| &n bsp; |

+------------BONE CODE LOOK UP------------+

| Category Bone Name Side Segment |

|+-------++-------++----++---------+ |

||LONG LIMB BONE||FEMUR |

|+-------++-------++----++---------+ |

| &n bsp; |

+--------------------------------+

Menu #3

Press [Enter] twice to display BoneCode PullDown Menu #3. This menu requires the user to identify the bone asright or left.

+------ INVENTORY FOR COMMINGLED REMAINS ------+

| Key Number: 7 Catalog #:CAT7 |

| &n bsp; |

|Bone Code-Compl-MNI--Count--Weight--Age Code-SexCode-|

| 0 0 0 0.000 &nbs p; |

|-----------------------------|

+------------BONE CODE LOOK UP------------+

| Category Bone Name Side Segment |

|+-------++-------++----++---------+ |

||LONG LIMB BONE||FEMUR ||LEFT |

|+-------++-------++----++---------+ |

| &n bsp; |

+--------------------------------+

Menu #4
Press [Enter] twice to display Pull Down Menu #4. Thismenu requires the user to select the segment of the bone in question.
NOTE: A separate entry must be made for each segmentof each bone.
The database fields for completeness, MNI (minimumnumber of individuals), age code, and sex code all require the numericalcodes listed (F2). The fields for count and weight are self explanatory.

+------ INVENTORY FOR COMMINGLED REMAINS ------+

| Key Number: 7 Catalog #:CAT7 |

| &n bsp; |

|Bone Code-Compl-MNI--Count--Weight--Age Code-SexCode-|

| 0 0 0 0.000 &nbs p; |

|-----------------------------|

| &n bsp; |

| « Save and Exit » & nbsp; |

| <Save and Add Another |

| < Cancel &nb sp; |

| &n bsp; |

+F2 for list of Codes / F3 to Save and Exit /Esc to Cancel+

+------------BONE CODE LOOK UP------------+

| Category Bone Name Side Segment |

|+-------++-------++----++---------+ |

||LONG LIMB BONE||FEMUR ||LEFT ||DISTAL EPIPHYSIS | |

|+-------++-------++----++---------+ |

| &n bsp; |

+--------------------------------+

SUPPLEMENTAL INFORMATION

As stated previously, data must be entered in the generalinformation table and in addition, a single entry in the inventory of completeremains or one or more entries in the inventory for commingled remains.After completing the data e ntry in one of the inventory tables, SOD displaysthe supplemental menu. This menu lists the remaining tables available forskeletal information and displays an option to open a submenu for dentalinformation. Like the inventory for complete remains table, m ost of thesupplemental skeletal information tables allow only one entry per key number.Once data has been entered and saved into one of the single entry tablesa "<" is displayed to the left of the table name on the supplementalmenu and you are prevente d from entering more data in that table for thatkey number. The tables containing taphonomic changes, burned bone, skeletalpathology and trepanation allow multiple entries. After you save one ormore records in these tables the supplemental menu marks the table namewith a "" character to the left of the table name to indicate data inthe table for the current key number, but you may still enter additionalinformation in these tables. A "" character to the right of a table nameon the supplemental menu indicat es that a submenu exists.

To access options on the supplemental menu clickyour left mouse buttom on the desired item or use your arrow keys to highlightthe item, then and press [Enter].

SUPPLEMENTAL MENU:

+-CURRENT KEY NUMBER: 7--+

| Commingled Inventory |

| Adult Age & Sex Info. |

| Adult Measurements |

| Immature Measurements |

| Immature Union & Closure |

| Non-Metric Traits |

| Taphonomic Changes |

| Burned Bone

| Skeletal Pathology |

| Cranial Deformation |

| Trepanation |

| Skeletal Samples |

| Dental Information |

| Exit Menu |

+-------------+

+--Dental Information--+

| --PERMANENT TEETH-- |

| Maxillary Inventory |

| Mandibular Inventory |

+-------------|

| Maxillary Measurements |

| Mandibular Measurements |

+-------------|

| Hypoplasia |

| Dental Morphology |

| Suppernumerary Teeth |

| Samples Curated/Cast |

| --DECIDUOUS TEETH-- |

|Maxillary Inventory |

| Mandibular Inventory |

|Hypoplasia |

+-------------+

ADULT AGE AND SEX
The age & sex screen consists of two windows.
Pull Down Codes (F2) (Standards, pp. 16-19, Attachment11).
Summary Age/Sex: Unlimited text field.

Adult Age & Sex Information window #1:

+-------- ADULT AGE RECORDING FORM --------+

| +-------- ADULT SEX RECORDING FORM --------+

| |Key Number: 7 Catalog #: CAT7 |

| |-----------SEX DETERMINATION----------|

| | PELVIS Left/Right SKULL |

| | Ventral Arc: 0 / 0 Nuchal Crest: 0 |

| | Subpubic Concavity: 0 / 0 Mastoid Process: 0 |

| | Ridge on I-P Ramus: 0 / 0 Supraorbital Margin: 0 |

| | Greater Sciatic Notch: 0 / 0 Glabella 0 |

| | Preauricular Sulcus: 0/ 0 Mental Eminence: 0 |

| | |

| | Pelvis Sex Summary: 0 Skull Sex Summary: 0 |

| | |

| | Summary Sex Code: 0 ; |

| +--F2 for list of Codes / F3 to Save / Escto Cancel---+

| Sup. Sphenofrontal: Summary age code: 0 |

|Summary Age/Sex: (Ctrl+Tab to exit) +------+|

| &n bsp;_ | « Save » ||

| &n bsp;_ | <cancel ||

| &n bsp;_ +------+|

+--F2 for list of Codes / F3 to Save / Esc toCancel---+

Note: The sex recording form in Standards contains fieldsfor recording development of right and left characteristics of the skull. In recording here, we suggest that observer lean toward midline of thetwo numbers; i.e., if right side a 1 and left side a 2, choose 2; if rightside a 3 and left side a 4, choose 3.

Adult Age & Sex Information window #2:

+-------- ADULT SEX RECORDING FORM --------+

|K+-------- ADULT AGE RECORDING FORM --------+

|-| PUBIC SYMPHYSIS AURICULAR SURFACE |

| | Todd(L/R): 0 0 (L/R): 0 0 |

| | Suchey-Brookes(L/R): 0 0 |

| | SUTURE CLOSURE &nbs p; |

| | EXTERNAL CRANIAL VAULT PALATE |

| | Midlamboid: Incisive: |

| | Lambda: Ant. Med. Palatine: |

| | Obelion: Post. Med. Palatine: |

| | Anterior Sagittal: Transverse Palatine: |

| | Bregma: INTERNAL CRANIAL VAULT |

| | Midcoronal: Sagittal: |

+-| Pterion: Lambdoid: |

+-| Sphenofrontal: Coronal: |

| Inf. Sphenofrontal: ; |

| Sup. Sphenofrontal: Summary age code: 0 |

|Summary Age/Sex: (Ctrl+Tabto exit) +------+|

| & nbsp; _ | « Save » ||

| & nbsp; _ | <cancel ||

| & nbsp; _ +------+|

+--F2 for list of Codes / F3 to Save /Esc to Cancel---+

ADULT MEASUREMENTS
The adult measurement data entry screen consistsof five windows with fields grouped by measuring device and bone category.(Standards, pp. 71-84, Attachment 21)
Notes: Be aware that this organization does not reflectthe exact order of the fields on the Standards data recording sheet. Pay careful attention to the specific measurement when encoding data.
The measurements screen does not include fields for indicatingif a measurement was taken from the right side of the body, or if the measurementwas taken from a reconstructed bone. If these circumstances shouldarise, we urge the u ser to record all measurements regardless of side andput a note in the comments section of the Inventory screen stating thatsome measurements may be from the right side and to check the hard copiesfor specifics.

Adult Measurements window #1:

+----------- LONG LIMB BONES -----------+

| +----------- LONG LIMB BONES -----------+

| +-------- SHOULDER / OS COXAE / FEET --------+

| +------------- CRANIUM -------------+

| +-- CRANIAL AND POSTCRANIAL MEASUREMENTS (ADULTREMAINS)--+

|Key Number: 7 Catalog#:CAT7 |

| &n bsp; |

|U|R| |U|--------------CRANIUM--------------|

| SPREADING CALIPER &nb sp; |

|Maximum Cranial Length: 0.0 Basion-ProsthionLength: 0.0 |

|Maximum Cranial Breadth: 0.0 Maxillo-AlveolarBreadth: 0.0 |

|Basion-Bregma Height: 0.0 Maxillo-Alveolar Length: 0.0 |

|Cranial Base Length: 0.0 &nb sp;|

|O+---------F3 to Save / Esc to Cancel---------+

|Biorbital Breadth: 0.0 Maximum Ramus Breadth: 0.0 |

|Interorbital Breadth: 0.0 Maximum Ramus Height: 0.0 |

|Frontal Chord: 0.0 Mandibular Length: 0.0 |

|Parietal Chord: 0.0 Mandibular Angle: 0 |

|Occipital Chord: 0.0 & nbsp; |

+---------F3 toSave / Esc to Cancel---------+

Adult Measurements window #2:

+-- CRANIAL AND POSTCRANIAL MEASUREMENTS (ADULTREMAINS)--+

|K+----------- LONG LIMB BONES -----------+

| | +----------- LONG LIMB BONES -----------+

+-------- SHOULDER / OS COXAE / FEET --------+

| +------------- CRANIUM -------------+

| SLIDING CALIPER ; |

|Bizygomatic Diameter: 0.0 Foramen Magnum Length: 0.0 |

|Biauricular Breadth: 0.0 Foramen Magnum Breadth: 0.0 |

|Upper Facial height: 0.0 Mastoid Length: 0.0 |

|Minimum Frontal Breadth: 0.0 ChinHeight: 0.0 |

|Upper Facial Breadth: 0.0 Mandibular Body Height: 0.0 |

|Nasal Height: 0.0 Mandibular Body Breadth: 0.0 |

|Nasal Breadth: 0.0 Bigonial Width: 0.0 |

|Orbital Breadth: 0.0 Bicondylar Breadth: 0.0 |

|Orbital Height: 0.0 Minimum Ramus Breadth: 0.0 |

|Biorbital Breadth: 0.0 Maximum Ramus Breadth: 0.0 |

|Interorbital Breadth: 0.0 Maximum Ramus Height: 0.0 |

|Frontal Chord: 0.0 Mandibular Length: 0.0 |

|Parietal Chord: 0.0 Mandibular Angle: 0 |

|Occipital Chord: 0.0 & nbsp; |

+----

Adult Measurements window #3:

+------------- CRANIUM -------------+

| +-- CRANIAL AND POSTCRANIAL MEASUREMENTS (ADULTREMAINS)--+

|K+----------- LONG LIMB BONES -----------+

| +----------- LONG LIMB BONES -----------+

| +-------- SHOULDER / OS COXAE / FEET --------+

| &n bsp; |

| SLIDING CALIPER &nbs p; |

|CLAVICLE SACRUM |

| Ant-Post Dia. Midshaft: 0.0 Anterior Length: 0.0 |

| Vertical Dia. Midshaft: 0.0 Superior Breadth: . |

|SCAPULA Max Trans. Dia. Base: . |

| Anatomical Height: 0.0 OSTEOMETRIC BOARD |

|OS COXAE CLAVICLE &nbs p; |

| Height: 0.0 Maximum Length: 0.0 |

| Pubis Length: 0.0 &nb sp; |

| Ischium Length: 0.0 SPREADING CALIPER |

|CALCANEUS SCAPULA &nbs p; |

| Maximum Length: 0.0 Anatomical Breadth: 0.0 |

| Middle Breadth: 0.0 OS COXAE |

| Iliac Breadth: 0.0 |

+---------F3to Save / Esc to Cancel---------+

Adult Measurements window #4:

+-------- SHOULDER / OS COXAE / FEET --------+

| +------------- CRANIUM -------------+

| | +-- CRANIAL AND POSTCRANIAL MEASUREMENTS(ADULT REMAINS)--+

|K+----------- LONG LIMB BONES -----------+

| +----------- LONG LIMB BONES -----------+

| SLIDING CALIPER ; |

|HUMERUS FEMUR &n bsp; |

| Vertical Dia. of head: 0.0 Max. Dia. of Head: 0.0|

| Max. Dia. Midshaft: 0.0 Sagittal Subtrochan. Dia: 0.0|

| Min. Dia. Midshaft: 0.0 Trans. Subtrochan. Dia: 0.0|

|RADIUS: Sagittal Midshaft Dia.: 0.0|

| Ant-Post Dia. Midshaft: 0.0 Trans.Midshaft Dia.: 0.0|

| Trans. Dia. Midshaft: 0.0 |

|ULNA: TIBIA &nbs p; |

| Ant-Post Dia. Midshaft: 0.0 Max.Dia. Nutr. Fora.: 0.0|

| Trans. Dia. Midshaft: 0.0 Trans. Dia. Nutr. Fora.: 0.0|

|FIBULA &n bsp; |

| Maximum Dia. Midshaft: 0.0 |

| +---------F3to Save / Esc to Cancel---------+

Adult Measurements window #5:

+----------- LONG LIMB BONES -----------+

| +-------- SHOULDER / OS COXAE / FEET --------+

+------------- CRANIUM -------------+

| | | +-- CRANIAL AND POSTCRANIAL MEASUREMENTS(ADULT REMAINS)--+

|K+----------- LONG LIMB BONES -----------+

| OSTEOMETRIC BOARD TIBIA &nb sp;|

|HUMERUS Length: 0.0 |

| Maximum Length: 0.0 Prox. Epiphyseal Breadth: 0.0 |

| Epicondylar Breadth: 0.0 Dist.Epiphyseal Breadth: 0.0 |

|RADIUS: SPREADING CALIPER |< /P

| Maximum Length: 0.0 ULNA |< /P

|ULNA: Physiological Length: 0.0 |

| Maximum Length: 0.0 TAPE MEASURE |

|FEMUR ULNA ; |

| Maximum Length: 0.0 Minimum Circumference: 0.0|

| Bicondylar length: 0.0 FEMUR |

| Epicondylar Breadth: 0.0 MidshaftCircumference: 0.0 |

|FIBULA TIBIA &nb sp; |

| Maximum Length: 0.0 Circum. Nutrient Foramen: 0.0 |

| « Save » <Cancel &nbs p; |

+---------F3to Save / Esc to Cancel---------+

IMMATURE REMAINS MEASUREMENTS
The immature measurement data entry screen consistsof five windows with data fields grouped by bone category (Standards, p.45-46, Attachment 13).
Note: The Standards data recording form contains fieldsfor recording the right and left measurements of the Lesser Wing of theSphenoid. SOD contains only one field for recording this measurement. In cases where you have both right and left measurements, the average shouldbe encoded into SOD.
Immature Remains Measurements window #1:

+---------- LONG LIMB BONES ----------+

| +---------- LONG LIMB BONES ----------+

| +--------- SHOULDER / OS COXAE ---------+

+------------ CRANIUM ------------+

| +------ IMMATURE REMAINS MEASUREMENTS -------+

|Key Number: 7 Catalog #: CAT7 |

|-------------CRANIUM-------------|

| &n bsp;Left Right |

|Lesser wing of sphenoid........ Length: 0.0 |

| Width: &n bsp; 0.0 |

|Greater wing of sphenoid....... Length: 0.0 0.0 |

| Width: 0.0 &nbs p; 0.0 |

|Body of sphenoid............... Length: 0.0 |

| Width: &n bsp; 0.0 |

|Petrous-mastoid of temporal.... Length: 0.0 0.0 |

| Width: 0.0 &nbs p; 0.0 |

| &n bsp; |

+--------F3to Save / Esc to Cancel--------+

Immature Remains Measurements window #2:

+------ IMMATURE REMAINS MEASUREMENTS -------+

|K+---------- LONG LIMB BONES ----------+

| +---------- LONG LIMB BONES ----------+

| +--------- SHOULDER / OS COXAE ---------+

| +------------ CRANIUM ------------+

| &n bsp;Left Right |

|Basilar occipital.............. Length: 0.0 |

| Width: &n bsp; 0.0 |

|Zygomatic...................... Length: 0.0 0.0 |

| Width: 0.0 &nbs p; 0.0 |

|Maxilla........................ Length: 0.0 0.0 |

| Height: 0.0 &nb sp; 0.0 |

| Width: 0.0 &nbs p; 0.0 |

| Oblique Length: 0.0 0.0 |

|Mandible....................... Length: 0.0 0.0 |

| Width: 0.0 &nbs p; 0.0 |

| Full Length: 0.0 0.0 |

+--------F3to Save / Esc to Cancel--------+

Immature Remains Measurements window #3:

+------------ CRANIUM ------------+

| +------ IMMATURE REMAINS MEASUREMENTS -------+

+---------- LONG LIMB BONES ----------+

| |-| +---------- LONG LIMB BONES ----------+

| +--------- SHOULDER / OS COXAE ---------+

| &n bsp;Left Right |

|Clavicle........................ Length: 0.0 0.0 |

| Diameter: 0.0 & nbsp; 0.0 |

|Scapula......................... Length: 0.0 0.0 |

| Width: 0.0 &nbs p; 0.0 |

| Length of spine: 0.0 0.0 |

| &n bsp; |

|Ilium........................... Length: 0.0 0.0 |

| Width: 0.0 &nbs p; 0.0 |

|Ischium......................... Length: 0.0 0.0 |

| Width: 0.0 &nbs p; 0.0 |

|Pubis........................... Length: 0.0 0.0 |

+--------F3to Save / Esc to cancel--------+

Immature Remains Measurements window #4:

+--------- SHOULDER / OS COXAE ---------+

| +------------ CRANIUM ------------+

| +------ IMMATURE REMAINS MEASUREMENTS -------+

|K+---------- LONG LIMB BONES ----------+

|-| +---------- LONG LIMB BONES ----------+

| &n bsp; Left Right |

|Humerus......................... Length: 0.0 0.0 |

| Width: 0.0 &nbs p; 0.0 |

| Diameter: 0.0 & nbsp; 0.0 |

|Ulna............................ Length: 0.0 0.0 |

| Diameter: 0.0 & nbsp; 0.0 |

|Radius.......................... Length: 0.0 0.0 |

| Diameter: 0.0 & nbsp; 0.0 |

|Femur......................... Length: 0.0 0.0 |

| Width: 0.0 &nbs p; 0.0 |

| Diameter: 0.0 & nbsp; 0.0 |

| &n bsp; |

+--------F3to Save / Esc to cancel--------+

Immature Remains Measurements window #5:

+---------- LONG LIMB BONES ----------+

| +--------- SHOULDER / OS COXAE ---------+

| +------------ CRANIUM ------------+

| +------ IMMATURE REMAINS MEASUREMENTS -------+

|K+---------- LONG LIMB BONES ----------+

| &n bsp;Left Right |

|Tibia......................... Length: 0.0 0.0 |

| Diameter: 0.0 & nbsp; 0.0 |

|Fibula........................ Length: 0.0 0.0 |

| Diameter: 0.0 & nbsp; 0.0 |

| &n bsp; |

|-----------------------------|

| &n bsp; |

| « Save » <Cancel ; |

| &n bsp; |

+-| +--------F3 to Save /Esc to Cancel--------+

IMMATURE REMAINS UNION AND CLOSURE
The immature remains bone union and epiphysealclosure data entry screen consists of four windows. All data fields requirethe codes (F2) (Standards, pp. 40-44, Attachment 12).
NOTE: Although the data recording screen followsthe same order as the Standards data recording form, the numerical codingis inconsistent between the two. For example, Standards uses thefollowing codes: Blank= Unobservable; 0= open; 1= partial union;2= complete union.
The F2 codes for the data recording screen are as follows:
Blank= Unobservable; 1= open; 2= partial union; 3= completeunion.
**Please note this inconsistency and make adjustmentsto the codes accordingly.
Also, whereas Standards contains fields for occipitalclosure, SOD does not. The field for closure of the basilar synchondrosisin SOD refers to, and is the same as, the field for the spheno-occipitalsynchondrosis in Standar ds.
Immature Remains Bone Union and Epiphyseal Closurewindow #1:

+--- BONE UNION AND EPIPHYSEAL CLOSURE (window4) ---+

|B+--- BONE UNION AND EPIPHYSEAL CLOSURE (window3) ---+

| | +--- BONE UNION AND EPIPHYSEAL CLOSURE (window2) ---+

|-| | +--- BONE UNION AND EPIPHYSEAL CLOSURE(window 1) ---+

| | | | Immature Remains &nbs p; |

| |-| |Key Number: 7 Catalog #:CAT7 |

| | |-|-----------------------------|

| | | | BONE EPIPHYSIS STAGE OF UNION |

|S| | |-----------------------------|

| | | | Cervical Vertebrae & nbsp; |

| | | | Superior 0 &nbs p; |

| | | | Inferior 0 &nbs p; |

| | | | Thoracic Vertebrae & nbsp; |

| | | | Superior 0 &nbs p; |

| | | | Inferior 0 &nbs p; ||-| | |

Lumbar Vertebrae ; |

| +-| | Superior 0 &nbs p; |

+--+-| Inferior 0 ; |

+--F2 for listof Codes / F3 to Save / Esc to Cancel---+

Immature Remains Bone Union and Epiphyseal Closure window#2:

+--- BONE UNION AND EPIPHYSEAL CLOSURE (window1) ---+

| +--- BONE UNION AND EPIPHYSEAL CLOSURE (window4) ---+

| |B+--- BONE UNION AND EPIPHYSEAL CLOSURE (window3) ---+

|-| | +--- BONE UNION AND EPIPHYSEAL CLOSURE(window 2) ---+

| |-| | BONE | BONE &nb sp; |

|-| | | EPIPHYSIS STAGE OFUNION| EPIPHYSIS STAGE OF UNION |

| | |-| L R | &nb sp; L R |

| | | |--------------|---------------|

| | | | Scapula | Humerus &nb sp; |

| | | | Coracoid 0 0 | Head 0 0 |

| | | | Acromion 0 0 | Distal 0 0 |

| | | | Inferior angle 0 0 | Medial Epicondyle 0 0 |

| | | | Medial border 0 0 | Radius |

| | | | Clavicle | Proximal 0 0 |

| | | | Sternal 0 0 | Distal 0 0 |

+-| | | | Ulna &n bsp; |

|-| | | Proximal ; 0 0 |

| +-| | Distal & nbsp; 0 0 |

+--+--F2 for list of Codes / F3 to Save/ Esc to Cancel---+

Immature Remains Bone Union and Epiphyseal Closurewindow #3:

+--- BONE UNION AND EPIPHYSEAL CLOSURE (window2) ---+

| +--- BONE UNION AND EPIPHYSEAL CLOSURE (window1) ---+

| | +--- BONE UNION AND EPIPHYSEAL CLOSURE (window4) ---+

| | |B+--- BONE UNION AND EPIPHYSEAL CLOSURE(window 3) ---+

|-|-| | BONE | BONE &nb sp; |

| | |-| EPIPHYSIS STAGE OFUNION| EPIPHYSIS STAGE OF UNION |

| |-| | L R | &nb sp; L R |

| | | |--------------|---------------|

| | | | Os Coxae | Tibia &nbs p; |

| | | | Iliac Crest 0 0 | Proximal 0 0 |

| | | | Ischial Tuberosity 0 0 | Distal 0 0 |

| | | | Femur | Fibula |

| | | | Head 0 0 | Proximal 0 0 |

| | | | Greater Trochanter 0 0 | Distal 0 0 |

| | | | Lesser Trochanter 0 0 | |

+-| | | Distal 0 0 &nbs p; |

+-| | &nb sp; |

|-| ; |

| +--F2 for list of Codes/ F3 to Save / Esc to Cancel---+

Immature Remains Bone Union and Epiphyseal Closurewindow #4:

+--- BONE UNION AND EPIPHYSEAL CLOSURE (window3) ---+

| +--- BONE UNION AND EPIPHYSEAL CLOSURE (window2) ---+

| | +--- BONE UNION AND EPIPHYSEAL CLOSURE (window1) ---+

| | | +--- BONE UNION AND EPIPHYSEAL CLOSURE(window 4) ---+

|-| | |BONE | BONE &nbs p; |

| |-|-| AREA OF UNION EXTENT | AREA OF UNION EXTENT|

| | | |------------|-----------------|

| | | |Os Coxae | Cervical Vertebrae |

| | | | Ilium-Pubis 0 | Neural Arches to each other 0 |

| | | | Ischium-Pubis 0 | Neural Arches to Centrum 0 |

| | | | Ischium-Ilium 0 | Thoracic Vertebrae |

| | | |Sacral Segments | Neural Arches to each other 0 |

| | | | 1-2 0 | Neural Arches to Centrum 0 |

| | | | 2-3 0 | Lumbar Vertebrae |

| | | | 3-4 0 | Neural Arches to each other 0 |

+-| | | 4-5 0 | Neural Arches to Centrum 0 |

+-| | | Cranium |

+-| | Basilar Synchondrosis 0 |

|-----------------------------|

| « Save » <Cancel &nbs p; |

+--F2 for listof Codes / F3 to Save / Esc to Cancel---+

NON-METRIC SKELETAL TRAITS
The Non-Metric Skeletal Traits data entry screenconsists of five windows. The data fields require numeric codes (F2) (Standards,pp. 87-94, Attachment 22)

Note: Standards contains one field for recording Flexureof Superior Sagittal Sulcus, whereas, SOD has two indicating right andleft observations. Since this is a median observation, we suggestthat the user enter the median code from Standards into both fields inSOD.

Non-Metric Skeletal Traits window #1:

+------- NONMETRIC TRAITS (Window5) -------+

|-+------- NONMETRIC TRAITS (Window4) -------+

| |-+------- NONMETRIC TRAITS (Window3) -------+

| | |-+------- NONMETRIC TRAITS (Window2) -------+

| | | |-+------- NONMETRIC TRAITS (Window1) -------+

| | | | |Key Number: 7 Catalog #:CAT7 |

| | | | |-------------------------L-M-R-|

| | | | | Metopic Suture................................: 0 |

| | | | | |

| | | | | Supra-orbital Structures |

| | | | | Supra-orbital Notch..........................:0 0 |

| | | | | Supra-orbital Foramen........................:0 0 |

| | | | | |

|-| | | | Infra-orbital Suture..........................:0 0 |

| | | | | |

+-| | | | Multiple Infra-orbital Foramina...............:0 0 |

+-| | | & nbsp; |

+-| | Zygomatico-facial Foramen.....................:0 0 |

+-| ; |

+--F2for list of Codes / F3 to Save / Esc to Cancel---+

Non-Metric Skeletal Traits window #2:

+------- NONMETRIC TRAITS (Window1) -------+

|K+------- NONMETRIC TRAITS (Window5) -------+

|-|-+------- NONMETRIC TRAITS (Window4) -------+

| | |-+------- NONMETRIC TRAITS (Window3) -------+

| | | |-+------- NONMETRIC TRAITS (Window2) -------+

| | | | |-------------------------L-M-R-|

| | | | | Parietal Foramen..............................:0 0 |

| | | | | |

| | | | | Sutural Bones &nbs p; |

| | | | | Epipteric Bone...............................:0 0 |

| | | | | Coronal Ossicle..............................:0 0 |

| | | | | Bregmatic Bone...............................: 0 |

| | | | | Sagittal Ossicle.............................: 0 |

| | | | | Apical Bone..................................: 0 |

| |-| | | Lambdoid Ossicle.............................:0 0 |

+-| | | | Asterionic Bone..............................:0 0 |

+-| | | Ossicle in Occipito-MastoidSuture...........: 0 0 |

+-| | Parietal NotchBone..........................: 0 0 |

+-| ; |

+--F2for list of Codes / F3 to Save / Esc to Cancel---+

Non-Metric Skeletal Traits window #3:

+------- NONMETRIC TRAITS (Window2) -------+

|-+------- NONMETRIC TRAITS (Window1) -------+

| |K+------- NONMETRIC TRAITS (Window5) -------+

| |-|-+------- NONMETRIC TRAITS (Window4) -------+

| | | |-+------- NONMETRIC TRAITS (Window3) -------+

| | | | |-------------------------L-M-R-|

| | | | | Inca Bone.....................................: 0 |

| | | | | |

| | | | | Condylar Canal................................:0 0 |

| | | | | |

| | | | | Divided Hypoglossal Canal.....................:0 0 |

| | | | | |

| | | | | Flexure of Superior Sagittal Sulcus...........:0 0 |

| | | | | |

| | | | | Foramen Ovale Incomplete......................:0 0 |

+-| |-| | |

+-| | | Foramen Spinosum Incomplete...................:0 0 |

+-| | &nb sp; |

+-| Pterygo-spinousBridge........................: 0 0 |

+--F2for list of Codes / F3 to Save / Esc to Cancel---+

Non-Metric Skeletal Traits window #4:

+------- NONMETRIC TRAITS (Window3) -------+

|-+------- NONMETRIC TRAITS (Window2) -------+

| |-+------- NONMETRIC TRAITS (Window1) -------+

| | |K+------- NONMETRIC TRAITS (Window5) -------+

| | |-|-+------- NONMETRIC TRAITS (Window4) -------+

| | | | |-------------------------L-M-R-|

| | | | | Pterygo-alar Bridge...........................:0 0 |

| | | | | |

| | | | | Tympanic Dehiscence...........................:0 0 |

| | | | | |

| | | | | Auditory Exostosis............................:0 0 |

| | | | | |

| | | | | Mastoid Foramen &n bsp; |

| | | | | Location.....................................:0 0 |

| | | | | Number.......................................:0 0 |

+-| | | | |

+-| |-| Mental Foramen................................:0 0 |

+-| | &nb sp; |

+-| MandibularTorus..............................: 0 0 |

+--F2for list of Codes / F3 to Save / Esc to Cancel---+

Non-Metric Skeletal Traits window #5:

+------- NONMETRIC TRAITS (Window4) -------+

|-+------- NONMETRIC TRAITS (Window3) -------+

| |-+------- NONMETRIC TRAITS (Window2) -------+

| | |-+------- NONMETRIC TRAITS (Window1) -------+

| | | |K+------- NONMETRIC TRAITS (Window5) -------+

| | | |-|-------------------------L-M-R-|

| | | | | Mylohyoid Bridge & nbsp; |

| | | | | Location.....................................:0 0 |

| | | | | Degree.......................................:0 0 |

| | | | | |

| | | | | Atlas Bridging &nb sp; |

| | | | | Lateral Bridging.............................:0 0 |

| | | | | Posterior Bridging...........................:0 0 |

| | | | | |

| | | | | Accessory Transverse Foramina.................:0 0 |

+-| | | | |

+-| | | Septal Aperture...............................:0 0 |

+-| |-----------------------------|

+-| « Save » <Cancel &n bsp; |

+--F2for list of Codes / F3 to Save / Esc to Cancel---+

TAPHONOMIC CHANGES
Postmortem changes (Bone Taphonomy) is recordedon a data entry screen with one window. In this table the user may recordone or many records for the same key number. The data fields require codes(F2) (Standards, pp. 95-106, Attach ment 24).
Bone Code: The codes used in this field are thesame as those used in the inventory for commingled remains described previouslyin this manual.
Type of Alteration: The codes used in this fieldfollow the order of the alterations listed in Standards (pp. 106) and onthe Standards Taphonomy Recording Form II, with the exception of "OtherForms of Cultural Modification Includ ing the Creation of Artifacts".
Location of Modification: This is an 80-characterfield to describe the physical location of the modification.
Photo/Drawing Number: Catalog or ID number.
Descriptive information: This is a memo fieldthat allows unlimited text entry.

+--------- TAPHONOMIC CHANGES ---------+

|Key Number: 7 Catalog #:CAT7 |

|-----------------------------|

| Type of & nbsp; |

| Bone Code Alteration Location of Modification |

| 0 & nbsp; |

| &n bsp; |

| Photo Number/ Additional Descriptive Information |

| Drawing Number (Ctrl+Tab to exit)|

| &n bsp; _|

|-----------------------------|

| « Save and Exit » & nbsp; |

| <Save and Add Another |

| < Cancel &nb sp; |

+-F2 for list of Codes / F3 to Save & Exit/ Esc to cancel-+

BURNED BONES
The burned bone recording form is a single windowallowing multiple entries. The data fields require codes (F2) (Standards,pp. 95-106, Attachment 23).
Bone Code: The codes used in this field are thesame as those used in the inventory for commingled remains described previouslyin this manual.
Color: The codes used in this field follow thecodes outlined on the Standards Taphonomy Recording Form I and can be easilytransferred to the database.
% Affected: There is no F2 lookup menu for thisfield. The user is required to enter a percentage value between 0-100percent.
Surface Texture: The codes used in this fieldfollow the codes outlined on the Standards Taphonomy Recording Form I andcan be easily transferred to the database.
Warped: This field requires a "Y" (Yes or Present)or "N" (No or Not Present).
Shield Surfaces: the presence of surfaces shieldedthrough articulation or by dense soft tissues should also be recorded as"Y" (Yes or Present) or "No" (No or Not Present).

+-------- BURNED BONE CODING FORM --------+

Key Number: 7 Catalog #:CAT7 |

|-----------------------------|

| Bone Code Color % Affected Surface Warped Shield |

| Texture & nbsp; Surface |

| 0% 0 0 |

| &n bsp; |

|-----------------------------|

| « Save and Exit » & nbsp; |

| <Save and Add Another |

| < Cancel &nb sp; |

+--F2 for list of Codes / F3 to Save / Esc tocancel---+

ARTIFICIAL CRANIAL DEFORMATION
The artificial cranial deformation recording screenconsists of one window with all fields requiring numeric codes (F2) (Standards,pp. 160-163, Attachment 28).
Note: In some instances, the database fields do not followthe exact format or chronology as the fields on the Standards data recordingsheet. The following information takes you through each section ofthe database and explains som e of the inconsistencies:
General Category: the field codes in the databasefollow those in Standards.

Posterior Aspect:
The numerical codes for the first three fieldsin this section of the database follow the numerical codes for the samefields in Standards, however, the wording for the third field is inconsistentbetween the two sources. Do not let this confuse you.
The fourth database field (Pads, Shape) of thissection corresponds to the seventh field (Pad Shape) in the same sectionof Standards, however, the numerical codes are inconsistent.

(SOD) 0 = no data; not in Standards
(Standards) 4 = Irregular; not in SOD
(SOD) 9 = Not Observable; (Standards) 5 =Not Observable Pay careful attention to the F2 codes and how they correspondto the data on your recording form.
The fifth database field (Impressions of Bindings Visible)in the Posterior Aspect section corresponds to the fifth field (Pad Impressions)in Standards, however, the format is different between the two sources. The field in SOD req uires a yes/no answer (represented as a numerical code)for the existence of pad impressions, whereas the field in Standards requiresyou to choose a numerical code representing the number of pad impressions. There is an easy way to transfer these data from Standards to SOD if youfollow these instructions: 1) If the field on your Standards data recordingform is blank, enter zero into the database for "No Data".
2) If the Standards field contains a zero, enter2 into the database for "No" (no pad impressions).
3) If the field contains a one, two, or three onyour Standards data recording sheet, enter 1 into the database for "Yes"(yes, there are pad impressions). The sixth database field (Deformation Symmetric) correspondsto the sixth field (Pad location) in the Posterior Aspect section of theStandards data recording sheet, however, the format is inconsistent betweenthe two sources. Observe the foll owing instructions to transfer datafrom Standards to SOD: 1) If the field on your Standards data recordingform is blank, enter 0 into the database for "No Data".
2) If the Standards field contains a 1 (Midline),enter this description into the discussion section of the screenbecause there is no corresponding numerical code in SOD.
3) If the Standards field contains a 2 (symmetricallylateral to midline), enter 1 into the database for "Yes".
4) If the Standards field contains a 3 (Asymmetricallyleft) , enter 3 into the database for "No, left side".
5) If the Standards field contains a 4 (Asymmetricallyright), enter a 2 into the database for "No, right side". Anterior Aspect:
The first database field corresponds to the firstfield in Standards and follows the same numerical codes.
The second database field (Pad Impressions) correspondsto the fifth field (Pad impressions) in of Standards and follows the samenumerical codes.
The second database field (Pad Impressions) correspondsto the fifth field (Pad impressions) in of Standards and follows the samenumerical codes.
The third database field (Pad locations) correspondsto the second field (Pad location) in Standards and follows the same numericalcoding.
The fourth database field (Pads centered on midline)corresponds to the sixth data field (Pad location) in Standards, however,the format is inconsistent between the two sources. The followinginstructions will help you easily transfer data from your recording sheetto SOD: 1) If the data sheet is blank, enter 0 for "NoData".
2) If the data sheet contains a 1, enter 1 for"Yes" (yes, the pad is centered on the midline).
3) If the data sheet contains a 2,3, or 4, enter 2 for "No" (no, the pad is not centered on the midline). The fifth database field (Impressions of bindings visiblecorresponds to the eighth field (Impression of binding visible) in Standardsand follows the same numerical codes.
Discussion: This is an unlimited free textfield.

--------- CRANIAL DEFORMATION ---------+

|Key Number: 7 Catalog #:CAT7 |

|-----------------------------|

| General Category.....: 0 |

| &n bsp; |

| POSTERIOR ASPECT ANTERIOR ASPECT |

| Deformation Present..: 0 Deformation Present..: 0 |

| Pressure centered at.: 0 Pad Impressions......: 0 |

| Plane of pressure is Pad locations........: 0 |

| perpendicular to Pads centered on |

| transverse plane....: 0 midline....: 0 |

| Pads, Shape..........: 0 Impressions of |

| Impression of bindings visible...: 0 |

| bindings visible....: 0 |

| Deformation Symmetric: 0 |

| &n bsp; |

|Discussion: (Ctrl+Tab to exit text field) |

| &n bsp; _ « Save » |

| &n bsp; _ |

| &n bsp; _ <Cancel |

+--F2 for list of Codes / F3 to Save / Esc toCancel---+

TREPANATION
Trepanation (surgical removal of cranial vaultsections from living individuals) is recorded on a data entry screen withone window. The data fields require codes (F2) (Standards, pp. 159-160,Attachment 27).
Bone Code: The codes used in this field are thesame as those used in the inventory for commingled remains described previously,with the exclusion of the post-cranial bones.
Certainty: The codes used in this field followthose outlined on the Trepanation Recording Form.
Technique: The codes used in this field followthose outlined on the Trepanation Recording Form.
Healing: The codes used in this field follow thoseoutlined on the Trepanation Recording Form.
Maximum Dimensions, Minimum Dimensions, Number ofAttached Drawings: These fields are self explanatory.
Discussion: This is an unlimited free text area.

+-------- Trepanation Coding Form --------+

|Key Number: 7 Catalog #:CAT7 |

|-----------------------------|

| Location----- Bonecode: |

| &n bsp; |

| Certainty: 0 Technique: 0 Healing: 0 |

| &n bsp; |

| Maximum Dimension (mm): 0.0 |

| Minimum Dimension (mm): 0.0 |

| &n bsp; |

| Number of attached drawings: 0 |

| &n bsp; |

|Discussion: (Ctrl+Tab to exit textfield) |

| &n bsp; _ « Save » |

| &n bsp; _ |

| &n bsp; _ <Cancel |

+--F2 for list of Codes / F3 to Save / Esc toCancel---+

SKELETAL SAMPLES
Skeletal samples data entry screen consists oftwo windows. This data entry screen is a yes/no checklist of samples curated.The location field is the location of the items stored (Standards, p. 164-174,Attachment 29)
Note: Unlike the Standards data recording form, the databasetable for Skeletal Samples does not contain a text field to record comments. Any additional information can be recorded in the relevant location field.

+----- Checklist for Human Skeletal Samples -----+

|6+----- Checklist for Human Skeletal Samples-----+

| |Key Number: 7 Catalog#:CAT7 |

| |-----------------------------|

| |1. Middle portion of femur midshaft (Y/N).........: |

|7| Location: &n bsp; |

| | |

| |2. Upper central incisor (Y/N)....................: |

|8| Side (L/R).....................................: |

| | Location: &n bsp; |

| | |

|9|3. Left lower canine (Y/N)........................: |

| | Right lower canine (Y/N).......................: |

| | Location: &n bsp; |

| | |

| |4. Two lower premolars (Y/N)......................: |

| | Location: &n bsp; |

| | |

+-|5. Lower 2nd molar (Y/N)..........................: |

| Side (L/R).....................................: |

| Location: &nb sp; |

| & nbsp; |

+--------F3 to Save / Esc to Cancel--------+

+----- Checklist for Human Skeletal Samples -----+

|K+----- Checklist for Human Skeletal Samples-----+

|-|6. 5 Grams of trabecular bone (Y/N)...............: |

|1| Bone....: &n bsp; |

| | Location: &n bsp; |

| | |

|2|7. Middle 1/3 of clavicle (Y/N)...................: |

| | Location: &n bsp; |

| | |

| |8. 6th rib (Y/N)..................................: |

|3| Location: &n bsp; |

| | |

| |9. 5 CT scans of both humeri (Y/N)................: |

| | 5 CT scans of one femur (Y/N)..................: |

|4| Location: &n bsp; |

| | |

|5| « Save » <Cancel &nb sp; |

| | |

| +--------F3 to Save / Esc to Cancel--------+

|

SKELETAL PATHOLOGY
Many of the users may find the skeletal pathologydata recording screen and field requirements limiting when trying to recordthe wide pathological effects which health and disease have on the humanskeleton. The database and this t able in particular, places emphasis ondata integrity and comparative analysis of a population's health. Therefor,the data fields have a strict hierarchical structure. The observationsof the pathological bone conditions have been grouped into eight categor ies.Standards for Data Collection From Human Skeletal Remains groups data intonine categories with the ninth being miscellaneous conditions. This categorywas not included in this program due to lack of standard codes.
This section includes a step-by-step guide for encodingskeletal pathology beginning with how the data appears on the Standardsdata recording form.
Step 1: The pathology data appears as a set ofnumerical codes on the Pathology Recording Form.
Find the field for "bone" and match up the codewith one in the Skeletal Pathology Code Key (Table #_ , Attachment fromStandards). This will help you make your selections from the Bone Codepull down menus.
Once you've identified the bone from the Standards key

1. Press F2 and Enter to display pulldown menu number1. This menu requires you to choose the area of the skeleton that the affectedbone comes from.
Bone Code: The codes used in the field are the same asthose used in the inventory for commingled remains described previouslyin this manual with the addition of codes for the whole skull and skeleton(Appendix A). Standards uses n umerical codes to identify the bone,aspect, section, and side. We have included the Skeletal PathologyCode Key for you to refer to as you encode the data.
After you've made your choice, press Enter twice to displaypull down menu number 2.
2. Pull down menu number 2 requires you to choosea specific bone.
After you've made your choice, press Enter twice to displaypull down menu number 3.
3. Pull down menu number 3 requires you to identify thebone as right or left.
This information appears as a numerical code on the PaleopathologyRecording Form. Find the field for "side" and match up the code withone in the Skeletal Pathology Code Key. *NOTE: The Standards data recording form contains a thirdfield which indicates that both sides of a particular bone is affected.SOD does not contain this field, therefore, a separate entry must be madefor each side.
After you've made your selection press Enter twiceto display pull down menu number 4. 4. Pull down menu number 4 requires you to select thesegment of the bone in question. This information is represented as a numericalcode on the Paleopathology Recording Form. Find the field for "section"and match it up with the correct code on th e Code Key. Press Enter to display bonecode.
When you have completed the Bone code selection process,your sample selection will look like this: RFEMDEPI.
Note: A separate entry must be made for each affectedsegment of each bone .
Press Enter to move on to "Aspect" field.

Step 2: Locate the numerical code for "Aspect"on the Paleopathology Recording Form and match it up with one on the SkeletalPathology Code Key. This will help you make your selection from theAspect pull down menu.
Press F2 to display Aspect pull down menu. You may clickon your selection or use the up and down arrow keys. When you'vemade your selection, press enter.
Note: Aspect Codes: Be aware that the aspect codeslisted in SOD do not follow the exact order as those enumerated in Standards.The lists are presented as follows:

Standards Aspect codes: SOD Aspect Codes:
1-5 same
6=Dorsal/Posterior (Standards); 6=Both Medial and Lateral(SOD)
7=Ventral/Anterior (Standards); Posterior/Dorsal (SOD)
8=Circumferential (Standards); Ventral/Anterior (SOD)
9=Both Medial and Lateral(Standards); Circumferential(SOD) Pay careful attention to the F2 Aspect codes and how they correspond to the data on your recording form.
Press Enter to move on to "Condition" field.

Step 3: Condition
The condition code corresponds to eight generalobservations of pathology. The eight conditions are representedon the Paleopathology Recording Form as a bold header separating each section(example 4.0 FORMATION). The numerical code associated withthe header should be entered under the data field for condition. Or press F2 to display codes and scroll down to the desired condition.
Press Enter to move on to category field.

Step 4: Category: Depending on the condition codechosen, the required category fields are activated. The categoriesare specific descriptions of the general pathology. Each general pathologycan have as many as nine specific observations or categories. Thisinformation can be found on the Paleopathology Recording Form under theabbreviations "Obs1-Obs9" -
The observation or category codes appear on thePaleopathology Recording Form as a three digit number separated by periods.
The first digit of the code refers to the conditionor type of pathology. This information has already been entered underthe condition field and will not be a part of the category code. (See previous screen)
The second digit will correspond to the specificcategory number (for example, if the observation is 4.1.2, choose the pulldown screen from category 1 in SOD, or if the observation is 4.6.2, choosethe pull down screen from categor y 6 in SOD).
Press F2 to display pull down menus
Once you've displayed the pull down menu, choose thepathological observation that matches the one you found in the Pathologycode key.
The category code will be represented in the databaseby a two digit code which corresponds to the final two digits of the observationcode. Don't be confused by the periods which separate the observationcodes. They wil l not be part of the final category code.
Note: We recommend that you make your selectionsfrom the pull down menus rather than just entering the final two digitsof the pathology observation code. The reason for this being thatthe order of some of the "Categor y" pull down menus are inconsistent withthe lists of observations in the Skeletal Pathology Code Key.

Repeat Step 4 for all observations.

Skeletal Pathology Coding Form.

+------- Skeletal Pathology Code Form -------+

|Key Number: 7 Catalog#:CAT7 |

|-----------------------------|

| Bonecode Aspect Condition Categories 1-9 |

| 1 2 3 4 5 6 7& nbsp; 8 9 |

| 0 0 0 0 0 0 0 0 0 0 0 |

| &n bsp; |

|-----------------------------|

| « Save and Exit » & nbsp; |

| <Save and Add Another |

| < Cancel &nb sp; |

| &n bsp; |

+F2 for list of Codes / F3 to Save and Exit /Esc to Cancel+

Bone Code: The codes used in the field are thesame as those used in the inventory for commingled remains described previouslyin this manual with the addition of codes for the whole skull and skeleton(Appendix A).
Depending on the condition code chosen, the requiredcategory fields are activated. The category fields are activated accordingto the following chart:

Condition 1 Catalog 1-9
Condition 2 Catalog 1-3
Condition 3 Catalog 1-7
Condition 4 Catalog 1-8
Condition 5 Catalog 1-5
Condition 6 Catalog 1-3
Condition 6 Catalog 1-5 Each of the categories fields may contain numeric code valueswith a range determined by the number of the category field. The requiredfields value range is listed below: category 1 = 10-19
category 2 = 20-29
category 3 = 30-39
category 4 = 40-49
category 5 = 50-59
category 6 = 60-69
category 7 = 70-79
category 8 = 80-89
category 9 = 90-99 The category values are determined by the skeletal pathologycodes (F2) (minus the periods ".'s" in Table 6, Standards , pp. 114-115).
Example Coding for Skeletal Pathology:

|-----------------------------|

| Bonecode Aspect Condition Categories 1-9 |

| 1 2 3 4 5 6 7& nbsp; 8 9 |

| SKULL 0 1 0 0 0 0 53 61 0 0 0 |

| &n bsp; |

|-----------------------------|

* One cause of abnormal skull shape is craniostenosis orpremature close of the sutures. Skull is entered under the bone code. The condition is abnormal shape (1). If the abnormal shape is causedby premature closure of the sagittal suture then 53 is entered under category5. In some cases, such as in this example, the fusion is incompleteand 61 is entered under category 6. If fusion had been complete then62 would have been entered under category 6.&nbs p; Note that thecodes are the same as in the "Standards" volume except that the period(.) between the numerals is omitted.

|-----------------------------|

| Bonecode Aspect Condition Categories 1-9 |

| 1 2 3 4 5 6 7& nbsp; 8 9 |

| T10CEN 0 1 0 0 0 0 0 0 73 0 0 |

| &n bsp; |

|-----------------------------|

* The spinal column can deviate from its normal curvaturein either lateral or anterior directions. Scoliosis is a lateralcurvature which can result from a number of conditions including congenital. The position of the curva ture is identified by the most superior vertebrainvolved. If the tenth thoracic vertebrae is the most superior vertebrainvolved in the curvature then T10 is entered under bone code. Asthis is a condition of abnormal shape then 1 is entered in the conditioncategory. If the curvature of the vertebrae is to the right then73 is entered under category 7.

|-----------------------------|

| Bonecode Aspect Condition Categories 1-9 |

| 1 2 3 4 5 6 7& nbsp; 8 9 |

| LTIBM1_3 0 5 11 0 0 42 0 0 0 0 0 |

| &n bsp; |

|-----------------------------|

* Fractures can require a number of observations to be recorded. If the fracture is located in the middle third of the left tibia then LTIBM1_3is entered in the bone code. As this is a fracture then 5 is enteredin the condi tion space. A complete fracture would be recorded as11 in the category 1 column. Mature callus formation is entered as42 under category 4.

|-----------------------------|

| Bonecode Aspect Condition Categories 1-9 |

| 1 2 3 4 5 6 7& nbsp; 8 9 |

| LFEMP1_3 0 8 12 21 32 42 52 62 71 82 92 |

| &n bsp; |

|-----------------------------|

* The recording of arthritis requires the observation andrecording a number of surface features and the extent of bone area involvedestimated as thirds. This example is for the proximal end of theleft femur and requires LFEMP1_3 to be entered under the bone code. Arthritis is entered as 8 in the condition column. Lipping is observedto exhibit a sharp ridge and 11 is entered in the category 1 column. Less than 1/3 of the surface is involved so 21 is entered next.& nbsp; Thereis surface porosity with coalesced holes covering between 1/3 and 2/3 ofthe surface and thus 32 (coalesced porosity) and 42 representing the areaare entered. Eburnation represented by polishing without groovesis entered as 52 and its exte nt of 1/3 to 2/3 of the surface area is codedas 62. There are clearly observable periarticular resorptive foci(82) covering 1/3 to 2/3 of the area (92).

Dental Information

Dental information consists of database tables for adultmaxillary and mandibular inventory, adult hypoplasia, adult maxillary andmandibular measurements, adult dental morphology, supernumerary teeth anddental samples. There are also database tables for de ciduous maxillaryand mandibular teeth inventory and deciduous hypoplasia.
For each collection (key number), only one entryin an inventory table is allowed. You can not enter data into the otherdental tables unless you have previously made an entry in the inventorytables. All of the data fields for a specific tooth are dea ctivated untilit is coded as present in the inventory table.
The fields in the inventory tables correspond directlywith the fields on the Dental Caries and Wear Recording Form in Standards. This should make data entry into these tables very straightforward.

PERMANENT DENTITION:
INV(inventory): The inventory automatically defaultsto "(3)-missing with no associated alveolar bone". All of the fieldsassociated with a particular tooth are deactivated until the inventorycode is changed to a value other than (3). If the inventory codeis (3) and [Enter] is pressed, the cursor will move to the next tooth (line). If the inventory code is changed to a value other than (3) and [Enter]is pressed the remainder of the fields for that tooth (line) wil l activateand the cursor will move to the next field. Once the cursor has movedto a field other than the inventory field, the user can move the cursorforward to the next tooth's inventory field by pressing F4. You maypress F2 to display codes or simply type in the code number found on theDental Caries and Wear Recording Form.
DEVEL (development): The numeric database codes(F2) follow the codes for tooth development in Standards (pp. 55). If a code is not entered, the field will default to zero ("No Data").
Wear: The first field under Wear is the Smithwear encoding system. It is used in assessing the wear of the anteriorteeth and the values range from 0-8. The second field under Wearis the Scott wear encoding system. It is us ed in assessing the wear ofthe posterior teeth and the values range from 0-40 (1-10 for each toothquadrant). See Standards , pp. 47-49, 52-53 (Attachments 16 and 17).
Caries: The numeric database codes (F2) followthe codes for caries data in Standards (pp. 55).
ABSC (abscesses): The numeric database codes (F2)follow the codes for abscess data in Standards (pp. 55).
CALC (calculus): The numeric database codes scorefor the presence or absence of calculus, whereas, Standards scores thedegree of calculus build up. The database automatically defaults to 0 for"Not Observable" unless a numeric co de is entered. Therefore, if the fieldon the data recording form contains a 1, 2, or 3, record a 2 in the databasefield for "Present" . If the field on the data recording sheet containsa 0 or is blank, record a 1 for "Absent".
MODIF (Modifications): The numeric database codesfollow the codes for dental modifications in Standards (pp. 58).

Adult Maxillary Dental Inventory

+---------- MAXILLARY TEETH ----------+

|Key Number: 7 Catalog #: CAT7 |

| TOOTH INV DEVEL WEAR CARIES ABSC CALC MODIF|

|RIGHT---------------------------|

| 1) M3 3 0 0 0 0 0 0 0 0 0 0 |

| 2) M2 3 0 0 0 0 0 0 0 0 0 0 |

| 3) M1 3 0 0 0 0 0 0 0 0 0 0 |

| 4) P2 3 0 0 0 0 0 0 0 0 0 0 |

| 5) P1 3 0 0 0 0 0 0 0 0 0 0 |

| 6) C 3 0 0 0 0 0 0 0 0 0 0 |

| 7) I2 3 0 0 0 0 0 0 0 0 0 0 |

| 8) I1 3 0 0 0 0 0 0 0 0 0 0 |

|LEFT---------------------------|

| 9) I1 3 0 0 0 0 0 0 0 0 0 0 |

| 10) I2 3 0 0 0 0 0 0 0 0 0 0 |

| 11) C 3 0 0 0 0 0 0 0 0 0 0 |

| 12) P1 3 0 0 0 0 0 0 0 0 0 0 |

| 13) P2 3 0 0 0 0 0 0 0 0 0 0 |

| 14) M1 3 0 0 0 0 0 0 0 0 0 0 |

| 15) M2 3 0 0 0 0 0 0 0 0 0 0 |

| 16) M3 3 0 0 0 0 0 0 0 0 0 0 |

| « Save » <Cancel ; |

+-F2 for list of codes / F3 to Save / F4 go tonext tooth-+

Adult Mandibular Dental Inventory

+---------- MANDIBULAR TEETH ----------+

|Key Number: 7 Catalog #:CAT7 |

| TOOTH INV DEVEL WEAR CARIES ABSC CALC MODIF|

|LEFT---------------------------|

| 17) M3 3 0 0 0 0 0 0 0 0 0 0 |

| 18) M2 3 0 0 0 0 0 0 0 0 0 0 |

| 19) M1 3 0 0 0 0 0 0 0 0 0 0 |

| 20) P2 3 0 0 0 0 0 0 0 0 0 0 |

| 21) P1 3 0 0 0 0 0 0 0 0 0 0 |

| 22) C 3 0 0 0 0 0 0 0 0 0 0 |

| 23) I2 3 0 0 0 0 0 0 0 0 0 0 |

| 24) I1 3 0 0 0 0 0 0 0 0 0 0 |

|RIGHT---------------------------|

| 25) I1 3 0 0 0 0 0 0 0 0 0 0 |

| 26) I2 3 0 0 0 0 0 0 0 0 0 0 |

| 27) C 3 0 0 0 0 0 0 0 0 0 0 |

| 28) P1 3 0 0 0 0 0 0 0 0 0 0 |

| 29) P2 3 0 0 0 0 0 0 0 0 0 0 |

| 30) M1 3 0 0 0 0 0 0 0 0 0 0 |

| 31) M2 3 0 0 0 0 0 0 0 0 0 0 |

| 32) M3 3 0 0 0 0 0 0 0 0 0 0 |

| « Save » <Cancel ; |

+-F2 for list of codes / F3 to Save / F4 go tonext tooth-+

ADULT DENTAL MEASUREMENTS
The dental measurement fields are self explanatory.The measurement fields for each tooth (line) are activated only if thetooth is recorded in the dental inventory table as something other than"(3) missing, with no associated alve olar bone". To activate fields fora tooth, "Edit_data" must be chosen from the Main Menu and inventory valuemust be changed for the specific tooth in the inventory table. Then themeasurement table must be edited. See Standards, pp. 51-53, Attachment 20).
If you have made a mistake in the inventory field andcannot activate the measurements fields, "Edit_data" must be chosen fromthe Main Menu and inventory values must be changed for the specific toothin the inventory table. Then th e measurement must be edited.
Note: The Dental Measurements Recording Form containsfields for recording three measurements from each tooth type on the leftside of the dental arcade. The right measurement may be substitutedwhen the left is not observable and will be identified by an "R" writtenin the margin above or below the specific column.
The database contains fields for recording rightand left measurements, thus, any measurements take from the right sideof the dental arcade should be recorded in the fields for the same side.
Also, the database contains a field for recordingroot length, a measurement not recorded on the Standards data recordingform. Therefore, this database field should remain blank unless themeasurement has been recorded elsewh ere.

+-------- MAXILLARY DENTAL MEASUREMENTS --------+

|Key Number: 7 Catalog #:CAT7 |

| TOOTH MESIO-DISTAL BUCCO-LINGUAL CROWN HEIGHT ROOT LENGTH |

|RIGHT----------------------------- |

| 1) M3 0.000 0.000 0.000 0.000 |

| 2) M2 0.000 0.000 0.000 0.000 |

| 3) M1 0.000 0.000 0.000 0.000 |

| 4) P2 0.000 0.000 0.000 0.000 |

| 5) P1 0.000 0.000 0.000 0.000 |

| 6) C 0.000 0.000 0.000 0.000 |

| 7) I2 0.000 0.000 0.000 0.000 |

| 8) I1 0.000 0.000 0.000 0.000 |

|LEFT----------------------------- |

| 9) I1 0.000 0.000 0.000 0.000 |

| 10) I2 0.000 0.000 0.000 0.000 |

| 11) C 0.000 0.000 0.000 0.000 |

| 12) P1 0.000 0.000 0.000 0.000 |

| 13) P2 0.000 0.000 0.000 0.000 |

| 14) M1 0.000 0.000 0.000 0.000 |

| 15) M2 0.000 0.000 0.000 0.000 |

| 16) M3 0.000 0.000 0.000 0.000 |

| « Save » <Cancel ; |

+--F2 for list of Codes / F3 to Save / F4 goto next tooth--+

+------- MANDIBULAR DENTAL MEASUREMENTS --------+

|Key Number: 7 Catalog #:CAT7 |

| TOOTH MESIO-DISTAL BUCCO-LINGUAL CROWN-HEIGHT ROOT-LENGTH |

|LEFT------------------------------|

| 17) M3 0.000 0.000 0.000 0.000 |

| 18) M2 0.000 0.000 0.000 0.000 |

| 19) M1 0.000 0.000 0.000 0.000 |

| 20) P2 0.000 0.000 0.000 0.000 |

| 21) P1 0.000 0.000 0.000 0.000 |

| 22) C 0.000 0.000 0.000 0.000 |

| 23) I2 0.000 0.000 0.000 0.000 |

| 24) I1 0.000 0.000 0.000 0.000 |

|RIGHT-----------------------------|

| 25) I1 0.000 0.000 0.000 0.000 |

| 26) I2 0.000 0.000 0.000 0.000 |

| 27) C 0.000 0.000 0.000 0.000 |

| 28) P1 0.000 0.000 0.000 0.000 |

| 29) P2 0.000 0.000 0.000 0.000 |

| 30) M1 0.000 0.000 0.000 0.000 |

| 31) M2 0.000 0.000 0.000 0.000 |

| 32) M3 0.000 0.000 0.000 0.000 |

| « Save » <Cancel ; |

+--F2 for list of Codes / F3 to Save / F4 goto next tooth--+

ADULT HYPOPLASIA
The hypoplasiatable may contain one or more records. For codes (F2), and Standards, pp. 56-58 , (Attachment 18).
Tooth Code: Press F2 to display the toothcodes. You may click on the desired selection or use the "up" and"down" arrow keys to cursor to the tooth you want. Press Enter tomove along to the next field.
Type Code: The field for "type code" corresponddirectly to the codes in Standards, therefore, you can simply transferthe number from the "type" data field on the recording form to the "typecode" field in the database. You may also press F2 to display codes.
Measurement: Transfer the measurement fromthe data recording sheet to the database.
Color Code: The order in which the colorcodes appear in the database corresponds directly to the order in Standards,therefore, you can simply transfer the number from the "color" field onthe data recording form to the "col or code" field in the database. You may also press F2 to display codes.

+---------- ADULT HYPOPLASIA ----------+

|Key Number: 7 Catalog#:CAT7 |

|-----------------------------|

| Tooth Code Type Code Measurement Color Code |

| 0 0.000 & nbsp; 0 |

|-----------------------------|

| « Save and Exit » & nbsp; |

| <Save and Add Another |

| < Cancel &nb sp; |

+-F2 for list of codes / F3 to Save & Exit/ Esc to Cancel-+

DENTAL MORPHOLOGY
The dental morphology table consists of informationfrom both the maxillary and mandibular teeth. All of the data fields usenumerical codes. See Standards , pp. 63-68, Attachment 20, for codingcriteria. NOTE: You will need to press F2 for the GroovePattern fields in the mandibular section. These observations willnot appear as numerical values on your data recording sheet.

+----------- DENTAL MORPHOLOGY -----------+

|Key Number: 7 Catalog #:CAT7 |

|Trait M3 M2 M1 P1 I2 I1|I1 I2 P1 M1 M2 M3 |

|---Maxillary------Right-----|-----Left-----|

|Winging: 0|0 &nb sp; |

|Shoveling: 0 0|0 0 &nb sp; |

|Double Shoveling: 0 0|0 0 &n bsp; |

|Peg-Shaped: 0 | 0 &nbs p; |

|Root Number: 0 | 0 &nb sp; |

|Hypocone: 0.0 0.0 0.0 | 0.0 0.0 0.0 |

|Cusp 5(Metaconule): 0 0 0 | 0 0 0 |

|Carabelli's Trait: 0 0 0 | 0 0 0 |

|Enamel Extensions: 0 0 0 | 0 0 0 |

|---Mandibular-----Right-----|-----Left-----|

|Groove Pattern: 0 0 0 | 0 0 0 |

|Cusp Number: 0 0 0 | 0 0 0&nb sp; |

|Protostylid: 0 0 0 | 0 0 0&nb sp; |

|Cusp 5: 0 0 0 | 0 ; 0 0 |

|Cusp 6: 0 0 0 | 0 ; 0 0 |

|Cusp 7: 0.0 0.0 0.0 | 0.0 0.0 0.0 |

|Root Number: 0 0 0 | 0 0 0&nb sp; |

|Root Number: 0 | 0 &nb sp; |

| « Save » <Cancel ; |

+----F2 for list of codes / F3 to Save / Escto Cancel----+

Adult Supernumerary Teeth (Standards, Attachment 15):

+--------- SUPERNUMERARY TEETH ---------+

|Key Number: 7 Catalog #:CAT7 |

| &n bsp; |

|POSITION ADJ. TEETH INV DEVEL WEAR CARIES ABSC CALC|

|-----------------------------|

| 0 3 0 0 0 0 0 0 0 0 0 |

|-----------------------------|

| « Save and Exit » & nbsp; |

| <Save and Add Another |

| < Cancel &nb sp; |

+----F2 for list of Codes / F3 to Save and exit----+

Adjacent Teeth: Use tooth codes (F2) from adulthypoplasia.
Inventory, Development, Wear, Caries, Abscess andCalculus fields use the same codes (F2) as the adult dental inventoryscreens.

Dental Samples Curated/Cast Made
This screen uses check boxes which act like toggleswitches. They indicate a state that is one of two values, such as "yes"or "no". The state of a check box may be changed by pressing [Enter] whilethe cursor is in a box or by clic king the mouse in a box. To move the cursorwithout changing a check box use the [Tab] key.

+------- Samples Curated or Cast Made -------+

|Key Number: 7 Catalog #:CAT7 |

|----------------BLANK = NO, X = YES----|

| SAMPLES CURATED CASTS MADE |

| Mandibular Teeth Cast: [ ] |

| Maxillary Teeth Cast: [ ] |

| Maxillary Central Incisor: [ ] [] |

| Mandibular Canine: [ ] [] |

| Mandibular Second Molar: [ ] [] |

| Mandibular First Premolar: [ ] |

| Mandibular Second Premolar: [ ] |

| Calculus Sample: [ ] |

| Tooth calculus sample collected from: |

| Describe Premortem Modifications: Ctrl+tabto exit |

| &n bsp; _ |

| « Save » <Cancel ; |

+----Press ENTER or click mouse to toggle ON/OFF----+

Tooth calculus sample collected from: This field usesthe tooth codes used in the adult hypoplasia table.

Deciduous Maxillary and Deciduous Mandibular TeethInventory and Hypoplasias
The deciduous dental information tables (Deciduous MaxillaryInventory, Deciduous Mandibular Inventory, Deciduous Hypoplasia) collectthe same data as the permanent teeth tables.

+------- DECIDUOUS MANDIBULAR TEETH -------+

|Key Number: 7 Catalog #:CAT7 |

| TOOTH INV DEVEL WEAR CARIES ABSC CALC MODIF|

|LEFT---------------------------|

| 61) M2 3 0 0 0 0 0 0 0 0 0 0 |

| 62) M1 3 0 0 0 0 0 0 0 0 0 0 |

| 63) C 3 0 0 0 0 0 0 0 0 0 0 |

| 64) I2 3 0 0 0 0 0 0 0 0 0 0 |

| 65) I1 3 0 0 0 0 0 0 0 0 0 0 |

|RIGHT---------------------------|

| 66) I1 3 0 0 0 0 0 0 0 0 0 0 |

| 67) I2 3 0 0 0 0 0 0 0 0 0 0 |

| 68) C 3 0 0 0 0 0 0 0 0 0 0 |

| 69) M1 3 0 0 0 0 0 0 0 0 0 0 |

| 70) M2 3 0 0 0 0 0 0 0 0 0 0 |

| &n bsp; |

| « Save » <Cancel ; |

+-F2 for list of codes / F3 to save / F4 go tonext tooth-+

+------- DECIDUOUS MAXILLARY TEETH --------+

|Key Number: 7 Catalog #:CAT7 |

| TOOTH INV DEVEL WEAR CARIES ABSC CALC MODIF|

|RIGHT---------------------------|

| 51) M2 3 0 0 0 0 0 0 0 0 0 0 |

| 52) M1 3 0 0 0 0 0 0 0 0 0 0 |

| 53) C 3 0 0 0 0 0 0 0 0 0 0 |

| 54) I2 3 0 0 0 0 0 0 0 0 0 0 |

| 55) I1 3 0 0 0 0 0 0 0 0 0 0 |

|LEFT---------------------------|

| 56) I1 3 0 0 0 0 0 0 0 0 0 0 |

| 57) I2 3 0 0 0 0 0 0 0 0 0 0 |

| 58) C 3 0 0 0 0 0 0 0 0 0 0 |

| 59) M1 3 0 0 0 0 0 0 0 0 0 0 |

| 60) M2 3 0 0 0 0 0 0 0 0 0 0 |

| &n bsp; |

| « Save » <Cancel ; |

+-F2 for list of Codes / F3 to Save / F4 go tonext tooth-+

+--------- DECIDUOUS HYPOPLASIA ---------+

|Key Number: 7 Catalog#:CAT7 |

|-----------------------------|

| Tooth Code Type Code Measurement Color Code |

| 0 0.000 & nbsp; 0 |

|-----------------------------|

| « Save and Exit » & nbsp; |

| <Save and Add Another |

| < Cancel &nb sp; |

+-F2 for list of codes / F3 to Save & Exit/ Esc to Cancel-+

UPDATING DATA

The "Update_data" option on the Main Menu is usedto add new records to the supplemental database tables. To use the "Update_data"option records must exist in the general information table and the inventoryfor complete remains or inventory for commingled remains for the key numberthat you wish to update. For example, if you had entered information aboutkey number 10 into the general information and the inventory for completeremains tables but no other tables and you wished to add dental inventoryinformation you would choose "Update_data" from the Main Menu. When "update_data"is chosen the Main Menu is remove from the screen and replaced with the"Locate Record" screen below.

+----- LOCATE RECORD -----+

| Current key # Current Catalog #|

| 1 CAT1 |

|------------------|

| < Enter New |

| < Browse |

| « OK » |

| < Cancel |

+------------------+

From the "LOCATE RECORD" screen you must choose an existingrecord from the general information table. This can be done by choosingthe "<Enter New" button and entering a valid key number and/or catalognumber.
The user can also choose the "<Browse" buttonand use the keyboard or mouse to highlight the desired record and pressthe [Esc] key to exit the browse window (browse window will be explainedin detail in the Browse option). Once the desired key number is chosenand displayed on the "LOCATE RECORD" screen the user must press the "<OK " key. When a valid existing record has been chosen the "SupplementalMenu" is displayed and the table names on the menu are marked if they alreadyc ontain records with the chosen key number. The user may, at this time,add new records to one or more or the supplemental tables. The data entryscreen for the supplemental tables are described in the "Supplemental Information"section of "Adding New Data". To exit the "Update_data" mode press the"Exit Menu" option on the supplemental menu.

EDITING DATA

The "Edit_data" option on the Main Menu displaysa pull-down menu which lists all of the data tables in SOD. Once the userchooses a table to edit, SOD displays a screen form like the Add Data screenforms, plus a "Controls" win dow. The "Controls" window is always the topor current window, which contains the cursor. From the control window theuser may scroll through the tables records, edit the records or deleterecords. If the table selected for editing has no data, a "No data t o edit"message is displayed and the user is returned to the Main Menu.
The "Controls" windows will have one of two layouts.Depending upon the window design of the data screen, the tables which havedata entry screens with all of the data fields on one window have the followinglayout.
The first four buttons (Top, Next, Prior, Bottom)are designed to move the user through the records in the table. "<Top"causes the first record in the table (smallest key number) to be displayed."<Next" displays the next rec ord and "<Prior" moves backs one record."<Bottom" displays the last record in the table (largest key number).The "<locate" button displays the "Locate Record" window, as seen below:

+----- LOCATE RECORD -----+

| Current key # Current Catalog #|

| 1 CAT1 |

|------------------|

| < Enter New |

| < Browse |

| « OK » |

| < Cancel |

+------------------+

+-Controls-+

| |

| < Top |

| |

| < Next |

| |

| < Prior |

| |

| < Bottom |

| |

| < Locate |

| |

| < Edit |

| |

| < Delete |

| |

| < Quit |

| |

+------+

On the "LOCATE RECORD" screen an existing recordmay be chosen from the table. This can be done by selecting the "<EnterNew" button and entering a valid key number and/or catalog number or byselecting the "<Browse " button which displays a BROWSE window.Within a BROWSE window, the user may use the keyboard or mouse to scrollto the desired record. As the user highlights the desired record, the highlightedrecord's key number and catalog number are displayed in th e "LOCATE RECORD"window. The user must then press the [Esc] key to exit the BROWSE window.The Browse window will be explained in detail in the Browse section ofthis manual. Once the desired key number is chosen and displayed on the"LOCATE RECORD" screen t he user must press the "< OK " key. The datascreen then displays the chosen record.

The "Edit" button, on the "Controls" window,moves the cursor to the first active field on the data window and makesthat window the current window. The user may also activate "Edit" by clickingthe mouse on the data screen or any data field on the data screen. Thesame procedures are used to edit data as when adding new data. "F2" opensa list window and "F3" saves the changes and move the cursor back to the"Controls" window. Pressing the "Esc" key cancels the ch angesand moves the cursor to the "Controls" window. The program also checksthe data fields for valid codes and will not allow the user to exit thefield unless a valid code is used or "Esc" is pressed, thus canceling thechanges for the current record.

The "Delete" button marks the current record inthe current table as Deleted. When the user presses the "Delete" button,a warning is displayed which asks the user to confirm the delete. The "Delete"key can also affect records wit h the same key number in other tables. Thedata in some tables depends on data in other tables. For example, if thereis an entry in the Dental Measurement Table, there must also be an entryin the Dental Inventory Table. Therefore, if a record is deleted in theDental Inventory Table, the corresponding record must also be deleted inthe Dental Measurement Table. SOD has built-in delete procedures that followthe rules below:

Browse
The "Browse" option on the Main Menu displays apull-down menu which lists all of the data tables. The user then choosesa table and the Browse Window is displayed. A Browse Window is a convenienttool for viewing data. The Browse W indow displays data in a tabular form.Each row is a record in the table and each column is a field in the table.In a browse window the user can scroll horizontally or vertically to seedifferent parts of the database table. The browse can be manipulated in a variety of ways by the mouse or keyboard. A Browse Window has standardFoxPro windows symbols around the perimeter, which can be used with a mouseto manipulate the window. An example browse window with its componentslabeled is displayed below:
Close Box: Click the left mouse button on theclose box or press the "Esc" key to close a browse window.
Zoom Control: Click the left mouse button on thezoom box to enlarge browse window to fill the screen, or, if the browsewindow is already full size, click the left mouse button to return screento previous size.
Arrow symbols: Click the left mouse button onthe appropriate symbol to scroll horizontally or vertically. Use the arrowkeys to scroll using the keyboard.
Thumb: Click and hold the left mouse button anddrag the thumb to scroll rapidly.
Size Control: Point the mouse and drag to resizethe browse window.
Window Splitter: Point the mouse and drag this symbolto split the browse window into two windows. This is useful for viewingdifferent portions of a table. For example, a user may split the windowto simultaneously view the first field a nd the last two fields in a table.

There are several other functions to manipulate the browsewindow.
Moving the Window: Point the mouse to the windowtitle and click and hold the mouse button to drag the browse window toa new location.
Changing the size of data fields: Point the mouseto the line between the data fields, and press the mouse button and drag.
Viewing "Memo" fields: Memo fields can containunlimited text. To view the information in these fields the user must highlightthe word "Memo" in the desired row (record) and press Ctrl+PgDn. This willopen a memo window. Resize th e memo window, then move it so that it appearsbelow the browse window. The user may now return to the browse window andscroll through the records. The memo information will be displayed in thememo window. When the browse window is closed, the memo window will closealso.

REPORTS

The "Reports" option on the Main Menu is a wayto obtain information from the database tables. This option displays apull-down menu with options to run Standard Reports or Custom Reports.Standard Reports option provides the us er with a point-and-click interfacethat creates database queries from the General Information table put canproduce output from any data table. The Custom Reports option providesuses with the ability to write their own SQL (Structured Query Language)Select statements, thus, giving the users unlimited report output options.

Standard Reports
When the user chooses the "Standard Reports" option,the following window is displayed.
Define Query Box: The check boxes (brackets) inthe define query section allow the user to define delimiting statementsfor the query. If the "All Records" check box is toggled the remainingcheck boxes are automatically deactivate d. Each check box following the"All Records" check box displays a window with instructions and a dataentry area. An example of these windows is shown below. The user may togglemore than one check box.

+------------- DEFINE QUERY -------------+

|+----Define Query-----+ &nb sp; |

||Choose one or more options: | Choose Database Table |

|| Use Space Bar to toggle | +-----------------+ |

|| On or Off. | |GENERAL INFORMATION | |

|| | +-----------------+ |

|| [ ] All Records: | & nbsp; |

|| [ ] By Key Number Range | Choose Output Format |

|| [ ] By Catalog Number | +-----+ |

|| [ ] By Sex code | | Formated| &n bsp;|

|| [ ] By Age Code | +-----+ & nbsp; |

|| [ ] By Site Name | & nbsp; |

|| [ ] By Site Number | Choose Output Destination |

|| [ ] By State and County | +-----+ |

|| [ ] By Collection Locat. | | Screen | |

|| [ ] By Collection Affil. | +-----+ |

|+--------------+ &nbs p;|

| «Run Report» < Exit & nbsp; |

+----------------------------------+

[X] By Catalog Number:

+-------------------+

| Type catalog number or any part of |

| the catalog number using the |

| following wildcard charactors: |

| "_" single unknown charactor. |

| "%" one or more unknown charactors. |

| |

| Catalog Number: |

| | & nbsp; « Ok » <Cancel &nb sp; |

+-------------------+

[X] By Collection Affiliation:

+------------------------+

| Enter Affiliation Information in one or more |

| of the following fields. You may use the |

| following wildcard charactors: |

| "_" single unknown charactor. |

| "%" one or more unknown charactors. |

| &n bsp; |

|Tribal Affil: |

| Period: |

| Culture: ;|

| Phase: & nbsp; |

| Variant: ;|

| « Ok » <Cancel |

+------------------------+

Choose Database Table: The user must choose a databasetable from which information is taken. All of the data tables are listedin this pop-up list. Choose the table by highlighting its name and clickingthe mouse or pressing ente r.
Choose Output Format: The user has a choices "Formated"or "ASCII" output formats. The Formated output has the same layout as thedata entry screens and the ASCII format is in tabular form.
Choose Output Destination: The three choices foroutput destination are Screen, Printer or File. There must be a printerinstalled in the Printer Setup Option on the Maintenance Option of theMain Menu to use the printer destinatio n. If the user chooses the Filedestination, a file is created in the directory "OUTPUT" under the SODinstallation directory with the name of the output table plus a ".TXT".For example, if SOD is installed in "Z:\SOD" the output file for the GeneralInforma tion Table will be "Z:\SOD\OUTPUT\MAIN.TXT". It is recommended thatusers send the output destination to the Screen the first time to checkthe query results.

Custom Reports
When the user chooses the "Custom Reports" option, thefollowing window is displayed:

+----------- CUSTOM QUERY SCREEN -----------+

| &n bsp; +------+|

| Query Description: | < Top ||

| LIST ALL INFO. STORED IN TABLE MAIN, | ||

| WHERE THE SITE NAME IS "SITE 1" | < Next ||

| &n bsp; | ||

| Query (SQL): Press Ctrl+Tab to Exit | < Prior ||

| SELECT * ; | ||

| FROM MAIN &nbs p; | < Bottom ||

| WHERE site1nam == "SITE 1" | ||< /P

| &n bsp; | < Add ||

| &n bsp; | ||

| &n bsp; | < Edit ||

| &n bsp; | ||

| &n bsp; | < Delete ||

| &n bsp; | ||

| &n bsp; | < Run ||

| &n bsp; | ||

| « Save » <Cancel | < ; Quit ||

| &n bsp; +------+|

+----------Press F1 For Help with SQL----------+

The "Custom Query Screen" consists of areas forthe user to create custom Select-SQL statements, thus, giving the userunlimited report output ability. The user's Select-SQL statements may alsobe saved, with descriptive text, to b e reused or modified to form differentqueries. The right side of the "Custom Query Screen" is the control section.The first four buttons (Top, Next, Prior, Bottom) give the user the abilityto scroll through the saved queries. The "<Add" button clears t he QueryDescription and Query (SQL) areas and moves the cursor to the query descriptionarea. The "<Edit" button moves the cursor to the Query Descriptionarea, allowing the user to edit the current query. The "<Delete" buttondeletes the currently dis played query. The "<Run" button causes SODto interpret the SQL statement and produce output.

The Query Description area should contain a shortdescription of the custom query, but is not required. The Query (SQL) areamust contain standard SQL query language statements. The SQL statementsmust be syntactically correct. The user may press th e "F1" key to displaya help window for the Select-SQL statements. The user must press "<<Save"or "<Cancel" to return to the controls area of the screen to "Run"the query. If the SQL statements are syntactically incorrect, a warningmessage is disp layed and no output is produced.

A complete description of Select-SQL syntax is availableon the help window by pressing "F1". Only a short overview is discussedin this manual. Select-SQL statements can be broken into several componentparts: SELECT, FROM, WHERE and GROUP/ORDER co mponents. The minimum Select-SQLstatement consists of SELECT and FROM components. The Select-SQL statementcan be expressed in a text format as:
SELECT one or more database fields FROM one or more databasetables WHERE table join-conditions AND query filter-conditions.

The SELECT component SQL syntax is as follows:

SELECT [DISTINCT] tablename.fieldname, tablename.fieldname,...
SELECT clause specifies the database fields, constantsand expressions to be displayed in the query results. If DISTINCT is specified,duplicate information is excluded in the query results. DISTINCT can onlybe used once in a SELECT stat ement and operates on the fieldname it precedes. The FROM component SQL syntax is as follows: FROM tablename, tablename,...
The FROM clause lists the tables that contain the dataretrieved by the query. The user must list each table that has a fieldlist in the SELECT component. The user may also list a table that doesnot have a field in the SELECT list, as l ong as a field in that table isused as a filter condition in the WHERE clause. If more than one tableis listed, the WHERE clause must contain a table join condition. The WHERE component syntax is as follows: WHERE join-condition AND join-condition AND/OR filter-conditionAND/OR filter-condition AND/OR...
The WHERE clause specifies fields that link tables inthe FROM clause (join-condition) and delimits the records retrieved bythe query (filter-condition). All join-conditions must be linked by a logicalAND operator. The join-conditions h ave the form:
<tablename1.fieldname <comparison <tablename2.fieldname The comparison is one of the following: <Less than
Greater than
=Equal to (numeric)
<,!=Not equal to
<=Less than or equal to
=Greater than or equal to
==Equal to (character) The join-conditions must be linked to the filter-conditionsby a logical AND or a logical OR operator. All filter-conditions must beconnected by an AND or OR operator. The filter_conditions may use the comparisonoperator listed above plus any of the fol lowing condition forms: FORM:<field [NOT] BETWEEN <start-rangeAND <end-range
EXAMPLE:customer.balance BETWEEN 100 AND 200
FORM:<field [NOT] IN <comma-delimited-list
EXAMPLE:age.code IN (3,4,8,9)
FORM:<field [NOT] LIKE <charactor-expression
EXAMPLE:student.name LIKE "BOB%"
A charactor expression can be a string in quotes or astring in quotes with a wildcard charactor % (percent sign: one or moreunknown charactors) or _ (underscore: a single unknown charactor). The ORDER BY component syntax is as follows: ORDER BY <tablename.fieldname,<tablename.fieldname2,...
The ORDER BY clause sorts the query results by one ormore fields. Each field listed in the ORDER BY clause must also be in theSELECT list. The query result will be displayed in a browse window unlessa DESTINATION clause is included in the SELECT-SQL statement. A DESTINATIONclause is placed after the FROM clause in a SELECT-SQL statement and canhave one of the following forms: TO FILE <filename [ADDITIVE}]
TO PRINTER
The TO FILE DESTINATION clause writes the query resultin a text file or appends the query result to a text file if the word "ADDITIVE"is included. The TO PRINTER DESTINATION clause sends the query result toa printer.

MAINTENANCE

The "Maintenance" option on the Main Menu is forSOD configuration and setup or are utilities that take action on all databasetables in SOD. When the "maintenance" option is chosen the following pull-downmenu is displayed.
Setup
The "Setup" option sets the default configurationfor SOD. The following data entry window is displayed:

+--------+

| Setup |

+--------|

| Printer Setup |

+--------|

| Pack all |

| ReIndex |

| Delete records |

+--------|

| Export Data |

| Import Data |

+--------+

+--------- SOD SETUP INFORMATION ----------+

| &n bsp; |

|Key Number Range: &nb sp; |

| Minimum Key Number: 1 ; |

| Maximum key Number: 10 &nbs p; |

|Collection location: |

| Organization: CAST/NCRI-SW |

| Address: 12 OZARK HALL &nbs p; |

| City: FAYETTEVILLE &n bsp; |

| State: AR ; |

| Zip Code: 72701 ; |

| System Information: |

| Where is SOD installed? &n bsp; |

| Disk Drive [C:]: C: & nbsp; |

| Directory [\SOD\]: \SOD\ &n bsp;|

|Disk Drive Where Data Backups will Written[A:]:A: |

| « Save » <Cancel ; |

+-------------------------------+

Key Number Range: The Key Number value is used asan unique identifier for each collection. When SOD software is distributed,a range of Key Numbers is also distributed. This range of Key Numbers mustbe entered in the Minimum and Maximum Key Number fields before the userstarts entering data. If the user is intending to install SOD on more thanone computer, the range should be divided so that each computer has anunique subset of Key Numbers.
Location Collection: This information is usedas the default values on the General Information table data entry screen.
System Information: This information is used bySOD to find its different components.

Printer Setup
The "Printer Setup" option allows SOD to take advantageof the characteristics of the user's printer. The following "Printer DriverSetups" window is displayed when "Printer Setup" is chosen:

+--------------------------+

| Printer Driver Setups: |

| +-------------+ |

| | <None | < Edit |

| | prorpinter | |

| | kx-p1125 | < New |

| | hp3 | & nbsp; |

| | psprint | < Delete |

| | HPIII | ; |

| | prorpinterSMALL | < Set Default |

| | EPLX800 | &nb sp;|

| | GENERIC | < Cancel |

| | | ; |

| | | « Set & amp;raquo; |

| +-------------+ |

| &n bsp; |

+--------------------------+

From this window, you can create a print driver setup,delete an existing setup, modify a setup, specify a default setup, loada setup and clear the current setup. The user may select an existing printerdriver from the list on the "Printer Setup" window and edit the printersetup to match the characteristics of their printer, but it is highly suggestedthat the user create a new printer setup.

Creating a new printer setup: A new user willneed to create a new printer setup. This is done by choosing the <Newpush button to display the "Printer Setup Editing" window.

To create a new printer driver, choose a printer from the"Printers" list. If your printer is not listed, choose one that most closelymatches your printer type. Once a printer has been chosen the general characteristics,fonts, page size, line and charac ter size, and margins may be specified.Enter the printer name in the "Setup Name" text box and choose the <OKpush button to save the setup. The "Printer Setup Editing" window willclose and the "Printer Driver Setup" window will open. Highlight the setu pname and press the <Set Default push button.

Pack All
This option permanently removes all records markedfor deletion. Records may be marked for deletion while editing data orby choosing the "Delete Records" option on the Maintenance menu. Recordsmarked for deletion are not physicall y removed from the data tables untilthe "Pack All" option is chosen. When this option is chosen the followingwindow is displayed:

+-------------------------+

| &n bsp; |

| 'Pack All' will REMOVE all records markedfor |

| deletion in all of the database tables.ARE |

| YOU SURE? &nbs p;|

| &n bsp; |

| < Yes « No » |

+-------------------------+

ReIndex
The "ReIndex" option recreates the database tablesindex files. This should be done any time SOD stops (hangs) or if the userexits SOD without choosing the "Quit" option on the Main Menu (rebootingthe computer without quitting SOD ). The following window is displayed whenthis option is chosen:

+-------------------------+

| &n bsp; |

| 'ReIndex' will RECREATE the index filesfor |

| all of the database tables. This maytake some |

| time. ARE YOU SURE YOU WISH TO REINDEX? |

| &n bsp; |

| < Yes « No » |

+-------------------------+

Delete Records
This option provides the user with the abilityto mark for deletion large groups of records by entering a range of KeyNumbers. After choosing the "<Delete" button, SOD asks the userto confirm the range of Key Numbers to b e deleted. The user is thenreminded the run "Pack All" to remove the marked records.

+----------------------+

| &n bsp; |

| Pick a range of key numbers todelete |

| &n bsp; |

| Delete Key Number: 0 |

| &n bsp; |

| through Key Number: 0 |

| &n bsp; |

&nb sp;|

| <Delete <Cancel |

| | |

| Are you sure you wish to DELETE all records |

| with key numbers 0 through 2? |

| &n bsp; |

| < Yes « No » |

+-------------------------+

+---------MESSAGE WINDOW---------+

&nb sp; |

| Record keys 0 through 2 have been markedfor |

| deletion. Run 'Pack all' under the maintenance|

| option on the main menu to removethe records |

| from the database files. |

| &n bsp; |

|Press any key to continue ... |

Export Data
SOD provides a method to copy the data tables todisk as Dbase (.DBF) files or ASCII (text) fixed field format files. Theuser must choose the output format from the data format pop-up listand press the "<Export" button. T he files are written to the "EXPORT"subdirectory of the SOD installation directory. When all the data filesare copied, a message window is displayed with the location of the files.The following is the "Export Data" window:

+----------------------+

| &n bsp; |

| Export SOD Data |

| &n bsp; |

| Choose data format |

| +------------+ |

| |DBF(Dbase type format) | |

| +------------+ |

| &n bsp; |

| <Export <Cancel |

| &n bsp; |

+----------------------+

Import Data
SOD provides this option to copy data files intothe database tables. The import option is a complement to the data exportoption. Import can read in Dbase (.DBF) files or ASCII (text) fixed fieldformat files and append the data to the database files. The "Import Data"window follows:

+----------------------+

| &n bsp; |

| Import SOD Data |

| &n bsp; |

| Chooseincoming data format |

| +------------+ |

| |DBF(Dbase type format) | |

| +------------+ |

| &n bsp; |

| <Import <Cancel |

| &n bsp; |

+----------------------+

BACKING UP DATABASE FILES
All of the data files in SOD are in "DATA" subdirectoryof the SOD installation directory. For example, if SOD is installed onthe "Z:" drive in the directory "\SOD" the data file can be found in thedirectory "Z:\SOD\DATA". Therefo re, only the "DATA" directory needs tobe copied to floppy disk or tape. Making a backup copy of the data filesmay be done using the DOS "copy" or "backup" commands or by using one ofthe many fine commercial disk backup utilities or MS Windows File Manager .The following is an example of using the DOS "copy" command to backup theSOD data to floppy drive A:

cd \sod\data[Enter] #change directory to the SOD data directory.
copy *.* A:[Enter] #copy all files in directory to the A: drive. Making backup copies of the SOD installation directory filesor subdirectories other than the data subdirectory is not necessary. Thesefiles may be recovered by reinstalling SOD.