{"id":299,"date":"2026-03-30T15:00:34","date_gmt":"2026-03-30T15:00:34","guid":{"rendered":"https:\/\/anchurus.co.uk\/?page_id=299"},"modified":"2026-08-27T09:27:53","modified_gmt":"2026-08-27T09:27:53","slug":"the-anchurus-ii-release-2-database-tables","status":"publish","type":"page","link":"https:\/\/anchurus.co.uk\/?page_id=299","title":{"rendered":"The Anchurus II database"},"content":{"rendered":"\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-is-layout-794e3cfa wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\" style=\"flex-basis:33.33%\"><div class=\"root-eb-toc-s81i3 wp-block-essential-blocks-table-of-contents\"><div class=\"eb-parent-wrapper eb-parent-eb-toc-s81i3 \"><div class=\"eb-toc-container eb-toc-s81i3 eb-toc-sticky-left eb-toc-is-sticky eb-toc-collapsible eb-toc-initially-not-collapsed eb-toc-scrollToTop style-2 list-style-none\" data-scroll-top=\"false\" data-scroll-top-icon=\"fas fa-angle-up\" data-collapsible=\"true\" data-sticky-hide-mobile=\"false\" data-sticky=\"true\" data-scroll-target=\"scroll_to_toc\" data-copy-link=\"false\" data-editor-type=\"\" data-hide-desktop=\"false\" data-hide-tab=\"false\" data-hide-mobile=\"false\" data-itemcollapsed=\"false\" data-highlight-scroll=\"false\"><div class=\"eb-toc-header\"><span class=\"eb-toc-close eb-toc-sticky-left\"><\/span><h2 class=\"eb-toc-title\">Table of Contents<\/h2><\/div><div class=\"eb-toc-wrapper \" data-headers=\"[{&quot;level&quot;:2,&quot;content&quot;:&quot;Summary&quot;,&quot;text&quot;:&quot;Summary&quot;,&quot;link&quot;:&quot;summary&quot;},{&quot;level&quot;:2,&quot;content&quot;:&quot;This is a relational database&quot;,&quot;text&quot;:&quot;This is a relational database&quot;,&quot;link&quot;:&quot;this-is-a-relational-database&quot;},{&quot;level&quot;:2,&quot;content&quot;:&quot;Organisations, Anchurus II systems and databases&quot;,&quot;text&quot;:&quot;Organisations, Anchurus II systems and databases&quot;,&quot;link&quot;:&quot;organisations-anchurus-ii-systems-and-databases&quot;},{&quot;level&quot;:2,&quot;content&quot;:&quot;Overview of the database&quot;,&quot;text&quot;:&quot;Overview of the database&quot;,&quot;link&quot;:&quot;overview-of-the-database&quot;},{&quot;level&quot;:3,&quot;content&quot;:&quot;Table and column names&quot;,&quot;text&quot;:&quot;Table and column names&quot;,&quot;link&quot;:&quot;table-and-column-names&quot;},{&quot;level&quot;:3,&quot;content&quot;:&quot;Archaeological base tables&quot;,&quot;text&quot;:&quot;Archaeological base tables&quot;,&quot;link&quot;:&quot;archaeological-base-tables&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;site table&quot;,&quot;text&quot;:&quot;site table&quot;,&quot;link&quot;:&quot;site-table&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;anomaly table&quot;,&quot;text&quot;:&quot;anomaly table&quot;,&quot;link&quot;:&quot;anomaly-table&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;context table&quot;,&quot;text&quot;:&quot;context table&quot;,&quot;link&quot;:&quot;context-table&quot;},{&quot;level&quot;:3,&quot;content&quot;:&quot;Finds tables&quot;,&quot;text&quot;:&quot;Finds tables&quot;,&quot;link&quot;:&quot;finds-tables&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;find table&quot;,&quot;text&quot;:&quot;find table&quot;,&quot;link&quot;:&quot;find-table&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;Find Specialist tables&quot;,&quot;text&quot;:&quot;Find Specialist tables&quot;,&quot;link&quot;:&quot;find-specialist-tables&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;findgroup table&quot;,&quot;text&quot;:&quot;findgroup table&quot;,&quot;link&quot;:&quot;findgroup-table&quot;},{&quot;level&quot;:3,&quot;content&quot;:&quot;Stratigraphic analysis tables&quot;,&quot;text&quot;:&quot;Stratigraphic analysis tables&quot;,&quot;link&quot;:&quot;stratigraphic-analysis-tables&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;Stratigraphic analysis concepts&quot;,&quot;text&quot;:&quot;Stratigraphic analysis concepts&quot;,&quot;link&quot;:&quot;stratigraphic-analysis-concepts&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;Doing stratigraphic analysis&quot;,&quot;text&quot;:&quot;Doing stratigraphic analysis&quot;,&quot;link&quot;:&quot;doing-stratigraphic-analysis&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;The single table solution&quot;,&quot;text&quot;:&quot;The single table solution&quot;,&quot;link&quot;:&quot;the-single-table-solution&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;The multi-table solution&quot;,&quot;text&quot;:&quot;The multi-table solution&quot;,&quot;link&quot;:&quot;the-multi-table-solution&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;Interpretation table&quot;,&quot;text&quot;:&quot;Interpretation table&quot;,&quot;link&quot;:&quot;interpretation-table&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;Phases table&quot;,&quot;text&quot;:&quot;Phases table&quot;,&quot;link&quot;:&quot;phases-table&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;Groups table&quot;,&quot;text&quot;:&quot;Groups table&quot;,&quot;link&quot;:&quot;groups-table&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;Sets table&quot;,&quot;text&quot;:&quot;Sets table&quot;,&quot;link&quot;:&quot;sets-table&quot;},{&quot;level&quot;:3,&quot;content&quot;:&quot;Data access tables&quot;,&quot;text&quot;:&quot;Data access tables&quot;,&quot;link&quot;:&quot;data-access-tables&quot;},{&quot;level&quot;:4,&quot;content&quot;:&quot;The Query table&quot;,&quot;text&quot;:&quot;The Query table&quot;,&quot;link&quot;:&quot;the-query-table&quot;},{&quot;level&quot;:2,&quot;content&quot;:&quot;The data held in tables and columns&quot;,&quot;text&quot;:&quot;The data held in tables and columns&quot;,&quot;link&quot;:&quot;the-data-held-in-tables-and-columns&quot;},{&quot;level&quot;:2,&quot;content&quot;:&quot;Table identifiers&quot;,&quot;text&quot;:&quot;Table identifiers&quot;,&quot;link&quot;:&quot;table-identifiers&quot;},{&quot;level&quot;:2,&quot;content&quot;:&quot;Referential integrity&quot;,&quot;text&quot;:&quot;Referential integrity&quot;,&quot;link&quot;:&quot;referential-integrity&quot;}]\" data-visible=\"[true,true,true,true,true,true]\" data-delete-headers=\"[{&quot;label&quot;:&quot;Summary&quot;,&quot;value&quot;:&quot;summary&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;This is a relational database&quot;,&quot;value&quot;:&quot;this-is-a-relational-database&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Organisations, Anchurus II systems and databases&quot;,&quot;value&quot;:&quot;organisations-anchurus-ii-systems-and-databases&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Overview of the database&quot;,&quot;value&quot;:&quot;overview-of-the-database&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Table and column names&quot;,&quot;value&quot;:&quot;table-and-column-names&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Archaeological base tables&quot;,&quot;value&quot;:&quot;archaeological-base-tables&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;site table&quot;,&quot;value&quot;:&quot;site-table&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;anomaly table&quot;,&quot;value&quot;:&quot;anomaly-table&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;context table&quot;,&quot;value&quot;:&quot;context-table&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Finds tables&quot;,&quot;value&quot;:&quot;finds-tables&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;find table&quot;,&quot;value&quot;:&quot;find-table&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Find Specialist tables&quot;,&quot;value&quot;:&quot;find-specialist-tables&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;findgroup table&quot;,&quot;value&quot;:&quot;findgroup-table&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Stratigraphic analysis tables&quot;,&quot;value&quot;:&quot;stratigraphic-analysis-tables&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Stratigraphic analysis concepts&quot;,&quot;value&quot;:&quot;stratigraphic-analysis-concepts&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Doing stratigraphic analysis&quot;,&quot;value&quot;:&quot;doing-stratigraphic-analysis&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;The single table solution&quot;,&quot;value&quot;:&quot;the-single-table-solution&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;The multi-table solution&quot;,&quot;value&quot;:&quot;the-multi-table-solution&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Interpretation table&quot;,&quot;value&quot;:&quot;interpretation-table&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Phases table&quot;,&quot;value&quot;:&quot;phases-table&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Groups table&quot;,&quot;value&quot;:&quot;groups-table&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Sets table&quot;,&quot;value&quot;:&quot;sets-table&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Data access tables&quot;,&quot;value&quot;:&quot;data-access-tables&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;The Query table&quot;,&quot;value&quot;:&quot;the-query-table&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;The data held in tables and columns&quot;,&quot;value&quot;:&quot;the-data-held-in-tables-and-columns&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Table identifiers&quot;,&quot;value&quot;:&quot;table-identifiers&quot;,&quot;isDelete&quot;:false},{&quot;label&quot;:&quot;Referential integrity&quot;,&quot;value&quot;:&quot;referential-integrity&quot;,&quot;isDelete&quot;:false}]\" data-smooth=\"true\" data-top-offset=\"46\"><div class=\"eb-toc__list-wrap\"><ul class=\"eb-toc__list\"><li><a href=\"#summary\">Summary<\/a><li><a href=\"#this-is-a-relational-database\">This is a relational database<\/a><li><a href=\"#organisations-anchurus-ii-systems-and-databases\">Organisations, Anchurus II systems and databases<\/a><li><a href=\"#overview-of-the-database\">Overview of the database<\/a><ul class=\"eb-toc__list\"><li><a href=\"#table-and-column-names\">Table and column names<\/a><li><a href=\"#archaeological-base-tables\">Archaeological base tables<\/a><ul class=\"eb-toc__list\"><li><a href=\"#site-table\">site table<\/a><li><a href=\"#anomaly-table\">anomaly table<\/a><li><a href=\"#context-table\">context table<\/a><\/li><\/ul><li><a href=\"#finds-tables\">Finds tables<\/a><ul class=\"eb-toc__list\"><li><a href=\"#find-table\">find table<\/a><li><a href=\"#find-specialist-tables\">Find Specialist tables<\/a><li><a href=\"#findgroup-table\">findgroup table<\/a><\/li><\/ul><li><a href=\"#stratigraphic-analysis-tables\">Stratigraphic analysis tables<\/a><ul class=\"eb-toc__list\"><li><a href=\"#stratigraphic-analysis-concepts\">Stratigraphic analysis concepts<\/a><li><a href=\"#doing-stratigraphic-analysis\">Doing stratigraphic analysis<\/a><li><a href=\"#the-single-table-solution\">The single table solution<\/a><li><a href=\"#the-multi-table-solution\">The multi-table solution<\/a><li><a href=\"#interpretation-table\">Interpretation table<\/a><li><a href=\"#phases-table\">Phases table<\/a><li><a href=\"#groups-table\">Groups table<\/a><li><a href=\"#sets-table\">Sets table<\/a><\/li><\/ul><li><a href=\"#data-access-tables\">Data access tables<\/a><ul class=\"eb-toc__list\"><li><a href=\"#the-query-table\">The Query table<\/a><\/li><\/ul><\/li><\/ul><li><a href=\"#the-data-held-in-tables-and-columns\">The data held in tables and columns<\/a><li><a href=\"#table-identifiers\">Table identifiers<\/a><li><a href=\"#referential-integrity\">Referential integrity<\/a><\/ul><\/div><\/div><button class=\"eb-toc-button  eb-toc-button-left\"><div>Table of Contents<\/div><\/button><\/div><\/div><\/div><\/div>\n\n\n\n<div class=\"wp-block-column is-vertically-aligned-center is-layout-flow wp-block-column-is-layout-flow\" style=\"flex-basis:66.66%\"><\/div>\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\">Summary<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This page of the user manual describes the tables used to record and interpret an archaeological excavation and explains how you can find details of the data held in the tables.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">This is a relational database<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The Anchurus II release 2 database is a relational database so data is held in tables. The tables hold their data in columns and rows. The tables are linked together with relationships. This structure of tables, table columns, table rows and inter-table relationships help to manage the integrity of the data from an excavation and during post excavation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You access these tables using the Anchurus II web application.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Organisations, Anchurus II systems and databases<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Each organisation using Anchurus II does so through an Anchurus II system; a self-contained entity which runs on a server and is completely independent of any other Anchurus system. This system is owned by the organisation and is operationally their responsibility.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Each system has its own database which is completely separate to the databases associated with other systems,<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Within their system, an organisation can record the archaeological fieldwork on many different sites. The organisation can assign one or more sites to a project but within Anchurus II each site is treated as a separate entity with its own site manager and group of workers. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Overview of the database<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The figure below shows the overall structure of an Anchurus II database. There are four main groups of tables.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>The Archaeological base tables<\/strong>: shown in blue, are the tables that are used to record the site, anomalies and contexts<\/li>\n\n\n\n<li><strong>The Finds tables<\/strong>: shown in green, are the tables used to record finds and used by find specialists to develop find reports<\/li>\n\n\n\n<li><strong>The Interpretation tables<\/strong>: shown in orange: are used to interpret the evidence from the site<\/li>\n\n\n\n<li><strong>The Data access tables<\/strong>: shown in pink, are used to write SQL queries to give users access to the data in the other tables<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The next sections in this manual page summarise the data held in these tables.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Table and column names<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Anchurus II is supported by a MariaDB database, the naming conventions for table and column names are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Table names are in lower case alphabetic characters<\/li>\n\n\n\n<li>Column names in principle start with a capital alphabetic character followed by a sequence of alphanumeric capital and lower case characters &#8211;  <strong>PascalCase<\/strong> or <strong>UpperCamelCase<\/strong><\/li>\n\n\n\n<li>Columns which are part of the candidate key of a table have a leading capital letter followed by all lower case letters and end with &#8220;Id&#8221; a capital &#8220;I&#8221; and lower case &#8220;d&#8221;<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"700\" height=\"765\" src=\"https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/08\/ANII-release-02-User-manual-ER-diagram-v22d.jpg\" alt=\"\" class=\"wp-image-598\" srcset=\"https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/08\/ANII-release-02-User-manual-ER-diagram-v22d.jpg 700w, https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/08\/ANII-release-02-User-manual-ER-diagram-v22d-275x300.jpg 275w\" sizes=\"auto, (max-width: 700px) 100vw, 700px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Figure 14.1. The Anchurus II database used to record and interpret an archaeological site<\/em><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Archaeological base tables<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">These tables are:<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">site table<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">A site is located at a single modern address with single ownership and reflects the permissions required for archaeological intervention. As an archaeological site, it is a discrete geo-located area of ground that is undergoing archaeological investigation and excavation.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">anomaly table<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">An anomaly is a two dimensional representation of human activity in a geophysics survey plot, a topological survey, a Lidar plot or a map of evidence. All the above can be geopositioned but in Anchurus II release 2, we record a textual record of the anomaly and its significance. so we can integrate this information in group with the other information to provide a fuller interpretation of the site.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">context table<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">A context is the smallest unit into which the archaeological record may be divided (Clarke <em>et al.<\/em> 2019: 15).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A context is recorded in terms of:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Type: what is represents, one of: deposit, cut, fill, structure<\/li>\n\n\n\n<li>Name1: the name given by the diggers<\/li>\n\n\n\n<li>Description1: in terms of the soil colour etc and its inclusions, written by the diggers<\/li>\n\n\n\n<li>Interpretation: written by the diggers<\/li>\n\n\n\n<li>Name2: given by the interpreters. This is the name used in reports<\/li>\n\n\n\n<li>Description2: given by interpreters. This is the interpreter\u2019s description.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Note: when the content is first recorded. Name1 and Name2 are the same and Descritption1 and Description2 are the same. Thereafter Name1 and Description 1 are frozen so as to preserve the digger\u2019s words, the interpreters can change Name2 and Description2<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Finds tables<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A find is a term applied to all artefacts, building materials, industrial residues, environmental material, biological remains (including human remains) and decay products (Introduction, Chartered Institute for Archaeologists).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The find tables enable you to record, catalogue, file away and store finds and to present them to Find Specialists to help identify their production, life histories and use of site and thereby write comprehensive finds report.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These tables are:<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">find table<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">All finds are recorded in the find table. This table represents the minimum details needed to link finds to contexts, and the other Stratigraphic Analysis tables together with the details necessary to maintain a catalogue, and a filing and storage system that embraces all your finds.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">See the user manual page 18 <em>Recording finds<\/em> for the use of this table.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Find Specialist tables<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Experience has shown that most find specialists have their own way of recording finds in their area of interest; typically this is recorded in a spreadsheet. Anchurus II supports this by providing a service whereby the Find Specialists spreadsheets can be converted into Find Specialist tables. This then allows us to combine the information their table with the Stratigraphic Analyse data and hence into matrices and plans.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Figure 14.1 shows some of the Finds Specialist tables that were used to record the finds found at our Blounts Court excavation.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">findgroup table<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">For many years, pottery specialists have been identifying pottery groups, based on pottery fabrics and vessel forms etc. In parallel, in the IT industry, system architects have been using object oriented data analysis methods to analyse data. These two groups of people are doing the same task using different terminology.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In Anchurus II we recommend and teach users how to apply object oriented data analysis methods to most of the other find material types. The result of doing this is that for each material type we can identify findgroups.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A find group is a collection of finds that share characteristics which were established when the finds in that group were produced. For example a group of pottery finds made of the same fabric or a group of worked flints dating to the Bronze Age. Ideally, a find specialist will have identified the specific characteristics of finds in a find group. You identify find groups because they are going to be described in a finds report. For example if for a particular material type such as pottery or peg tile, you identify 20 find groups, you would expect to have a finds report with at least 20 find group paragraphs, describing what you found and its significance to the site you are excavating.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The findgroup table lists your find groups each with a name, description and, with luck, a production date range. Typically, each find in a find group will have a production date range inherited from that FindGroup but in some cases, a find has other features or marking which provide a spot date (a tighter date range). See user manual page 20 <em>Finds analysis.<\/em><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Stratigraphic analysis tables<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\"><em>Stratigraphic analysis concepts<\/em><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Stratigraphic analysis involves identifying and consolidating definitions of:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Phases<\/strong>: where a phase represents a period of use of a site embracing a succession of groups representing structures and\/or areas of human activity on the site over time<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Groups: <\/strong>where a group represents a discrete area or period of human activity on the site as represented by a structure built on the site or a deposit or deposits which record the remains of human activity<\/li>\n\n\n\n<li><strong>Sets<\/strong>: which are subgroups. A set is a number of contexts usually found in a single excavation area. It represents the evidence or remains of some human activity. A typical example of a set are a post hole recorded as a cut context and one or more fill contexts<\/li>\n\n\n\n<li><strong>Anomalies<\/strong>: identified in surveys of the site<\/li>\n\n\n\n<li><strong>Contexts<\/strong>: identified during the excavation of the site<\/li>\n\n\n\n<li><strong>KeyFinds<\/strong>: which are key insofar as they provide key dating evidence or evidence of key human activity<\/li>\n\n\n\n<li><strong>Dates periods<\/strong>: for the above together with your rationale for choosing them<\/li>\n\n\n\n<li><strong>Brief descriptions<\/strong>: to remind you of all the above.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">In the above, we have kept groups and sets separate from each other because it simplifies extracting data from the database to move it into the StratVis dating algorithm and Phase and group stratigraphy matrices.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><em>Doing stratigraphic analysis<\/em><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">What is quite clear that doing stratigraphic analysis imposes as significant cognitive load on anybody who undertakes the task. One of the objectives of Anchurus II is to provide tools which reduces that load.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Anchurus II supports this objective by encouraging you to accumulate all this information in:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Spreadsheets<\/li>\n\n\n\n<li>The database<\/li>\n\n\n\n<li>Phase and group matrices<\/li>\n\n\n\n<li>Site plans: typically one for each phase of use of the site. It should be presented in your archaeological report<\/li>\n\n\n\n<li>The Stratigraphic Analysis chapter of your archaeological report.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The Anchurus II database supports two approaches to supporting stratigraphic analysis. They are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>The single table solution<\/strong>: where you use the stratigraphic analysis spreadsheet to develop your understanding of the site import the spread sheet into the stratigraphicanalysis table and then use queries to produce lists of phases and groups and to ensure that your stratigraphic analysis matches the excavated evidence<\/li>\n\n\n\n<li><strong>The multi-table solution<\/strong> spread the evidence across the database solution: which uses separate phase, group, set and interpretation tables<br>Note: IADB 2017 spread these details more widely across phase, group, set, context and find tables ; we have yet to implement some of that solution in Anchurus II.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">There is no doubt that different approaches will be implemented as users gain experience of undertaking stratigraphic analysis.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><em>The single table solution<\/em><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">This approach records all the stratigraphic analysis information in one spreadsheet and a matching table<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You start by creating the stratigraphic analysis spreadsheet. This records:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>The details of your stratigraphic analysis<\/strong>: the system allows you to hold several different versions so you can compare the differences you make as you learn more about your site<\/li>\n\n\n\n<li><strong>The phases<\/strong>: with the names that you are going to present to your report readers rather than the names given by the excavators<\/li>\n\n\n\n<li><strong>The groups<\/strong>: again with meaningful names that you are going to present in your report<\/li>\n\n\n\n<li><strong>Anomalies<\/strong>: with a combination of the surveyors\u2019 evidence and your stratigraphic analysis<\/li>\n\n\n\n<li><strong>The sets<\/strong><\/li>\n\n\n\n<li><strong>The contexts<\/strong>: with descriptions with a combination of the excavators\u2019 evidence and your stratigraphic analysis of the site. This approach ensures that the excavators\u2019 evidence in the context table remains unchanged<\/li>\n\n\n\n<li><strong>The keyfinds<\/strong>: these are finds that provide significant evidence that underpins your analysis<\/li>\n\n\n\n<li>Date periods: for the above<\/li>\n\n\n\n<li><strong>Datesrationale<\/strong>: which explains why you have used these dates<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">From time to time you import the spreadsheet into the database stratigraphicanalysis table.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The benefits of using the stratigraphicanalysis spreadsheet is that you can keep it in chronological order and use colour to differentiate the details of different phases and groups and it is easy to move groups to keep them in chronological order.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The benefits of using the database is that you can use write queries to check the consistency between your analysis and the field work evidence as recorded in anomalies, sets, contexts and finds.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><em>The multi-table solution<\/em><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">This uses several tables to record your stratigraphic analysis. They are:<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Interpretation table<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">This is similar to the stratigraphicanalysis table insofar as you start by producing an interpretation spreadsheet and then load the details into the interpretation table.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This table records a series of interpretations that you make of a site which gives you a record of how your understanding of the site changed over time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For each interpretation you record:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Phases and within each phase the groups that existed during that phase<\/li>\n\n\n\n<li>Groups and within each group the sets, contexts and anomalies that contain the evidence confirming the existence and use of the group<\/li>\n\n\n\n<li>Sets and within each set the contexts that support it<\/li>\n\n\n\n<li>Date periods and dates rationale<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This table is used to generate queries which link phases to contexts and it finds within that context or conversely to a find or collection of finds and shows the sets, groups and phases in which they were deposited.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Phases table<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">A report of a site usually identifies several phases starting the earliest dated phase and progressing through time. This approach is taken because human activities in the early phases influence the latest phases.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Each phase record has associated with it: a name. a description, a rationale as to why the archaeologist highlighted this as a phase and the time period when the phase was in use. Recording the rationale for choosing a phase is important because the choice can be influenced by a variety of factors including, in no particular order:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The Ownership of the site and changes of ownership over time<\/li>\n\n\n\n<li>The structures found on the site<\/li>\n\n\n\n<li>The finds found on the site<\/li>\n\n\n\n<li>The use made of the site<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The phases are recorded in the database as fully as possible and then exported to form the basis of an archaeological report.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Groups table<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">A Group record has a name, chosen to help anybody reading your archaeological report to understand what you found<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Sets table<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Note: in the Archaeologists Guide to Good Practice handbook (see user manual page 2) this concept is called a Subgroup, a name which detracts from its archaeological significance. If you would prefer the word \u201cSubgroup\u201d to \u201cSets\u201c then this is done in the Anchurus II database definition.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Data access tables<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">The Query table<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">One of the challenges of providing an IT system to support archaeologists is that many of them have little or no interest in technology. The way forward is to work towards the position where everybody working on the project has an understanding of Figure 14.1 above and the data sets it represents and hence can explain the information that want to access.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The workflow for creating a query involves the following steps:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>As an Anchurus II user, you write your requirement of the query in natural language and identify the tables you want to access<\/li>\n\n\n\n<li>The system administrator takes your request, translates it into a SQL statement (SQL is the language used to access the Anchurus II database) and runs it to retrieve data from the database and present it as a list<\/li>\n\n\n\n<li>You and the system administrator then review this together to confirm that it is producing the required results<\/li>\n\n\n\n<li>The system administrator completes the entry in the query table by adding guidelines to remind you how to use the query<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">The data held in tables and columns<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Every table consists of a columns and rows. The easiest way for you to learn what data is held in a table is to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>List the table. Figure 14.2 shows the contents of the Context table. The table header reminds you of \u201cWhat is a context\u201d<\/li>\n\n\n\n<li>You then select a row and view it. Figure 14.3 shows the columns in the table with, for each column a reminder of its contents and the value for the chosen context<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">See user manual <em>Using the Anchurus II web application<\/em> for how to list a table and view a table row.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/04\/image-1024x576.png\" alt=\"\" class=\"wp-image-335\" srcset=\"https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/04\/image-1024x576.png 1024w, https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/04\/image-300x169.png 300w, https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/04\/image-768x432.png 768w, https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/04\/image.png 1380w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Figure 14.2 Screen shot of the Anchurus II web application showing the contents of the Context table<\/em><\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/04\/image-1-1024x576.png\" alt=\"\" class=\"wp-image-336\" srcset=\"https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/04\/image-1-1024x576.png 1024w, https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/04\/image-1-300x169.png 300w, https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/04\/image-1-768x432.png 768w, https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/04\/image-1.png 1380w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Figure 14.3. Screen shot of the Anchurus II web application showing the details of Context C01001<\/em><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Table identifiers<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Every row in a table is uniquely identified by the table\u2019s candidate key. In the Anchurus II design, for most tables this consists of two columns:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>The SiteId: which identifies the site to which this column is related<\/li>\n\n\n\n<li>A table identifier: For the context table this is ContextId column, for the find table this is the FindId column<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">In Anchurus II all identifiers are 15 alpha-numeric characters with the strong recommendation that all identifiers start with an alphabetic character chosen so that all table identifier columns in a table start with the same character. This approach improves the accuracy of recording the archaeology and hence reduces errors and the costs of correcting them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Figure 14.4 below shows the characters that has been used to start table identifiers following the SiteId column.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It should be stressed that the ideas presented in table 14.4 are examples of what you could do with this system. The system itself makes no checks to enforce these examples. This approach has been adopted so that organisations can easily migrate their existing approach to this system.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"639\" height=\"783\" src=\"https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/08\/image-24.png\" alt=\"\" class=\"wp-image-811\" srcset=\"https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/08\/image-24.png 639w, https:\/\/anchurus.co.uk\/wp-content\/uploads\/2026\/08\/image-24-245x300.png 245w\" sizes=\"auto, (max-width: 639px) 100vw, 639px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Figure 14.4. Table identifiers<\/em><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Referential integrity<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">One of the features of using a relational database is that it manages the relationships between the tables (Figure 14.1). For example, when you register a find in the database, you include the context identifier of the context in which it was found. If there is no record of the context in the system, it will not allow you to register the find. Similarly, should a site leader decide to delete a context from the database, the system will check that there are no finds related to that context. If such finds exist, the site leader cannot delete the context until all the finds have been edited to delete their relationships with the context. These checks maintain the referential integrity of the database.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The table below lists the referential integrity checks carried out by the Anchurus II web application and its supporting database.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>The relationship between tables<\/strong><br><\/td><td><strong>Checks made by the system<\/strong><br><\/td><\/tr><tr><td>site to all other tables<\/td><td>These checks are all automated once you have selected a site.<br>You cannot delete a site record if there are any other tables with records points to it. This includes the site user records.<\/td><\/tr><tr><td>context to find<\/td><td>The context must be recorded before you register a find found in that context.<br>You cannot delete a context record if there are find records linked to it.<\/td><\/tr><tr><td>find to box<\/td><td>You must record the box before you link find records to it.<br>You cannot delete a box record if there are find records linked to it.<\/td><\/tr><tr><td>box to trackbox<\/td><td>You must record a box before you record its movement in the trackbox table.<br>You cannot delete a box record if there are trackbox records linked to it.<\/td><\/tr><tr><td>find to all specialist find tables<\/td><td>You must record a find before you can create an associated find specialist table record.<br>You cannot delete a find record if there is an associated find specialist table records linked to it.<\/td><\/tr><tr><td>find to findgroup<\/td><td>The findgroup record must be inserted before you link a find record to it.<br>You cannot delete a findgroup record if there are find records linked to it.<\/td><\/tr><tr><td>interpretation to anomaly<\/td><td>An anomaly record must be created before you can link to it from the interpretation table<br>You cannot delete an anomaly record if it is linked to an interpretation record.<\/td><\/tr><tr><td>interpretation to phase<\/td><td>A phase record must be created before you can link to it from the interpretation table.<br>You cannot delete a phase record if it is linked to an interpretation record.<\/td><\/tr><tr><td>interpretation to groups<\/td><td>A group record must be created before you can link to it from the interpretation table.<br>You cannot delete a group record if it is linked to an interpretation record.<\/td><\/tr><tr><td>interpretation to sets<\/td><td>A set record must be created before you can link to it from the interpretation table.<br>You cannot delete a set record if it is linked to an interpretation record.<\/td><\/tr><tr><td>interpretation to context<\/td><td>A context record must be created before you can link to it from the interpretation table<br>You cannot delete a context record if it is linked to an interpretation record.<\/td><\/tr><tr><td>stratigraphicanalysis to context<\/td><td>A context record must be created before you can link to it from the Stratigraphic analysis table.<br>You cannot delete a context record if it is linked to a Stratigraphic analysis record.<\/td><\/tr><tr><td>stratigraphicanalysis to anomaly<\/td><td>An anomaly record must be created before you can link to it from the Stratigraphic analysis table.<br>You cannot delete an anomaly record if it is linked to a stratigraphic analysis record.<\/td><\/tr><tr><td>stratigraphicanalysis to find via the KeyFind column<\/td><td>A find record must be created before you can link to it from the stratigraphic analysis table.<br>You cannot delete a find record if it is linked to a stratigraphic analysis key find record.<\/td><\/tr><tr><td><\/td><td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><br><em>Figure 14.5. List of referential integrity constraints managed by Anchurus II web application<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Andrew Hutt<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Version v20e<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">21\/08\/2026<\/p>\n\n\n\n<div class=\"wp-block-essential-blocks-button  root-eb-button-p7nwx\"><div class=\"eb-parent-wrapper eb-parent-eb-button-p7nwx \"><div class=\"eb-button-wrapper eb-button-alignment eb-button-p7nwx\"><div class=\"eb-button\"><div class=\"eb-button-inner-wrapper \"><a class=\"eb-button-anchor  \" href=\"#\" rel=\"noopener\">Back to top<\/a><\/div><\/div><\/div><\/div><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Summary This page of the user manual describes the tables used to record and interpret an archaeological excavation and explains how you can find details of the data held in the tables. This is a relational database The Anchurus II release 2 database is a relational database so data is held in tables. The tables [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_eb_attr":"","footnotes":""},"class_list":["post-299","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/anchurus.co.uk\/index.php?rest_route=\/wp\/v2\/pages\/299","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/anchurus.co.uk\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/anchurus.co.uk\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/anchurus.co.uk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/anchurus.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=299"}],"version-history":[{"count":34,"href":"https:\/\/anchurus.co.uk\/index.php?rest_route=\/wp\/v2\/pages\/299\/revisions"}],"predecessor-version":[{"id":818,"href":"https:\/\/anchurus.co.uk\/index.php?rest_route=\/wp\/v2\/pages\/299\/revisions\/818"}],"wp:attachment":[{"href":"https:\/\/anchurus.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=299"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}