West Heslerton: WEB-CD. Explanation of Sample Page

Return to the Sample page.

[Title of the document]

This is the KeyIdentification Number (the Key-Id), always ten characters in length. Every context on site was issued with a unique number comprised of the site number (e.g. 002) followed by the area code (e.g. DD) followed by the context number (e.g. 00034). These three elements combine to form a unique Key-Id of a feature. It enables the context to be located in any database, matrix or plan and is the vital link between them. A Master Number is a number issued to a structure or group of contexts closely related, intended to tie together individual contexts into a coherent whole. Where a master number was issued, it will always appear as the title of the document. Where there is no master, the cut number of the feature will always be used.

[A quick assessment of the feature/s in the document]

The clickable map shows a small part of the digitised site plan.

The clickable map shows a small part of the digitised site plan. The clickable map is generated so that the features or structure which represents the master context is centrally positioned. A scale bar is always in the bottom left hand corner of the plan. North is always to the top of the page, as indicated by the north arrow in the top left hand corner of the plan. The full OS grid co-ordinates appear on the bottom (easting) and the left (northing) of the plan.

Any other feature that appears on the plan will have a hyper-link to take you to the relevant document. If you click on a button and nothing happens, or a query comes up to say the document has not been found, then that document has not yet been created.

[table of details]

Where applicable, a summary of structural details is included, so that the structure's vital statistics can be viewed without having to read any more of the document. The table of details for different types of feature reflect the nature of the feature, so that only the table for a burial would indicate the burial position of the skeleton, i.e. flexed. Where there is no table, most of the necessary statistics can be found in the master or cut context notes or in the discussion element of the document. Most of the statistics should be self-explanatory, but a few need further comment.

Length, Width and Depth are all maximum statistics, unless stated otherwise, and are always in centimetres. The dimensions are measured in G-Sys from the digitised plans.

Ratio is the length divided by the width.

Area is the area of the of the structure, always in square metres.

Volume has been included although an accurate method of calculating it has not yet been established, and will be expressed in cubic metres.

Elevation is obtained from a 3-dimensionally recorded point taken during excavation. The lowest elevation value of the Grubenhaus will be the highest elevation minus the depth of the cavity. In the post hole structure table, the highest elevation will be the highest post hole fill, the lowest will be the deepest post hole cut.

Bearing is measured in G-Sys and is the alignment of the structure, starting from 0 degrees at due north and working clockwise to 359 degrees. When measuring the alignment of a burial, a line from the base of the spine through the skull is used.

[phasing and matrix]

Much of the phasing has yet to be completed, more detail will be added to this part of the document as analysis progresses and specialist reports are received.

The difficulty in phasing sites of the Anglo-Saxon period is such that the phasing is very much a product of the analysis rather than a precursor to it. As the analysis proceeds this section will be updated with alternative views of the phasing based both upon the pure stratigraphic sequence and upon the specialist analysis of the material culture. In either case, the degree of certainty needs to be articulated since real precision is unlikely in data sets from the Early Anglo-Saxon period.

This example based upon a single fairly simple structure does not demonstrate stratigraphic links to other features above and below. In daily use the stratigraphic matrix displayed on the page is designed to support hyper-links that allow one to browse the site stratigraphically.

[discussion]

The feature or structure can be discussed in any detail with any relevant information. This field will be added to as analysis proceeds.

[context and finds table]

Where a master number was issued, that number will always appear in the top left hand side of the table, otherwise there will be a short description of the context. The objects associated with a context are hyper-linked to the Object Totals by Material tables, or, in the case of few finds (i.e. less than 5), straight to the Objects by Context table. Similarly, the animal bone in the table is hyper-linked to the Animal Bone Totals by Species tables or the Animal Bone by Context.

[totals tables]

The aim of the totals tables is to provide a quick resume of the finds in a given context without having to go through the entire list of objects or animal bones. Totals tables only appear in documents where there were a large number of finds. Each context has its own table and each one of these tables is hyper-linked to the main Objects by Context or Animal Bone by Context tables further down in the document.

[Sections]

Scanned images of the original section drawings with a scale bar added.

[context table]

An abridgment of the context database. Usually, every cut number and its associated fills will have its own context table. Incongruities in the context record are due to the primacy of the data.

[objects table]

An reduced field abstract from the objects database.

OB or OBJ - The object number in the database to allow the individual object to be traced in the full objects database.

No - The number of objects/fragments under the object number.

[animal bone table]

A reduced field set from the animal bone database.

QUANT - the quantity of bone recovered

CHEW - evidence of chew marks

BURNT - signs of burning

BUTCH - signs of butchery

FBRK - fresh breaks

 CONTENTS