Skip to content

Submitting an Event

Documenting a harmful algal event requires high scientific detail. The modernized HAEDAT interface organizes this data into six functional tabs.

The Required Checklist Figure: The submission checklist highlighting the required fields that must be completed before publication.

1. General Information

This tab establishes the identity and core nature of the event.

  • Event Year & Country (*): Mandatory fields. The Event ID (e.g., FR-25-001) is generated automatically based on these selections once the event is saved.
  • Nature of the Event (*): Select at least one core characteristic (e.g., Seafood Toxin, Mass Mortality).
  • Resources Affected (*): Select the biological or human resources impacted.
  • Permissions: Note that you can only submit events for the country assigned to your user profile.

2. Location & Date

Establishing "Where" and "When" is critical for the global mapping system.

  • HAB Area Code (Grid) (*): You must select at least one administrative grid. This allows the system to map the event even if exact coordinates are missing.
  • Coordinates: Provide decimal Latitude and Longitude if known.
  • The Timeline:
    • Event Date: The primary date used for archival.
    • Bloom & Quarantine Dates: Specific ranges for the biological event and the management response.
    • Date Unknown Toggle: If specific dates are unavailable, use this toggle and provide context in the "Additional Date Info" field (e.g., "Summer 2025").

3. Microalgae (Biology)

This section documents the organisms using the WoRMS Accepted Species workflow.

  • WoRMS Accepted Species Rows: Click + Add WoRMS Accepted Species Row to add a causative or co-occurring organism.
  • Live WoRMS Search: When you type a name, the system searches accepted WoRMS taxa. If the selected accepted taxon is not yet stored locally, HAEDAT creates the local canonical record when you save the event.
  • HAB Context: Species shown in event details can also display a HAB Listed label when the selected accepted taxon appears in the local HAB reference snapshot.
  • Concentrations: Record the maximum Cells/L observed for each causative or co-occurring species row.

4. Environment

Detailed environmental data helps researchers understand the conditions that lead to blooms.

  • Physical Conditions: Record weather, wind direction/velocity, and current details.
  • Water Chemistry: Input data for Temperature, Salinity, and Dissolved Oxygen.
  • Nutrients: A dedicated sub-section for Ammonium, Nitrate, Phosphate, and Silicate. Please ensure you include the units (e.g., µmol/L).

5. Toxin Assays

This tab links the biological event to chemical evidence.

  • Toxin Synchronization: When adding a row, the Specific Toxin dropdown is populated from the official HAIS Toxins Database.
  • Assay Details: Record the species containing the toxin, the assay method (e.g., HPLC, ELISA), and the maximum concentration detected.
  • Management & Economics (*): You must specify if a management action was taken (e.g., harvesting ban) and if economic losses occurred. Select "Unknown" or "None" if applicable to satisfy validation.

Toxin Assay Rows Figure: The toxin assay section where synchronized toxin rows can be added to an event record.

6. Contacts

Identify the scientists or authorities responsible for the data.

  • Search Directory: By default, this searches contacts within your country. Toggle "Global Directory" to search the entire HAEDAT network.
  • Inline Creation: If a contact is not in the system, click "+ Create New Contact" to add them immediately without leaving the form.

The Lifecycle of an Event

Events in HAEDAT V2 follow a streamlined workflow:

  1. Draft: The initial state. Only visible to you. Use this while gathering data.
  2. Submitted (Published): Once you click "Publish" from your dashboard, the event becomes live and visible to the public.
  3. Under Review: If a regional editor or admin requests corrections, the event returns to this state.
  4. Archived: Used for historical records that have been superseded.

Important Note: Editing a Published event will temporarily revert it to Draft status until you re-submit it. This ensures that partially edited data is not visible to the public.