Class: Experiment

Experiment metadata applies to a specific study but remains consistent across datasets.

classDiagram class Experiment click Experiment href "../Experiment" Experiment <|-- Intervention click Intervention href "../Intervention" Experiment : additional_details Experiment : data_conflicts_and_unreported_data Experiment : description Experiment : end_datetime Experiment : experiment_id Experiment : experiment_type Experiment --> "1" ExperimentType : experiment_type click ExperimentType href "../ExperimentType" Experiment : investigators Experiment --> "1..*" Investigator : investigators click Investigator href "../Investigator" Experiment : meteorological_and_tidal_data Experiment --> "*" NamedLink : meteorological_and_tidal_data click NamedLink href "../NamedLink" Experiment : name Experiment : project_id Experiment : spatial_coverage Experiment --> "1" Place : spatial_coverage click Place href "../Place" Experiment : start_datetime Experiment : vertical_coverage Experiment --> "1" VerticalExtent : vertical_coverage click VerticalExtent href "../VerticalExtent"

Inheritance

Experiment
- Intervention

Slots

Name	Cardinality and Range	Description	Inheritance
name	0..1 String	A human-readable name for the thing	direct
description	1 String	A narrative description of the experiment	direct
spatial_coverage	1 Place	Latitude/longitude bounds of observed data in experiment, provided in decimal...	direct
vertical_coverage	1 VerticalExtent	Minimum and maximum depths of observations in meters	direct
experiment_id	1 String	The experiment to which the data belong	direct
project_id	0..1 String	Project ID must be included in the Experiment-level metadata in order to link...	direct
experiment_type	1 ExperimentType	The type of mCDR experiment conducted	direct
investigators	1..* Investigator	Provide details for each investigator including: Name, institutional informat...	direct
start_datetime	1 Datetime	Start date and time of experiment in UTC ISO-8601	direct
end_datetime	1 Datetime	End date and time of experiment in UTC ISO-8601	direct
data_conflicts_and_unreported_data	0..1 String	If data exist that are or have been used by the project but are not provided ...	direct
meteorological_and_tidal_data	* NamedLink	Include links to relevant open datasets if referenced in the experiment but n...	direct
additional_details	0..1 String	Open text area to include additional information	direct

Usages

used by	used in	type	used
OAEProject	experiments	range	Experiment

Identifier and Mapping Information

Schema Source

from schema: OAEDataManagementProtocol

Mappings

Mapping Type	Mapped Value
self	oae:Experiment
native	oae:Experiment

LinkML Source

Direct

name: Experiment
description: Experiment metadata applies to a specific study but remains consistent
  across datasets.
from_schema: OAEDataManagementProtocol
slots:
- name
- description
- spatial_coverage
- vertical_coverage
slot_usage:
  description:
    name: description
    description: A narrative description of the experiment. For example, what part
      of the project do these data represent (e.g., baseline, intervention, control)
      and what do they contribute to the overall project? Are all project research
      questions listed in Project description relevant? What were the processes to
      achieve these goals and answer these questions? Data submitters are encouraged
      to note any significant changes to the original experimental plan due to unforeseen
      circumstances here.
    title: Experiment Description
    required: true
  spatial_coverage:
    name: spatial_coverage
    description: Latitude/longitude bounds of observed data in experiment, provided
      in decimal degrees as westernmost longitude, southernmost latitude, easternmost
      longitude, northernmost latitude. [S, W, N, E]
    required: true
  vertical_coverage:
    name: vertical_coverage
    description: Minimum and maximum depths of observations in meters.
    required: true
