Data Management Plan
GUID: gov.noaa.nmfs.inport:8083 | 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 NEFSC Food Habits Database has two major sources of data. The first, and most extensive, is the standard NEFSC Bottom Trawl Surveys Program. During these surveys, food habits data are collected for a variety of species. Additionally, "process-oriented" cruises are conducted periodically to address specific questions related to the feeding ecology of the fish in the ecosystem.
Both sources provide primarily stomach content information; composition, total and individual prey weights or volumes, and length of prey. Additional information associated with each fish predator is also collected. Other databases encompass the prey fields of these fish, and include zooplankton, ichthyoplankton, and benthic surveys.
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.
Approximately Cape Hatteras, NC to Nova Scotia, Canada
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 Food Web Dynamics Program website at http://nefsc.noaa.gov/femad/pbb/fwdp/ for a description of data and sources
(describe or provide URL of description):
The FHDBS data undergo a 15-point data quality assurance check conducted by experienced personnel of the Food Web Dynamics Program. These checks range from ensuring the final data are complete (e.g. prey percentages sum to 100%, eliminate duplicate data, and all necessary fields are populated) to more complex quality assurance in the form of accurate prey selection and prey taxonomy, and other biological constraints (e.g. size of prey versus predator size, and volume or weight of prey versus weight of predator).
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.
NEFSC Data Access Constraint:
If data is stored on an internal NEFSC network, the requester may not have direct access to query the data unless they are also authorized for network access.
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.
NEFSC Data Access Procedure:
1. Formal request in writing usually to the data owner/contact or Center Director;
2. Requester is contacted by data owner to review and verify the request content and details for data delivery options.
3. If data is confidential then owner will determine if the data may be released to the requester;
4. If data can be released, the data is downloaded and packaged for delivery electronically; or the requester may be directed to where the data is available online.
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
Archival of source data preserving unaltered collected data, Scheduled backups, Remote storage backups, Password protection
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.