BCO-DMO ERDDAP
Accessing BCO-DMO data
log in    
Brought to you by BCO-DMO    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  DNA microsatellite alleles for hatchery-produced oyster cohorts   RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_769969)
Information:  Summary ? | License ? | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 STUDY (unitless) ?              
 POPULATION (unitless) ?              
 SAMPLE_ID (unitless) ?              
 Cvi4313E_a (bp (base pairs)) ?          0    282
 Cvi4313E_b (bp (base pairs)) ?          0    335
 RUCV73_a (bp (base pairs)) ?          0    477
 RUCV73_b (bp (base pairs)) ?          0    481
 RUCV74_a (bp (base pairs)) ?          0    168
 RUCV74_b (bp (base pairs)) ?          0    171
 Cvi1i24b_a (bp (base pairs)) ?          0    157
 Cvi1i24b_b (bp (base pairs)) ?          0    157
 Cvi2i23_a (bp (base pairs)) ?          0    479
 Cvi2i23_b (bp (base pairs)) ?          0    510
 RUCV1_a (bp (base pairs)) ?          0    213
 RUCV1_b (bp (base pairs)) ?          0    241
 Cvi11_a (bp (base pairs)) ?          0    155
 Cvi11_b (bp (base pairs)) ?          0    155
 RUCV66_a (bp (base pairs)) ?          0    332
 RUCV66_b (bp (base pairs)) ?          0    338
 Cvi9_a (bp (base pairs)) ?          95    140
 Cvi9_b (bp (base pairs)) ?          98    157
 Cvi13_a (bp (base pairs)) ?          0    299
 Cvi13_b (bp (base pairs)) ?          0    304
 Cvi2k14_a (bp (base pairs)) ?          206    212
 Cvi2k14_b (bp (base pairs)) ?          206    224
 Cvi2j24_a (bp (base pairs)) ?          0    421
 Cvi2j24_b (bp (base pairs)) ?          0    421
 
Server-side Functions ?
 distinct() ?
? (" ")

File type: (more info)

