Data Management Plan
GUID: gov.noaa.nmfs.inport:26571 | Published / External
Data Management Plan
DMP Template v2.0.1 (2015-01-01)
Please provide the following information, and submit to the NOAA DM Plan Repository.Reference to Master DM Plan (if applicable)
As stated in Section IV, Requirement 1.3, DM Plans may be hierarchical. If this DM Plan inherits provisions from a higher-level DM Plan already submitted to the Repository, then this more-specific Plan only needs to provide information that differs from what was provided in the Master DM Plan.
1. General Description of Data to be Managed
The trawl database contains multiple tables of data. The ‘haul’ table contains the location, date, time and depth of the trawl haul. The ‘catch’ table contains the numbers and weights of the taxa in each haul. The ‘length’ table contains the lengths of selected taxa in each haul. There is data for the eastern Bering Sea for 2008, 2010, 2012, and 2014. There is Gulf of Alaska trawl data from 1993 to 2015.
Notes: Only a maximum of 4000 characters will be included.
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Notes: All time frames from all extent groups are included.
Gulf of Alaska and Bering Sea
Notes: All geographic areas from all extent groups are included.
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
(e.g., satellite, airplane, unmanned aerial system, radar, weather station, moored buoy, research vessel, autonomous underwater vehicle, animal tagging, manual surveys, enforcement activities, numerical model, etc.)
2. Point of Contact for this Data Management Plan (author or maintainer)
Notes: The name of the Person of the most recent Support Role of type "Metadata Contact" is used. The support role must be in effect.
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
3. Responsible Party for Data Management
Program Managers, or their designee, shall be responsible for assuring the proper management of the data produced by their Program. Please indicate the responsible party below.
Notes: The name of the Person of the most recent Support Role of type "Data Steward" is used. The support role must be in effect.
4. Resources
Programs must identify resources within their own budget for managing the data they produce.
5. Data Lineage and Quality
NOAA has issued Information Quality Guidelines for ensuring and maximizing the quality, objectivity, utility, and integrity of information which it disseminates.
(describe or provide URL of description):
Lineage Statement:
Descriptive Information about the methods used.
Bering Sea cruises:
Fish were collected using a 3.05-m plumb staff beam trawl with 7-mm mesh and 4-mm codend liner (after Gunderson and Ellis, 1986). Towing speed was 0.5 m s21 (1.0 knot) in 2003, and 1 m s21 in 2008 and 2010.
In 2003 and 2010, total length (TL) of northern rock sole was recorded to the nearest mm. In 2008, northern rock sole were measured to standard length (SL) if ,80 mm SL and to TL if .80 mm SL. Standard lengths were converted to total lengths using conversion
factors developed by measuring both standard and total length of frozen northern rock sole. For fish ,40 mm SL, the conversion factor was TL ¼ 1.2044(SL) + 0.0415, r2 ¼ 0.95, n ¼ 120; and for fish .40 mm SL, the conversion factor was TL ¼ 1.231(SL) –
1.325, r2 ¼ 0.99, n ¼ 106. In all years, subsamples of at least 25 fish were measured if a size class of fish contained too many individuals to measure in the available time.
Gulf of Alaska cruises
Midwater trawl
The Stauffer (a.k.a., anchovy) trawl was deployed to a depth of 200 meters, or 10 meters, off the bottom, whichever is shallowest. Net depth was monitored using the ship’s Simrad ITI (trawl eye) or FURUNO system.
Walleye pollock (all age classes), Pacific cod, capelin, eulachon, and flatfishes were sorted from the catch. It was sometimes necessary to sort walleye pollock into ca. <120 mm SL and ca. >12 cm FL to ensure adequate representation of age-0 and age-1+ components, respectively, in the catch and length data. Flatfishes were sorted to species. For each of these groups, all individuals or a randomly drawn subsample of all individuals was used to determine length composition. For walleye pollock, approximately 100 age-0 and 100 age-1+ walleye pollock were measured for body length. Standard length (SL) is the body-length metric for age-0 walleye pollock. Fork length (FL) is the body-length metric for age-1+ walleye pollock. Subsampling may have been necessary prior to enumerating and measuring individuals. A sample of each of the following groups were frozen for subsequent examination in the laboratory: age-0 walleye pollock, age-0 Pacific cod, age-0 and age-1 yellowfin sole, and each of the other flatfish species (age-0 only). These were flash frozen in the –80 oC freezer and then moved to the –20 oC freezer.
3-m Beam Trawl
A modified plumb-staff, 3-m beam trawl was deployed to collect juvenile flatfishes from the seafloor. Flatfishes, Pacific cod and walleye pollock were the priority for catch processing, other fishes were sorted to the finest taxonomic level practical and then will be enumerated and weighed and the discarded (but see Special Projects). None of the invertebrate portion of the catch was quantified. Flatfish juveniles, walleye pollock, and Pacific cod were sorted to species, then counted, weighed, and lengthed. If catch of any one target species is very high (more than 50 individuals of one species), a subsample was taken for counting and weighing, and the remainder of the sample was weighed and frozen or discarded. After counting and weighing, the fish (age-0 walleye pollock, age-0 Pacific cod, age-0 and age-1 yellowfin sole, and age-0 individuals of all other flatfish species) were put into individual freezer bags (1 bag per species) and put in the -80 C freezer in the rough lab.
(describe or provide URL of description):
Na
6. Data Documentation
The EDMC Data Documentation Procedural Directive requires that NOAA data be well documented, specifies the use of ISO 19115 and related standards for documentation of new data, and provides links to resources and tools for metadata creation and validation.
Missing/invalid information:
- 1.7. Data collection method(s)
- 7.2. Name of organization of facility providing data access
- 7.2.1. If data hosting service is needed, please indicate
(describe or provide URL of description):
7. Data Access
NAO 212-15 states that access to environmental data may only be restricted when distribution is explicitly limited by law, regulation, policy (such as those applicable to personally identifiable information or protected critical infrastructure information or proprietary trade information) or by security requirements. The EDMC Data Access Procedural Directive contains specific guidance, recommends the use of open-standard, interoperable, non-proprietary web services, provides information about resources and tools to enable data access, and includes a Waiver to be submitted to justify any approach other than full, unrestricted public access.
User must read and fully comprehend the metadata prior to use. Applications or inferences derived from the data should be carefully considered for accuracy. Data will reside at the Alaska Fisheries Science Center.
Notes: The name of the Organization of the most recent Support Role of type "Distributor" is used. The support role must be in effect. This information is not required if an approved access waiver exists for this data.
Notes: This field is required if a Distributor has not been specified.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Not processed automatically.
Notes: This field is required if applicable.
8. Data Preservation and Protection
The NOAA Procedure for Scientific Records Appraisal and Archive Approval describes how to identify, appraise and decide what scientific records are to be preserved in a NOAA archive.
(Specify NCEI-MD, NCEI-CO, NCEI-NC, NCEI-MS, World Data Center (WDC) facility, Other, To Be Determined, Unable to Archive, or No Archiving Intended)
Notes: This field is required if archive location is World Data Center or Other.
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
local and offsite backups
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.