Skip to content

Commit

Permalink
callout box formats added
Browse files Browse the repository at this point in the history
  • Loading branch information
eshumchenia committed Oct 18, 2024
1 parent 2af434b commit 3891feb
Show file tree
Hide file tree
Showing 4 changed files with 54 additions and 17 deletions.
41 changes: 34 additions & 7 deletions _site/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -322,7 +322,7 @@ <h3 class="anchored" data-anchor-id="map">II. Add acoustic telemetry instrument
<i class="callout-icon no-icon"></i>
</div>
<div class="callout-title-container flex-fill">
Recommended Practice
Recommended Practices
</div>
</div>
<div class="callout-body-container callout-body">
Expand Down Expand Up @@ -357,21 +357,36 @@ <h3 class="anchored" data-anchor-id="participate">IV. Participate in Regional Te
<i class="callout-icon no-icon"></i>
</div>
<div class="callout-title-container flex-fill">
Recommended Practice
Recommended Practices
</div>
</div>
<div class="callout-body-container callout-body">
<p>Participate in the regional acoustic telemetry network for the study area (e.g., Atlantic Cooperative Telemetry Network (ACT), FACT Network, Ocean Tracking Network (OTN)).</p>
<ul>
<li><p>Participate in the regional acoustic telemetry network for the study area (e.g., Atlantic Cooperative Telemetry Network (ACT), FACT Network, Ocean Tracking Network (OTN)).</p></li>
<li><p>Project data and metadata submitted to regional telemetry networks should be set to “public”.</p></li>
</ul>
</div>
</div>
<p>Participation involves submitting all completed data products and metadata forms <a href="https://drive.google.com/drive/folders/1buFHbEu3Iy5YoVKUp9NULP2UNF78FcbQ">(templates provided by ACT)</a>. Visit the ACT Network’s Data Portal, MATOS (<a href="https://matos.asascience.com" class="uri">https://matos.asascience.com</a>), for the mid-Atlantic and Northeast U.S. or FACT (<a href="https://secoora.org/fact" class="uri">https://secoora.org/fact</a>) for the Southeast U.S. for more information including User Agreements.</p>
<p>Project data and metadata submitted to regional telemetry networks should be set to “public”.</p>
<p>Participation involves submitting all completed data products and metadata forms <a href="https://drive.google.com/drive/folders/1buFHbEu3Iy5YoVKUp9NULP2UNF78FcbQ">(templates provided by ACT)</a>.</p>
<p>Visit the ACT Network’s Data Portal, MATOS (<a href="https://matos.asascience.com" class="uri">https://matos.asascience.com</a>), for the mid-Atlantic and Northeast U.S. or FACT (<a href="https://secoora.org/fact" class="uri">https://secoora.org/fact</a>) for the Southeast U.S. for more information including User Agreements.</p>
<hr>
</section>
<section id="navy" class="level3">
<h3 class="anchored" data-anchor-id="navy">V. Navy awareness of acoustic telemetry receiver deployments on the Atlantic OCS</h3>
<p>The purpose of the following steps is to ensure that the US Navy is aware of and can provide feedback on the precise location of bottom-mounted acoustic monitoring equipment on the Atlantic OCS. The Navy is requesting that all individuals consider the following steps prior to deployment. Developers may be subject to additional requirements under the BOEM issued permits.</p>
<p>RWSC is coordinating with Beth Levy, Program Coordinator for the US Navy’s Ocean Observing Systems Situational Awareness Office (OOS SAO), so that the Navy may operate safely in the vicinity of deployed sensors. RWSC periodically shares data from the Research Planning Map directly with the Navy OOS SAO.</p>
<div class="callout callout-style-default callout-note no-icon callout-titled">
<div class="callout-header d-flex align-content-center">
<div class="callout-icon-container">
<i class="callout-icon no-icon"></i>
</div>
<div class="callout-title-container flex-fill">
Recommended Practice
</div>
</div>
<div class="callout-body-container callout-body">
<p>RWSC periodically shares data from the Research Planning Map directly with Beth Levy, Program Coordinator for the US Navy’s Ocean Observing Systems Situational Awareness Office (OOS SAO), so that the Navy may operate safely in the vicinity of deployed sensors.</p>
</div>
</div>
<p>Investigators may also email Beth Levy directly to share deployment plans for US Navy awareness: <a href="mailto:[email protected]">[email protected]</a></p>
<hr>
</section>
Expand Down Expand Up @@ -401,7 +416,19 @@ <h2 class="anchored" data-anchor-id="arv">3. Analysis &amp; Visualization</h2>
<section id="archive" class="level2">
<h2 class="anchored" data-anchor-id="archive">4. Archiving &amp; Access</h2>
<p>Raw data, metadata, and citations that are submitted to an Ocean Tracking Network OTN compatible regional networks (i.e., ACT or FACT) can also be transferred to global databases such as the <a href="https://www.usgs.gov/ocean-biodiversity-information-system-usa">Ocean Biodiversity Information System</a> (OBIS) and/or <a href="https://www.ncei.noaa.gov/">NOAA’s National Centers for Environmental Information</a> (NCEI) upon request.</p>
<p>Archiving data products through NCEI, OBIS, and other permanent archives will maintain the integrity of the data through standardized product delivery and make the data publicly accessible.</p>
<div class="callout callout-style-default callout-note no-icon callout-titled">
<div class="callout-header d-flex align-content-center">
<div class="callout-icon-container">
<i class="callout-icon no-icon"></i>
</div>
<div class="callout-title-container flex-fill">
Recommended Practice
</div>
</div>
<div class="callout-body-container callout-body">
<p>Archive data products through NCEI, OBIS, and other permanent archives to maintain the integrity of the data through standardized product delivery and to make the data publicly discoverable.</p>
</div>
</div>
<p>[to be populated with content from <em>Bowers, et al.&nbsp;in prep</em>]</p>
<hr>
</section>
Expand Down
4 changes: 2 additions & 2 deletions _site/search.json
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@
"href": "index.html#planning",
"title": "Acoustic Telemetry Data",
"section": "1. Planning & Coordination Steps",
"text": "1. Planning & Coordination Steps\nPlanning steps include pre-deployment coordination and communication best practices that help ensure that any new deployments are responsive to acoustic telemetry data gaps and needs in the region (to the extent practicable), and that individuals or entities responsible for deployments and data are connected to the existing network of experts and can benefit from lessons learned and other existing bodies of knowledge.\n\nI. Engage with the RWSC Protected Fish Species or Sea Turtle Subcommittees and Responsible Offshore Science Alliance\nGroups or individuals planning to deploy acoustic telemetry receivers and/or tag animals on the Atlantic OCS are encouraged to attend RWSC Subcommittee meetings to introduce their project, discuss their deployment plan with experts, and receive input on optimal location and other considerations (visit https://rwsc.org/events to view the Subcommittee meeting schedule).\n\n\n\nII. Add acoustic telemetry instrument metadata to the RWSC Research Planning Map\nIn collaboration with ACT, ROSA and the Subcommittees are maintaining an understanding of acoustic telemetry receivers deployed on the Atlantic OCS and periodically updating maps that show current deployments on the RWSC Research Planning Map.\nThe maps are developed from location and deployment information shared by principal investigators and ACT. The following best practices ensure that information about new and completed deployments is shared so that the maps maintain their accuracy and relevance.\n\n\n\n\n\n\nRecommended Practice\n\n\n\n\nShare any instrument metadata using the template provided by ACT.\nSend the completed Instrument Metadata form to [email protected] for inclusion in the Acoustic Telemetry Layer of the RWSC Research Planning Map.\n\n\n\nThe Research Planning Map and regional ocean data portals (https://www.northeastoceandata.org, https://portal.midatlanticocean.org) also contain data products that may assist funders and researchers in selecting locations for receiver deployment. For example, the Research Planning Map and Portals contain data products representing monthly and annual vessel traffic for several classes of vessels; commercial fishing activity; offshore wind planning and leasing areas; and bathymetry and seafloor composition information. The Subcommittees encourages users to examine these data to inform acoustic telemetry receiver deployment site selection.\n\n\n\nIII. Codeployment of other sensors\nIntroducing new instruments and moorings into the environment presents an opportunity to co-locate other sensors and equipment. For example, several active and planned PAM deployments include support for acoustic telemetry receiver devices. This type of co-deployment builds the receiver network for studies of other taxa such as sea turtles and highly migratory fish species, and is strongly encouraged.\nWhile the location of PAM instruments and moored PAM arrays may not represent ideal receiver locations needed to address research questions answered with acoustic telemetry for other taxa, RWSC and its partners encourage the deployment of multiple sensors per mooring, when practicable, while research questions and best practices for acoustic telemetry are under development.\nIn August 2022, the RWSC Sea Turtle Subcommittee recommended that acoustic telemetry receivers be included on each new PAM deployment as the RWSC Marine Mammal Subcommittee considers the design and implementation of a regional PAM network.\nThe locations of actively deployed PAM sensors on the Atlantic OCS can be viewed in the RWSC Research Planning Map. Clicking on each point will open a popup box that indicates whether an acoustic telemetry receiver is codeployed with the PAM hydrophone.\n\n\n\nMap showing current passive acoustic monitoring (PAM) for baleen whales deployments in U.S. Atlantic waters. The highlighted instrument location north of Georges Bank shows a codeployed VR2AR (acoustic receiver) and FPOD (sensor to detect dolphin clicks). View an interactive version of this map: https://rwsc.org/map/?link=c8XVYns3.\n\n\n\n\n\nIV. Participate in Regional Telemetry Networks and set project to “public”\n\n\n\n\n\n\nRecommended Practice\n\n\n\nParticipate in the regional acoustic telemetry network for the study area (e.g., Atlantic Cooperative Telemetry Network (ACT), FACT Network, Ocean Tracking Network (OTN)).\n\n\nParticipation involves submitting all completed data products and metadata forms (templates provided by ACT). Visit the ACT Network’s Data Portal, MATOS (https://matos.asascience.com), for the mid-Atlantic and Northeast U.S. or FACT (https://secoora.org/fact) for the Southeast U.S. for more information including User Agreements.\nProject data and metadata submitted to regional telemetry networks should be set to “public”.\n\n\n\nV. Navy awareness of acoustic telemetry receiver deployments on the Atlantic OCS\nThe purpose of the following steps is to ensure that the US Navy is aware of and can provide feedback on the precise location of bottom-mounted acoustic monitoring equipment on the Atlantic OCS. The Navy is requesting that all individuals consider the following steps prior to deployment. Developers may be subject to additional requirements under the BOEM issued permits.\nRWSC is coordinating with Beth Levy, Program Coordinator for the US Navy’s Ocean Observing Systems Situational Awareness Office (OOS SAO), so that the Navy may operate safely in the vicinity of deployed sensors. RWSC periodically shares data from the Research Planning Map directly with the Navy OOS SAO.\nInvestigators may also email Beth Levy directly to share deployment plans for US Navy awareness: [email protected]"
"text": "1. Planning & Coordination Steps\nPlanning steps include pre-deployment coordination and communication best practices that help ensure that any new deployments are responsive to acoustic telemetry data gaps and needs in the region (to the extent practicable), and that individuals or entities responsible for deployments and data are connected to the existing network of experts and can benefit from lessons learned and other existing bodies of knowledge.\n\nI. Engage with the RWSC Protected Fish Species or Sea Turtle Subcommittees and Responsible Offshore Science Alliance\nGroups or individuals planning to deploy acoustic telemetry receivers and/or tag animals on the Atlantic OCS are encouraged to attend RWSC Subcommittee meetings to introduce their project, discuss their deployment plan with experts, and receive input on optimal location and other considerations (visit https://rwsc.org/events to view the Subcommittee meeting schedule).\n\n\n\nII. Add acoustic telemetry instrument metadata to the RWSC Research Planning Map\nIn collaboration with ACT, ROSA and the Subcommittees are maintaining an understanding of acoustic telemetry receivers deployed on the Atlantic OCS and periodically updating maps that show current deployments on the RWSC Research Planning Map.\nThe maps are developed from location and deployment information shared by principal investigators and ACT. The following best practices ensure that information about new and completed deployments is shared so that the maps maintain their accuracy and relevance.\n\n\n\n\n\n\nRecommended Practices\n\n\n\n\nShare any instrument metadata using the template provided by ACT.\nSend the completed Instrument Metadata form to [email protected] for inclusion in the Acoustic Telemetry Layer of the RWSC Research Planning Map.\n\n\n\nThe Research Planning Map and regional ocean data portals (https://www.northeastoceandata.org, https://portal.midatlanticocean.org) also contain data products that may assist funders and researchers in selecting locations for receiver deployment. For example, the Research Planning Map and Portals contain data products representing monthly and annual vessel traffic for several classes of vessels; commercial fishing activity; offshore wind planning and leasing areas; and bathymetry and seafloor composition information. The Subcommittees encourages users to examine these data to inform acoustic telemetry receiver deployment site selection.\n\n\n\nIII. Codeployment of other sensors\nIntroducing new instruments and moorings into the environment presents an opportunity to co-locate other sensors and equipment. For example, several active and planned PAM deployments include support for acoustic telemetry receiver devices. This type of co-deployment builds the receiver network for studies of other taxa such as sea turtles and highly migratory fish species, and is strongly encouraged.\nWhile the location of PAM instruments and moored PAM arrays may not represent ideal receiver locations needed to address research questions answered with acoustic telemetry for other taxa, RWSC and its partners encourage the deployment of multiple sensors per mooring, when practicable, while research questions and best practices for acoustic telemetry are under development.\nIn August 2022, the RWSC Sea Turtle Subcommittee recommended that acoustic telemetry receivers be included on each new PAM deployment as the RWSC Marine Mammal Subcommittee considers the design and implementation of a regional PAM network.\nThe locations of actively deployed PAM sensors on the Atlantic OCS can be viewed in the RWSC Research Planning Map. Clicking on each point will open a popup box that indicates whether an acoustic telemetry receiver is codeployed with the PAM hydrophone.\n\n\n\nMap showing current passive acoustic monitoring (PAM) for baleen whales deployments in U.S. Atlantic waters. The highlighted instrument location north of Georges Bank shows a codeployed VR2AR (acoustic receiver) and FPOD (sensor to detect dolphin clicks). View an interactive version of this map: https://rwsc.org/map/?link=c8XVYns3.\n\n\n\n\n\nIV. Participate in Regional Telemetry Networks and set project to “public”\n\n\n\n\n\n\nRecommended Practices\n\n\n\n\nParticipate in the regional acoustic telemetry network for the study area (e.g., Atlantic Cooperative Telemetry Network (ACT), FACT Network, Ocean Tracking Network (OTN)).\nProject data and metadata submitted to regional telemetry networks should be set to “public”.\n\n\n\nParticipation involves submitting all completed data products and metadata forms (templates provided by ACT).\nVisit the ACT Network’s Data Portal, MATOS (https://matos.asascience.com), for the mid-Atlantic and Northeast U.S. or FACT (https://secoora.org/fact) for the Southeast U.S. for more information including User Agreements.\n\n\n\nV. Navy awareness of acoustic telemetry receiver deployments on the Atlantic OCS\nThe purpose of the following steps is to ensure that the US Navy is aware of and can provide feedback on the precise location of bottom-mounted acoustic monitoring equipment on the Atlantic OCS. The Navy is requesting that all individuals consider the following steps prior to deployment. Developers may be subject to additional requirements under the BOEM issued permits.\n\n\n\n\n\n\nRecommended Practice\n\n\n\nRWSC periodically shares data from the Research Planning Map directly with Beth Levy, Program Coordinator for the US Navy’s Ocean Observing Systems Situational Awareness Office (OOS SAO), so that the Navy may operate safely in the vicinity of deployed sensors.\n\n\nInvestigators may also email Beth Levy directly to share deployment plans for US Navy awareness: [email protected]"
},
{
"objectID": "index.html#deploy",
Expand All @@ -39,6 +39,6 @@
"href": "index.html#archive",
"title": "Acoustic Telemetry Data",
"section": "4. Archiving & Access",
"text": "4. Archiving & Access\nRaw data, metadata, and citations that are submitted to an Ocean Tracking Network OTN compatible regional networks (i.e., ACT or FACT) can also be transferred to global databases such as the Ocean Biodiversity Information System (OBIS) and/or NOAA’s National Centers for Environmental Information (NCEI) upon request.\nArchiving data products through NCEI, OBIS, and other permanent archives will maintain the integrity of the data through standardized product delivery and make the data publicly accessible.\n[to be populated with content from Bowers, et al. in prep]"
"text": "4. Archiving & Access\nRaw data, metadata, and citations that are submitted to an Ocean Tracking Network OTN compatible regional networks (i.e., ACT or FACT) can also be transferred to global databases such as the Ocean Biodiversity Information System (OBIS) and/or NOAA’s National Centers for Environmental Information (NCEI) upon request.\n\n\n\n\n\n\nRecommended Practice\n\n\n\nArchive data products through NCEI, OBIS, and other permanent archives to maintain the integrity of the data through standardized product delivery and to make the data publicly discoverable.\n\n\n[to be populated with content from Bowers, et al. in prep]"
}
]
2 changes: 1 addition & 1 deletion _site/sitemap.xml
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,6 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://rwscollab.github.io/at-data-mgmt/index.html</loc>
<lastmod>2024-10-18T13:23:50.854Z</lastmod>
<lastmod>2024-10-18T14:19:20.452Z</lastmod>
</url>
</urlset>
Loading

0 comments on commit 3891feb

Please sign in to comment.