Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:27998 | Published / External
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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 majority of octopus bycatch occurs in Pacific cod pot fisheries and recent data collected by North Pacific Groundfish Observers indicate that immediate mortality of octopus caught in these fisheries is very small. The objectives of the proposed research were to examine the delayed mortality of E. dofleini captured in Pacific cod pot fisheries. These data are necessary to make sound management decisions for octopus based on appropriate scientific information. This data set contains observations and measurements on the condition, weight, and survivorship of North Pacific giant octopus that were caught as bycatch in commercial fishing operations utilizing pot gear to target Pacific cod. These octopus were captured during commercial fishing operations that occurred during three fishing seasons from January 2014 through February 2015. These commercial fishing operations occurred in the central Gulf of Alaska in either Shelikof Strait or Marmot Bay. Data collected included information on octopus condition, size, sex, and injury presence. Other data collected included the location of capture, water depth, octopus air exposure time, water temperature, and gear soak time. These octopus were transported to the Kodiak sea water facility and held for a period of several months. During this period data were collected on condition, injury presence, and survivorship at 21 days. After this period octopus were held for an additional five to six weeks to assess growth within the laboratory. Octopus were fed to satiation every 72 hours during this period. Food was weighed prior to feeding and remaining food was weighed after a four hour period. The final food weight was corrected for water soaking time. Octopus were weighed once per week during this period of time. Several metrics of octopus feeding and growth were measured after this period including specific growth rate, absolute growth rate, absolute feeding rate, specific feeding rate, feeding efficiency, and daily growth rate.
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.
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:
Parameters associated with capture events (dates, air temperature, water temperature, etc.) were collected by a biological technician. Air temperature was measured using standard thermometers and water temperatures were collected using temperature tid-bits that were attached to pot gear. All equipment utilized was in appropriate working order during these collections. All biological data collected in the laboratory (weight, food weight, etc.) were measured using laboratory bench top scales which were calibrated regularly to minimize measurement error.
Process Steps:
- Octopus were collected from commercial fishers during regular fishing operations targeting Pacific cod using pot gear. Octopus were assessed for condition and placed in tanks on board the fishing vessels. After a period of seventy two hours or less they were transported to the Kodiak Laboratory either via a tender vessel or the fishing vessel. Octopus were placed in individual tanks upon arrival at the laboratory. Within a 48 hour period a detailed assessment of the condition of each octopus was conducted, the gender of the octopus was determined, and each octopus was weighed. To weigh individual octopus, they were removed from their tanks, excess water was released from the mantle, and the octopus were weighed using standard bench top scales. Octopus were held for twenty one days; during this period they were fed herring to satiation two times per week. After 21 days, another detailed assessment was conducted. 20150515
(describe or provide URL of description):
unknown
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
(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.
There are no legal restrictions on access to the data. They reside in public domain and can be freely distributed.
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.
E-mail PI
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.