Provide detailed information about the hydrophone deployment configuration and station location. Accurate metadata ensures proper data provenance and reproducibility of acoustic analyses.
Deployment ID
Deployment Date/Time (UTC)
Scheduled Recovery Date/Time (UTC)
Latitude (decimal degrees)
Longitude (decimal degrees)
Water Depth at Site (meters)
Hydrophone Depth (meters)
Distance to Nearest Commercial Shipping Lane (meters)
Is deployment location within 500 meters of a commercial shipping lane?
Average Daily Vessel Traffic Count
Sea State (Beaufort Scale)
0 - Calm
1 - Light Air
2 - Light Breeze
3 - Gentle Breeze
4 - Moderate Breeze
5 - Fresh Breeze
6 - Strong Breeze
7 - Near Gale
8 - Gale
9 - Strong Gale
10 - Storm
11 - Violent Storm
12 - Hurricane
Weather Conditions
Deployment Platform Type
Fixed Mooring
Drifting Buoy
Research Vessel
Autonomous Underwater Vehicle (AUV)
Remotely Operated Vehicle (ROV)
Cabled Observatory
Other
Record critical oceanographic parameters that affect sound propagation, including temperature, salinity, and water chemistry. These variables directly influence acoustic absorption coefficients and transmission loss calculations.
Water Salinity (PPT)
Water Temperature (°C)
pH Level
Dissolved Oxygen (mg/L)
Turbidity (NTU)
Rate the following environmental conditions at time of deployment
Very Low | Low | Moderate | High | Very High | |
|---|---|---|---|---|---|
Surface Current Speed | |||||
Thermocline Stability | |||||
Biological Activity Level | |||||
Anthropogenic Background Noise |
Is a distinct thermocline present?
Thermocline Depth (meters)
Tide Stage at Deployment
Document all technical specifications and calibration status of the hydrophone system. Proper equipment configuration is essential for accurate source level estimation and distance calculations.
Hydrophone Model
SoundTrap ST300
SoundTrap ST600
Ocean Sonics icListen
Seiche Subsea Digital Hydrophone
Other
Hydrophone Serial Number
Sampling Rate (kHz)
Frequency Response Range (Hz to kHz)
Preamplifier Gain (dB)
High-Pass Filter Cutoff (Hz)
Low-Pass Filter Cutoff (kHz)
Last Calibration Date
Upload Calibration Certificate
Battery Voltage at Deployment (V)
Data Storage Capacity Available (GB)
Is anti-fouling protection applied?
Describe anti-fouling method and expected duration of effectiveness
Log all significant acoustic detections. The system automatically calculates estimated distance to source using the passive sonar equation accounting for spherical spreading loss and frequency-dependent chemical absorption. Check the proximity alert box if the calculated distance is less than 500 meters.
Acoustic Detections Table
Timestamp (UTC) | Peak Frequency (kHz) | Received Level (dB re 1μPa) | Visual Match | Estimated Distance to Source (m) | Proximity Alert (<500m) | Follow-up Notes | Audio Clip File | ||
|---|---|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | G | H | ||
1 | 6/30/2025, 2:23 PM | 0.025 | 145 | Blue Whale | 56.09 | ||||
2 | 6/30/2025, 3:47 PM | 2.5 | 165 | Orca | 5.08 | ||||
3 | 6/30/2025, 4:12 PM | 0.05 | 180 | Submarine Noise | 1 | ||||
4 | 0 | ||||||||
5 | 0 | ||||||||
6 | 0 | ||||||||
7 | 0 | ||||||||
8 | 0 | ||||||||
9 | 0 | ||||||||
10 | 0 |
Were any detections manually verified through spectrogram analysis?
Describe verification methodology and confidence level
Document any visual observations that correlate with acoustic detections. Visual validation significantly increases confidence in species identification and behavioral interpretation.
Were visual sightings of marine mammals made during the monitoring period?
Provide species, count, behavior, and time of visual observation
Acoustic Detection Rate (detections per hour)
Behavioral context observed (select all that apply)
Feeding
Socializing
Traveling
Resting
Breeding
Vocalizing
Surface Active
Mother-Calf Interaction
None Observed
Estimated Group Size
Mother-calf pairs detected acoustically?
Describe acoustic characteristics supporting mother-calf identification
Upload supporting photographs or video screenshots
Identify and characterize all human-generated noise sources that could interfere with biological signal detection or pose acoustic habitat degradation risks.
Vessel noise detected during monitoring period?
Describe vessel type, estimated distance, engine type, and activity pattern
Active sonar signals detected?
Document frequency range, pulse characteristics, duty cycle, and estimated source level
Construction or industrial activity audible?
Specify activity type and estimated distance from hydrophone
Seismic survey activity detected?
Document airgun signatures, shot interval, and received levels
Aircraft overflight noise recorded?
Aircraft type and altitude if known
Noise mitigation measures implemented (select all that apply)
Speed restrictions
Route deviation
Time-area closures
Sound source reduction
No mitigation applied
Not applicable
Evaluate the quality and completeness of the acoustic dataset. Identify any technical issues, data gaps, or interference that could affect analysis validity.
Overall Signal Quality Rating (1=Poor, 5=Excellent)
Rate noise interference level for each frequency band
0.01-0.1 kHz (Infrasonic) | |
0.1-1 kHz (Low) | |
1-10 kHz (Mid) | |
10-50 kHz (High) | |
50+ kHz (Ultra-high) |
Data gaps or interruptions present?
Specify gap duration, timestamps, and suspected cause
Equipment malfunctions or anomalies detected?
Describe malfunction, affected data segments, and resolution actions
Data processing steps completed (select all that apply)
High-pass filtering
Spectrogram generation
Automated detection algorithm
Manual verification
Source level calculation
Noise floor analysis
Data archiving
Primary Analyst Name
Analysis Completion Date
Ensure all monitoring activities comply with marine mammal protection protocols and data sharing agreements. Document any sensitive detections requiring special handling.
Marine mammal mitigation protocols active during deployment?
Specify protocol type and any shutdown events triggered
Upload relevant regulatory permits or authorizations
Data sharing restrictions
No restrictions - public domain
Embargoed until publication
Sensitive species - restricted access
Proprietary - institutional only
Government classified
Endangered or protected species detected?
Specify species and required reporting actions
Provide a comprehensive summary of findings, identify key patterns, and outline recommended actions for future deployments or immediate conservation interventions.
Key Findings Summary
Recommendations for Future Monitoring
Follow-up Actions Required
Immediate vessel traffic management
Extended monitoring period
Species-specific behavioral study
Noise pollution assessment
No further action needed
Additional Comments or Contextual Information
Analyst Digital Signature
Report Finalization Date
Analysis for Oceanographic Bio-Acoustic Log Form
Important Note: This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes. Please remove this content before publishing the form to the public.
The Oceanographic Bio-Acoustic Log Form demonstrates exceptional sophistication in its comprehensive approach to underwater acoustic monitoring. The form successfully integrates critical environmental metadata, equipment specifications, and real-time detection logging with automated calculations, creating a robust framework for marine bio-acoustic research. Its strength lies in the meticulous attention to data provenance and scientific reproducibility, essential for peer-reviewed research and regulatory compliance.
From a user experience perspective, the form's logical section progression—from deployment metadata through environmental conditions to detection logging and final validation—creates an intuitive workflow that mirrors the actual fieldwork process. The inclusion of contextual paragraphs explaining the scientific rationale behind each section enhances usability for both novice and experienced researchers, reducing errors and improving data quality. However, the form's complexity may present challenges for rapid field deployment scenarios where time is limited.
Purpose of the Question: The Deployment ID serves as the primary unique identifier for the entire acoustic monitoring event, functioning as the cornerstone of data management and provenance. In oceanographic research, where datasets may span decades and involve multiple institutions, a standardized, descriptive identifier enables seamless data retrieval, cross-referencing with other studies, and integration into larger meta-analyses. This field ensures that every acoustic detection, environmental measurement, and equipment parameter can be definitively traced back to its source deployment.
Effective Design & Strengths: The placeholder example "NEP25-BC-001" demonstrates a well-structured naming convention that likely encodes region, year, platform type, and sequence number. This systematic approach facilitates automated database management and sorting. Making this field mandatory is a critical design choice that prevents orphaned records and ensures data integrity across the entire research infrastructure. The single-line text format appropriately constrains input length while allowing flexibility for various institutional naming schemes.
Data Collection Implications: The Deployment ID creates a persistent link between field operations and post-processing analysis, enabling robust version control and audit trails. This is particularly crucial when acoustic data informs regulatory decisions or conservation policy, as it allows stakeholders to verify data authenticity and methodology. The unique identifier also supports proper citation in scientific publications, enhancing research transparency and reproducibility.
User Experience Considerations: While the field is mandatory, its placement at the very beginning of the form leverages the fresh attention of users, reducing the likelihood of omission. The clear placeholder format reduces cognitive load by providing an immediate template. For field teams working across multiple deployments, this systematic approach minimizes confusion and prevents duplicate or ambiguous identifiers that could compromise entire datasets.
Purpose of the Question: These temporal anchors establish the exact observation window for the acoustic monitoring period, which is fundamental for all subsequent time-series analysis and event correlation. In bio-acoustic research, marine mammal vocalizations and anthropogenic noise sources exhibit strong diel, tidal, and seasonal patterns. Precise UTC timing ensures that detections can be synchronized with other datasets (satellite telemetry, visual surveys, vessel traffic data) and accounts for operations across different time zones, eliminating ambiguity that could arise from local time conventions.
Effective Design & Strengths: Using UTC as the standardized time reference demonstrates scientific rigor and international best practices, preventing errors during data sharing between institutions in different time zones. The mandatory nature of both deployment and recovery times ensures complete temporal coverage documentation, allowing calculation of exact deployment duration and detection rates per hour. This completeness is vital for comparative studies and meta-analyses where sampling effort must be normalized across different studies.
Data Collection Implications: These timestamps enable precise calculation of acoustic detection rates and support rigorous statistical analysis of temporal patterns. They also facilitate correlation with external databases such as AIS vessel traffic, weather buoy data, and lunar cycles. The data quality is enhanced by eliminating timezone conversion errors, which are a common source of data corruption in multi-institutional research programs.
User Experience Considerations: The datetime picker interface (implied by the field type) reduces input errors compared to manual text entry, while enforcing UTC standardization. Making both fields mandatory ensures researchers consciously define their sampling period, preventing open-ended deployments that could complicate data management. The clear labeling with "(UTC)" serves as a constant reminder of the required format, reducing the need for data cleaning later.
Purpose of the Question: These geographic coordinates provide the essential spatial context for every acoustic detection, enabling habitat modeling, species distribution mapping, and assessment of anthropogenic threats. In marine conservation, precise location data is critical for identifying critical habitats, migration corridors, and areas of high biological significance. The coordinates also determine proximity to shipping lanes, protected areas, and other spatially-explicit management zones, directly supporting regulatory compliance and conservation planning.
Effective Design & Strengths: Requiring decimal degree format ensures compatibility with GIS systems and spatial databases, facilitating seamless integration with other georeferenced datasets. The mandatory status reflects the fundamental principle that acoustic data without location metadata has severely limited scientific value. The placeholder examples with appropriate precision (4 decimal places ≈ 10 meters) guide users toward the required accuracy level without explicit instructions, reducing input variability.
Data Collection Implications: High-quality geospatial data enables sophisticated spatial analyses including kernel density estimation of species presence, acoustic habitat modeling, and assessment of noise pollution gradients. The coordinates also support automated quality control checks, such as verifying that the location falls within expected marine boundaries or identifying potential coordinate transposition errors (e.g., longitude values outside -180 to +180 range).
User Experience Considerations: For field deployments using GPS-equipped vessels or platforms, these coordinates can be auto-populated or copied from navigation systems, reducing manual entry burden. The mandatory requirement ensures that location data collection becomes a non-negotiable step in the deployment protocol, preventing the common problem of "data without location" that plagues legacy datasets. Clear decimal degree format avoids confusion with degree-minute-second notation.
Purpose of the Question: These depth parameters are critical for acoustic propagation modeling and understanding the vertical distribution of both sound sources and receivers. Water depth determines the potential for multi-path propagation, bottom interactions, and waveguide effects that significantly influence detection ranges. Hydrophone depth is equally crucial as it determines the thermal and pressure environment of the sensor and affects which water column layers are being monitored, particularly important in stratified water columns with distinct thermoclines.
Effective Design & Strengths: Making both depth measurements mandatory ensures that transmission loss calculations—which rely on accurate bathymetric and deployment geometry data—can be properly computed. The form's design acknowledges that these parameters are not merely descriptive but are active inputs to the automated distance estimation formula. The numeric field type with appropriate placeholders guides users toward realistic values, preventing entry of nonsensical data.
Data Collection Implications: These depth measurements directly impact the accuracy of the estimated distance to source calculation, which is a central feature of this form. Inaccurate depth data would propagate errors through the entire localization algorithm, compromising the scientific validity of all range estimates. The data also supports habitat characterization, as different species prefer different depth zones, and anthropogenic noise sources vary with depth (e.g., surface vessels vs. submerged infrastructure).
User Experience Considerations: For teams using echosounders or CTD profilers, these values can be directly transferred from digital readouts, minimizing estimation errors. The mandatory status ensures that deployment teams take the time to accurately measure and record these critical parameters rather than estimating them roughly. The clear unit specification "(meters)" eliminates ambiguity and prevents unit conversion errors that could introduce systematic biases into the dataset.
Purpose of the Question: Salinity is a fundamental parameter in the sonar equation that directly affects chemical sound absorption in seawater. The absorption coefficient varies significantly with salinity, temperature, and frequency, influencing how far sound propagates and thus how distance to source is calculated. For accurate bio-acoustic monitoring, especially in coastal areas where salinity can vary dramatically due to river outflows or ice melt, this parameter is essential for correcting propagation models and avoiding systematic underestimation or overestimation of source distances.
Effective Design & Strengths: The mandatory status of this field demonstrates scientific rigor, recognizing that salinity is not an optional environmental note but a required input for quantitative acoustic analysis. The placeholder "32.5" represents a typical oceanic value that guides users toward realistic entries, while the numeric field type prevents text-based entries that would break calculation formulas. The unit specification "(PPT)" is unambiguous and aligns with oceanographic standards.
Data Collection Implications: Salinity data, combined with temperature, allows calculation of sound speed profiles which determine acoustic ray paths and detection zones. This directly affects the quality of distance estimates and the ability to distinguish between distant loud sources and nearby quiet sources. The data also supports broader oceanographic research, as salinity patterns influence marine mammal distribution and prey availability, providing valuable context for interpreting acoustic detections.
User Experience Considerations: Modern CTD instruments provide digital salinity readings that can be directly entered, reducing manual calculation errors. The mandatory requirement ensures researchers prioritize this measurement during pre-deployment site characterization, preventing the common oversight of collecting acoustic data without the supporting oceanographic parameters needed for proper interpretation. The field's prominence in the Environmental Parameters section emphasizes its importance.
Purpose of the Question: The hydrophone model determines the frequency response characteristics, sensitivity, and calibration parameters that are essential for accurate source level estimation. Different hydrophone models have varying self-noise levels, frequency ranges, and directional responses that directly impact what signals can be detected and how received levels should be interpreted. This information is fundamental for normalizing data across different deployments and comparing results between studies using different equipment.
Effective Design & Strengths: The single-choice format with specific commercial models (SoundTrap ST300, ST600, Ocean Sonics icListen, etc.) plus an "Other" option provides both standardization and flexibility. Making this field mandatory prevents the common problem of archived data lacking equipment specifications, which renders the data unusable for quantitative comparisons. The predefined options also facilitate database queries and meta-analyses across multiple deployments.
Data Collection Implications: The hydrophone model directly affects the detection threshold and frequency range of the monitoring system, influencing which species can be detected and how reliably. This metadata is essential for calculating absolute source levels from received levels, as the conversion requires knowledge of the hydrophone's sensitivity. The data also supports equipment performance tracking, helping institutions identify which models provide the best cost-effectiveness for specific research applications.
User Experience Considerations: The single-choice format is faster and more accurate than manual text entry, reducing typographical variations (e.g., "SoundTrap" vs "Sound Trap" vs "ST300"). The mandatory status ensures that equipment documentation becomes a standard part of deployment procedures, not an afterthought. For institutions with standardized equipment pools, this field could potentially be auto-populated based on serial number lookup, further streamlining the workflow.
Purpose of the Question: The sampling rate determines the Nyquist frequency (half the sampling rate), which sets the maximum frequency that can be reliably detected without aliasing. This parameter fundamentally defines the scope of the bio-acoustic investigation—whether the study can detect ultrasonic porpoise clicks (100+ kHz) or is limited to low-frequency baleen whale calls (<20 Hz). The sampling rate also affects data file sizes, battery consumption, and storage requirements, making it a critical planning parameter.
Effective Design & Strengths: The mandatory numeric field with placeholder "96" (a common ecological sampling rate) guides users toward appropriate values. The unit specification "(kHz)" is clear and prevents confusion with Hz. Making this field mandatory ensures that researchers explicitly document their sampling strategy, which is essential for interpreting negative results (e.g., no porpoise detections could be due to insufficient sampling rate rather than true absence).
Data Collection Implications: The sampling rate directly impacts the frequency range available for analysis and determines which species vocalizations can be captured. This parameter is crucial for data quality assessment, as undersampling can lead to aliasing artifacts that corrupt the entire dataset. The data also supports meta-analyses of detection probabilities across studies with different technical capabilities, allowing researchers to account for methodological differences when comparing results.
User Experience Considerations: The numeric field format allows direct entry from instrument configuration settings, reducing transcription errors. The mandatory requirement ensures that this fundamental parameter is not overlooked during deployment preparation, preventing the costly mistake of deploying equipment with inappropriate settings. Clear unit labeling avoids the serious error of entering Hz values when kHz is expected, which would represent a 1000-fold difference.
Purpose of the Question: These fields establish accountability and temporal context for the data interpretation process, which is fundamental to scientific transparency and peer review. The analyst name provides a point of contact for questions about methodology, species identification decisions, and data quality judgments. The completion date documents when the interpretation was performed, which is important for understanding the state of knowledge at the time of analysis and for tracking any subsequent re-analysis or updates.
Effective Design & Strengths: Making both fields mandatory in the Data Quality Assessment section ensures that every dataset has clear attribution and timestamping before finalization. This design supports data governance policies and facilitates proper citation in publications. The single-line text format for the name allows for proper academic attribution (e.g., "Dr. Sarah Chen"), while the date field provides unambiguous temporal documentation.
Data Collection Implications: Analyst attribution is critical for data quality control, as different observers may have varying expertise levels or interpretation biases. The completion date helps track analysis turnaround times and can identify potential bottlenecks in research workflows. This metadata is essential for long-term data archiving, as it allows future researchers to understand the analytical context and potentially contact the original analyst for clarification on specific decisions.
User Experience Considerations: The mandatory status reinforces professional responsibility and prevents anonymous data submission, which is important for quality assurance. The placement near the end of the form ensures that the analyst has reviewed all preceding data before signing off, creating a natural workflow for final verification. The clear labeling encourages proper attribution rather than generic entries like "lab team" or "field staff."
Purpose of the Feature: The integrated formula column for "Estimated Distance to Source" represents a sophisticated approach to real-time data analysis, applying the passive sonar equation to automatically calculate source distances based on received level and peak frequency. This feature transforms the form from a simple data entry tool into an analytical platform that provides immediate actionable intelligence about the proximity of marine mammals or anthropogenic noise sources.
Effective Design & Strengths: The formula's incorporation of both geometric spreading loss and frequency-dependent chemical absorption demonstrates advanced acoustic modeling capabilities typically found only in specialized software. The automatic proximity alert checkbox (<500m) provides an immediate visual warning system for potential conservation concerns or safety issues. The table structure with predefined columns ensures standardized data collection across all detections, facilitating subsequent statistical analysis and pattern recognition.
Data Collection Implications: Automated calculations reduce the potential for human mathematical errors and provide immediate feedback that can inform field decisions. The distance estimates, while simplified, provide sufficient accuracy for management applications such as triggering mitigation measures when animals approach within critical distances of construction activities. The table format with file upload capability for audio clips creates a comprehensive detection record that links acoustic metrics with raw data verification.
User Experience Considerations: The table's pre-populated example rows demonstrate the expected data format and help users understand how to complete entries. The automatic calculation eliminates tedious manual computations, allowing researchers to focus on detection validation and interpretation. The proximity alert checkbox serves as an intuitive risk indicator, making it immediately obvious when a detection requires urgent attention or follow-up action.
Mandatory Question Analysis for Oceanographic Bio-Acoustic Log Form
Important Note: This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes. Please remove this content before publishing the form to the public.
Question: Deployment ID
Justification: The Deployment ID is absolutely essential as the primary key for data management and provenance in oceanographic research. This unique identifier enables unambiguous data retrieval, linking of acoustic detections to specific hardware configurations and environmental conditions, and integration across multi-year research programs. Without a standardized ID, datasets become orphaned and irreproducible, compromising scientific integrity and regulatory compliance. Mandatory enforcement ensures institutional database compatibility and supports proper citation in peer-reviewed publications.
Question: Deployment Date/Time (UTC) and Scheduled Recovery Date/Time (UTC)
Justification: These temporal parameters establish the fundamental observation window for all acoustic monitoring activities, enabling precise calculation of detection rates and temporal pattern analysis. UTC standardization eliminates timezone ambiguity critical for multi-institutional collaborations and international data sharing. The mandatory requirement ensures complete temporal documentation, preventing data gaps and enabling rigorous correlation with external datasets such as vessel traffic, weather events, and lunar cycles. This temporal anchoring is non-negotiable for time-series analysis and meta-analytical studies.
Question: Latitude and Longitude (decimal degrees)
Justification: Geographic coordinates provide the essential spatial foundation for all bio-acoustic interpretation, enabling habitat modeling, species distribution mapping, and proximity-based risk assessment. Decimal degree format ensures seamless GIS integration and spatial database compatibility. Mandatory collection prevents the creation of spatially ambiguous datasets that would be scientifically unusable for location-dependent analyses such as critical habitat identification, migration corridor mapping, and anthropogenic threat assessment. This spatial metadata is fundamental to meeting marine mammal protection regulatory requirements.
Question: Water Depth at Site and Hydrophone Depth (meters)
Justification: These depth parameters are critical inputs to the sonar equation and acoustic propagation models that underpin distance estimation and source level calculations. Water depth determines potential multi-path propagation and boundary interactions, while hydrophone depth defines the thermal environment and detection layer of the water column. Mandatory collection ensures that transmission loss calculations can be properly validated and that detection ranges can be accurately estimated. Without precise depth data, the automated distance calculation feature would produce unreliable estimates, compromising the scientific validity of all localization results.
Question: Water Salinity (PPT)
Justification: Salinity is a mandatory parameter because it directly affects chemical sound absorption coefficients in the sonar equation, with significant impact on acoustic propagation and distance estimation accuracy. In coastal and estuarine environments where salinity varies dramatically, this parameter is essential for correcting propagation models and avoiding systematic errors in source localization. The mandatory status reflects its role as a required input for quantitative acoustic analysis rather than optional environmental context. Without accurate salinity data, the estimated distances to biological and anthropogenic sources could be systematically biased, leading to flawed conservation decisions.
Question: Hydrophone Model
Justification: The hydrophone model is mandatory because it determines the frequency response, sensitivity, and self-noise characteristics that are fundamental to interpreting received levels and calculating source levels. Different models have varying capabilities that directly affect detection thresholds and species coverage, making this metadata essential for comparing results across studies and deployments. Without explicit model documentation, acoustic data cannot be properly calibrated or normalized, rendering quantitative comparisons scientifically invalid. This field ensures that equipment-specific performance characteristics are accounted for in all subsequent analyses.
Question: Sampling Rate (kHz)
Justification: Sampling rate is mandatory as it defines the Nyquist frequency and determines the maximum detectable frequency range, fundamentally constraining which species vocalizations can be captured and analyzed. This parameter directly affects data file sizes, storage requirements, and power consumption, making it critical for deployment planning and data management. The mandatory requirement ensures that researchers explicitly document their sampling strategy, enabling proper interpretation of negative results and supporting meta-analyses that account for methodological differences. Without this specification, the acoustic dataset's scope and limitations cannot be properly assessed.
Question: Primary Analyst Name and Analysis Completion Date
Justification: These fields are mandatory to ensure scientific accountability, data traceability, and proper attribution in research workflows. The analyst name provides a point of contact for methodological questions and supports quality control by linking interpretations to specific expertise levels. The completion date documents the analytical timeline, which is important for understanding the knowledge context and for tracking research productivity. Mandatory enforcement prevents anonymous data submission and supports institutional data governance policies, ensuring that every dataset has clear provenance and can be properly cited in publications.
To configure an element, select it on the form.