Provenience Data: Temporal-Spatial File

Part of the Dolores Archaeological Program project

Year: 1985

Summary

The provenience system used by the DAP allowed field personnel and analysts to identify where each item in a dataset was located within a site, as well as its spatial relationship with other archaeological contexts. Wilshusen et al. (1999:147) indicate that primary linkage among the DAP datasets is achieved through a few shared provenience attributes including the components of a Smithsonian trinomial designation, a field specimen number, and point location numbers—a subdivision of the field specimen number that indicates items found in association with a structure floor or occupation surface. However, the addition of an exhaustive set of contextual field observations moves the provenience dataset beyond a simple description of location. By using field specimen forms to record provenience data in the field, a “cohesive, comparable, and useful set of data” (Wilshusen et al. 1999:24) was produced through standardized terminology.These forms funnel contextual information from a general description of location, beginning with the archaeological site, into specific details about culturally and arbitrarily defined provenience units (Wilshusen et al. 1999).

The locational data in provenience file comes with basic attributes that minimally include components of a Smithsonian site number, a field specimen number, and point location number if applicable. A set of accepted conventions and terminology for describing and quantifying patterns in the archaeological record of the DAP area, otherwise known as program systematics in the DAP reports, has also been appended to the provenience dataset. The DAP systematics "package" actually incorporates a complementary set of temporal, spatial, and site typological units into a "common frame of reference" (Kane 1986:353) for navigating the archaeological record of the DAP. These units have been converted into attributes and made available to users in a single location. The size and complexity of temporal-spatial files such as this are consequences of reducing a vast amount of archaeological data into a theoretically based matrix of space and time. As a result, the interpretive power of these files should not be taken lightly (Wilshusen et al. 1999:147-148); but when used appropriately, the DAP's program systematics define and develop the plot, and even delineate the chapters, of the historic narrative detailing this portion of the Dolores River Valley (Wilshusen et al. 1999:33). Temporal-spatial designations for each location in the provenience dataset, supported by multiple lines of evidence, will be indicated by high confidence values; low-ranked values are supported by “best guesses” and the experience of crew members making the determination. Undisturbed cultural deposits provide the best contextual evidence for making temporal-spatial assignments and will be denoted by high integrity values. Items recovered from deposits containing increasingly higher proportions of extraneous materials will be represented by lower integrity values.

Variables for the temporal-spatial proveneince dataset have already been described by Wilshusen et al. (1999); see especially Chapter 2 by Christine G. Ward and Jonathan Till. In most cases, their descriptions are suitable for use as metadata and have been repeated almost verbatim here. Selected resources from the collection of published and unpublished DAP reports have been used for clarification in some cases and are appropriately referenced. The complexity of the temporal-spatial files is only minimally outlined here; anyone attempting to use the temporal-spatial provenience dataset should first consult Wilshusen et al (1999:31-42) and Kane (1986:353-435).

Cite this Record

Provenience Data: Temporal-Spatial File. 1985 ( tDAR id: 6254) ; doi:10.6067/XCV8BP00VV

Data Set Structure

Measurement Column
Count Column
Coded Column
Filename Column
Integration Column (has Ontology)

Table Information: dap-prov10

