1) 
What does this data set describe? 
Title: Depth-integrated midwater pollock biomass summary from echo integration-trawl survey of walleye pollock (Theragra chalcogramma) on the U.S. and Russian Bering Sea shelf in June and July 2008
Abstract:  Midwater walleye pollock biomass is measured during annual or biennial acoustic-trawl surveys conducted by the Midwater Assessment and Conservation Engineering (MACE) Program, Resource Assessment and Conservation Engineering (RACE) Division, of the NOAA-NMFS Alaska Fisheries Science Center (AFSC).  In 2008, the survey was conducted from 2 June to 31 July using the NOAA Ship Oscar Dyson.  Acoustic backscatter at 38 kHz was measured along north-south survey transects spaced at an east-west distance of 20 nautical miles (nmi); backscatter was classified through visual examination of the data by trained analysts.  Midwater and bottom trawling was used to determine the species and length frequency composition of detected aggregations of fish.  Pollock biomass (kg) was computed by applying length-specific target strength values and a length-weight relationship to 38 kHz backscatter data classified as pollock.  The summary data set submitted here includes pollock biomass values summed between 16 m below the sea surface and 3 m above the seafloor within a rectangle with a north-south distance of 0.5 nmi (averaging distance along the survey transect) and an east-west distance of 20 nmi (interpolation distance 10 nmi to either side of the survey transect).  The latitude, longitude, and vessel log distance values represent the starting location for each interval along the transect.  The sum of biomass in all of these intervals will yield the sum total midwater pollock biomass measured by the survey.  Further information and detail on the midwater pollock survey data can be found by consulting Honkelehto et al. 2009 or by contacting the author of this data set.
Purpose:  The purpose of the submitted data set is to provide a spatially explicit estimate of midwater pollock biomass for use according to the BEST-BSIERP data policy.  Those with a need for more detail should contact the Author of the data set.
a) How should this data set be cited?
Author:  Ressler, P.H.
Publication Date:  unpublished
Publication Information: (if publisher is different from the author, if a paper was published about the dataset use the journal name as the Publisher)
	Publisher:
	Publisher location:
	Series name (if any):
	Issue (if Series is used):
Online Linkages [URLs] to supporting documents:
This data set as submitted to the database is unpublished.  Use and citation of these data must conform to the BEST-BSIERP data policy (http://bsierp.nprb.org/posted/proj_mgmt/Final%20NPRB-NSF%20program%20management%20plan%202007%2012_21.pdf) and standard scientific practice.  The following is a publication about the data that describes the methods used to generate them and the survey analysis completed using the same source data:
HONKALEHTO, T., N. WILLIAMSON, D. JONES, A. McCARTHY, and D. McKELVEY. 2009. Results of the echo integration-trawl survey of walleye pollock (Theragra chalcogramma) on the U.S. and Russian Bering Sea shelf in June and July 2008. U. S. Dep. Commer., NOAA Tech. Memo., NMFS-AFSC-194, 56 p. (.pdf, 2 MB). 
URL: http://www.afsc.noaa.gov/Publications/AFSC-TM/NOAA-TM-AFSC-194.pdf

b) What geographic area does the data set cover? 
Bounding coordinates: (What bounding box of the dataset? Please use negative numbers for degrees West longitude, positive numbers for degrees East longitude, positive numbers for degrees North latitude and negative numbers for degrees South)
Eastern Bering Sea shelf
Longitude: [-180 -160]
Latitude:  [54 63]

c) What does it look like?
Optionally, include any URLs to graphics or supply example graphics with this metadata record.

http://ak.aoos.org/data/archive/2009/0000014/data/pollock_2008.gif

