Search Help Show/Hide Menu

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:
Northern fur seal foraging strategies, Bogoslof and St. Paul Islands 2004-2006
1.2. Summary description of the data:

These data are part of North Pacific Research Board Project 414 and Project 514. Project 514 provided a second year of data collection to the study detailed in Banks et al. (2006; North Pacific Research Board Project 414 Final Report; https://workspace.aoos.org/published/file/48ffae91-0274-4b2b-bc84-5378554070c1/f0414_final_report.pdf?source=catalog&portalId=92), and are summarized together in Springer et al. (2008; North Pacific Research Board Project 514 Final Report; https://workspace.aoos.org/files/2580819/514_Final%20report.pdf?source=catalog&portalId=92

Adult female northern fur seals were captured with hoop nets at 2 breeding colonies (Reef and Vostochni Rookeries) on St. Paul Island, Alaska, and at the single breeding colony on Bogoslof Island, Alaska. Captures occurred during November, 2004 (St. Paul Island only); July, 2005; October-November, 2005; and July 2006. 20 seals at each island and during each capture period were weighed, measured, flipper tagged, and instrumented with satellite tags (platform transmitter terminals, or PTTs), for a total of 140 deployments. Seals were also instrumented with archival time-depth recorders (TDRs) during the July, 2005 (n = 20 TDRs at each island) and July, 2006 (n = 17 TDRs at each island) capture periods. Seals were recaptured, and the instruments recovered, at the end of the each summer. Data collection began on 11/06/2004 and ended on 10/19/2006; data represent 2 winter (fur seal migration) and 2 summer (fur seal lactation) study seasons. PTT (model: Kiwisat 101 and 202; Sirtrack Limited, Havelock North, New Zealand) transmissions were programmed to duty cycle at 4 hours on, 8 hours off during the winter study seasons and at 4 hours on, 4 hours off during the summer study seasons. TDRs (model Mk9; Wildlife Computers, Redmond, WA) sampled depth and temperature every 5 second.

Data are composed of: fur seal capture and instrument deployment histories (1 spreadsheet); seal locations obtained from PTT deployments (4 spreadsheets, each containing all seal locations during a study season); TDR environmental sampling records (65 text files in 4 folders, each file representing a single TDR deployment and each folder representing the deployment island and summer study year for the included TDR files).

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:
2004-11-06 to 2006-10-19
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: 150, E: -175, N: 62, S: 34

Location of seal capture and instrument deployment: Bogoslof Island, St. Paul Island (Vostochni and Reef Rookeries).

Locations of seal summer foraging trips: Bering Sea.

Locations of seal winter migration: Bering Sea, North Pacific Ocean.

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.)
No information found
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:
Brian Fadely
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:
brian.fadely@noaa.gov
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:
206-526-6173
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:
Rolf Ream
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?
Yes
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
0

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):

Process Steps:

  • unknown
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):

Manual data entries were checked against written records and, when available, cross referenced against electronic records.

Electronically derived datasets represent raw data transmitted from Service Argos (for PTT location data) or downloaded directly from TDRs. Service Argos characterizes the accuracy of each transmitted location with location quality codes and these codes are included in each row of location data in the files. Further filtering of PTT location data, and of TDR data, occurs during subsequent, user defined processing (e.g., Wildlife Computers Dive Analysis for TDRs) specific to the desired analyses.

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?
No
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:

Missing/invalid information:

  • 1.7. Data collection method(s)
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: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf
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?
Yes
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?
No
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

No restriction for accessing this dataset

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:
Yes
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:

Data files are accessible through the NPRB URL listed in "Distribution Information"

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

Data are not processed automatically.

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)
OTHER
8.1.1. If World Data Center or Other, specify:
Information for this field exists in the InPort item but will not be included, since the answer to 8.1 is not one of the relevant values.
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:
Information for this field exists in the InPort item but will not be included, since the answer to 8.1 is not one of the relevant values.
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:
Unknown
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