Sites
TerraLID ID
ID and name: SI0 terralid_site_id
Provided by: TerraLID system
Obligation: mandatory
Occurrences: 1
Definition: The ID of the site in the TerraLID database.
Allowed values and other constraints: t.b.d.
Example: t.b.d.
1. Site name
ID and name: SI1 site_name
Provided by: data provider
Obligation: mandatory
Occurrences: 1
Definition: The name of the locality/site or "unknown". Details about the locality should be provided in SI5.3 Description. If the locality belongs to a cluster and/or site complex, enter its name in SI9 Keywords.
Allowed values and other constraints: free text. If the site is unknown, value is "unknown" and SI2 Project name must be provided.
Example: Agrileza
2. Project name
ID and name: SI2 project_name
Provided by: data provider
Obligation: recommended
Occurrences: 0–1
Definition: The name of the project.
Allowed values and other constraints: free text. Must be provided if SI1 Site name has value "unknown".
Example: The Dreamland University Archaeometallurgy project.
3. Project context
ID and name: SI3 project_context
Provided by: data provider
Obligation: recommended
Occurrences: 0–1
Definition: A brief summary of the main aims and objectives of the research (or alternative process). May include a link e.g. the project's webpage.
Allowed values and other constraints: free text
Example: Excavation of an ore washing site.
4. Site identifier
ID and name: SI4 site_id
Provided by: Data provider
Obligation: recommended
Occurrences: 0–n
Definition: The site's persistent identifier in one or more of the data infrastructures listed in SI4.2 Type.
with the two subproperties:
4.1 Value
ID and name: SI4.1 site_id_value
Provided by: data provider
Obligation: recommended
Occurrences: 0–n
Definition: The value of the persistent identifier.
Allowed values and other constraints: valid persistent identifier according to the associated data infrastructure in SI4.2 Type.
Example: Q129256661
4.2 Type
ID and name: SI4.2 site_id_type
Provided by: data provider
Obligation: mandatory
Occurrences: 1–n
Definition: The name of the data infrastructure. Mandatory if SI4.1 Value is provided.
Allowed values and other constraints: controlled vocabulary
5. Geolocation
ID and name: SI5 site_geolocation
Provided by: data provider
Obligation: mandatory
Occurrences: 1
Definition: Information about the (approximate) location of the object or site it was found. All coordinates must be given in the WGS 84 coordinate system and as decimal numbers. If the exact site location is unknown or must not be revealed, a polygon or boundary box must be used to delineate an area of sufficient precision around the site location.
Subproperties of Geolocation are:
5.1 Point
ID and name: SI5.1 site_geolocation_point
Provided by: data provider
Obligation: recommended
Occurrences: 0–1
Definition: A point location in space.
with the two subproperties:
5.1.1 Longitude
ID and name: SI5.1.1 site_geolocation_point_longitude
Provided by: data provider
Obligation: mandatory
Occurrences: 1
Definition: The longitudinal dimension of a point.
Allowed values and other constraints: decimal number, between -180 and 180
Example: 7.21685
5.1.2 Latitude
ID and name: SI5.1.2 site_geolocation_point_latitude
Provided by: data provider
Obligation: mandatory
Occurrences: 1
Definition: The latitudinal dimension of a point.
Allowed values and other constraints: decimal number, between -90 and 90
Example: 51.48867
5.2 Boundary box
ID and name: SI5.2 site_geolocation_box
Provided by: data provider
Obligation: recommended
Occurrences: 0–1
Definition: The spatial limits of a box.
with the four subproperties:
5.2.1 Western boundary
ID and name: SI5.2.1 site_geolocation_box_west
Provided by: data provider
Obligation: mandatory
Occurrences: 1
Definition: The western longitudinal dimension of the box.
Allowed values and other constraints: decimal number, between -180 and 180
Example: 21.02
5.2.2 Eastern boundary
ID and name: SI5.2.2 site_geolocation_box_east
Provided by: data provider
Obligation: mandatory
Occurrences: 1
Definition: The eastern longitudinal dimension of the box.
Allowed values and other constraints: decimal number, between -180 and 180
Example: 21.05
5.2.3 Southern boundary
ID and name: SI5.2.3 site_geolocation_box_south
Provided by: data provider
Obligation: mandatory
Occurrences: 1
Definition: The southern latitudinal dimension of the box.
Allowed values and other constraints: decimal number, between -90 and 90
Example: 40.23
5.2.4 Northern boundary
ID and name: SI5.2.4 site_geolocation_box_north
Provided by: data provider
Obligation: mandatory
Occurrences: 1
Definition: The northern latitudinal dimension of the box.
Allowed values and other constraints: decimal number, between -90 and 90
Example: 40.53
5.3 Description
ID and name: SI5.3 site_geolocation_description
Provided by: data provider
Obligation: optional
Occurrences: 0–1
Definition: Further information about the site such as a description. If the site's exact location cannot be given, this must include a reasoning why and information about the level of precision.
Allowed values and other constraints: free text
Example: Entire valley given to obfuscate exact location of site as protection against illicit excavations; Area of Saudi-Arabia recorded as location because more precise information not available.
5.4 Polygon
ID and name: SI5.4 site_geolocation_polygon
Provided by: data provider
Obligation: recommended
Occurrences: 0–1
Definition: A drawn polygon area, defined by a set of points and lines connecting the points in a closed chain. At least four points must be recorded. The last point must be identical with the first point to close the polygon.
with the subproperty:
5.4.1 Polygon point data
ID and name: SI5.4.1 site_geolocation_polygon_point
Provided by: data provider
Obligation: mandatory
Occurrences: 1–n
Definition: A point marking an edge of the polygon.
with the two subproperties
5.4.1.1 Longitude
ID and name: SI5.4.1.1 site_geolocation_polygon_point_longitude
Provided by: data provider
Obligation: mandatory
Occurrences: 1
Definition: The longitudinal dimension of a point.
Allowed values and other constraints: decimal number, between -180 and 180
Example: 7.21685
5.4.1.2 Latitude
ID and name: SI5.4.1.2 site_geolocation_polygon_point_latitude
Provided by: data provider
Obligation: mandatory
Occurrences: 1
Definition: The latitudinal dimension of a point.
Allowed values and other constraints: decimal number, between -90 and 90
Example: 51.48867
6. Registry
ID and name: SI6 site_registry
Provided by: data provider
Obligation: recommended
Occurrences: 0–1
Definition: The entry of the site in the registry of the local authority (e.g., heritage authority, geological survey).
with the two subproperties:
6.1 Registry ID
ID and name: SI6.1 site_registry_id
Provided by: data provider
Obligation: recommended
Occurrences: 0–1
Definition: The site's identifier in the registry of the local authority.
Allowed values and other constraints: free text
Example: t.b.d.
6.2 Registry name
ID and name: SI6.2 site_registry_name
Provided by: data provider
Obligation: mandatory
Occurrences: 1
Definition: The name of the registry of the local authority. Mandatory if SI6.1 Registry ID is provided.
Allowed values and other constraints: free text
Example: t.b.d.
7. Dating
ID and name: SI7 site_date
Provided by: data provider
Obligation: recommended
Occurrences: 0–1
Definition: The time period represented by the site.
with the eight subproperties:
7.1 Persistent identifier
ID and name: B3.1 date_pid
Provided by: data provider
Obligation: recommended
Occurrences: 0–n
with the two subproperties:
7.1.1 Value
ID and name: B3.1.1 date_pid_value
Provided by: data provider
Obligation: recommended
Occurrences: 0–1
Definition: The value of the persistent identifier.
Allowed values and other constraints: The period's persistent identifier in one or more of the data infrastructures listed in B3.1.2 Type.
Example: 99152/p0qhb66vvth
7.1.2 Type
ID and name: B3.1.2 date_pid_type
Provided by: data provider
Obligation: mandatory
Occurrences: 1
Definition: The name of the data infrastructure. Mandatory if B3.1.1 Value is provided.
Allowed values and other constraints: controlled vocabulary
7.2 Date type
ID and name: B3.2 date_type
Provided by: data provider
Obligation: mandatory
Occurrences: 1–n
Definition: Is this an archaeological or geological age? Archaeological dates must be given in calendar years, with BCE dates as negative values. Geological dates must be given in million years.
Allowed values and other constraints: geological, archaeological
Example: archaeological
7.3 Absolute Date
ID and name: B3.3 date_absolute
Provided by: data provider, API
Obligation: recommended
Occurrences: 0–1
Definition: The absolute date of a point in time or period.
with the four subproperties:
7.3.1 Start
ID and name: B3.3.1 date_absolute_start
Provided by: data provider, API
Obligation: recommended
Occurrences: 0–1
Definition: The oldest possible date of the period.
Allowed values and other constraints: integer
Example: -15
7.3.2 End
ID and name: B3.3.2 date_absolute_end
Provided by: data provider, API
Obligation: recommended
Occurrences: 0–1
Definition: The youngest possible date of the period.
Allowed values and other constraints: integer
Example: 15
7.3.3 Dating method
ID and name: B3.3.3 date_absolute_method
Provided by: data provider
Obligation: mandatory
Occurrences: 1–n
Definition: The method used to determine the absolute date. Mandatory if B3.3.1 Start is provided.
Allowed values and other constraints: controlled vocabulary
7.3.4 Unit of date
ID and name: B3.3.4 date_absolute_unit
Provided by: TerraLID system
Obligation: mandatory
Occurrences: 1
Definition: The unit of the date. Mandatory if B3.3.1 Start is provided.
Allowed values and other constraints: a, Ma
Example: a
7.4 Relative Date
ID and name: B3.4 date_relative
Provided by: data provider, API
Obligation: recommended
Occurrences: 0–1
Definition: The relative date of a point in time or period.
with the two subproperties:
7.4.1 Chronological unit
ID and name: B3.4.1 date_relative_period
Provided by: data provider, API
Obligation: recommended
Occurrences: 0–1
Definition: The relative date expressed as a chronological unit.
Allowed values and other constraints: free text
Example: Ha B2; Emsium
7.4.2 Dating method
ID and name: B3.4.2 date_relative_method
Provided by: data provider
Obligation: mandatory
Occurrences: 1–n
Definition: The method used to determine the relative date. Mandatory if B3.4.1 Chronological unit is provided.
Allowed values and other constraints: controlled vocabulary
7.5 Cultural unit
ID and name: B3.5 date_archaeo_cultural
Provided by: data provider
Obligation: optional
Occurrences: 0–n
Definition: Relevant cultural and user created labels for the relative date of the item.
Allowed values and other constraints: free text, only available if B3.2 Date type = "archaeological".
Example: Roman
7.6 Orogenesis
ID and name: B3.6 date_geol_orogensis
Provided by: data provider
Obligation: recommended
Occurrences: 0–1
Definition: The relative date expressed as anorogenic event.
Allowed values and other constraints: controlled vocabulary, only available if B3.2 Date type = "geological".
7.7 Definition of chronological unit
ID and name: B3.7 date_relative_reference
Provided by: data provider
Obligation: recommended
Occurrences: 0–n
Definition: The reference where the relative date or period name is defined.
with the five subproperties:
7.7.1 Persistent Identifier
ID and name: B5.1 relation_pid
Provided by: data provider
Obligation: recommended
Occurrences: 0–n
Definition: The persistent identifier or TerraLID ID associated with a resource or related research output. If referring to another entity in the TerraLID database, the TerraLID identifier must be used.
with the two subproperties:
# 7.7.1.1 Value
ID and name: B5.1.1 relation_pid_value
Provided by: data provider
Obligation: recommended
Occurrences: 0–n
Definition: Value of the persistent identifier or TerraLID ID.
Allowed values and other constraints: valid persistent identifier according to the options listed in B5.1.2 Type.
Example: 10.60510/ICDP5054ESYI201
# 7.7.1.2 Type
ID and name: B5.1.2 relation_pid_type
Provided by: data provider
Obligation: mandatory
Occurrences: 0–n
Definition: The type of the identifier. Mandatory if B5.1.1 Value is provided.
Allowed values and other constraints: controlled vocabulary
7.7.2 Full reference
ID and name: B5.2 relation_text
Provided by: data provider, API (DOI)
Obligation: recommended
Occurrences: 0–1
Definition: The full reference of a publication.
Allowed values and other constraints: free text
Example: Palinkaš, L. A., 1985, Lead isotope patterns in galenas from some selected ore deposits in Croatia and NW Bosnia, Geološki Vjesnik, 38, 175–89.
7.7.3 Kind of relation
ID and name: B5.3 relation_kind
Provided by: data provider
Obligation: mandatory
Occurrences: 1–n
Definition: Relationship between item and the research output.
Allowed values and other constraints: controlled vocabulary
7.7.4 Type of resource
ID and name: B5.4 relation_resource
Provided by: data provider
Obligation: mandatory
Occurrences: 1–n
Definition: Type of resource or research output.
Allowed values and other constraints: controlled vocabulary
7.7.5 Additional details
ID and name: B5.5 relation_detail
Provided by: data provider
Obligation: optional
Occurrences: 0–n
Definition: Additional information about the relation, e.g., if the related work addresses a specific aspect of the item (e.g., the geological setting).
Allowed values and other constraints: free text
Example: Information about the dating of the site.
8. Site type
ID and name: SI8 site_type
Provided by: data provider
Obligation: mandatory
Occurrences: 1–n
Definition: The type of the site, geological or how it was used by humans.
Allowed values and other constraints: controlled vocabulary
9. Keywords
ID and name: SI9 site_keywords
Provided by: data provider
Obligation: recommended
Occurrences: 0–1
Definition: Keywords to further characterise the site. This includes any overarching complexes or clusters the site is part of.
Allowed values and other constraints: free text
Example: ore beneficiation, Laurion
10. Project dates
ID and name: SI10 project_date
Provided by: data provider
Obligation: mandatory
Occurrences: 1
Definition: The date of the investigation or project in which the site was/is studied.
with the two subproperties:
10.1 Start date
ID and name: SI10.1 project_date_start
Provided by: data provider
Obligation: mandatory
Occurrences: 1–n
Definition: Start date of the investigation or project in which the site was studied and sampled.
Allowed values and other constraints: date formatted as YYYY-MM-DD
Example: 1980-01-15
10.2 End date
ID and name: SI10.2 project_date_end
Provided by: data provider
Obligation: recommended
Occurrences: 0–n
Definition: End date of the investigation or project in which the site was/is studied and sampled, if known. Leave empty if investigation is still ongoing at the time of data entry.
Allowed values and other constraints: date formatted as YYYY-MM-DD
Example: 2000-04-20
11. Relations
ID and name: SI11 site_relation
Provided by: data provider
Obligation: recommended
Occurrences: 0–n
Definition: Information about related entities, including assemblages belonging to the site, and other research output such as publications providing relevant information about the site. This includes any literature from which information about the site was extracted.
with the five subproperties:
11.1 Persistent Identifier
ID and name: B5.1 relation_pid
Provided by: data provider
Obligation: recommended
Occurrences: 0–n
Definition: The persistent identifier or TerraLID ID associated with a resource or related research output. If referring to another entity in the TerraLID database, the TerraLID identifier must be used.
with the two subproperties:
11.1.1 Value
ID and name: B5.1.1 relation_pid_value
Provided by: data provider
Obligation: recommended
Occurrences: 0–n
Definition: Value of the persistent identifier or TerraLID ID.
Allowed values and other constraints: valid persistent identifier according to the options listed in B5.1.2 Type.
Example: 10.60510/ICDP5054ESYI201
11.1.2 Type
ID and name: B5.1.2 relation_pid_type
Provided by: data provider
Obligation: mandatory
Occurrences: 0–n
Definition: The type of the identifier. Mandatory if B5.1.1 Value is provided.
Allowed values and other constraints: controlled vocabulary
11.2 Full reference
ID and name: B5.2 relation_text
Provided by: data provider, API (DOI)
Obligation: recommended
Occurrences: 0–1
Definition: The full reference of a publication.
Allowed values and other constraints: free text
Example: Palinkaš, L. A., 1985, Lead isotope patterns in galenas from some selected ore deposits in Croatia and NW Bosnia, Geološki Vjesnik, 38, 175–89.
11.3 Kind of relation
ID and name: B5.3 relation_kind
Provided by: data provider
Obligation: mandatory
Occurrences: 1–n
Definition: Relationship between item and the research output.
Allowed values and other constraints: controlled vocabulary
11.4 Type of resource
ID and name: B5.4 relation_resource
Provided by: data provider
Obligation: mandatory
Occurrences: 1–n
Definition: Type of resource or research output.
Allowed values and other constraints: controlled vocabulary
11.5 Additional details
ID and name: B5.5 relation_detail
Provided by: data provider
Obligation: optional
Occurrences: 0–n
Definition: Additional information about the relation, e.g., if the related work addresses a specific aspect of the item (e.g., the geological setting).
Allowed values and other constraints: free text
Example: Information about the dating of the site.