d) Does the data set describe conditions during a particular time period?
Time Period of Content: (Generally a start and end date/time of the dataset).  Please use the GMT timezone). 
2 June and 31 July 2008
Currentness Reference: (Ex: The dates/times of the dataset refer to CTD casts, bottom grab times, bird observation time, referred time/date being described in Local Traditional Knowledge testimony)
Start and end dates of the survey.
e) What is the general form of this data set?
Data Presentation Form: digital, paper, samples.  (In most cases, the answer is digital form)
Digital (.csv formatted file)
f) How does the data set represent geographic features? 
Direct Spatial Reference Method: (Single word description of spatial references in the dataset. Can be one of Point, Vector or Raster. Ex: XBT/CTD casts may be considered Point locations, cruise track lines are composed of connected points (to form Lines/Vectors) and Raster is typically used for gridded datasets (model output, satellite, etc). If the dataset does not strictly conform to any of these types, provide an Indirect Spatial Reference instead.)
Point
Indirect Spatial Reference: (Use this area to describe how to spatially define this dataset if it cannot be defined by a typical method above)
g) How does the data set describe geographic features? 
How are the features defined?  Is it stored in a particular format? (e.g., CSV, Excel, database)
CSV
Within these data or file formats, how is the information defined?  What are the columns or variable names used?  What are the units for each column?
For each column or variable, describe:
	Name: variable or column name
	Units: if applicable
	Valid Range: valid range of values or enumerated list
	Missing value: if a value is missing, how is that shown in the dataset?
Column 1:
	Name: Longitude
	Units: degrees west of prime meridian (west is negative)
	Valid Range: [-360 0]
	Missing value: missing or invalid values are indicated by ‘NaN’
Column 2:
	Name: Latitude
	Units: degrees north of equator
	Valid Range: [0 90]
	Missing value: missing or invalid values are indicated by ‘NaN’
Column 3:
	Name: Pollock biomass 
	Units: kg
	Valid Range: [0 +inf]
	Missing value: missing or invalid values are indicated by ‘NaN’
Column 4:
	Name: Vessel log number (distance along survey track)
	Units: nautical miles
	Valid Range: [0 +inf]
	Missing value: missing or invalid values are indicated by ‘NaN’
Each pollock biomass value is a sum between 16 m below the sea surface and 3 m above the seafloor within a rectangle with a north-south distance of 0.5 nmi (averaging distance along the survey transect) and an east-west distance of 20 nmi (interpolation distance 10 nmi to either side of a survey transect).  The latitude, longitude, and vessel log distance values represent the starting location for each interval along the transect.  The sum of biomass in all of these intervals will yield the sum total midwater pollock biomass measured by the survey.  

2) Who produced the data set?
a) Who are the originators of the data set?
Author: (repeated above, may skip, included for completeness)
This digital file was created for submission to the database by Ressler, Patrick H.
b) Who also contributed to the data set? 
Data Set Credit: Recognition of those who contributed to the data set.
These data came from a survey conducted by the Midwater Assessment Program (MACE) of the Resource Assessment and Conservation Engineering Division (RACE) of the NOAA National Marine Fisheries Service Alaska Fisheries Science Center (AFSC).  A citation of the NOAA Technical Memorandum describing the survey data collection, analysis, and results is as follows:
HONKALEHTO, T., N. WILLIAMSON, D. JONES, A. McCARTHY, and D. McKELVEY. 2009. Results of the echo integration-trawl survey of walleye pollock (Theragra chalcogramma) on the U.S. and Russian Bering Sea shelf in June and July 2008. U. S. Dep. Commer., NOAA Tech. Memo., NMFS-AFSC-194, 56 p. (.pdf, 2 MB). 
URL: http://www.afsc.noaa.gov/Publications/AFSC-TM/NOAA-TM-AFSC-194.pdf
c) To whom should users address questions about the data? 
Point of Contact: for this dataset Name, Organization, Phone, Email, etc.
Patrick H. Ressler, Ph.D.
NOAA Fisheries
AFSC-RACE, Midwater Assessment and Conservation Engineering
7600 Sand Point Way NE
Seattle, WA  98115
Phone:  206-526-4785
Email:  Patrick.Ressler@noaa.gov
3) Why was the data set created? 
   Purpose: (repeated from above, may skip) Why were the data collected?
   These data come from a regular stock assessment survey of midwater walleye pollock in the eastern Bering Sea.  The digital data file described here was created for submission to the BEST-BSIERP program database.