attributes:
  experiment_id:
    name: experiment_id
    description: 'The experiment to which the data belong. Any naming convention that
      produces a unique ID is usable. The recommended naming convention is:

      Project ID + Experiment type + Optional numerical indicator to differentiate
      between various experiments of the same type for a project. A two digit consecutive
      number beginning with 01'
    title: Experiment ID
    from_schema: Experiment
    rank: 1000
    domain_of:
    - Experiment
    range: string
    required: true
  project_id:
    name: project_id
    description: 'Project ID must be included in the Experiment-level metadata in
      order to link all experiments to the main project.

      The project to which the submitted data belong. A unique project identifier
      that can be used to link project data across data submissions, and link baseline
      data to intervention data, for example.

      If no Project ID has been assigned, one may be generated by combining the following
      fields, as described in Cross-linking Data Sets with Common Identifiers.

      Any method that creates a unique ID that will link all project data (e.g., a
      project''s baseline data to intervention data, and various data submissions
      within an experiment type) is acceptable.'
    title: Project ID
    from_schema: Experiment
    domain_of:
    - OAEProject
    - Experiment
    range: string
  experiment_type:
    name: experiment_type
    description: The type of mCDR experiment conducted. See Controlled Vocabularies
      section for definitions.
    title: mCDR Experiment Type
    from_schema: Experiment
    rank: 1000
    domain_of:
    - Experiment
    range: ExperimentType
    required: true
  investigators:
    name: investigators
    description: 'Provide details for each investigator including: Name, institutional
      information (name, address), phone, email, ID type (e.g., ORCID, etc), researcher
      ID, and role.'
    title: Investigators
    from_schema: Experiment
    rank: 1000
    domain_of:
    - Experiment
    range: Investigator
    required: true
    multivalued: true
    inlined: true
    inlined_as_list: true
  start_datetime:
    name: start_datetime
    description: Start date and time of experiment in UTC ISO-8601
    title: Start Date and Time
    from_schema: Experiment
    rank: 1000
    domain_of:
    - Experiment
    range: datetime
    required: true
  end_datetime:
    name: end_datetime
    description: End date and time of experiment in UTC ISO-8601
    title: End Date and Time
    from_schema: Experiment
    rank: 1000
    domain_of:
    - Experiment
    range: datetime
    required: true
  data_conflicts_and_unreported_data:
    name: data_conflicts_and_unreported_data
    description: If data exist that are or have been used by the project but are not
      provided due to conflicts (e.g., geopolitical or other), data availability (e.g.,
      a dataset is no longer available), it may be noted here.
    title: Data Conflicts and Unreported Data
    from_schema: Experiment
    rank: 1000
    domain_of:
    - Experiment
    range: string
  meteorological_and_tidal_data:
    name: meteorological_and_tidal_data
    description: Include links to relevant open datasets if referenced in the experiment
      but not provided in the submission.
    title: Meteorological and Tidal Data
    from_schema: Experiment
    rank: 1000
    domain_of:
    - Experiment
    range: NamedLink
    multivalued: true
    inlined: true
    inlined_as_list: true
  additional_details:
    name: additional_details
    description: Open text area to include additional information. These may include
      information for sediment processes data, biological data, or any other required
      information if not included in the main metadata or data files; see General
      Guidelines for Your Data for relevant sections of your data. Additional informational
      files, such as digitized laboratory notebooks, blogs, etc., may be linked here.
    title: Additional Details
    from_schema: Experiment
    domain_of:
    - OAEProject
    - Experiment
    range: string

Induced

name: Experiment
description: Experiment metadata applies to a specific study but remains consistent
  across datasets.
from_schema: OAEDataManagementProtocol
slot_usage:
  description:
    name: description
    description: A narrative description of the experiment. For example, what part
      of the project do these data represent (e.g., baseline, intervention, control)
      and what do they contribute to the overall project? Are all project research
      questions listed in Project description relevant? What were the processes to
      achieve these goals and answer these questions? Data submitters are encouraged
      to note any significant changes to the original experimental plan due to unforeseen
      circumstances here.
    title: Experiment Description
    required: true
  spatial_coverage:
    name: spatial_coverage
    description: Latitude/longitude bounds of observed data in experiment, provided
      in decimal degrees as westernmost longitude, southernmost latitude, easternmost
      longitude, northernmost latitude. [S, W, N, E]
    required: true
  vertical_coverage:
    name: vertical_coverage
    description: Minimum and maximum depths of observations in meters.
    required: true
