Table: ALS_ANNUAL_FACTORS_FL
Entity (ENT) | Southeast Fisheries Science Center (SEFSC)GUID: gov.noaa.nmfs.inport:5387 | Updated: August 9, 2022 | Published / External
Item Identification
Title: | Table: ALS_ANNUAL_FACTORS_FL |
---|---|
Short Name: | ALS_ANNUAL_FACTORS_FL |
Status: | Completed |
Abstract: |
This is a table of factors based upon the best estimates of the port agents that will allow generation of totals by Gear, Watrbody , and Distance From Shore that will be put into the table ALS_GENERAL_CANVASS which contains Florida Annual Data. Barring any further changes to Fl data 1996 and prior, this table may be considered obsolete. |
Purpose: |
This is a lookup table which runs against Florida non-shrimp data in the ALS.ALS_LANDINGS table. The purpose is to assign gear, waterbody, and distance from shore to the FL monthly data in ALS.ALS_LANDINGS to create the annual table als.als_general_canvass. |
Notes: |
Loaded by batch 1686, 10-12-2007 09:48 |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
UNCONTROLLED | |
None | apportionment |
None | area |
None | county |
None | distance from shore |
None | gear |
None | species |
None | water body |
Spatial Keywords
Thesaurus | Keyword |
---|---|
UNCONTROLLED | |
None | Florida |
Physical Location
Organization: | Southeast Fisheries Science Center |
---|---|
City: | Miami |
State/Province: | FL |
Country: | USA |
Location Description: |
75 Virginia Beach Drive Miami, FL 33016 |
Entity Information
Entity Type: | Data Table |
---|---|
Active Version?: | Yes |
Schema Name: | ALS |
Description: |
This is a table of factors based upon the best estimates of the port agents that will allow generation of totals by Gear, Watrbody , and Distance From Shore that will be put into the table ALS_GENERAL_CANVASS. which contains Florida Annual Data |
Data Attributes
Attribute Summary
![]() |
![]() |
Name | Type | Description |
---|---|---|---|---|
100
|
NMFS_CODE | VARCHAR2 | Four Digit NMFS Species Code | |
100
|
ALSCTYIN | VARCHAR2 | Three CHaracter NMFS County Code Table | |
100
|
ALSSTATE | VARCHAR2 | Two character NMFS State Code | |
100
|
WATERBODY | VARCHAR2 | Four Digit Water Body Code | |
100
|
NMFSGEAR | VARCHAR2 | Three Character NMFS Gear COde | |
100
|
DISTANCE | VARCHAR2 | Distance From Shore Code | |
100
|
PERCENTAGE | NUMBER | Factor to be used in caluclation. 30 percent is expressed as 30. | |
100
|
YEAR_LANDED | VARCHAR2 | Year The Factor Is To Be Used For | |
100
|
OLD_WATERBODY | VARCHAR2 | OLD_WATERBODY Code. This has been included because there was a project to modify the ALS data that involved substantial changing of Waterbody Codes | |
100
|
REGION | VARCHAR2 | Region Code |
Attribute Details
NMFS_CODE
Seq. Order: | 1 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 4 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Four Digit NMFS Species Code |
General Data Type: | VARCHAR2 |
ALSCTYIN
Seq. Order: | 2 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 3 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Three CHaracter NMFS County Code Table |
General Data Type: | VARCHAR2 |
ALSSTATE
Seq. Order: | 3 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Two character NMFS State Code |
General Data Type: | VARCHAR2 |
WATERBODY
Seq. Order: | 4 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 4 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Four Digit Water Body Code |
General Data Type: | VARCHAR2 |
NMFSGEAR
Seq. Order: | 5 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 3 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Three Character NMFS Gear COde |
General Data Type: | VARCHAR2 |
DISTANCE
Seq. Order: | 6 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Distance From Shore Code |
General Data Type: | VARCHAR2 |
PERCENTAGE
Seq. Order: | 7 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 7 |
Scale: | 3 |
Status: | Active |
Description: |
Factor to be used in caluclation. 30 percent is expressed as 30. |
General Data Type: | NUMBER |
YEAR_LANDED
Seq. Order: | 8 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 4 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Year The Factor Is To Be Used For |
General Data Type: | VARCHAR2 |
OLD_WATERBODY
Seq. Order: | 9 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 4 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
OLD_WATERBODY Code. This has been included because there was a project to modify the ALS data that involved substantial changing of Waterbody Codes |
General Data Type: | VARCHAR2 |
REGION
Seq. Order: | 10 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Region Code |
General Data Type: | VARCHAR2 |
Access Information
Security Class: | Confidential |
---|---|
Security Classification System: |
Password Restricted. Rule of 3: Data summaries must include at least 3 dealers to be considered non-confidential. See: NOAA FORM 58-5 (1-84) TRANSMITTAL 127, National Oceanic and Atmospheric Administration NOAA Administrative Order 216-100 NOAA ADMINISTRATIVE ORDER SERIES Date of Issuance: July 26, 1994 |
Security Handling Description: |
Confidential data may only be released to entities having a signed non-disclosure agreement on file with the Director of the Information Resources Management Division (IRMD). Otherwise, confidentiality may be suppressed by the following methods used for aggregation of confidential data: Data that are submitted as confidential can be released to the public under the following circumstances: 1. Combined or aggregated data. Confidential data can be released if the data are aggregated or summarized in a manner that prevents the identification of the person or organization that submitted the data. The "rule of three" and identification of majority allocations" are the primary data suppression methods. 2. Obscure (scramble) or remove the data identifier. For some types of data, confidential data Can be released as non-confidential if the identity of the person, vessel, company, etc. that submitted the data is not included or is scrambled as part of the data that are released. 3. Submitter. Confidential data collected under federal authority Can be released to the original entity (person, vessel, business, etc.) that sUbmitted the data. 4. Confidential data waived. The protection of confidential data can be waived by the person or business that submitted the data. |
Data Access Policy: |
See NOAA Administrative Order 216-100 NOAA ADMINISTRATIVE ORDER SERIES Date of Issuance: July 26, 1994 |
Data Access Procedure: |
These standards and procedures apply to all employees of the SEFSC that need access to confidential fisheries statistics. This includes full time or term employees, contractors, volunteers, and/or other employees associated with the SEFSC, but not directly employed by either organization. Any SEFSC employee that needs or desires access to confidential data must have read NOA 216-100 and submitted a signed nondisclosure statement to the Director, Information Resources Management Division (IRMD). The non-disclosure statement must be approved by the Director of IRMD and maintained on file by IRMD. It is the responsibility of the Director of IRMD to certifY upon request, that a person or organization that requests access to confidential data is authorized access to those data. All employees that have access to and/or use confidential data (federal and nonfederal) are responsible to protect those data from unauthorized access or release. Contractors or grantees that have an agreement with NMFS can be granted access to confidential data as an authorized user (See NOA 216-100 1 Section 6.03e). It should be clearly understood that confidential data cannot be released simply by an individual signing a nondisclosure statement. There must be a clear and demonstrable need for the confidential data that are requested as part of a contract or grant. Confidential data can only be released for the specific contract or grant. Upon completion of the contract or grant, the recipient must either return the data or state that it has been destroyed. The contractor or grantee cannot use the data for any purpose other than the uses stated in the agreement. The Contracting Officers Technical Representative (COTR) or the Technical Monitor (TM) that has been assigned to the contract or grant, respectively, has the following? responsibilities: 1. The COTR/TM has the responsibility to determine whether the contractor/grantee is eligible to receive the confidential data that are requested in the agreement. 2. The COTR/TM has the responsibility to assure that all persons included in the agreement have read NOA 2l6-l00 and have signed a nondisclosure statement. A statement must be signed by each person that will have access to the confidential data under the agreement, i.e., a blanket statement cannot be used for the company or firm. The COTR/TM also has the responsibility to make sure that the Director, IRMD has signed and approved the nondisclosure statement and the statement is on file with IRMD. 3. The COTR/TM has the responsibility to assure that confidential data are not released in any publication, report, oral presentation, or other means to the public by the contractor or grantee. |
Data Access Constraints: |
To access confidential data a completed non-disclosure agreement must be on file with NOAA-SEFSC. Otherwise Data that are submitted as confidential can be released to the public under the following circumstances: 1. Combined or aggregated data. Confidential data can be released if the data are aggregated or summarized in a manner that prevents the identification of the person or organization that submitted the data. The "rule of three" and identification of majority allocations" are the primary data suppression methods. 2. Obscure (scramble) or remove the data identifier. For some types of data, confidential data Can be released as non-confidential if the identity of the person, vessel, company, etc. that submitted the data is not included or is scrambled as part of the data that are released. 3. Submitter. Confidential data collected under federal authority Can be released to the original entity (person, vessel, business, etc.) that sUbmitted the data. 4. Confidential data waived. The protection of confidential data can be waived by the person or business that submitted the data. |
Data Use Constraints: |
NOAA/SEFSC Internal use only. |
Metadata Access Constraints: |
Non-published Metadata access is restricted. Published Metadata is available to the public. |
Metadata Use Constraints: |
Non-published Metadata access is restricted. Published Metadata is available to the public. |
Catalog Details
Catalog Item ID: | 5387 |
---|---|
GUID: | gov.noaa.nmfs.inport:5387 |
Metadata Record Created By: | Lee M Weinberger |
Metadata Record Created: | 2007-10-12 09:48+0000 |
Metadata Record Last Modified By: | SysAdmin InPortAdmin |
Metadata Record Last Modified: | 2022-08-09 17:11+0000 |
Metadata Record Published: | 2021-05-06 |
Owner Org: | SEFSC |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2021-05-06 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2022-05-06 |