Data Management Plan
GUID: gov.noaa.nmfs.inport:32854 | 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
Description of the core columns that persist throughout OES bottomfish sampling datasets.
While the data have not changed from previous InPort records (see Nodes 11630, 11652), this is part of an effort to standardize and streamline all life history program databases for past and future cruises. This data set includes separate catch logs from each LHP Bottomfishing cruise both within and outside of the Main Hawaiian Islands, as well as a master file with all records.
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.
north and south pacific ocean
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:
This data were entered by various personell, typically M Leuers/Sundberg or M Kapur following collection on LHP cruises beginning in 2008. This data was sourced from data sheets filled out by fishermen and scientists aboard the ship or small boats. In May of 2016 M Kapur took over as data steward and metadata specialist for this and all LHP program databases.
(describe or provide URL of description):
SE-16-01 Samoa and Western Samoa Directory & R Project
Consolidated by M Kapur 13 May 2016
maia.kapur@noaa.gov
NOTICE: THE DATA FILES IN THE 'DATA' DIRECTORY ARE LINKED TO A RELATIONAL DATABASE IN MS ACCESS.
MODIFICATIONS THEREOF WILL BE REFLECTED IN THE OVERALL DATABASE.
This folder has raw and cleaned data recorded on SE-16-01 from Mar to Apr 2016.
The 'code' folder is a growing compilation of scripts used to clean and visualize catch data from this cruise.
SE-16-01 Samoa catchLog.xls:
Each record (row) represents an single fishing outcome for a given drop.
Drops with multiple fish caught result in duplicate records.
Data were entered by Maia Kapur on 05 - 10 May 2016.
GPS coordinates, as recorded by fishermen, were converted within excel to Decimal degrees
with the following formula:
(Hours + Minutes/60) * -1 ; ensuring that the "minutes" are comprised of a FLOAT value.
The CSV version of this sheet is entitled "catch.csv".
Notes:
Certain crew did not record depth in fathoms for their trips.
Wherever possible, species names have been substituted by four-letter codes.
See "Spp Code" sheet in /Data for conversion key.
Location was designated based on what was indicated for that date
on the Bio Sampling data sheet, and is therefore approximate.
SE-16-01 Samoa bioSampling.xls:
Each row represents a single processed fish and its respective data number (beginning in SE-16-01) which will
follow through histology and aging. The Zip Tie # connects it to the Catch dataset.
The 'spurious' tab indicates records that are likely incorrect.
The CSV version of this sheet is entitled "raw.csv".
Notes:
Some fish were saved for outreach or left unprocessed, and thus have no ZipTie number.
Many such species did not undergo gonad extraction or other measurements.
The affiliated R Projects detail the QA/QC procedures used to check data for typographical errors
and possible outliers. Users are advised to use spatial visualization tools (eg GIS) to ensure that
GPS coordinates are accurate within the catch log; and graphical tools in R to check for outlier points
in life history parameters. Because SPP codes can only be verified by hand, we recommend checking ~20% of entries
for accuracy.
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)
- 2.1. Point of Contact Name
- 2.4. Point of Contact Email
- 3.1. Responsible Party for Data Management
(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.
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.
Send written request to PIFSC and requires approval by data owner.
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.
Original documents, copies and electronic files are stored at the IRC.
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
PIFSC ITS performs scheduled backups.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.