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:

IFQ Halibut/Sablefish and CDQ Halibut Permit Program

Taken From: Item Identification | Title

1.2. Summary description of the data:

Under the IFQ Halibut/Sablefish Permit Program and CDQ Halibut Permit Program permits are issued for harvesting and receiving/processing halibut, and non-trawl sablefish.

For IFQ Halibut/Sablefish Permits, owners of vessels with specific historical participation in non-trawl halibut and sablfish fisheries were issued Quota Share (QS). Quota share was initially issued to persons who owned or leased vessels that made legal commercial fixed-gear landings of Pacific halibut or sablefish during 1988-1990 off Alaska. QS is transferable to other initial issuees or to those who have become transferable eligible on NMFS' approval of an Application for Transfer Eligibility Certificate. Once issued to a person (at no charge), QS is held by that person until it is transferred, suspended, or revoked. QS permits are authorized at 50 CFR Part 679.4(d).

Quota Share holders are entitled to a proportional share of the annual Total Allowable Catch allocated to the IFQ Program. An IFQ permit authorizes participation in fixed-gear harvests of Pacific halibut off Alaska, and most sablefish fisheries off Alaska. The permits are not specific to vessels. Permits are issued annually, at no charge, to persons holding fishable Pacific halibut and sablefish Quota Share (QS); or to those who are recipients of IFQ-only transfers from QS holders. Authorized pounds for annual IFQ permits are determined by the number of QS units held, the total number of QS units in the "pool" for a species and area, and the total amount of halibut or sablefish allocated for IFQ fisheries in a particular year. IFQ permits are authorized at 50 CFR Part 679.4(d).

The Western Alaska Community Development Quota (CDQ) Program allocates a percentage of all Bering Sea and Aleutian Islands quotas for groundfish, prohibited species, halibut, and crab to eligible communities. A CDQ permit is required to harvest CDQ halibut. Permits are issued annually and without charge to CDQ groups with approved CDQ plans and directed fishing allocations of halibut.

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?

Ongoing series of measurements

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:

1993 to Present

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: -180, E: -130, N: 72, S: 50

BSAI

GOA

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

Document (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:

Tracy Buck

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:

tracy.buck@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:

907-586-7889

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:

Tracy Buck

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

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

Cost Recovery/Unknown

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

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

Submitted data is reviewed by NMFS staff prior to data entry. Source data are validated against business rules when loaded into NMFS' Oracle database. Data input is reviewed against output on a routine basis to ensure quality.

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)

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/11799

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?

No

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:

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.

Taken From: Access Info | Data Access Constraints

7.2. Name of organization of facility providing data access:

Alaska Regional Office (AKRO)

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:

unknown

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/permits-licenses?field_fishery_pm_value=Individual+Fishing+Quota+%28IFQ%29+Halibut%2FSablefish+and+CDQ+Halibut+IFQ

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:

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

Taken From: Access Info | Data Access Procedure

7.4. Approximate delay between data collection and dissemination:

unknown

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:

Data may need to be aggregated for confidentiality before dissemination. If data does not need to be aggregated dissemination may be made daily.

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

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:

35 days

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

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.

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