attributes:
  experiment_id:
    name: experiment_id
    description: 'The experiment to which the data belong. Any naming convention that
      produces a unique ID is usable. The recommended naming convention is:

      Project ID + Experiment type + Optional numerical indicator to differentiate
      between various experiments of the same type for a project. A two digit consecutive
      number beginning with 01'
    title: Experiment ID
    from_schema: Experiment
    rank: 1000
    alias: experiment_id
    owner: Experiment
    domain_of:
    - Experiment
    range: string
    required: true
  project_id:
    name: project_id
    description: 'Project ID must be included in the Experiment-level metadata in
      order to link all experiments to the main project.

      The project to which the submitted data belong. A unique project identifier
      that can be used to link project data across data submissions, and link baseline
      data to intervention data, for example.

      If no Project ID has been assigned, one may be generated by combining the following
      fields, as described in Cross-linking Data Sets with Common Identifiers.

      Any method that creates a unique ID that will link all project data (e.g., a
      project''s baseline data to intervention data, and various data submissions
      within an experiment type) is acceptable.'
    title: Project ID
    from_schema: Experiment
    alias: project_id
    owner: Experiment
    domain_of:
    - OAEProject
    - Experiment
    range: string
  experiment_type:
    name: experiment_type
    description: The type of mCDR experiment conducted. See Controlled Vocabularies
      section for definitions.
    title: mCDR Experiment Type
    from_schema: Experiment
    rank: 1000
    alias: experiment_type
    owner: Experiment
    domain_of:
    - Experiment
    range: ExperimentType
    required: true
  investigators:
    name: investigators
    description: 'Provide details for each investigator including: Name, institutional
      information (name, address), phone, email, ID type (e.g., ORCID, etc), researcher
      ID, and role.'
    title: Investigators
    from_schema: Experiment
    rank: 1000
    alias: investigators
    owner: Experiment
    domain_of:
    - Experiment
    range: Investigator
    required: true
    multivalued: true
    inlined: true
    inlined_as_list: true
  start_datetime:
    name: start_datetime
    description: Start date and time of experiment in UTC ISO-8601
    title: Start Date and Time
    from_schema: Experiment
    rank: 1000
    alias: start_datetime
    owner: Experiment
    domain_of:
    - Experiment
    range: datetime
    required: true
  end_datetime:
    name: end_datetime
    description: End date and time of experiment in UTC ISO-8601
    title: End Date and Time
    from_schema: Experiment
    rank: 1000
    alias: end_datetime
    owner: Experiment
    domain_of:
    - Experiment
    range: datetime
    required: true
  data_conflicts_and_unreported_data:
    name: data_conflicts_and_unreported_data
    description: If data exist that are or have been used by the project but are not
      provided due to conflicts (e.g., geopolitical or other), data availability (e.g.,
      a dataset is no longer available), it may be noted here.
    title: Data Conflicts and Unreported Data
    from_schema: Experiment
    rank: 1000
    alias: data_conflicts_and_unreported_data
    owner: Experiment
    domain_of:
    - Experiment
    range: string
  meteorological_and_tidal_data:
    name: meteorological_and_tidal_data
    description: Include links to relevant open datasets if referenced in the experiment
      but not provided in the submission.
    title: Meteorological and Tidal Data
    from_schema: Experiment
    rank: 1000
    alias: meteorological_and_tidal_data
    owner: Experiment
    domain_of:
    - Experiment
    range: NamedLink
    multivalued: true
    inlined: true
    inlined_as_list: true
  additional_details:
    name: additional_details
    description: Open text area to include additional information. These may include
      information for sediment processes data, biological data, or any other required
      information if not included in the main metadata or data files; see General
      Guidelines for Your Data for relevant sections of your data. Additional informational
      files, such as digitized laboratory notebooks, blogs, etc., may be linked here.
    title: Additional Details
    from_schema: Experiment
    alias: additional_details
    owner: Experiment
    domain_of:
    - OAEProject
    - Experiment
    range: string
  name:
    name: name
    description: A human-readable name for the thing.
    title: Name
    from_schema: OAEDataManagementProtocol
    rank: 1000
    alias: name
    owner: Experiment
    domain_of:
    - Organization
    - NamedLink
    - ExternalProject
    - MonetaryGrant
    - Experiment
    - Investigator
    range: string
  description:
    name: description
    description: A narrative description of the experiment. For example, what part
      of the project do these data represent (e.g., baseline, intervention, control)
      and what do they contribute to the overall project? Are all project research
      questions listed in Project description relevant? What were the processes to
      achieve these goals and answer these questions? Data submitters are encouraged
      to note any significant changes to the original experimental plan due to unforeseen
      circumstances here.
    title: Experiment Description
    from_schema: OAEDataManagementProtocol
    rank: 1000
    alias: description
    owner: Experiment
    domain_of:
    - ExternalProject
    - Experiment
    range: string
    required: true
  spatial_coverage:
    name: spatial_coverage
    description: Latitude/longitude bounds of observed data in experiment, provided
      in decimal degrees as westernmost longitude, southernmost latitude, easternmost
      longitude, northernmost latitude. [S, W, N, E]
    title: Spatial Coverage
    from_schema: OAEDataManagementProtocol
    rank: 1000
    slot_uri: schema:spatialCoverage
    alias: spatial_coverage
    owner: Experiment
    domain_of:
    - OAEProject
    - ExternalProject
    - Experiment
    range: Place
    required: true
  vertical_coverage:
    name: vertical_coverage
    description: Minimum and maximum depths of observations in meters.
    title: Vertical Coverage
    from_schema: OAEDataManagementProtocol
    rank: 1000
    alias: vertical_coverage
    owner: Experiment
    domain_of:
    - OAEProject
    - Experiment
    range: VerticalExtent
    required: true