4) How was the data set created? 
a) What methods were used to collect the data? 
See the following references for survey methodology:
HONKALEHTO, T., N. WILLIAMSON, D. JONES, A. McCARTHY, and D. McKELVEY. 2009. Results of the echo integration-trawl survey of walleye pollock (Theragra chalcogramma) on the U.S. and Russian Bering Sea shelf in June and July 2008. U. S. Dep. Commer., NOAA Tech. Memo., NMFS-AFSC-194, 56 p. (.pdf, 2 MB). 
URL: http://www.afsc.noaa.gov/Publications/AFSC-TM/NOAA-TM-AFSC-194.pdf
HONKALEHTO, T., N. WILLIAMSON, and S. De BLOIS. 2002. Echo integration-trawl survey results for walleye pollock (Theragra chalcogramma) on the Bering Sea shelf and slope during the summer 1999. U.S. Dep. Commer., NOAA Tech. Memo. NMFS-AFSC-125, 77 p. (.pdf, 5.74mb) 
URL: http://www.afsc.noaa.gov/Publications/AFSC-TM/NOAA-TM-AFSC-125.pdf

Methodology:
b) From what previous works were the data drawn?
Source Information: 
See Honkalehto et al. 2009.
c) How were the data generated, processed, and modified?
Process Steps: 
d) What similar or related data should the user be aware of?
Optionally, indicate information about other, related data sets that are likely to be of interest; or papers using this data set. 
--The NOAA AFSC bottom trawl survey estimates pollock biomass within 3 m of the seafloor.  For 2008 see http://www.afsc.noaa.gov/Quarterly/jas2008/divrptsRACE1.htm  A formal report of the 2008 bottom trawl survey is not yet available.  For a formal report of the 2007 bottom trawl survey, see 
ACUNA, E., and R. R. LAUTH 2008. Results of the 2007 Eastern Bering Sea continental shelf bottom trawl survey of groundfish and invertebrate resources. U. S. Dep. Commer., NOAA Tech. Memo., NMFS-AFSC-181, 195 p. (.pdf, 7.15MB). 
URL: http://www.afsc.noaa.gov/Publications/AFSC-TM/NOAA-TM-AFSC-181.pdf
--Eastern Bering Sea walleye pollock stock assessment documents, which model the annual status of the pollock stock using these and other data sets, can be found at http://www.afsc.noaa.gov/refm/stocks/assessments.htm.  The reference and URL for the 2008 stock assessment is 
Ianelli, J. N., Barbeaux, S., Honkalehto, T., Kotwicki, S., Aydin, K., and Williamson, N. 2008. Assessment of the Walleye Pollock stock in the Eastern Bering Sea.  In:  Stock assessment and fishery evaluation report for the groundfish resources of the Bering Sea/Aleutian Islands regions. North Pacific Fishery Management Council, Anchorage, AK, section 1: 47-136. http://www.afsc.noaa.gov/refm/docs/2008/EBSpollock.pdf
5) How reliable are the data; what problems remain in the data set? 
a) How well have the observations been checked? 
Data Accuracy Report: (FGDC calls this Attribute Accuracy Report.) Explanation of the accuracy of the identification of columns/variables and assignment of values in the data set. The report can reference more extensive descriptions in other documents.  (e.g. Calibration sheets, etc.  Are there accuracy considerations that need to be stated about any of the particular data columns that might show up in subsequent quality control checks that might be explained by instrument or equipment changes or quirks)
The data are very reliable and have been checked many times for accuracy.  No problems remain.  
b) How accurate are the geographic locations? 
Horizontal Positional Accuracy Report: Explanation of the accuracy of the horizontal coordinate measurements (e.g. GPS location) and a description of the tests used.
Geographic position is determined using differential GPS.
c) How accurate are the heights or depths?
Vertical Positional Accuracy Report: Explanation of the accuracy of the vertical coordinate measurements and a description of the tests used.
These are depth-integrated measurements.  Each value is a sum between 16 m below the sea surface and 3 m above the seafloor within a rectangle with a north-south distance of 0.5 nmi (distance along the survey transect) and an east-west distance of 20 nmi (10 nmi to either side of a survey transect).  The latitude, longitude, and vessel log distance values represent the along-track starting location for each interval.  
d) Where are the gaps in the data? What is missing?
Logical Consistency Report: Explanation of the fidelity of relationships in the dataset and tests used. (e.g. What gross quality control checks were done to ensure data integrity? Example:  Data and/or locations seem correct upon visual inspection when plotted on graphs/maps.  A large data gap exists due to the elimination of data based on such and such a test). The report can reference more extensive descriptions in other documents. If creating a Logical Consistency Report is not logical, use the default "not applicable".
See Honkalehto et al. 2009.
e) How consistent are the relationships among the data, including topology?
Completeness Report: Information about omissions, selection criteria, generalizations, definitions used, and other rules used to derive the data set. The report can reference more extensive descriptions in other documents.
See Honkalehto et al. 2009.
6) How can someone get a copy of the data set? 
a) Are there legal restrictions on access or use of the data? 
Access Constraints: Restrictions on accessing or obtaining the data set.
Use Constraints: Restrictions on using the data set after access is granted.
This data set as submitted is unpublished.  Use and citation of these data must conform to the BEST-BSIERP data policy (http://bsierp.nprb.org/posted/proj_mgmt/Final%20NPRB-NSF%20program%20management%20plan%202007%2012_21.pdf) and standard scientific practice.  Users should contact the author of the data set to ensure proper interpretation and use of these data.
b) Who distributes the data? 
This is the contact information for the dataset, if different from the Author, should data management get a question about the dataset we cannot answer.
c) What's the catalog number I need to order this data set?
Optional, if the dataset has a unique identifier.
d) What legal disclaimers am I supposed to read?
Distribution Liability: What legal disclaimers is the user suppose to read? 
e) How can I download or order the data? 
If there is a way to download or order the data than having to use the contact information above, include that information here.
7) Who wrote the metadata? 
Metadata Author: (If different from the Author of the dataset.)
8) What other elements are required by BSIERP data management?
Status: (Status of the dataset.  Is it in a completed form or is more information expected later, are updates expected if errors are found or corrections made?)

Dataset is complete.  If errors are found or corrections must be made, an updated file will be submitted.
9) Taxonomy (if applicable) 
Common name:  walleye pollock
Scientific name:  Theragra chalcogramma
To include taxonomy in metadata records using this form we request a text file with a listing of scientific names.  A separate file is needed for each kingdom.  To make things easier, please use the kingdom name as part of the filename.

Example: Filename = Plantae.txt

name
Acer saccharum
Acer nigrum
Acer barbatum
Nyssa sylvatica
Liriodendron tulipifera
Fraxinus americana
Juglans nigra
Quercus alba
Quercus coccinea
Quercus velutina
Quercus rubra

Using these files, we will use the ITIS Tools page to convert the above scientific names to SGML/XML that we import to the FGDC metadata record to list taxonomy.   You may use this tool in advance to check and quality control your taxonomic information.   Please consult these ITIS web pages:

ITIS Tools: http://www.itis.gov/taxmatch_ftp.html

ITIS Web Page: http://www.itis.gov/

If you have specific scientific disputes or questions with information in the ITIS database please take it up with them.  We currently do not have the resources to affect changes to the ITIS database.