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.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:
Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:
AFSC/REFM: Inshore research surveys in the eastern and central Gulf of Alaska, 2010-2013, conducted by the middle trophic level component of the GOA Integrated Ecosystem Research Project
1.2. Summary description of the data:

This dataset contains the results of a series of inshore research surveys that took place during 2010-2013 as part of the Gulf of Alaska Integrated Ecosystem Research Program (GOAIERP), a multidisciplinary study of the GOA ecosystem funded by the North Pacific Research Board. The project is comprised of four groups of investigators, organized as upper, middle, and lower trophic levels plus a modeling group. Investigators from the middle trophic level component conducted the research covered by this dataset. The study area consists of two main spatial regions (eastern: the outer coast of Southeast Alaska, western: the east side of Kodiak Island and the southern coast of the Kenai Peninsula). Within each main region the surveys covered 5-6 inshore bays or systems of bays (east: Whale Bay, St. Lazaria Island, Salisbury Sound, Islas Bay, Graves Harbor, Torch Bay; west: Kiliuda Bay, Izhut Bay, Barren Islands, Port Dick, Aialik Bay).

At each of the inshore sites a number of research activities were conducted: 1) acoustic transects using 38- and 120-kHz split-beam transducers were conducted throughout the site to a depth of 20m; 2) sporadic nearshore acoustics were conducted from a skiff between depths of 5-20 m; 3) 10 m and 15 m beach seines were deployed along the shoreline; 4) a 50 m purse seine was deployed in depths from 3-7 m; 5) a 3-m beam trawl was deployed sporadically; 6) a 6 m X 3 m single-warp otter trawl was sporadically used for surface tows; 7) acoustic backscatter was groundtruthed using the otter trawl, jigging, and an underwater video camera; 8) oceanography stations were conducted using a Seabird 19+ CTD, a vertical zooplankton tow using a 1 m ring net, and collection of chlorophyll and nutrients samples at depths of 1 and 20 m at each station. Fish samples were taken for analyses of diet, nutritional condition, and energy content.

In 2010, pilot studies were conducted in the eastern region during July and in the western region during October. These studies did not employ all of the gears listed above, and little oceanography work was performed. In 2011, full 15-day seasonal surveys were conducted in each region (east: April, July, September; west: May, August, October). No fieldwork was conducted during 2012. In 2013 the full seasonal surveys once again took place, however due to the shutdown of the federal government the fall east survey was curtailed and the fall west survey was delayed until early November.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
1.3. Is this a one-time data collection, or an ongoing series of measurements?
One-time data collection
Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
1.4. Actual or planned temporal coverage of the data:
2010 to 2015
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
1.5. Actual or planned geographic coverage of the data:
W: -155, E: -133, N: 58, S: 55

Gulf of Alaska

Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
Table (digital)
1.7. Data collection method(s):
(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.)
Instrument: various
Platform: various
Physical Collection / Fishing Gear: various
1.8. If data are from a NOAA Observing System of Record, indicate name of system:
Always left blank due to field exemption
1.8.1. If data are from another observing system, please specify:
Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:
Metadata Coordinators MC
Taken From: Support Roles (Metadata Contact) | Person
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.
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
Taken From: Support Roles (Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
2.4. E-mail address:
Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.
2.5. Phone number:
No information found
Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

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.

3.1. Name:
Olav Ormseth
Taken From: Support Roles (Data Steward) | Person
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.
3.2. Position Title:
Data Steward
Always listed as "Data Steward"

4. Resources

Programs must identify resources within their own budget for managing the data they produce.

4.1. Have resources for management of these data been identified?
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):

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.

5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
(describe or provide URL of description):

Lineage Statement:
not available

5.1.1. If data at different stages of the workflow, or products derived from these data, are subject to a separate data management plan, provide reference to other plan:
Always left blank
5.2. Quality control procedures employed
(describe or provide URL of description):

not available

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.

6.1. Does metadata comply with EDMC Data Documentation directive?
Notes: All required DMP fields must be populated and valid to comply with the directive.
6.1.1. If metadata are non-existent or non-compliant, please explain:
Notes: Required DMP fields that are not populated or invalid are listed here.
6.2. Name of organization or facility providing metadata hosting:
NMFS Office of Science and Technology
Always listed as "NMFS Office of Science and Technology"
6.2.1. If service is needed for metadata hosting, please indicate:
Always left blank
6.3. URL of metadata folder or data catalog, if known:
Always listed as the URL to the InPort Data Set record
6.4. Process for producing and maintaining metadata
(describe or provide URL of description):
Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive:
Always listed with the above statement

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.

7.1. Do these data comply with the Data Access directive?
7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

The data set is still being analyzed and will not be available for distribution until it has been finalized and all QA/QC practices have been performed. Contact the Point Of Contact for estimated time of release.

7.2. Name of organization of facility providing data access:
North Pacific Research Board (NPRB)
Taken From: Support Roles (Distributor) | Organization
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.
7.2.1. If data hosting service is needed, please indicate:
Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
7.2.2. URL of data access service, if known:
Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
7.3. Data access methods or services offered:

NPRB will distribute the data.

7.4. Approximate delay between data collection and dissemination:
7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:


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.

8.1. Actual or planned long-term data archive location:
(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)
To Be Determined
8.1.1. If World Data Center or Other, specify:
Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.
8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:

to be determined by NPRB for the GOA IERP project

Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
8.2. Data storage facility prior to being sent to an archive facility (if any):
North Pacific Research Board - Anchorage, AK
Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
8.3. Approximate delay between data collection and submission to an archive facility:
8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
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.

Always left blank