Slide Menu
Search Help Show/Hide Menu

Item Identification

Title: Table: ALS_LAND_PUERTO_RICO_BAD
Short Name: ALS_LAND_PUERTO_RICO_BAD
Status: Completed
Abstract:

To Hold Puerto Rico Landings data that did not pass validation.

Notes:

Loaded by batch 1725, 10-16-2007 05:43

Keywords

Theme Keywords

Thesaurus Keyword
UNCONTROLLED
None failed validation
None landings

Spatial Keywords

Thesaurus Keyword
UNCONTROLLED
None puerto rico

Entity Information

Entity Type: Data Table
Active Version?: Yes
Schema Name: ALS
Description:

To Hold Puerto Rico Landings data that did not pass validation.

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
MONTH_LANDED VARCHAR2 wo Character Month Landed
100
YEAR_LANDED VARCHAR2 4 character Year Landed
100
STATE_LANDED VARCHAR2 State Code Landed. This is laways loaded with the NMFS STate Code For Puerto Rico.
100
FISHING_CENTER VARCHAR2 Fishing Center Code.
100
DEALER VARCHAR2 Dealer Code. Added For compatibility with other ALS Tables. This is column is always filled with all 9s as the Dealer is unknown.
100
WATER_BODY VARCHAR2 Water Body Code
100
GEAR VARCHAR2 NMFS Gear Code (If One exists. It is generated between a cross table Of Erdman Gear Codes to NMFS Gear Code)
100
SPECIES VARCHAR2 NMFS Species Code (If One exists. It is generated between a cross table Of Erdman Speciesr Codes to NMFS Species Codes)
100
SHELL_OR_FINFISH VARCHAR2 Finfish or shell fish code.
100
POUNDS NUMBER Pounds Caught. (Whole weight)
100
VALUE NUMBER Value in dollars
100
SECTION VARCHAR2 Section Code, Added for compatibility with ALS.ALS_LANDINGS
100
PRICE NUMBER Price payed for fish. (In dollars)
100
DISTANCE VARCHAR2 Distance From Shore Code. Added for compatibility with ALS.ALS_LANDINGS.
100
STATE_CAUGHT VARCHAR2 State Caught. Added For compatibility WIth ALS.ALS_LANDINGS
100
LANDING_DATE DATE Actual Date animal was landed.
100
PR_ID_CODE VARCHAR2 Identification Code asigned to Record by Puerto Rico data manager
100
PR_GEAR VARCHAR2 Erdman Gear Code
100
NUMBER_OF_TRIPS NUMBER Number Of Trips
100
PR_SPECIES VARCHAR2 Erdman Species Code
100
GEAR_QTY NUMBER Number Of Gear
100
GEAR_HOURS NUMBER Soak Time
100
DAY_LANDED VARCHAR2 Day landed. Derived from landing date
100
RNUMBER NUMBER Record Number
100
FILE_NAME VARCHAR2 Sorce File used to load records
100
USERID VARCHAR2 Oracle Id Of The Person Loading The Data
100
MINIMUM_DEPTH NUMBER Minimum Depth Fished
100
MAXIMUM_DEPTH NUMBER Maximum Depth Fished
100
TRIP_TICKET_NUMBER VARCHAR2 Trip Ticket Number

Attribute Details

MONTH_LANDED

CC ID: 17231
Seq. Order: 1
Data Storage Type: VARCHAR2
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

wo Character Month Landed

General Data Type: VARCHAR2

YEAR_LANDED

CC ID: 17230
Seq. Order: 2
Data Storage Type: VARCHAR2
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

4 character Year Landed

General Data Type: VARCHAR2

STATE_LANDED

CC ID: 17229
Seq. Order: 3
Data Storage Type: VARCHAR2
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

State Code Landed. This is laways loaded with the NMFS STate Code For Puerto Rico.

General Data Type: VARCHAR2

FISHING_CENTER

CC ID: 17228
Seq. Order: 4
Data Storage Type: VARCHAR2
Max Length: 3
Required: No
Primary Key: No
Status: Active
Description:

Fishing Center Code.

General Data Type: VARCHAR2

DEALER

CC ID: 17227
Seq. Order: 5
Data Storage Type: VARCHAR2
Max Length: 9
Required: No
Primary Key: No
Status: Active
Description:

Dealer Code. Added For compatibility with other ALS Tables. This is column is always filled with all 9s as the Dealer is unknown.

General Data Type: VARCHAR2

WATER_BODY

CC ID: 17226
Seq. Order: 6
Data Storage Type: VARCHAR2
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

Water Body Code

General Data Type: VARCHAR2

GEAR

CC ID: 17225
Seq. Order: 7
Data Storage Type: VARCHAR2
Max Length: 3
Required: No
Primary Key: No
Status: Active
Description:

NMFS Gear Code (If One exists. It is generated between a cross table Of Erdman Gear Codes to NMFS Gear Code)

General Data Type: VARCHAR2

SPECIES

CC ID: 17224
Seq. Order: 8
Data Storage Type: VARCHAR2
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

NMFS Species Code (If One exists. It is generated between a cross table Of Erdman Speciesr Codes to NMFS Species Codes)

