Data Model

This page describes how we model data from each form from the MPP project. Each form will be treated in a subsection. Loci forms will be treated together.

Loci Forms

Several pieces of each loci form are identical across the three types.

1. Earth Loci (Color: yellow - most common)

2. Architectural Loci (Color: pink)

3. Installation Loci (Color: purple)

Burials (Color: Brown) are not strictly a loci since they do not get a locus number, but are attached to an earth locus. THEREFORE, burial forms are child entities of an earth locus.

Identical Sections include the identity, rationale

Earth Locus

The earth locus sheet is the most common form used. Technically everything under 1. should be identifying (Key). However this is preposterous and we will assign a surrogate key.

• Section	Element Identifier	Element Type	Default	Description
  0.None
  	Cleanup	Boolean	False	Check only if debris is interseasonal erosion and if there are pottery, bones, and other objects that need listing
  	Balk Removal	Boolean	False	Check only if you excavated a locus during the balk removal and you don't have the original locus sheet
  1.Identification
  	A.Locus	Integer	None	IF there exists true in section 0. This is a Cleanup or Removal Excavation NOTE DEV. from Manual due to database constraints.
  	B.Site	Char	None	Single Char identifier of site
  	C.Season	Integer	Year(today)	Convention is last two digits of year $\rightarrow$ Bah make it four digits
  	D.Field	Char	None	Single letter field designation
  	E.Square	varchar(8)	None	Sample: "6L46" or "A6" seems random.
  	F.StartDate	Date	Today()	Sample: 18 Jul 2009 [dd/mm/yyyy]
  	F.EndDate	Date	NULL	same.
  	G.Sheet	Integer	NULL	NOT USED!} When we print out sheets they will have page numbers
  	H.Supervisor	varchar(25)[]	NOT NULL	If you worked on this sheet add your name to the list!
  	I.BALK	char(1)	NULL	Used for balk removal (seldom used)
  	J.Designation	varchar(80)	NULL	Free form description of the layer
  2.Rational
  	A.Reason	varchar(80)	NULL	Free form reason for change (Color change,...)
  	B.Separability.Top	selection	Average	Selection from Required Entity SeparabilityListing(ID,{Very Clear, Clear, Average, Unclear, Very Unclear, Arbitrary})
  	B.Separability.Bot	selection	Average	Bottom of locus is from Separability Entity
  3.Description				Description is significantly different across loci forms
  4.Stratigraphy	N/A	Child Element	NULL	Model: Association Table Stratigraphy(This, Loci, Spatial Relationship:above, below, equal, contiguous to, seals against, but by, cuts, FT, Abuts, Abutted by, sealed against by, bonded to)
  5.Levels				Spatial Object Query - We now collect all spatial information with the Total Station. Therefore this section now is just a reference to the coordinates take at different times. Use intersection Table with point sets
  6.Identification				Printed header on subsequent pages - not recorded!
  7.Pottery				List of pottery bucket numbers. Model data as an intersection table. Requires Entity: Pottery\_Bucket(see figure on p.26)
  8.Bones				List of bone bucket numbers and associated Pottery Bucket numbers. Requires Entity: Bones(Pail\#,Date,Location,Comments)
  9.Seeds				Identical to Bones model - Requires Entity: Seeds(Pail\#,Date,Sample\#,Location,Reading)
  10.Objects				Similar to Seeds model - Requires Entity: Object(Pail\#,Date,Field\#,Spatial Coordinates Set\#,Reading) : Associated with pictures,loci...
  11.Photographs				List of photo numbers model - intersection table.
  12.Biodata Samples	BioDataSamples	varchar(80)	Pollen	PROGRAMMING: list elements to check, allow additional information to be typed. The combination goes here.
  13.Drawings		Intersection Table	NULL	Requires Entity: Drawing(ID,Image,...)
  14.Interpretation
  	A.Fucntion	varchar(500)	NULL	What was this loci used for in antiquity
  	B.Stratigraphy	varchar(500)	NULL	This is a textual check on the data that we collect with the total station
  	C.CleanLocus	boolean	false	Did this layer produce pottery from one period only with no mixing of ceramic horizons? Yes$\rightarrow$ true
  	D.Locus Date	varchar(50)	NULL	Excavators dating of the layer
  	E.Phase	varchar(10)	NULL	Completed later ...
  	F.Stratum	varchar(10)	NULL	Completed later ...

Architectural Locus

There is an inconsistancy in MPP that allows an architectural locus to be a subsidiary locus to some other architectural locus. This creates a locus sheet with an identical locus number but a different "locus" making a locus or (sublocus) the most basic element in archaeology. We fix this inconsistancy by moving the J. FOUND(ation) and K.Phase out of the identification and put it into the stratigraphy relationship section. A wall locus then has a architectural-foundation relationship with a foundation instead of having a sub-locus. This makes a substantial change in the Handbook on how to use the forms.

HANDBOOK CHANGE: 15.J and 15.K should list the related locus and relationship type and phase number respectively. The locus gets a unique number.

Identification, Rationale = Earth Locus

|| || A.Masonry.X.Reused || Multi-dependency || NULL || Required Child Entity ReusedStone(LocusFound:LocusID,LocusFrom:LocusID, PercentMass:Integer)