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:

Spatial Management Areas

Taken From: Item Identification | Title

1.2. Summary description of the data:

Spatial management files combine all related and relevant spatial management files into an integrated fisheries management file. Overlaps of the redundant spatial restrictions were removed by defining the least to the most restrictive management measures and then doing updates on the less restrictive measures. FROM least restrictive to MOST Restrctive>>>>Habitat Conservation Areas || Habitat Protection Areas, Habitat Coral Areas || Special Habitat Areas || Steller Sea Lion Protection Measures, Walrus Protection Measures, Walrus No Entry Areas, and finally the most restrictive, the Steller No Transit Area. Arc operation employed: UPDATE.Data compiled from regulatory packages including ' 679.22 Closures. Tables 4, 5, 6, 22, 23, 24, 25, 26, 27'226.202 Critical habitat for Steller sea lions.50 CFR 223.202, No Transit AreasData was made available in several formats including: ArcGIS Featureclasses, shapefiles, AutoCad files, and within an integrated CarryMap application.

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:

2015-01-02 to 2016-01-02

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: -179.9999, E: -129, N: 66.522262, S: 44.580908

US\Alaska EEZ

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

Map (digital)

Taken From: Data Set Information | Data Presentation Form

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

Taken From: Acquisition Information | Instruments, Platforms

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:

No information found

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:

No information found

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:

Steve Lewis

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

Taken From: Data Management | 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"):

10

Taken From: Data Management | Approximate percentage of budget for these data devoted to data management

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:
Tool location \DeleteField Command issued DeleteField CVOA PERIMETER;CVOA_;CVOA_ID;DESC_; __ Tool location \AddField Command issued AddField CVOA HTM TEXT # # # # NULLABLE NON_REQUIRED # Tool location \CalculateField Command issued CalculateField CVOA HTM "CVOA.htm" VB # Tool location \Merge Command issued Merge CVOA;GOA_Type_1;GOA_Type_2;Red_King_Crab_Closure_Area_GHR __Current_Mngt.gdb\Lower Tool location __Toolboxes\Analysis Tools.tbx\Up Command issued Up Lower HCA __ ___Trawl_1.shp Tool location __Toolboxes\Analysis Tools.tbx\Up Command issued Up ___Trawl_1 HPA __Default.gdb\ ___Trawl_2_Up Tool location __Toolboxes\Analysis Tools.tbx\Up Command issued Up ___Trawl_2_Up MedHigh __Default.gdb\ ___Trawl_3_Up Tool location __Toolboxes\Analysis Tools.tbx\Up Command issued Up ___Trawl_3_Up iNTERMEDIATE __Default.gdb\ ___Trawl_3_Up _Up 1 Tool location __Toolboxes\Analysis Tools.tbx\Up Command issued Up ___Trawl_3_Up _Up 1 MedHigh __Default.gdb\ ___Trawl_3_Up _Up 1_ Tool location __Toolboxes\Analysis Tools.tbx\Up Command issued Up ___Trawl_3_Up _Up 1_ Higher __Default.gdb\ ___Trawl_3_Up _Up 1_1 Tool location __Toolboxes\Analysis Tools.tbx\Up Command issued Up ___Trawl_3_Up _Up 1_1 PWS_Rookeries_No_Fishing __Default.gdb\ ___Trawl_3_Up _Up 1_2 Tool location __Toolboxes\Analysis Tools.tbx\Up Command issued Up ___Trawl_3_Up _Up 1_2 AI_Open_Area_ ___Trawl __Default.gdb\ ___Trawl_3_Up _Up 1_5 Tool location \CalculateField Command issued CalculateField ___Trawl_3_Up _Up 1_5 HTM "3nm_No_Transit.htm" VB # Tool location __Toolboxes\Analysis Tools.tbx\Up Command issued Up ___Trawl_3_Up _Up 1_5 Bowers_Ridge __Default.gdb\ ___Trawl_3_Up _Up 1_6 Tool location __Toolboxes\Analysis Tools.tbx\Up Command issued Up ___Trawl_3_Up _Up 1_6 "3nm No Transit Zones" __Default.gdb\ ___Trawl_3_Up _Up 1_7 Tool location \CalculateField Command issued CalculateField ___Trawl_3_Up _Up 1_7 HTM "AI_No_ ___Trawl.htm" VB # Tool location \CalculateField Command issued CalculateField ___Trawl_3_Up _Up 1_7 HTM "Red_king_Crab_Closure_Area.htm" VB # Tool location \CalculateField Command issued CalculateField ___Trawl_3_Up _Up 1_7 HTM "Red_king_Crab_Closure_Area_GHR.htm" VB # Tool location __Toolboxes\Analysis Tools.tbx\Up Command issued Up " __ Trawl and Other Restrictions" Walrus_Transit_Areas __Default.gdb\ ___Trawl_3_Up _Up 1_4 Tool location \CalculateField Command issued CalculateField ___Trawl_3_Up _Up 1_4 HTM "Walrus_Transit_Area.htm" VB # Tool location \CalculateField Command issued CalculateField " __ Trawl and Other Restrictions" HTM "Walrus_Islands_Transit_Area.htm" VB # Tool location \CalculateField Command issued CalculateField " __ Trawl and Other Restrictions" HTM "Walrus_Round_Is_No_Entry.htm" VB # Tool location \CalculateField Command issued CalculateField " __ Trawl and Other Restrictions" HTM "Walrus_Protection_Area_W_FFP.htm" VB # Tool location \CalculateField Command issued CalculateField " __ Trawl Fishery" dtd "slewis akro 01/09/15" VB # Tool location \CalculateField Command issued CalculateField " __ Trawl Fishery" dtd "steve.lewis, akro, 01/09/15" VB # Tool location __Toolboxes\Analysis Tools.tbx\Up Command issued Up " __ Trawl and Other Restrictions" Marmot_Bay_Erase __Default.gdb\ ___Trawl_3_Up _Up 1_8 Tool location \CalculateField Command issued CalculateField " __ Trawl and Other Restrictions" HTM "Marmot_Bay_Tanner_Crab_Protection_Area.htm" VB #

Taken From: Lineage | Lineage Statement, Process Steps (Process Date/Time, Source Citation Title, Description)

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

Two internal reviews

Taken From: Data Quality | Quality Control Procedures Employed

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)
2.1. Point of Contact Name
2.4. Point of Contact Email
7.2. Name of organization of facility providing data access

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:

https://www.fisheries.noaa.gov/inport/item/27352

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

Taken From: Data Management | 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?

No

Taken From: Data Management | Is access to the data limited based on an approved waiver?

7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

None, the mariner is in charge of their own vessel. These management measures are for spatial restrictions only and do not directly account for safety of the vessel.

Taken From: Access Info | Data Access Constraints

7.2. Name of organization of facility providing data access:

No information found

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:

No

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:

https://alaskafisheries.noaa.gov/fisheries/sslpm

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:

Not classified

Taken From: Access Info | Data Access Procedure

7.4. Approximate delay between data collection and dissemination:

1 day

Taken From: Data Management | 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:

NA

Taken From: Data Management | If delay is longer than latency of automated processing, indicate under what authority data access is delayed
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.

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

Taken From: Data Management | Actual or planned long-term data archive location

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

Alaska Regional Office - Juneau, AK

Federal Building

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:

NA

Taken From: Data Management | 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

Yes

Taken From: Data Management | How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?

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