3. The Data Dictionary
In the following section the contents of each table are listed. The listing consists of a series of printed tables each of which lists and defines the columns that comprise one of the database tables. The headings used in these printed tables are explained below:
Column Mnemonic: The column name used for this column in the database implementation. Mnemonics are all upper case and, if they consist of more than one word, the words are joined by the underscore (_) character. Where a column mnemonic is printed in bold it indicates that it comprises part or all of the primary key for the table.
Column Name: The actual name of the column, a more readable alternative to the column mnemonic hopefully suggestive of the purpose of the column.
Oracle Data Type: The data type used to store data for this column in the database. This will be one of the types available in the OracleTM version 7 database system used to implement the database. Where the data type has a user specified maximum length (for instance the VARCHAR2 data type), this is indicated in brackets after the type name.
Definition: Defines the contents of the column or, in other words, the type of information intended to be stored in it.
Entry Rule: Indicates the types of characters that are allowed to be entered into the column. For instance, a column with a Positive Integer entry rule would only allow character strings consisting entirely of the digit characters (0-9) to be entered.
Entry Class: Defines, using code letters, the constraints imposed by the database on entries to the column. A code letter of U indicates that entries in the column must be unique, in other words no two rows in a table may specify the same value for a unique column. A code letter of M indicates that the column is mandatory; when adding a row to a table, such mandatory columns may not be left blank.
Examples: Where useful, one or more examples of actual data that has been entered in the column is given.
SURVEY_VISIT - Each record in this table describes a unique event at which a geophysical survey was carried out. Such an event, referred to here as a 'visit', is defined by place and time and each entry should have in addition to a name and county a location, expressed as an NGR coordinate, and encompassing dates when the it took place.
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
SURVEY_VISIT_NO |
Survey Visit Number |
NUMBER |
Unique system number for each survey visit record. |
Positive integer |
U M |
|
||||||
|
SURVEY_NAME |
Survey Name |
VARCHAR2(50) |
Name given to a survey where geophysical survey has been carried out. This may often correspond to the name used to refer to the site in a following Report. |
Alphanumeric upper case |
M |
DORCHESTER BY-PASS; ST.GILES HOSPITAL |
||||||
|
COUNTY_CODE |
County Code |
CHAR(2) |
Two character codes for each county of England, following those suggested as a data standard by the RCHME (1993), with additional codes for Scotland and Wales. |
Alphabetic upper case |
|
OX |
||||||
|
SURVEY_START |
Survey date start |
DATE |
Date that survey visit commenced. |
Alphanumeric |
|
26/04/94 |
||||||
|
SURVEY_END |
Survey date end |
DATE |
Date that survey visit ended. |
Alphanumeric |
|
28/06/94 |
||||||
|
DATE_CERT |
Date Certainty
|
VARCHAR2(1) |
Indicator of the certainty of the survey dates. This would either contain a "?" or be left null. |
Alphanumeric |
|
|
||||||
|
VISIT_PURPOSE |
Purpose of visit |
VARCHAR2(2000) |
Short free text description of reasons for the survey. |
Alphanumeric mixed case |
|
|
||||||
|
PROJECT_TITLE |
Project Title |
VARCHAR2(80) |
Name of a project that encompasses a particular survey visit. |
Alphanumeric upper case |
|
RAUNDS AREA PROJECT |
||||||
|
EH_JOB_NO |
English Heritage Job Number |
VARCHAR2(6) |
Internal Service Request Job Number used by English Heritage. |
Positive integer |
|
23456 |
||||||
|
AML_SURVEY_NO |
AML Geophysical Survey No. |
VARCHAR2(6) |
Internal number given to each survey by the AML Geophysics section prior to 1986. |
Alphanumeric upper case |
|
G34/83 |
||||||
|
REPORT_STATUS |
Report status |
VARCHAR2(30) |
Term to describe report status of the survey as per agreed list. |
Alphanumeric upper case |
|
FULL REPORT; ARCHIVE ONLY |
||||||
|
REPORT_ID |
Report Identifier |
NUMBER |
See REPORT table. |
Positive integer |
|
|
||||||
|
NGR100KM_ SQUARE |
NGR 100 km square |
CHAR(2) |
The two letters which uniquely identify the 100km square, as defined by the OS, that contains the centre of the site. |
Alphabetic upper case |
|
SK |
||||||
|
NGR_EASTING |
NGR Easting |
VARCHAR2(3) |
Conventional grid reference recording the easting component, relative to the 100 km origin expressed as a string of numbers. Precision to the nearest 100m ie. to 3 digits. |
Positive integer |
|
678 |
||||||
|
NGR_NORTHING |
NGR Northing |
VARCHAR2(3) |
Conventional grid reference recording the northing component, relative to the 100 km origin expressed as a string of numbers. Precision to the nearest 100m. |
Positive integer |
|
328 |
||||||
|
NGR_NO_EAST |
NGR Easting relative to false origin |
NUMBER |
Easting Component expressed as a numeric string relative to the National Grid false origin. (the SW corner of the primary National Grid 500 km Square "S"). Automatically calculated from NGR Easting. |
Positive integer
|
|
467800 |
||||||
|
NGR_NO_NORTH |
NGR Northing relative to false origin |
NUMBER |
Northing Component expressed as a numeric string relative to the conventional UK false origin. Automatically calculated from NGR Northing. |
Positive integer
|
|
332800 |
||||||
|
PRIVACY_CODE |
Privacy Code |
NUMBER |
Numeric indicator to flag sensitive surveys. This allows the administrator to limit access to some or all of the data relating to a particular survey. |
Positive integer |
M |
|
||||||
|
PRIMARY_ARCHIVE |
Primary Archive Location |
VARCHAR2 (80) |
Organisation or individual holding the primary archive from the survey, ie raw data, original notes etc. |
Alphanumeric upper case |
|
ANCIENT MONUMENTS LABORATORY; BARTLETT A |
||||||
|
DATA_SOURCE |
Data Source |
VARCHAR2(20) |
Main source of information for the entry. This should be updated when further details added. |
Alphanumeric upper case |
|
REPORT; AML; GSB |
||||||
|
COMPILATION_DATE |
Compilation Date |
Date |
Date entry created. |
|
|
|
||||||
|
UPDATE_DATE |
Update Date |
Date |
Date record updated. |
|
|
|
||||||
|
UNITARY_ AUTHORITY |
Unitary Authority |
VARCHAR2(30) |
Name of unitary authority as supplied by the NMR Data Standards Unit |
Alphanumeric upper case |
|
EAST RIDING OF YORKSHIRE |
||||||
|
MIN_EAST |
Minimum NGR Easting relative to false origin |
NUMBER |
Minimum Easting Component of the survey area expressed as a numeric string relative to the National Grid false origin. |
Positive integer |
|
|
||||||
|
MIN_NORTH |
Minimum NGR Northing relative to false origin |
NUMBER |
Minimum Northing Component of the survey area expressed as a numeric string relative to the National Grid false origin. |
Positive integer |
|
|
||||||
|
MAX_EAST |
Maximum NGR Easting relative to false origin |
NUMBER |
Maximum Easting Component of the survey area expressed as a numeric string relative to the National Grid false origin. |
Positive integer |
|
|
||||||
|
MAX_NORTH |
Maximum NGR Northing relative to false origin |
NUMBER |
Maximum Northing Component of the survey area expressed as a numeric string relative to the National Grid false origin. |
Positive integer |
|
|
||||||
|
SURVEY_COMMENTS - This contains a free text field linked to the Survey visit table, but stored in a separate table to improve SQL performance. Each entry must refer to a Survey Visit Number
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
SURVEY_VISIT_NO |
Survey Visit Number |
NUMBER |
See SURVEY_VISIT table |
Positive integer |
U M |
|
||||||
|
COMMENTS |
Survey Comments |
LONG |
Text field to cover additional information about a particular survey visit that might not be included in a Report Summary, or in the absence of a such a summary. |
Alphanumeric mixed case |
M |
|
||||||
|
SURVEY_ROLE - This table contains the names of parties involved in the survey and their respective roles be it as client, surveyor, or any other capacity. Each entry must refer to a Survey Visit Number.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
ROLE_ID |
Survey Role Record Identifier |
NUMBER |
Unique record identifier and primary key. |
Positive integer |
U M |
|
||||||
|
SURVEY_VISIT_NO |
Survey Visit Number |
NUMBER |
See SURVEY_VISIT table. |
Positive integer |
M |
|
||||||
|
TYPE |
Role type |
VARCHAR2 (20) |
Term for a party's role in relation to the survey. |
Alphanumeric upper case |
M |
SURVEYOR; CLIENT |
||||||
|
NAME |
Role Name |
VARCHAR2 (80) |
Name of organisation or individual having an interest in the survey in one of the above capacities. |
Alphanumeric upper case |
M |
ANCIENT MONUMENTS LABORATORY; TRUST FOR WESSEX ARCHAEOLOGY. |
||||||
|
SURVEY_PERSONNEL - Table for AMLAB purposes to record the surveying personnel involved in each AMLAB visit. Each entry must refer to a Survey Visit Number.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
PERS_ID |
Survey Personnel Record Identifier |
NUMBER |
Unique record identifier and primary key. |
Positive integer |
U M |
|
||||||
|
SURVEY_VISIT_NO |
Survey Visit Number |
NUMBER |
See SURVEY_VISIT table. |
Positive integer |
M |
|
||||||
|
NAME |
Survey Personnel |
VARCHAR2 (30) |
Name of surveyor taking part on the particular survey visit. |
Alphabetic upper case (Surname Initials) |
M |
PAYNE A: COTTRELL P |
||||||
|
SURVEY_TECHNIQUE - Each record in this table refers to a particular methodology of surveying used on a particular survey visit. That methodology is defined by type, recording method, instrument type and configuration if appropriate, and sample intervals. Each entry must refer to a Survey Visit Number which in combination with the Technique number forms a unique primary key.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
TECHNIQUE_NO |
Technique number |
NUMBER |
Sequential number used to identify each separate technique used on a particular survey visit. Always starts at "1" for each survey visit. |
Positive integer |
M |
|
||||||
|
SURVEY_VISIT_NO |
Survey Visit Number |
NUMBER |
See SURVEY_VISIT table. |
Positive integer |
M |
|
||||||
|
SURVEY_TYPE |
Survey Type |
VARCHAR2 (50) |
Single term describing the type of geophysical survey taken from an agreed list of terms. |
Alphanumeric upper case |
M |
MAGNETOMETER; RESISTIVITY. |
||||||
|
METHOD_OF_COVERAGE |
Method of Coverage |
VARCHAR2 (30) |
Term describing if and how the data from a particular survey type has been recorded, taken from an agreed list of terms. |
Alphanumeric upper case |
|
SCAN; RECORDED GRID; SPOT SAMPLE. |
||||||
|
TRAVERSE_ SEPARATION |
Survey Traverse Separation |
VARCHAR2 (6) |
Distance between traverses when the survey has been undertaken using a regular recorded grid. |
Alphanumeric mixed case |
|
1m |
||||||
|
READING_INTERVAL |
Reading Interval |
VARCHAR2 (10) |
Distance between readings along a traverse. |
Alphanumeric mixed case |
|
0.5m |
||||||
|
INSTRUMENT_TYPE |
Instrument Type |
VARCHAR2 (30) |
Generic term that describes the particular type of instrument used. |
Alphanumeric upper case |
|
FLUXGATE GRADIOMETER; FIELD LOOP |
||||||
|
INSTRUMENT_MAKE |
Instrument Make |
VARCHAR2(50) |
Make and version of instrument. |
Alphanumeric upper case |
|
GEOSCAN FM36; BARTINGTON MS2 |
||||||
|
PROBE_CONFIGURATION |
Resistivity Probe Configuration |
VARCHAR2 (20) |
Term that describes the arrangement of the probes in a resistivity array. |
Alphanumeric upper case |
|
TWIN-PROBE; WENNER |
||||||
|
PROBE_SPACING |
Resistivity Probe Spacing |
VARCHAR2 (6) |
Distance between the relevant adjacent probes of a resistivity array depending on the configuration being used. |
Alphanumeric mixed case |
|
0.5m; 1m |
||||||
|
ADD_REMARKS |
Additional Remarks |
VARCHAR2 (1000) |
Free text field for any extra details concerning a particular survey technique record. This could be used for unusual configurations or sampling strategies, weather conditions, equipment failures etc. |
Alphanumeric mixed case. |
|
|
||||||
|
LAND_USE |
Land Use |
VARCHAR2 (50) |
A term that describes the state of the surveyed land at the time of the survey. List of agreed terms. |
Alphanumeric upper case |
|
INTER-TIDAL; ARABLE. |
||||||
|
AREA_SURVEYED |
Area Surveyed |
NUMBER (3,1) |
Area to the nearest tenth of a hectare covered by a particular survey technique. |
Positive integer |
|
4.2 |
||||||
|
DATA_URL |
Data URL |
VARCHAR2(80) |
Uniform Resource Locator of file containing data collected by the techniquedescribed in the record. |
Alphanumeric mixed case. |
|
|
||||||
|
REPORT - Table of written reports that have been generated from the results of particular geophysical survey visits. Each entry must have a report title.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
REPORT_ID |
Report identifier |
NUMBER |
Unique record identifier and primary key. |
Positive integer |
U M |
|
||||||
|
TITLE |
Report Title |
VARCHAR2 (120) |
Full Title of Report. |
Alphanumeric upper case |
M |
GEOPHYSICAL SURVEY IN THE STONEHENGE AREA 1976 - 1979 |
||||||
|
REPORT_SERIES |
Report Series |
VARCHAR2 (50) |
Name of the series that a report appears in. |
Alphanumeric upper case |
|
AMLAB REPORTS (NEW SERIES) |
||||||
|
SERIES_NO |
Series Report Number |
VARCHAR2 (20) |
Number given by the authors of the report that uniquely identifies a report from a particular series. |
Alphanumeric mixed case |
|
49/92 |
||||||
|
REPORT_DATE |
Report Date |
DATE |
Date of report completion. |
|
|
|
||||||
|
AUTHOR |
Author |
VARCHAR2 (50) |
Writer of the Report. |
Alphabetic mixed case |
|
Payne A; Linford N and Cole M |
||||||
|
HOLDER |
Report Holder |
VARCHAR2 (80) |
Body holding copies of report. The body from whom copies should be requested. |
Alphanumeric upper case |
|
ANCIENT MONUMENTS LABORATORY |
||||||
|
URL |
Uniform Resource Locater |
VARCHAR2 (80) |
Character string that identifies the computer address and file name of a hypertext document containing the text of the report. |
Alphanumeric mixed case |
|
http://www.eng-h.gov.uk/reports/oldwinch |
||||||
|
COPY_HELD |
Copy Held |
VARCHAR2(3) |
Indication of whether the branch has a copy. |
Alphabetic mixed case |
|
Yes |
||||||
|
SECTION42 |
Section 42 licence |
VARCHAR2(1) |
Indication of whether report received as part of conditions of licence application. |
Alphabetic upper case |
|
Y |
||||||
|
COPY_OF_LICENCE |
Copy of licence |
VARCHAR2(1) |
Indication of whether branch has copy of Section 42 licence. |
Alphabetic upper case |
|
Y |
||||||
|
REPORT_SUMMARY - Extension of the Report Table using the same unique report identification number as its primary key. The table is separate for operational reasons.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
REPORT_ID |
Report identifier |
NUMBER |
Unique record identifier and primary key. |
Positive integer |
U M |
|
||||||
|
SUMMARY |
Report Summary |
LONG |
Summary of the results, either as entered in the report, or a compiler's synopsis. |
Alphanumeric mixed case |
M |
|
||||||
|
COMPILER_SYNOPSIS |
Compiler Synopsis |
VARCHAR2(1) |
Yes or No column to flag compiler synopsis. |
Upper Case |
M |
Y |
||||||
|
Classification Table - Each record in this table contains a classification by type and period of any monuments or archaeological site types that has been covered by the survey. These could be already known, detected by survey or discovered subsequently through excavation or other means.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
CLASS_ID |
Classification Identifier |
NUMBER |
Unique record identifier and primary key. |
Positive integer |
U M |
|
||||||
|
SURVEY_VISIT_NO |
Survey Visit Number |
NUMBER |
See SURVEY_VISIT table |
Positive integer |
M |
|
||||||
|
MONUMENT_TYPE |
Monument Type |
VARCHAR2 (50) |
Term by which a monument has been classified. Terminology is derived from the "Thesaurus of Monument Types" RCHME/English Heritage (1995). |
Alphanumeric upper case |
M |
ROUND BARROW; FORMAL GARDEN; HILL FORT. |
||||||
|
MONUMENT_ CERTAINTY |
Monument Certainty |
VARCHAR2 (1) |
Indicator of the certainty of the monument's type. Column can contain a "?" or "NULL". |
Alphanumeric mixed case |
|
|
||||||
|
BROAD_TERM |
Broad term for Monument Type |
VARCHAR2(50) |
Broad term for specific monument types only to help in searching the database. |
Alphanumeric upper case |
|
BARROW; GARDEN |
||||||
|
MONUMENT_PERIOD |
Monument Period |
VARCHAR2 (3) |
Coded field describing the period to which the monument belongs. Codes are as used by RCHME for NAR and are listed with their legends in a separate look-up table. |
Alphabetic upper case |
M |
ME; RO; PM; |
||||||
|
PERIOD_PRECISION |
Period Precision |
VARCHAR2 (1) |
Indicator of certainty of period. Either a "?" or null. |
Alphanumeric mixed case |
|
|
||||||
|
SOURCE |
Source of Classification |
VARCHAR2 (20) |
Indicator of how the monument or site was identified. |
Alphabetic upper case |
|
PREVIOUSLY KNOWN; DETECTED BY SURVEY |
||||||
|
MONUMENT_ID |
Monument Identifier |
NUMBER |
Link field to Monument Classification table. |
Positive integer |
|
|
||||||
|
Monument Classification Table - Each record in this table contains details of any archaeological monuments which fall within the boundaries of, or are associated with a survey. If applicable the monument can be identified by its Scheduled Monument or National Monument Record numbers.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
MONUMENT_ID |
Monument Identifier |
NUMBER |
Unique system number that identifies each record. |
Positive integer |
U M |
|
||||||
|
MONUMENT_NAME |
Monument Name |
VARCHAR2 (60) |
Commonly used name for monument. |
Alphanumeric upper case. |
|
WHISPERING KNIGHTS |
||||||
|
SAM_NO |
Scheduled Ancient Monument identifier |
VARCHAR2 (10) |
Alphanumeric string based on County Code and Monument no. that uniquely identifies the monument within the SAM system. |
Alphanumeric mixed case |
|
ST137b |
||||||
|
RSM_NO |
Scheduled Monument National Number |
NUMBER |
Number which uniquely identifies each monument in the Record of Scheduled Monuments ie. those scheduled under the Monuments Protection Programme. |
Positive integer |
|
12345 |
||||||
|
NAR_NO |
National Archaeological Record Ref. Number |
VARCHAR2 (15) |
Alphanumeric string which uniquely identifies an RCHME recorded monument. |
Alphanumeric upper case |
|
SU 96 NE 34; LINEAR 102; RRX 27 |
||||||
|
RELATED_MONUMENT - Linking table to relate a Survey Visit record to a Monument Record, using the primary keys from each table to form a unique, composite primary key.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
SURVEY_VISIT_NO |
Survey Visit Number |
NUMBER |
See SURVEY_VISIT table. |
Positive integer |
M |
|
||||||
|
MONUMENT_ID |
Monument Identifier |
NUMBER |
See MONUMENT_CLASSIFICATION table. |
Positive integer |
M |
|
||||||
|
SOLID_GEOLOGY - Table containing code and description of underlying solid geology types.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
CODE |
Solid Geology Code |
VARCHAR2 (6) |
Numerical Code that relates to a descriptive term for the underlying solid geology at the site. The codes are taken from the 1:625000 Geological Map of the United Kingdom (Solid Geology) 3rd Edition, 1979. |
Positive integer |
U M |
95 |
||||||
|
DESCRIPTION |
Solid Geology Description |
VARCHAR2 (60) |
Descriptive term for the underlying solid geology at the site that corresponds to the above code in the 1:625000 Geological Map of the United Kingdom (Solid Geology) 3rd Edition, 1979. |
Alphanumeric upper case |
M |
GREAT OOLITE |
||||||
|
DRIFT_GEOLOGY - Table containing description of underlying drift geology types.
|
||||||||||||
|
DRIFT_ID |
Drift Geology Type Identifier |
NUMBER |
Unique system number and primary key for each record. |
Positive integer
|
U M |
|
||||||
|
TERM |
Drift Geology Term |
VARCHAR2 (60) |
Descriptive term for any underlying drift deposits at the site. The terms are taken from the 1:625000 Quaternary map of the United Kingdom, 1st Edition, 1977, with some additions. See the lists of terms at the end of the report. |
Alphanumeric upper case |
M |
RIVER TERRACE DEPOSITS; ALLUVIUM |
||||||
|
RELATED_DRIFT_GEO and RELATED_SOLID_GEO - These two tables relate a survey visit record to tables containing details of the underlying geologies to be found at a particular survey site. Each entry must have a number or code representing the appropriate geological classification and an associated Survey Visit Number to form a unique, composite primary key.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
SURVEY_VISIT_NO |
Survey Visit Number |
NUMBER |
See SURVEY_VISIT table. |
Positive integer |
M |
|
||||||
|
SOLID_GEOLOGY |
Solid Geology Code |
VARCHAR2 (6) |
Code as defined in SOLID_GEOLOGY table. |
Positive integer |
M |
95 |
||||||
|
|
||||||||||||
|
SURVEY_VISIT_NO |
Survey Visit Number |
NUMBER |
See SURVEY_VISIT table. |
Positive integer |
M |
|
||||||
|
DRIFT_ID |
Drift Geology Type Identifier |
NUMBER |
See DRIFT_GEOLOGY table. |
Positive integer |
M |
|
||||||
|
FURTHER_COMMENTS - Table for added information pertaining to a particular survey such as details of subsequent excavation, survey, or other intervention on the site that might add to the interpretation of that survey. The comment should be dated and attributed to its author. Each entry must have a Survey Visit Number as a foreign key.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
FC_ID |
Further Comment Record Identifier |
NUMBER |
Unique system number and primary key for each record. |
Positive integer |
U M |
|
||||||
|
SURVEY_VISIT_NO |
Survey Visit Number |
NUMBER |
See SURVEY_VISIT table. |
Positive integer |
M |
|
||||||
|
COMMENT_DATE |
Comment Date |
DATE |
Date the comment is added to the database. This can be automatically generated. |
Alphanumeric |
M |
|
||||||
|
AUTHOR |
Comment Author |
VARCHAR2 (15) |
Initials of person adding the comment. |
Alphanumeric mixed case |
M |
|
||||||
|
COMMENT_DETAIL |
Comment Detail |
LONG |
Descriptive field for comments on any intervention at, or concerning, a site that has relevance to the interpretation of the survey carried out there. |
Alphanumeric mixed case |
M |
|
||||||
|
BIBLIOGRAPHIC_REFERENCE - Table of references to select bibliographic sources that are considered to have direct relevance to a particular survey. At present these are limited to publications where results or interpretations from a survey have been included in the work.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
BIB_REF_NO |
Bibliographic Reference Number |
NUMBER |
Unique system number that identifies each record. |
Positive integer |
U M |
|
||||||
|
AUTHOR |
Author |
VARCHAR2 (50) |
Author or authors of the publication cited. |
Alphabetic mixed case. (Surname, Initials); etc. |
|
David, A E U; Linford, P, and Cottrell, P, |
||||||
|
YEAR |
Year of publication |
VARCHAR2 (4) |
Year of publication in full. |
Positive integer |
|
1984 |
||||||
|
REFERENCE |
Bibliographic Reference |
VARCHAR2 (1000) |
Full reference to the publication, with the exception of the author and year. Reference should be set out in the manner suggested in the English Heritage pamphlet >Academic and Specialist Publications. Preparing your text for publication=. |
Alphanumeric mixed case |
M |
The Stonehenge Environs Project, English Heritage Archaeological Report No. 16, London. |
||||||
|
URL |
Uniform Resource Locater |
VARCHAR2 (100) |
Character string that identifies the computer address and file name of a hypertext version of the document referred to. |
Alphanumeric mixed case |
|
http://www.english-heritage.org.uk/knowledge/archaeology/archreview9697/weshill.htm |
||||||
|
RELATED_BIB_REF - Table to relate a bibliographic reference to a particular survey visit using the primary keys from each table to form a composite primary key.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
SURVEY_VISIT_NO |
Survey Visit Number |
NUMBER |
See SURVEY_VISIT table. |
Positive integer |
M |
|
||||||
|
BIB_REF_NO |
Bibliographic Reference Number |
NUMBER |
See BIBLIOGRAPHIC_REFERENCE table. |
Positive integer |
M |
|
||||||
|
ADDRESS - Table containing the addresses of any party involved in the survey. This will invariably be an interested party from the `Survey Role' table, or an archive holder listed in either the SURVEY_VISIT or REPORT tables and will be linked to these tables by the appropriate field. In some cases an entry may refer to another entry for address details where a body has changed its name or become part of another organisation since the survey took place.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
ADDRESS_ID |
Address |
NUMBER |
Unique system number that identifies each record. |
Positive integer |
U M |
|
||||||
|
NAME |
Name |
VARCHAR2 (80) |
Name of the body or person whose address details appear in the entry. |
Alphabetic upper case |
M |
|
||||||
|
POSTAL_ADDRESS |
Postal Address |
VARCHAR2 (1000) |
Full postal address of the above body or person, or a reference to another entry in the table if the name of the body has changed. |
Alphanumeric upper case |
|
|
||||||
|
TELEPHONE |
Telephone |
VARCHAR2 (15) |
Full telephone no. including code. |
Alphanumeric |
|
|
||||||
|
FAX |
Number |
VARCHAR2 (15) |
Full fax no. including code.
|
Alphanumeric |
|
|
||||||
|
E_MAIL |
Electronic mail address |
VARCHAR2 (30) |
Full Email address. |
Alphanumeric mixed case |
|
P.Cottrell@eng-h.gov.uk |
||||||
|
TAPE_ARCHIVE - An internal table to record the details of electronic data from a survey that has been archived onto magnetic tape. Each entry is defined by the survey it refers to and the directory that the survey data has been assigned to and consequently must have a Survey Visit Number as a foreign key.
|
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
TAPE_ID |
Tape identifier no. |
NUMBER |
Unique system number that identifies each record. |
Positive integer |
U M |
|
||||||
|
SURVEY_VISIT_NO |
Survey Visit Number |
NUMBER |
See SURVEY_VISIT Table. |
Positive integer |
M |
|
||||||
|
DIRECTORY |
Directory |
VARCHAR2 (20) |
Computer directory that holds an amount of data from a particular survey visit. |
Alphanumeric lower case |
M |
|
||||||
|
TAPE_NO |
Tape Number |
NUMBER |
Assigned number of the tape that the data has been archived to. |
Positive integer |
M |
|
||||||
|
TAPE_SUFFIX |
Tape Suffix |
VARCHAR2 (3) |
Three letter suffix that along with the Tape number gives the tape a unique identifier. |
Alphabetic lower case |
|
|
||||||
|
ARCHIVE_DATE |
Archive Date |
DATE |
Date that the data is transferred to archive. |
Alphanumeric |
|
|
||||||
|
Look-Up Tables The following tables contain lists of terms or codes currently acceptable for entry into certain fields within the main database tables. Their purpose is to act as look-up lists and to preserve the integrity of the fields in which they are used by the application of referential constraints.
COUNTY_CODE |
||||||||||||
|
Column Mnemonic |
Column name |
Oracle Data Type (size) |
Definition |
Entry Rule |
Entry Class |
Examples |
||||||
|
CODE |
County Code |
CHAR(2) |
Abbreviation, derived originally from the National Census, that can be used in the COUNTY_CODE field of the SURVEY_VISIT table. See lists of terms at the back of the report for derivation. |
Alphabetic upper case |
U M |
CO |
||||||
|
COUNTY |
County Name |
VARCHAR2 (40) |
Name of County indicated by one of the above codes. |
Alphabetic mixed case |
U M |
Cornwall |
||||||
|
REPORT_QUALIFIER |
||||||||||||
|
QUALIFIER |
Report Qualifier |
VARCHAR2 (30) |
Term that can be used in the REPORT_STATUS field of the SURVEY_VISIT table. See lists of terms at the back of the report for derivation. |
Alphanumeric upper case |
U M |
DRAFT REPORT; ARCHIVE ONLY |
||||||
|
ROLE_TYPE |
||||||||||||
|
ROLE_TYPE |
Role Type |
VARCHAR2 (20) |
Term that can be used in the TYPE field of the SURVEY_ROLE table. See lists of terms at the back of the report for derivation. |
Alphanumeric upper case |
U M |
CLIENT; SURVEYOR |
||||||
|
SURVEY_TYPE |
||||||||||||
|
TERM |
Survey Type |
VARCHAR2 (50) |
Term that can be used in the SURVEY_TYPE field of the SURVEY_TECHNIQUE table. See lists of terms at the back of the report for derivation. |
Alphanumeric upper case |
U M |
MAGNETOMETER |
||||||
|
METHOD_OF_COVERAGE |
||||||||||||
|
TERM |
Survey coverage method |
VARCHAR2 (30) |
Term that can be used in the METHOD_OF_COVERAGE field of the SURVEY_TECHNIQUE table. See lists of terms at the back of the report for derivation. |
Alphanumeric upper case |
U M |
RECORDED GRID; SCAN |
||||||
|
LAND_USE |
||||||||||||
|
TERM |
Land Use |
VARCHAR2 (50) |
Term that can be used in the LAND_USE field of the SURVEY_TECHNIQUE table. See lists of terms at the back of the report for derivation. |
Alphanumeric upper case |
U M |
ARABLE; |
||||||
|
MONUMENT_TYPE |
||||||||||||
|
MONTY_ID |
Monument type Id |
NUMBER |
Unique system number that identifies each record. Used to help manage the large list of terms in this table. |
Positive integer |
U M |
|
||||||
|
TERM |
Monument Type |
VARCHAR2 (50) |
Term that can be used in the MONUMENT_TYPE field of the MONUMENT_CLASSIFICATION table. See lists of terms at the back of the report for derivation. |
Alphanumeric upper case |
U M |
ABBEY; HILLFORT |
||||||
|
MONUMENT_PERIOD |
||||||||||||
|
PERIOD_ID |
Monument Period Id |
NUMBER |
Unique system number that identifies each record. |
Positive integer |
U M |
|
||||||
|
CODE |
Period Code |
VARCHAR2 (3) |
Code that represents a period definition, and can be used in the MONUMENT_PERIOD field of the MONUMENT_CLASSIFICATION table. See lists of terms at the back of the report for derivation. |
Alphabetic upper case |
U M |
NE; EM |
||||||
|
LEGEND |
Period Legend |
VARCHAR2 (30) |
Definition of the period represented by one of the above codes. |
Alphabetic mixed case |
U M |
Neolithic; Early Medieval |
||||||
|
UNITARY_ AUTHORITY |
||||||||||||
|
UA_ID |
Unitary Authority Id |
NUMBER |
Unique system number that identifies each record. |
Positive integer |
U M |
|
||||||
|
UNITARY_AUTHORITY |
Unitary Authority |
VARCHAR2 (30) |
Name of English Unitary Authority as at 1st April 1998 from list supplied by the Data Standards Unit, National Monuments Record. |
Alphanumeric upper case |
M |
PORTSMOUTH; EAST RIDING OF YORKSHIRE |
||||||
|
COUNTY_CODE |
County Code |
CHAR(2) |
Code for county in which the authority existed prior to local authority changes of 1998. See County Code Table for origin of codes. |
Alphabetic upper case |
|
HA |
||||||
|
SURVEYORS |
||||||
|
SURVEYOR_ID |
Surveyor Id |
NUMBER |
Unique system number that identifies each record. |
Positive integer |
U M |
|
|
NAME |
Surveyor Name |
VARCHAR2 (80) |
Name of Surveyor. |
Alphanumeric upper case |
M |
OXFORD ARCHAEOTECHNICS |
|
MARKER_GIF |
Marker Gif |
VARCHAR(128) |
Name and path of .gif file containing relevent icon for the surveyor. |
Alphanumeric mixed case |
|
|