Data Management Plan
GUID: gov.noaa.nmfs.inport:24167 | 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
Data from Localized Depletion study for Pacific cod 2001-2005. Study was conducted using cod pot gear to measure localized abundance of Pacific cod inside and outside of a trawl exclusion zone in the southeast Bering Sea, both before and after the intensive winter season cod trawl fishery. Data includes early feasibility and gear trials as well as before and after data from each of three years of the experiment. Pot gear was fished in 40 fixed stations in two adjacent areas, one of which was subject to heavy trawling and one within a trawl exclusion zone. Average of three or more pot catches at each station for each time period (before/after) was computed, the variable for final analysis was the change in catch at each station between the two periods. There are three main data tables. Cruise data identifies the dates, vessels, and personnel for each charter. Haul data includes information on location, date, soak time, and identifier for each pot launched, while Catch data includes numbers and weight of cod and bycatch by pot. Assorted small tables define categories for descriptive variables in main tables. Length and maturity data were collected on a random subset of cod catch. Some CTD profiles and oceanographic data were also collected.
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.
Southeast Bering Sea just north of Unimak Pass, off Cape Sarichef on the northwestern end of Unimak Island
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:
See method in uploaded FGDC view.
Process Steps:
- NA
(describe or provide URL of description):
See dataqual and method in uploaded FGDC view.
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)
(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.
For scientific, management, and regulation compliance purposes, particular business or proprietary information held by NMFS is considered confidential under several authorities,
including the Magnuson-Stevens Fishery Conservation and Management Act; as amended, Public Law 109-479; 16 U.S.C. Sec.1853,
and the Freedom of Information Act, 5 U.S.C. Sec. 552. herefore, unprocessed (raw) business or
proprietary information can be shared only with authorized persons; however aggregated forms of the data are generally available.
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.
na
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
IT Security and Contingency Plan for the system establishes procedures and applies to the functions,
operations, and resources necessary to recover and restore data as hosted in the Western Regional
Support Center in Seattle, Washington, following a disruption.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.