Column Name Data Type Type Category Coding Sheet Ontology
fs The most basic type of provenience data recorded for all information obtained during DAP fieldwork is the field specimen number. These values are sequentially assigned to unique vertical and horizontal locations within each site.
BIGINT  Uncoded Value Lookup : Code none none
collect This variable describes the manner in which an item was collected from the provenience described. Methods of screening, the size of mesh used, and sampling are conveyed here.
VARCHAR  Uncoded Value Provenience and Context : Recovery Method none none
fevert This variable indicates the vertical excavation strategy employed at any excavated provenience. The first digit (0-3, 9) indicates the type of vertical excavation performed (not applicable, natural strata, arbitrary levels, cultural surfaces, or full cut). The last two digits refer to the sequential numbering of the different types of vertical excavation for the study unit.
VARCHAR  Uncoded Value Provenience and Context : Recovery Method none none
fehoriz This variable indicates the horizontal excavation strategy employed in the recovery of a non-flaked-lithic tool item from a feature context. The seven possible horizontal provenience possibilities include: not applicable (0000), whole study unit (0001), locus (1001-1999), segment (2001-2999), half (3001-3999), strip (4001-4999), quadrant (5001-5999), grid square (6001-6999), and grid square tied to a local datum (7001-7999). Locus and segments are assigned a sequential number within each study unit. Half, strip, and quadrant designations are associated with one of eight cardinal directions: north (1), northeast (2), east (3), southeast (4), south (5), southwest (6), west (7), and northwest (8). Coordinates in meters south are provided for grid square excavations and are represented by the second through fourth digits in FEHORIZ.
BIGINT  Uncoded Value Provenience and Context : Recovery Method none none
fenum Since features within a site are sequentially numbered, this variable allows enables users to identify the exact feature from which a non-flaked lithic tool was recovered.
BIGINT  Uncoded Value Provenience and Context : Feature ID/Number none none
suvert This variable indicates the vertical excavation strategy employed at any provenience excavated by study unit. The first digit (0-3, 9) indicates the type of vertical excavation performed (not applicable, natural strata, arbitrary levels, cultural surfaces, or full cut). The last two digits refer to the sequential numbering of the different types of vertical excavation for the study unit.
BIGINT  Uncoded Value Provenience and Context : Recovery Method none none
suhoriz This variable indicates the horizontal excavation strategy employed at any provenience excavated by study unit. The seven possible horizontal provenience possibilities include: not applicable (0000), whole study unit (0001), locus (1001-1999), segment (2001-2999), half (3001-3999), strip (4001-4999), quadrant (5001-5999), grid square (6001-6999), and grid square tied to a local datum (7001-7999). Locus and segments are assigned a sequential number within each study unit. Half, strip, and quadrant designations are associated with one of eight cardinal directions: north (1), northeast (2), east (3), southeast (4), south (5), southwest (6), west (7), and northwest (8). Coordinates in meters south are provided for grid square excavations and are represented by the second through fourth digits in SUHORIZ.
VARCHAR  Uncoded Value Provenience and Context : Recovery Method none none
site Site number refers only to the sequential position of a site within a single Smithsonian state and county designation. To obtain a full site number for any entry, this value must be appended to the Smithsonian state and county designation.
BIGINT  Uncoded Value Provenience and Context : Horizontal Location none none
cobjectid The Anasazi Heritage Center (AHC) has given each specimen several unique codes, including cobjectid, to facilitate management of their DAP collections. Since this value is used in association with the AHC ARGUS database for tracking the location of a record, it is important for any researcher requesting objects from the curator.
VARCHAR  Uncoded Value Lookup : Code none none
felevel BIGINT  Uncoded Value uncategorized none none
fegrid BIGINT  Uncoded Value uncategorized none none
sulevl BIGINT  Uncoded Value uncategorized none none
stco VARCHAR  Uncoded Value uncategorized none none
flag This letter code (choices A-Y) corresponds to a specific project, site, or level of work conducted. Probability sampling, for instance, is the most commonly used code and is denoted by P.
VARCHAR  Uncoded Value Lookup : Code none none
fetype This variable describes the feature associated with each line of provenience data.
VARCHAR  Uncoded Value Provenience and Context : Feature Type none none
sutype The DAP study unit type represents a culturally or arbitrarily defined provenience context that is also sequentially numbered by occurrence within each site.
VARCHAR  Uncoded Value Provenience and Context : Unit none none
sufap The study unit fill/assemblage position variable is used to indicate the horizontal or vertical context from which data was collected, relative to its position within the study unit being examined.
VARCHAR  Uncoded Value Provenience and Context : Volume none none
csiteid The Anasazi Heritage Center has given each specimen several unique codes, including csiteid, to facilitate management of their DAP collections. This value denotes the entry's corresponding Smithsonian site number.
VARCHAR  Uncoded Value Provenience and Context : Horizontal Location none none
caccnid The Anasazi Heritage Center has given each specimen several unique codes, including caccnid, to facilitate management of their DAP collections. The first digits of this value indicate the year that it was accessioned.
DOUBLE  Uncoded Value Lookup : Code none none
susurf This variable specifies the study unit surface type, but is not necessarily applicable to each provenience.
VARCHAR  Uncoded Value Provenience and Context : Horizontal Location none none
fefat The fill/assemblage type designations are essentially attempting to identify the primary formation processes contributing to the deposition of materials within each study unit, or feature in this case.
VARCHAR  Uncoded Value Provenience and Context : Volume none none
cdept The Anasazi Heritage Center has given each specimen several unique codes, including cdept, to facilitate management of their DAP collections. This value specifies the tool department to which each record belongs.
VARCHAR  Uncoded Value Lookup : Description none none
sufat The study unit fill/assemblage type variable is used to indicate whether a particular provenience is associated with cultural, post-abandonment, or mixed deposits. Upon determining the origin of the deposits, DAP field personnel were able to select from a standard set of descriptions when providing their interpretation of how each recovered item was deposited.
VARCHAR  Uncoded Value Provenience and Context : Volume none none
sunum Instances of the same study unit type were sequentially numbered within a site.
BIGINT  Uncoded Value Provenience and Context : Horizontal Location none none
sugrid Used only when study units were excavated by grid squares, this number represents the coordinate value east in meters.
BIGINT  Uncoded Value Provenience and Context : Horizontal Location none none
subarea Sites excavated by subsections were given corresponding area designations. If further horizontal control was required, subarea numbers were sequentially assigned within each excavation area at each site.
VARCHAR  Uncoded Value Provenience and Context : Recovery Method none none
area Area numbers were sequentially assigned within each site when excavation by subsection was required.
VARCHAR  Uncoded Value Lookup : Code none none

Spatial Coverage

min long: -108.59; min lat: 37.47 ; max long: -108.5; max lat: 37.57 ;

Record Identifiers

Bureau of Reclamation(s): 8-07-40-S0562

Source Collections

DAP collections are curated at the Anasazi Heritage Center, Dolores, CO.

File Information

  Name Size Creation Date Date Uploaded Access
dap-prov10.csv 8.46mb Jul 30, 2012 2:56:35 PM Public