Data Management Plan
GUID: gov.noaa.nmfs.inport:26273 | 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
This is a database of a variety of biological, reproductive, and energetic data collected from fish on the continental shelf in the northwest Atlantic Ocean. Species sampled in this database thus far include winter flounder, yellowtail flounder, summer flounder, haddock, cusk, Atlantic wolffish, and Atlantic herring. Data are collected from fish provided principally from fishermen participating in the NECRP Study Fleet. Some fish are taken from other NECRP research studies, and a small number from NEFSC surveys and surveys by MADMF and URI GSO. The catch location data is provided in views from the relevant FVTR, SVDBS, or other tables for a few cooperative research or external programs. The biological data includes general physical data (weights, lengths, organ weights, macroscopic maturity stage), age data, and other reproductive data. Measures collected from preserved gonad samples includes data for estimation of fish fecundity (oocyte counts and diameters) and from grading gonad histology for determination of maturity and seasonal reproductive status. In addition, relative measures of energetic condition are collected (including tissue wet weight and dry weights and bioimpedance data), and for some fish food habits data were collected in the first 18 months of data collection.
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.
Continental shelf in southern New England, Gulf of Maine, and Georges Bank
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:
Fish samples are collected by cooperative research programs. Data were initially collected for the first 6 months of this program by hand on data sheets. The application express (APEX) form and oracle database were developed specifically for this project and began use in July 2010. Development of the software particular to the unique data for this project continues. Some tables are still in the developmental stage for some of the more unusual data types, and data is only partially loaded into Oracle tables.
(describe or provide URL of description):
The APEX form used to enter the data contains numerous data quality control restrictions. Some of these mandate specific data be collected or fit specified formats and levels of precision. Many of the variables collected also have warning prompts to users for data outside of the ranges typically observed for a particular species.
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.
Most of the fish capture locations come from the fishermen's commercial fishing locations and are imported from FVTR tables. These locations are protected proprietary information of the fishermen. Access is constrained by the same policies as all the FVTR data at the NEFSC.
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.
Data access is restricted, contact Dave McElroy.
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
Data are backed up and stored on a schema on sole or several computers on site in the Woods Hole lab that are backed up following the standard routines for all data at the NEFSC. The database also has data editing access limited to those principally collecting and auditing the data routinely.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.