Skip to content

Latest commit

 

History

History
72 lines (49 loc) · 5.21 KB

210.en.adoc

File metadata and controls

72 lines (49 loc) · 5.21 KB

Survey sampling design and event hierarchy

What is survey design and sampling event hierarchy?

Survey sampling design details the sampling strategy and how the survey event sites (e.g. stations, plots, transects) are laid out. The sampling event hierarchy is the translation of the survey sampling design into an event-based perspective using Darwin Core terms.

Sampling event hierarchy terms

Historically, only two (2) terms were available to explicitly structure and relate different levels of sampling event hierarchy in a dataset: term:dwc[dwc:eventID] and term:dwc[dwc:parentEventID]. One additional Darwin Core event term, term:dwc[dwc:fieldNumber], provided a means by which to relate a sampling event with a dataset- or project-specific field number. The Humboldt extension provides an additional two terms—term:eco[eco:siteCount] and term:eco[eco:siteNestingDescription]—to better support complex or nested datasets (see below NOTE: hyperlink to section number rather than using indexical text).

Review your DwC Event dataset to ensure that the survey design is accurately reflected in the use of the five (5) available sampling event hierarchy terms. Where additional events or event levels must be created, be sure to reference A Beginner’s Guide to Persistent Identifiers for guidance in creating new persistent identifiers.

Important
Do NOT change existing identifiers if it can be avoided!

Non-nested datasets

Fig 01 v1
Figure 1. A simple schematic of a non-nested event dataset structure (a) consisting of a single event with associated occurrences related to the event via the occurrence extension and (b) a series of individual events with associated occurrences related to the appropriate event via the occurrence extension.

Non-nested datasets may consist of a single sampling event with a single standardized sampling protocol that is not repeated (Figure 1a) or a series of single sampling events that are not joined by a larger parent event (Figure 1b).

  • Each event must have a unique term:dwc[dwc:eventID].

  • Non-nested datasets will not have a term:dwc[dwc:parentEventID].

  • term:eco[eco:siteNestingDescription] does not need to be populated.

Nested datasets

Nested datasets (multiple nested event levels) are established by relating a child event to a parent event through the child Event’s term:dwc[dwc:parentEventID]. The structure of these datasets can take various forms, but often center either first around the study site second and secondarily on protocol (Figure 2) or conversely, focusing on protocol at higher hierarchical levels and secondarily on locality (Figure 3). Alternatively, time-series dataset are temporally nested datasets (Figure 4).

  • Each event must have a unique term:dwc[dwc:eventID], and each parent event must have its own term:dwc[dwc:parentEventID].

  • Nested datasets should, at the parent event level, include the total number of sites sampled in term:eco[eco:siteCount] and provide a textual description of the hierarchical sampling design using term:eco[eco:siteNestingDescription].

  • If the survey data include a field number for each specific event, this should be shared using term:dwc[dwc:fieldNumber].

Fig 02a v1
Figure 2. Simplified example schematic of a nested event dataset structure representing a survey (Parent Event, dark red oval) with two survey sites (child-Events, medium red ovals) at each of which two protocols (child-child-Events, light red ovals) are implemented and occurrence information is collected and related to each sampling event using the occurrence extension.
Fig 02b v1
Figure 3. Simplified example schematic of a nested event dataset structure representing a survey (Parent Event, dark red oval) with two protocols (child-Events, medium red ovals) which are each implemented at two survey sites (four independently surveyed child-child-Events, light red ovals) wherein occurrence information is collected in four (likely quantitative) occurrences lists and related to each sampling event using the occurrence extension.
Fig 02c v1
Figure 4. Simplified example schematic of a nested event dataset structure representing a time series survey (Parent Event, dark red oval) with two survey sites (child-Events, medium red ovals) which are each independently sampled at two different times (four independently surveyed child-child-Events, light red ovals) wherein occurrence information is collected in four (likely quantitative) occurrences lists and related to each sampling event using the occurrence extension.
Table 1. Event hierarchy terms, their recommended usage (status), and example data entries
Status Term Example entry

Required

term:dwc[dwc:eventID]

survey2022_a-2

Required for nested datasets

term:dwc[dwc:parentEventID]

survey2022

Recommended

term:eco[eco:siteCount]

75

term:eco[eco:siteNestingDescription]

25 survey sites each with 3 1m2 quadrats

Share if available

term:dwc[dwc:fieldNumber]

RV Sol 87-03-08