Search Help Show/Hide Menu
Summary
Item Identification
Entity Info
Data Attributes
Catalog Details

Summary

Abstract

Prey Length data

Description

Prey Length data

Entity Information

Entity Type
Data Table

Data Attribute / Type Description
CRUISE6
VARCHAR2
Code uniquely identifying cruise. The first four digits indicate the year and the last two digit uniquely identify the cruise within the year.
CRUISE
VARCHAR2
Cruise code - first to digits reflect year and second 2 are numbers sequentially assigned to indicate the order in which the cruises were coded.
STATION
VARCHAR2
Unique sequential order in which stations have been completed. Hangups and short tows each receive a non-repeated consecutive number.
SVSPP
VARCHAR2
A three digit alphanumeric filed used to code each species caught in a trawl or dredge. Refer to the svdbs.svspecies_list table for all 3 digit species codes.
PDSEX
VARCHAR2
Predator sex code: 0=unknown, 1=male, 2=female, 4=transitional.
PDID
NUMBER
Predator ID number beginning in 1991.
LOGNUM
VARCHAR2
Prior to 1991, unique number assigned to each predator. In 1991 the LOGNUM was replaced with PDID.
PYSPP
VARCHAR2
Prey species name.
PYLEN
NUMBER
Prey length in millimeters
PYLEST
VARCHAR2
Prey length was estimated if value = E, actual length = N.
PYNAM
VARCHAR2
Prey scientific name.
PREYLEN_COMMENT
VARCHAR2
Comments on individual prey lengths.
DOC
DATE
Date when the current record was updated or changed. Date format (MM/DD/YY HH:MI:SS).
DOE
DATE
Date when record was inserted into Oracle. Date format (MM/DD/YY HH:MI:SS).
UOE
VARCHAR2
The Oracle username of the individual who entered the new record.
UOC
VARCHAR2
The Oracle username of the individual who changed the current record.

Child Items

No Child Items for this record.

Contact Information

No contact information is available for this record.

Please contact the owner organization (NEFSC) for inquiries on this record.

Item Identification

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

Prey Length data

Notes:

Loaded by batch 8930, 07-01-2016 13:03

Entity Information

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

Prey Length data

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
CRUISE6 VARCHAR2 Code uniquely identifying cruise. The first four digits indicate the year and the last two digit uniquely identify the cruise within the year.
100
CRUISE VARCHAR2 Cruise code - first to digits reflect year and second 2 are numbers sequentially assigned to indicate the order in which the cruises were coded.
100
STATION VARCHAR2 Unique sequential order in which stations have been completed. Hangups and short tows each receive a non-repeated consecutive number.
100
SVSPP VARCHAR2 A three digit alphanumeric filed used to code each species caught in a trawl or dredge. Refer to the svdbs.svspecies_list table for all 3 digit species codes.
100
PDSEX VARCHAR2 Predator sex code: 0=unknown, 1=male, 2=female, 4=transitional.
100
PDID NUMBER Predator ID number beginning in 1991.
100
LOGNUM VARCHAR2 Prior to 1991, unique number assigned to each predator. In 1991 the LOGNUM was replaced with PDID.
100
PYSPP VARCHAR2 Prey species name.
100
PYLEN NUMBER Prey length in millimeters
100
PYLEST VARCHAR2 Prey length was estimated if value = E, actual length = N.
100
PYNAM VARCHAR2 Prey scientific name.
100
PREYLEN_COMMENT VARCHAR2 Comments on individual prey lengths.
100
DOC DATE Date when the current record was updated or changed. Date format (MM/DD/YY HH:MI:SS).
100
DOE DATE Date when record was inserted into Oracle. Date format (MM/DD/YY HH:MI:SS).
100
UOE VARCHAR2 The Oracle username of the individual who entered the new record.
100
UOC VARCHAR2 The Oracle username of the individual who changed the current record.

Attribute Details

CRUISE6

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

Code uniquely identifying cruise. The first four digits indicate the year and the last two digit uniquely identify the cruise within the year.

General Data Type: VARCHAR2

CRUISE

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

Cruise code - first to digits reflect year and second 2 are numbers sequentially assigned to indicate the order in which the cruises were coded.

General Data Type: VARCHAR2

STATION

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

Unique sequential order in which stations have been completed. Hangups and short tows each receive a non-repeated consecutive number.

General Data Type: VARCHAR2

SVSPP

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

A three digit alphanumeric filed used to code each species caught in a trawl or dredge. Refer to the svdbs.svspecies_list table for all 3 digit species codes.

General Data Type: VARCHAR2

PDSEX

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

Predator sex code: 0=unknown, 1=male, 2=female, 4=transitional.

General Data Type: VARCHAR2

PDID

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

Predator ID number beginning in 1991.

General Data Type: NUMBER

LOGNUM

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

Prior to 1991, unique number assigned to each predator. In 1991 the LOGNUM was replaced with PDID.

General Data Type: VARCHAR2

PYSPP

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

Prey species name.

General Data Type: VARCHAR2

PYLEN

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

Prey length in millimeters

General Data Type: NUMBER

PYLEST

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

Prey length was estimated if value = E, actual length = N.

General Data Type: VARCHAR2

PYNAM

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

Prey scientific name.

General Data Type: VARCHAR2

PREYLEN_COMMENT

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

Comments on individual prey lengths.

General Data Type: VARCHAR2

DOC

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

Date when the current record was updated or changed. Date format (MM/DD/YY HH:MI:SS).

General Data Type: DATE

DOE

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

Date when record was inserted into Oracle. Date format (MM/DD/YY HH:MI:SS).

General Data Type: DATE

UOE

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

The Oracle username of the individual who entered the new record.

General Data Type: VARCHAR2

UOC

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

The Oracle username of the individual who changed the current record.

General Data Type: VARCHAR2

Catalog Details

Catalog Item ID: 33192
GUID: gov.noaa.nmfs.inport:33192
Metadata Record Created By: Patricia L Jones
Metadata Record Created: 2016-07-01 13:03+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+0000
Metadata Record Published: 2017-02-27
Owner Org: NEFSC
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2017-02-27
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2018-02-27