C14Samples
Ideally 14C dates should be associated with a specific PhaseID which allows them to be directly connected to a multitude of other data. However, most 14C dates can only be secured to a SiteID. The current table 14Cdeadhead will be gradually amalgamated into this table, as data are cleaned and harmonised. Some C14 samples are assigned to only a SiteID, and others assigned to a PhaseID AND its repective SiteID. Therefore the 14CSamples table uses a composite foreign key to connect to the Phases table.
Column name	Data type	Column description
C14ID	int	Unique identification code for each C14 sample
PhaseID	varchar	Please see the detailed description of the 'Phases' table.
SiteID	varchar	Unique site identification number
ItemID	varchar
Period	varchar	Broad chronological period e.g. Early Neolithic (EN), Middle Neolithic (MN)
Method	varchar	Method for obtaing the radiocarbon date
C14.Age	int	Uncalibrated years BP
C14.SD	int	Standard deviation
δ13C	decimal	C13 value with respect to the radiocarbon date.
δ13C.SD	decimal	C13 error (standard deviation) with respect to the radiocarbon date.
C/N_collagen	decimal	Carbon / Nitrogen Atomic ratio (C:N) of carbon and nitrogen in the collagen sample.
LabID	varchar	Unique Laboratory identification number. Lab suffixes must be in the C14laboratories table, which end with a hyphen. This is important as labcodes are automatically checked by string splitting on the first hyphen. Note, there are cases where multiple hyphen legitimately exist in a labcode (e.g. OxA-X-2135-46). Other non-standard characters are also permitted, such as ‘.’ or ‘/’. Case sensitivity is important, for example, prefix GD- and Gd- are two different laboratories. Spaces are NOT permitted, therefore rare occasions such as 'GIF FG 39a' will be automatically assigned 'GIFFG-39a'
Prefix	varchar	Laboratory prefix generated automatically (DO NOT ADD VALUES) by MySQL trigger, which automatically strips this from the LabID, as a sanity check that it is valid.
AltLabID	varchar	Alternative lab code such as where the sample first went to one lab for treatment but was eventually measured at another. In such situations the first lab code is considered the primary one and stored in LabID with the second code stored here. But it is true that sometimes the order is unknown or confusing.
AltPrefix	varchar	Laboratory prefix generated automatically (DO NOT ADD VALUES) by MySQL trigger, which automatically strips this from the AltLabID, as a sanity check that it is valid.
TaxonCode	varchar
Material	varchar	Material of the sample. See zoptions_Material for available options.
Preservation	varchar	Please see the detailed description of the 'zoptions_Preservation' table.
ABotAnatomy	varchar	Please see the detialed description of the 'zoptions_ABotAnatomy' table.
SkeletalElement	varchar	Please see the detailed description of the 'zoptions_SkeletalElement' table.
Quantity	varchar	Please see the detailed description of the 'zoptions_Quantity' table.
MaterialNotes	varchar	Additional information about the sample. If Citation specifies whether the sampled bone or tooth comes from the left or right side of the body, structure information as 'sin' (corresponding to sinestra = left) or 'dex' (corresponding to dexter = right)
Flag	varchar	Published issues or problems with the date.
ContextType	varchar	Specification of the feature dated directly by the 14C sample. Check the zoptions PhaseType table for categories.
Context	varchar
CitationID	varchar	See citation table for the strict character code.