General Data Type: VARCHAR2

SHELL_OR_FINFISH

CC ID: 17223
Seq. Order: 9
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Finfish or shell fish code.

General Data Type: VARCHAR2

POUNDS

CC ID: 17222
Seq. Order: 10
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 9
Scale: 0
Status: Active
Description:

Pounds Caught. (Whole weight)

General Data Type: NUMBER

VALUE

CC ID: 17221
Seq. Order: 11
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 9
Scale: 0
Status: Active
Description:

Value in dollars

General Data Type: NUMBER

SECTION

CC ID: 17220
Seq. Order: 12
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Section Code, Added for compatibility with ALS.ALS_LANDINGS

General Data Type: VARCHAR2

PRICE

CC ID: 17219
Seq. Order: 13
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 7
Scale: 3
Status: Active
Description:

Price payed for fish. (In dollars)

General Data Type: NUMBER

DISTANCE

CC ID: 17218
Seq. Order: 14
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Distance From Shore Code. Added for compatibility with ALS.ALS_LANDINGS.

General Data Type: VARCHAR2

STATE_CAUGHT

CC ID: 17217
Seq. Order: 15
Data Storage Type: VARCHAR2
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

State Caught. Added For compatibility WIth ALS.ALS_LANDINGS

General Data Type: VARCHAR2

LANDING_DATE

CC ID: 17216
Seq. Order: 16
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

Actual Date animal was landed.

General Data Type: DATE

PR_ID_CODE

CC ID: 17215
Seq. Order: 17
Data Storage Type: VARCHAR2
Max Length: 6
Required: No
Primary Key: No
Status: Active
Description:

Identification Code asigned to Record by Puerto Rico data manager

General Data Type: VARCHAR2

PR_GEAR

CC ID: 17214
Seq. Order: 18
Data Storage Type: VARCHAR2
Max Length: 3
Required: No
Primary Key: No
Status: Active
Description:

Erdman Gear Code

General Data Type: VARCHAR2

NUMBER_OF_TRIPS

CC ID: 17213
Seq. Order: 19
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 2
Scale: 0
Status: Active
Description:

Number Of Trips

General Data Type: NUMBER

PR_SPECIES

CC ID: 17212
Seq. Order: 20
Data Storage Type: VARCHAR2
Max Length: 3
Required: No
Primary Key: No
Status: Active
Description:

Erdman Species Code

General Data Type: VARCHAR2

GEAR_QTY

CC ID: 17211
Seq. Order: 21
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 4
Scale: 0
Status: Active
Description:

Number Of Gear

General Data Type: NUMBER

GEAR_HOURS

CC ID: 17210
Seq. Order: 22
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 3
Scale: 0
Status: Active
Description:

Soak Time

General Data Type: NUMBER

DAY_LANDED

CC ID: 17209
Seq. Order: 23
Data Storage Type: VARCHAR2
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

Day landed. Derived from landing date

General Data Type: VARCHAR2

RNUMBER

CC ID: 17208
Seq. Order: 24
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 6
Scale: 0
Status: Active
Description:

Record Number

General Data Type: NUMBER

FILE_NAME

CC ID: 17207
Seq. Order: 25
Data Storage Type: VARCHAR2
Max Length: 30
Required: No
Primary Key: No
Status: Active
Description:

Sorce File used to load records

General Data Type: VARCHAR2

USERID

CC ID: 17206
Seq. Order: 26
Data Storage Type: VARCHAR2
Max Length: 30
Required: No
Primary Key: No
Status: Active
Description:

Oracle Id Of The Person Loading The Data

General Data Type: VARCHAR2

MINIMUM_DEPTH

CC ID: 17205
Seq. Order: 27
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 4
Scale: 0
Status: Active
Description:

Minimum Depth Fished

General Data Type: NUMBER

MAXIMUM_DEPTH

CC ID: 17204
Seq. Order: 28
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 4
Scale: 0
Status: Active
Description:

Maximum Depth Fished

General Data Type: NUMBER

TRIP_TICKET_NUMBER

CC ID: 17203
Seq. Order: 29
Data Storage Type: VARCHAR2
Max Length: 11
Required: No
Primary Key: No
Status: Active
Description:

Trip Ticket Number

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:

Use Published Metadata only.

Activity Log

Activity Log 1

CC ID: 355833
Activity Date/Time: 2016-11-03
Activity Type: Change column POUNDS format to NUMBER (9,3)
Responsible Party: Joshua Bennett
Description:

Changed column POUNDS format to match changes in ALS.ALS_LANDINGS_PUERTO_RICO and ALS.ALS_TEMP_LAND_PUERTO_RICO.

Catalog Details

Catalog Item ID: 5445
GUID: gov.noaa.nmfs.inport:5445
Metadata Record Created By: Lee M Weinberger
Metadata Record Created: 2007-10-16 05:43+0000
Metadata Record Last Modified By: Lee M Weinberger
Metadata Record Last Modified: 2021-05-06 22:24+0000
Metadata Record Published: 2021-05-06
Owner Org: SEFSC
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Next Review Date: 2022-05-07