Data Management Plan
GUID: gov.noaa.nmfs.inport:11800 | 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
The Rockfish Pilot Program was a five-year project that allowed harvesters to form voluntary cooperatives and receive an exclusive harvest privilege for groundfish species in the Central Gulf of Alaska (GOA). This program sunset in in 2010 and was replaced by the Central Gulf of Alaska Rockfish Program.
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.
Central Gulf of Alaska
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:
Information is collected from participants on paper applications or, if allowed, through on-line data submissions in NMFS/AKR eFISH on-line services. Harvest data necessary for real-time account management may also be submitted through eLandings.
Information submitted on paper forms is entered/updated through NMFS/AKR Alaska Data Entry and Retrieval System (ALDERS) by permitting staff. Data entered into ALDERS is stored in appropriate database tables for use in generating permits, reports, views, etc.
(describe or provide URL of description):
n/a legacy data no new data introduced.
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)
(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.
Data are sensitive under the Privacy Act, FOIA and Magnuson-Stevens Fishery Conservation and Management Reauthorization Act (2007) and can only be shared with authorized persons or in summary format for public dissemination.
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.
Access to sensitive data shall only be granted to an individual that meets certain criteria. Access may be granted to the data submitter. Access can only be granted to a non-submitter if a signed and effective Confidentiality Agreement, Data Access Sharing Agreement, Memorandum of Understanding, Standard Statement of Nondisclosure, or similar agreement is in place. These signed agreements shall indicate that individuals have reviewed and understand the provisions in the manual governing the legal use of sensitive data. The signed agreements are maintained by the Alaska Regional Records office. The name of each individual that has signed a statement of nondisclosure for using sensitive data will be added to the Alaska Region list of authorized confidential data users.
Data may be released if aggregated in accordance with AKRO and/or MSA confidentiality protocols. Data may be released if confidential BII or PII information are re-dacted. .
data no longer being collected.
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.
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
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 Alaska Region in Juneau, Alaska, 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.