1. Project
Obligation: Mandatory
Definition:
The title (and any alternatives) of the site or project.
Allowed values, examples, other constraints:
188 Cumberland Street, The Rocks.
Sub-properties:
1.1 projectDescription¶
Obligation: Recommended
Definition:
A brief summary of the main aims and objectives of the research project (or alternative process) from which the sample collection arose together with a brief summary description of the sample content.
Allowed values, examples, other constraints:
Small historical archaeological project in The Rocks, Sydney, uncovering relics of domestic and commercial life from the 1820s through to the late 20th century.
1.2 siteLocation¶
Obligation: Mandatory
Definition:
The location from where the sample was collected, as accurately as possible—noting that this can be sensitive information and in such cases, generalized information should be provided to the level it is safe to publish (e.g. spatial region). Ideally, GPS or lat–long coordinates should be included using WGS-84 format in decimal degrees.
If the country, region, county, town or village covered by the sample collection is specified, then this should include current and contemporary name(s) and, where possible, a standardized reference such as the Getty Thesaurus of Geographic Names or GeoNames should be used.
If names or administrative units change during the time period of the sample collection, they should be recorded separately. Site coordinates can also be entered as a National Grid Reference in a number of different ways (e.g., as a point, line, polygon).
It is helpful to include the full postal code of the site, if applicable.
Allowed values, examples, other constraints:
At least one of the below geolocation subproperties must be included.
Additional information concerning the site location should be captured in the free-text locationPlace subproperty.
1.2.1 locationPoint¶
Obligation: Recommended
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.1.1 pointLongitude¶
Obligation: Mandatory
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.1.2 pointLatitude¶
Obligation: Mandatory
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.2 locationBox¶
Obligation: Recommended
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.2.1 westBoundLongitude¶
Obligation: Mandatory
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.2.2 eastBoundLongitude¶
Obligation: Mandatory
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.2.3 southBoundLatitude¶
Obligation: Mandatory
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.2.4 northBoundLatitude¶
Obligation: Mandatory
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.3 locationPlace¶
Obligation: Recommended
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.4 locationPolygon¶
Obligation: Recommended
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.4.1 polygonPoint¶
Obligation: Mandatory
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.4.1.1 pointLongitude¶
Obligation: Mandatory
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.4.1.2 pointLatitude¶
Obligation: Mandatory
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.4.2 inPolygonPoint¶
Obligation: Recommended
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.4.2.1 pointLongitude¶
Obligation: Mandatory
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.2.4.2.2 pointLatitude¶
Obligation: Mandatory
Definition:
These subproperties follow from the DataCite Metadata Schema. Please see the documentation for the latest version of the DataCite Schema for the definitions of these subproperties.
Allowed values, examples, other constraints:
Please see the documentation of the latest version of the DataCite Schema for examples of these subproperties.
1.3 agencyIdentifier¶
Obligation: Recommended
Definition:
Agency or project site identifier used as a local identifier of the site.
Allowed values, examples, other constraints:
Smithsonian Trinomial, AZ State Museum (ASM) number,...
1.4 siteTemporalCoverage¶
Obligation: Recommended
Definition:
The dates/period covered by samples collected at the site, regardless of whether all samples have been (or will be) preserved or registered with persistent identifiers. Use an existing thesaurus where possible, such as the RCHME Period List or PeriodO.
Allowed values, examples, other constraints:
Bronze Age, Medieval,...
1.4.1 temporalClassification¶
Obligation: Mandatory
Definition:
Mandatory if siteTemporalCoverage is included. Should contain at least one, and ideally all, of the following:
- The name of the standard vocabulary being used for siteTemporalCoverage
- The URI of the standard vocabulary being used
- The URI of the exact term used in siteTemporalCoverage
- The classification code (if one exists) of the exact term used in siteTemporalCoverage
Note that a&b and c&d are normally pair values, so it is encouraged to include both where possible. For machine readability, and if you are using a FAIR vocabulary, it is recommended to include the URI values, with c, being optimal.
Allowed values, examples, other constraints:
http://n2t.net/ark:/99152/p072r4qmq9s
Historic England Periods, https://heritagedata.org/live/schemes/eh_period.html
1.5 siteOwner¶
Obligation: Optional
Definition:
The organization that owns the land on which the sample was collected; the default is 'Private'.
Allowed values, examples, other constraints:
Sydney Harbour Foreshore Authority, Private,...
1.6 siteType¶
Obligation: Recommended
Definition:
Type of past activity area(s) identified at the site. An existing controlled vocabulary should be used where possible, such as the Getty Research Institute Art & Architecture Thesaurus or the tDAR Data Dictionary.
Allowed values, examples, other constraints:
Cemetery, Cave settlement, Castle, Monastery,...
1.6.1 siteClassification¶
Obligation: Mandatory
Definition:
Mandatory if siteType is used. Should contain at least one, and ideally all, of the following:
- The name of the standard vocabulary being used for siteType
- The URI of the standard vocabulary being used
- The URI of the exact term used in siteType
- The classification code (if one exists) of the exact term used in siteType
Note that a&b and c&d are normally pair values, so it is encouraged to include both where possible. For machine readability, and if you are using a FAIR vocabulary, it is recommended to include the URI values, with c, being optimal.
Allowed values, examples, other constraints:
300006891, http://vocab.getty.edu/page/aat/300006891
tDAR Data Dictionary Site Types, https://tdar-arch.atlassian.net/wiki/spaces/TDAR/pages/557203/Site+Types
1.7 Keywords¶
Obligation: Optional
Definition:
User created values to describe aspects of the site not covered by other metadata.
Allowed values, examples, other constraints:
Coastal, Eroded, Waterlogged,...