(Documentation / Bypass this form ? )
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  STUDY {
    String description "unique identifier for the 3 components of this dataset";
    String ioos_category "Unknown";
    String long_name "STUDY";
    String units "unitless";
  }
  POPULATION {
    String description "unique identifier for the site/populations sampled";
    String ioos_category "Unknown";
    String long_name "POPULATION";
    String units "unitless";
  }
  SAMPLE_ID {
    String description "unique identifier for each individual in this dataset";
    String ioos_category "Identifier";
    String long_name "SAMPLE ID";
    String units "unitless";
  }
  Cvi4313E_a {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 282;
    String description "allele 1 for locus Cvi4313E";
    String ioos_category "Unknown";
    String long_name "Cvi4313 E A";
    String units "bp (base pairs)";
  }
  Cvi4313E_b {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 335;
    String description "allele 2 for locus Cvi4313E";
    String ioos_category "Unknown";
    String long_name "Cvi4313 E B";
    String units "bp (base pairs)";
  }
  RUCV73_a {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 477;
    String description "allele 1 for locus RUCV73";
    String ioos_category "Unknown";
    String long_name "RUCV73 A";
    String units "bp (base pairs)";
  }
  RUCV73_b {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 481;
    String description "allele 2 for locus RUCV73";
    String ioos_category "Unknown";
    String long_name "RUCV73 B";
    String units "bp (base pairs)";
  }
  RUCV74_a {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 168;
    String description "allele 1 for locus RUCV74";
    String ioos_category "Unknown";
    String long_name "RUCV74 A";
    String units "bp (base pairs)";
  }
  RUCV74_b {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 171;
    String description "allele 2 for locus RUCV74";
    String ioos_category "Unknown";
    String long_name "RUCV74 B";
    String units "bp (base pairs)";
  }
  Cvi1i24b_a {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 157;
    String description "allele 1 for locus Cvi1i24b";
    String ioos_category "Unknown";
    String long_name "Cvi1i24b A";
    String units "bp (base pairs)";
  }
  Cvi1i24b_b {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 157;
    String description "allele 2 for locus Cvi1i24b";
    String ioos_category "Unknown";
    String long_name "Cvi1i24b B";
    String units "bp (base pairs)";
  }
  Cvi2i23_a {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 479;
    String description "allele 1 for locus Cvi2i23";
    String ioos_category "Unknown";
    String long_name "Cvi2i23 A";
    String units "bp (base pairs)";
  }
  Cvi2i23_b {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 510;
    String description "allele 2 for locus Cvi2i23";
    String ioos_category "Unknown";
    String long_name "Cvi2i23 B";
    String units "bp (base pairs)";
  }
  RUCV1_a {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 213;
    String description "allele 1 for locus RUCV1";
    String ioos_category "Unknown";
    String long_name "RUCV1 A";
    String units "bp (base pairs)";
  }
  RUCV1_b {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 241;
    String description "allele 2 for locus RUCV1";
    String ioos_category "Unknown";
    String long_name "RUCV1 B";
    String units "bp (base pairs)";
  }
  Cvi11_a {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 155;
    String description "allele 1 for locus Cvi11";
    String ioos_category "Unknown";
    String long_name "Cvi11 A";
    String units "bp (base pairs)";
  }
  Cvi11_b {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 155;
    String description "allele 2 for locus Cvi11";
    String ioos_category "Unknown";
    String long_name "Cvi11 B";
    String units "bp (base pairs)";
  }
  RUCV66_a {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 332;
    String description "allele 1 for locus RUCV66";
    String ioos_category "Unknown";
    String long_name "RUCV66 A";
    String units "bp (base pairs)";
  }
  RUCV66_b {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 338;
    String description "allele 2 for locus RUCV66";
    String ioos_category "Unknown";
    String long_name "RUCV66 B";
    String units "bp (base pairs)";
  }
  Cvi9_a {
    Int16 _FillValue 32767;
    Int16 actual_range 95, 140;
    String description "allele 1 for locus Cvi9";
    String ioos_category "Unknown";
    String long_name "Cvi9 A";
    String units "bp (base pairs)";
  }
  Cvi9_b {
    Int16 _FillValue 32767;
    Int16 actual_range 98, 157;
    String description "allele 2 for locus Cvi9";
    String ioos_category "Unknown";
    String long_name "Cvi9 B";
    String units "bp (base pairs)";
  }
  Cvi13_a {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 299;
    String description "allele 1 for locus Cvi13";
    String ioos_category "Unknown";
    String long_name "Cvi13 A";
    String units "bp (base pairs)";
  }
  Cvi13_b {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 304;
    String description "allele 2 for locus Cvi13";
    String ioos_category "Unknown";
    String long_name "Cvi13 B";
    String units "bp (base pairs)";
  }
  Cvi2k14_a {
    Int16 _FillValue 32767;
    Int16 actual_range 206, 212;
    String description "allele 1 for locus Cvi2k14";
    String ioos_category "Unknown";
    String long_name "Cvi2k14 A";
    String units "bp (base pairs)";
  }
  Cvi2k14_b {
    Int16 _FillValue 32767;
    Int16 actual_range 206, 224;
    String description "allele 2 for locus Cvi2k14";
    String ioos_category "Unknown";
    String long_name "Cvi2k14 B";
    String units "bp (base pairs)";
  }
  Cvi2j24_a {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 421;
    String description "allele 1 for locus Cvi2j24";
    String ioos_category "Unknown";
    String long_name "Cvi2j24 A";
    String units "bp (base pairs)";
  }
  Cvi2j24_b {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 421;
    String description "allele 2 for locus Cvi2j24";
    String ioos_category "Unknown";
    String long_name "Cvi2j24 B";
    String units "bp (base pairs)";
  }
 }
  NC_GLOBAL {
    String access_formats ".htmlTable,.csv,.json,.mat,.nc,.tsv";
    String acquisition_description 
"In April 2012, we collected 100 adult oysters (80-100 mm shell length) from
3-5 separate reefs at each of 6 sites: St. Augustine, FL (FL-1; 30.0224,
-81.3287), Jacksonville, FL (FL-2; 30.4446, -81.4199), Sapelo Island, GA
(GA/SC-1; 31.4777, -81.2726), Ace Basin, SC (GA/SC-2; 32.4846, -80.6001),
Masonboro, NC (NC-1; 34.1510, -77.8551), and Middle Marsh, NC (NC-2; 34.6951,
-76.6183). They were held in flowing seawater tanks or suspended in cages from
docks in their home region for 2-3 weeks until 30 oysters from each site could
be tested and certified as disease free. The remaining 70 oysters were then
shipped on ice to a single hatchery facility in Florida (Research Aquaculture
Inc., Tequesta, FL; 26.9607, -80.0931) at the end of April.
 
The adult oysters from each site were used as the broodstock to produce 6
separate site-specific \\\"cohorts\\\" (one cohort per site). From their arrival
at the hatchery, the adult oysters were held for 2 weeks until they were ready
to spawn under the same conditions in separate flow-through seawater systems
to prevent cross-contamination. All families were manually spawned (i.e.,
strip spawned) on May 7 (see details below). Because the original FL-1 family
did not produce many offspring, the remaining broodstock oysters from this
site were spawned on June 1 using the same process. Due to variation in
ripeness and sex, the number of oysters spawned and the ratio of males to
females varied across broodstock (Table 1 of Hughes et al., 2019), though our
broodstock numbers for each cohort are comparable to those commonly used in
hatchery settings (30-60 individuals; Morvezen et al. 2016).
 
The broodstock oysters from each source site were strip spawned, sexed, and
fertilized on the same day by a team of 7 people, who each had a specific job
to perform: shucking the animals, sampling and preparing tissue for
microscopic analysis of sex, identifying the sex, stripping the male sperm,
stripping the female eggs, mixing the sperm and eggs after all of the animals
from a particular source were stripped, overseeing the process and keeping
track of broodstock source. We sanitized equipment between individuals and
again between broodstock sources. Stripping was done by broodstock source
independently and quickly so that the sperm and eggs would remain viable, and
all viable sperm and eggs were used. During the gamete mixing process, the
eggs from all females and the sperm from all males were first pre-mixed and
then combined to ensure equal access of gametes to one another. We allowed
30-60 minutes for fertilization; once 75-90% of the eggs were fertilized, they
were moved to larval tanks. All larvae were retained except for minimal
numbers of individuals in each cohort that did not grow or had improper
development. Larval culture occurred in 60-gallon conical tanks utilizing a
flow-through seawater system with Banjo screens that is commercially used in
multiple bivalve hatcheries (e.g., Taylor Shellfish in WA; Cherrystones in
VA).
 
Over a period of 3 days the week of May 28, oysters were sieved on a
250-micron sieve and settled on crushed oyster cultch in a recirculating flow-
through system. The week of June 11, once they reached 800 microns in size,
they were moved into a nursery facility compliant with state regulations,
again under flow-through seawater conditions (salinity = 32 ppt, temperature =
30\\u00baC). In the hatchery and nursery stages, the oysters were fed a mixed
diet of T. isochrysis, Chaetocerous gracilis, and Tetraselmis via a constantly
running peristaltic pump. Although growth was similar during the larval
culture phase, some cohorts produced more juvenile oysters (\\\"spat\\\") than
others during settlement, despite following the same procedures for all. To
maintain consistency in their growing conditions, we selected a random sample
of each cohort to yield similar total abundances across cohorts on June 18. At
the end of June (June 27) at approximately 4mm in size, the 6 cohorts were
transferred to a common flow-through facility at the Whitney Marine Biological
Laboratory in St. Augustine, FL. To assess genetic diversity within and
between oyster cohorts produced in the hatchery, 50 individuals were
haphazardly collected from each juvenile cohort prior to the start of the
field experiments and preserved at -80\\u1d52C for genetic analysis. This
sample size is sufficient to estimate allele frequencies accurately (Hale et
al. 2012).
 
To extract DNA, we ground each tissue sample with a pestle, and used the
tissue centrifugation protocol from the Omega Bio-Tek E-Z 96 Tissue DNA Kit.
We determined genetic diversity and population structure using 12 highly
variable microsatellite loci developed for C. virginica: Cvi9, Cvi11, and
Cvi13 from Brown et al. (2000); Cvi1i24b, Cvi2i23, Cvi2j24, and Cvi2k14 from
Reece et al. (2004); Cvi4313E-VIMS from Carlsson and Reece (2007); and RUCV1,
RUCV66, RUCV73, and RUCV74 from Wang and Guo (2007). We amplified four loci in
each multiplexed polymerase chain reaction (PCR) using the Qiagen Type-It
Microsatellite PCR Kit. Each 10 l reaction consisted of 1 l DNA template, 5 l
2X type-it multiplex master mix (Qiagen), 2.4 l water, and 0.2 l each 10 M
primer. Using a T100 thermal cycler (Bio-Rad), PCR cycling conditions included
initial activation/denaturation at 95\\u1d52C for 5 min, followed by 28 cycles
of 95\\u1d52C for 30 sec, 60\\u1d52C for 90 sec, and 72\\u1d52C for 30 sec, and
final extension at 60\\u1d52C for 30 min. PCR products were separated on a
3730xl Genetic Analyzer (Applied Biosystems) with the internal size standard
GeneScan 500 LIZ (Applied Biosystems), and fragment analysis was performed
using GeneMarker version 2.6 (SoftGenetics).
 
We created panels for each multiplexed reaction in GeneMarker, which included
bins that were assigned manually for all alleles; the same panels were used to
score all samples, and the alignment of the panels was checked prior to each
analysis to account for any run-to-run variation and to identify any new
alleles. We used these panels to do a preliminary first assignment of alleles
based on peak position and bin position, but every sample was then scored
manually for all loci to examine signal intensity, to confirm the
presence/absence of alleles, and to identify any reruns. A subset of samples
was then rerun (at least 15% per multiplex PCR reaction) and manually scored
again to confirm any uncertain allele calls and account for any genotyping
error.";
    String awards_0_award_nid "709941";
    String awards_0_award_number "OCE-1652320";
    String awards_0_data_url "http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=1652320";
    String awards_0_funder_name "NSF Division of Ocean Sciences";
    String awards_0_funding_acronym "NSF OCE";
    String awards_0_funding_source_nid "355";
    String awards_0_program_manager "Dr Michael E. Sieracki";
    String awards_0_program_manager_nid "50446";
    String cdm_data_type "Other";
    String comment 
"Oyster Cohort Genetics 
  PI: Randall Hughes 
  Version date: 06-June-2019";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_type "institution";
    String creator_url "https://www.bco-dmo.org/";
    String data_source "extract_data_as_tsv version 2.2d  13 Jun 2019";
    String date_created "2019-06-06T18:01:48Z";
    String date_modified "2019-06-11T18:39:33Z";
    String defaultDataQuery "&time";
    String doi "10.1575/1912/bco-dmo.769969.1";
    String history 
"2019-11-14T00:47:04Z (local files)
2019-11-14T00:47:04Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_769969.html";
    String infoUrl "https://www.bco-dmo.org/dataset/769969";
    String institution "BCO-DMO";
    String instruments_0_acronym "Automated Sequencer";
    String instruments_0_dataset_instrument_nid "770021";
    String instruments_0_description "General term for a laboratory instrument used for deciphering the order of bases in a strand of DNA. Sanger sequencers detect fluorescence from different dyes that are used to identify the A, C, G, and T extension reactions. Contemporary or Pyrosequencer methods are based on detecting the activity of DNA polymerase (a DNA synthesizing enzyme) with another chemoluminescent enzyme. Essentially, the method allows sequencing of a single strand of DNA by synthesizing the complementary strand along it, one base pair at a time, and detecting which base was actually added at each step.";
    String instruments_0_instrument_name "Automated DNA Sequencer";
    String instruments_0_instrument_nid "649";
    String instruments_0_supplied_name "3730xl Genetic Analyzer (Applied Biosystems)";
    String instruments_1_acronym "Thermal Cycler";
    String instruments_1_dataset_instrument_nid "770020";
    String instruments_1_description 
"General term for a laboratory apparatus commonly used for performing polymerase chain reaction (PCR). The device has a thermal block with holes where tubes with the PCR reaction mixtures can be inserted. The cycler then raises and lowers the temperature of the block in discrete, pre-programmed steps.

(adapted from http://serc.carleton.edu/microbelife/research_methods/genomics/pcr.html)";
    String instruments_1_instrument_name "PCR Thermal Cycler";
    String instruments_1_instrument_nid "471582";
    String instruments_1_supplied_name "T100 thermal cycler (Bio-Rad)";
    String keywords "bco, bco-dmo, biological, chemical, cvi11, Cvi11_a, Cvi11_b, cvi13, Cvi13_a, Cvi13_b, cvi1i24b, Cvi1i24b_a, Cvi1i24b_b, cvi2i23, Cvi2i23_a, Cvi2i23_b, cvi2j24, Cvi2j24_a, Cvi2j24_b, cvi2k14, Cvi2k14_a, Cvi2k14_b, cvi4313, Cvi4313E_a, Cvi4313E_b, cvi9, Cvi9_a, Cvi9_b, data, dataset, dmo, erddap, identifier, management, oceanography, office, population, preliminary, rucv1, RUCV1_a, RUCV1_b, rucv66, RUCV66_a, RUCV66_b, rucv73, RUCV73_a, RUCV73_b, rucv74, RUCV74_a, RUCV74_b, sample, SAMPLE_ID, study";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    String metadata_source "https://www.bco-dmo.org/api/dataset/769969";
    String param_mapping "{'769969': {}}";
    String parameter_source "https://www.bco-dmo.org/mapserver/dataset/769969/parameters";
    String people_0_affiliation "Northeastern University";
    String people_0_affiliation_acronym "NEU";
    String people_0_person_name "A. Randall Hughes";
    String people_0_person_nid "522929";
    String people_0_role "Principal Investigator";
    String people_0_role_type "originator";
    String people_1_affiliation "Woods Hole Oceanographic Institution";
    String people_1_affiliation_acronym "WHOI BCO-DMO";
    String people_1_person_name "Shannon Rauch";
    String people_1_person_nid "51498";
    String people_1_role "Data Manager";
    String people_1_role_type "related";
    String project "CAREER: Linking genetic diversity, population density, and disease prevalence in seagrass and oyster ecosystems";
    String projects_0_acronym "Seagrass and Oyster Ecosystems";
    String projects_0_description 
"NSF Award Abstract:
Disease outbreaks in the ocean are increasing, causing losses of ecologically important marine species, but the factors contributing to these outbreaks are not well understood. This 5-year CAREER project will study disease prevalence and intensity in two marine foundation species - the seagrass Zostera marina and the Eastern oyster Crassostrea virginica. More specifically, host-disease relationships will be explored to understand how genetic diversity and population density of the host species impacts disease transmission and risk. This work will pair large-scale experimental restorations and smaller-scale field experiments to examine disease-host relationships across multiple spatial scales. Comparisons of patterns and mechanisms across the two coastal systems will provide an important first step towards identifying generalities in the diversity-density-disease relationship. To enhance the broader impacts and utility of this work, the experiments will be conducted in collaboration with restoration practitioners and guided by knowledge ascertained from key stakeholder groups. The project will support the development of an early career female researcher and multiple graduate and undergraduate students. Students will be trained in state-of-the-art molecular techniques to quantify oyster and seagrass parasites. Key findings from the surveys and experimental work will be incorporated into undergraduate courses focused on Conservation Biology, Marine Biology, and Disease Ecology. Finally, students in these courses will help develop social-ecological surveys and mutual learning games to stimulate knowledge transfer with stakeholders through a series of workshops.
The relationship between host genetic diversity and disease dynamics is complex. In some cases, known as a dilution effect, diversity reduces disease transmission and risk. However, the opposite relationship, known as the amplification effect, can also occur when diversity increases the risk of infection. Even if diversity directly reduces disease risk, simultaneous positive effects of diversity on host density could lead to amplification by increasing disease transmission between infected and uninfected individuals. Large-scale field restorations of seagrasses (Zostera marina) and oysters (Crassostrea virginica) will be utilized to test the effects of host genetic diversity on host population density and disease prevalence/intensity. Additional field experiments independently manipulating host genetic diversity and density will examine the mechanisms leading to dilution or amplification. Conducting similar manipulations in two marine foundation species - one a clonal plant and the other a non-clonal animal - will help identify commonalities in the diversity-density-disease relationship. Further, collaborations among project scientists, students, and stakeholders will enhance interdisciplinary training and help facilitate the exchange of information to improve management and restoration efforts. As part of these efforts, targeted surveys will be used to document the perceptions and attitudes of managers and restoration practitioners regarding genetic diversity and its role in ecological resilience and restoration.";
    String projects_0_end_date "2022-01";
    String projects_0_geolocation "Coastal New England";
    String projects_0_name "CAREER: Linking genetic diversity, population density, and disease prevalence in seagrass and oyster ecosystems";
    String projects_0_project_nid "709942";
    String projects_0_start_date "2017-02";
    String publisher_role "BCO-DMO Data Manager(s)";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary "DNA microsatellite alleles for hatchery-produced oyster cohorts.";
    String title "DNA microsatellite alleles for hatchery-produced oyster cohorts";
    String version "1";
    String xml_source "osprey2erddap.update_xml() v1.5-beta";
  }
}

 

Using tabledap to Request Data and Graphs from Tabular Datasets

tabledap lets you request a data subset, a graph, or a map from a tabular dataset (for example, buoy data), via a specially formed URL. tabledap uses the OPeNDAP (external link) Data Access Protocol (DAP) (external link) and its selection constraints (external link).

The URL specifies what you want: the dataset, a description of the graph or the subset of the data, and the file type for the response.

Tabledap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/pmelTaoDySst.htmlTable?longitude,latitude,time,station,wmo_platform_code,T_25&time>=2015-05-23T12:00:00Z&time<=2015-05-31T12:00:00Z
Thus, the query is often a comma-separated list of desired variable names, followed by a collection of constraints (e.g., variable<value), each preceded by '&' (which is interpreted as "AND").

For details, see the tabledap Documentation.


 
ERDDAP, Version 1.82
Disclaimers | Privacy Policy | Contact