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:
AFSC/MML: Eastern Bering Sea Beluga Whale Aerial Surveys, 1992-1995, 1999-2000
1.2. Summary description of the data:

In 1992-95 and 1999-2000, the U.S. Government provided funds for the Alaska Beluga Whale Committee (ABWC) to conduct studies of belugas in Alaska. Part of the ABWC research program consisted of aerial surveys of western Alaska beluga stocks, including the Eastern Bering Sea (EBS) stock. In 1992, several aerial surveys were conducted during three periods: 27-29 May, 17-21 June, and 18-22 September to assess the distribution of belugas during those periods. The surveys found relatively few belugas in May and September, but a large number of belugas in June. Based on those results, surveys in subsequent years were conducted only in June: 14-18 June 1993, 11-16 June 1994, 5-8 and 20-22 June 1995, 15-17 June 1999, and 17-20 June 2000. This dataset contains aerial survey data from the surveys described above.

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:
1992 to 2000
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: -166.3412, E: -156.6493, N: 66.367, S: 58.382

Norton Sound and Bristol Bay

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:
Janice Waite
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:
janice.waite@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-6554
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:
Megan Ferguson
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?
No
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
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:
The survey was designed to cover coastal and offshore waters of Norton Sound and the Yukon Delta. Coastal transects were parallel to the shoreline with the centerline of the aircraft approximately 0.9 km offshore. Offshore transects were flown east to west along lines of latitude, north to south along lines of longitude, or on diagonals when travelling to and from airports. An adaptive sampling design was used in 1992 to 1995 to increase survey effort in areas where belugas had been sighted. When the belugas were seen on an offshore transect, additional parallel transects were flown at a 3.6-9.3 km spacing on both sides of the original line. Parallel transects were continued as long as belugas were seen, and usually stopped after two transects if there were no sightings. In 1999 and 2000, the survey was designed to cover all of Norton Sound and the Yukon River mouth with east to west transects regularly spaced at 9.3 km intervals. The total length of survey transects flown during each survey period was limited by the aircraft time available. The completion of transects was sometimes limited by weather conditions, particularly fog or high winds, and in June 1999 ice cover was a factor. The survey aircraft was a high-wing, twin-engine Aero Commander equipped with bubble windows, based in Nome. The crew included the pilot, a data recorder in the right front seat, and two observers seated behind the pilot on the left and right sides of the aircraft. Survey altitude was usually 305m, and ground speed was 274 km/hr (150 knots) in 1992 and 220 km/hr (120 knots) in all other years except some transit lines were flown at 274 km/hr in 1994. Navigation was done by reference to landmarks and with a Global Positioning System. The survey was done in passing mode, where whales were counted while staying on effort on the trackline. On the coastal transects, all belugas visible along the survey track were counted. The 1992 surveys were conducted as strip transect surveys; for the offshore transects, observers counted whales within 915 m wide strips on each side of the aircraft. The strips were offset 305 m from the centerline to eliminate the blind spot under the plane. The 1993 to 95 and 1999 to 2000 surveys were conducted as line transect surveys; the offshore transects on each side of the aircraft were divided into seven zones and each beluga sighting was recorded in one of the zones. Inclinometers were used to delineate the inner and outer bounds of zones from 0 to 51 deg. In 1992 and 1993, sightings and other data were recorded on datasheets by observers in one-minute intervals and were then entered into a computer database. In 1994 to“1995 and 1999 to 2000, a computer-based data entry program was used, logging the locations and times for the beginning and end of transects, the position on transect every 1 minute, and the exact time and position of each sighting. Environmental data and sighting conditions were also recorded. Data fields with S at the beginning of the field title (e.g., SOBSNUM, SGROUPSIZ) indicate sighting-related fields. Data fields with W at the beginning of the field title (WCLOUD, WBEAUSTAT, etc.) indicate weather-related fields.

Process Steps:

  • NA
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):
No information found

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)
  • 5.2. Quality control procedures employed
  • 7.3. Data access methods or services offered
  • 8.2. Data storage facility prior to being sent to an archive facility
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:

There are no legal restrictions on access to the data. They reside in public domain and can be freely distributed.

7.2. Name of organization of facility providing data access:
National Centers for Environmental Information - Silver Spring, Maryland (NCEI-MD)
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:
No information found
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:

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)
NCEI_MD
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:
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):
Partial information found
National Marine Mammal Laboratory
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