PREYLEN
Entity (ENT) | Alaska Fisheries Science Center (AFSC)GUID: gov.noaa.nmfs.inport:22161 | Updated: August 9, 2022 | Published / External
Item Identification
Title: | PREYLEN |
---|---|
Short Name: | PREYLEN |
Status: | In Work |
Abstract: |
REEM North Pacific Groundfish Diet Data PreyLen Data Table |
Notes: |
Loaded by FGDC Metadata Uploader, batch 5084, 09-02-2014 16:45 |
Entity Information
Description: |
REEM North Pacific Groundfish Diet Data PreyLen Data Table |
---|
Data Attributes
Attribute Summary
![]() |
![]() |
Name | Type | Description |
---|---|---|---|---|
100
|
QUARTER | NUMBER | This is a one-digit numeric field with acceptable values of null, 1, 2, 3, 4. Quarter 1 represents January through March, quarter 2 represents April through June, quarter 3 represents July through September and quarter 4 represents October through December. | |
100
|
YEAR | NUMBER | This is a 4-digit numeric field that does not accept null values, acceptable values are any four-digit year | |
100
|
VESSEL | NUMBER | A 4-digit numeric field that does not accept null values, acceptable values are any vessel code. | |
100
|
CRUISE | NUMBER | A 4-digit numeric field that does not accept null values, acceptable values are any cruise code. | |
100
|
TYPE | NUMBER | A 1-digit numeric field that does not accept null values indicating the stomach analysis type performed to generate the associated data. | |
100
|
STA_ID_LET | CHAR | A 2-digit character field that allows null values or a station ID letter based on the RACE station grid. Bering Sea Data only. This field indicates the station ID letter from which the samples were collected. Not maintained, use Station_ID from the Haul table | |
100
|
STA_ID_NUM | NUMBER | A 2-digit character field that allows null values or a station ID number based on the RACE station grid. Bering Sea Data only. This field indicates the station ID number from which the samples were collected. Not maintained, use Station_ID from the Haul table. | |
100
|
SEQ_NUM | NUMBER | A 4-digit numeric field that allows null values. This represents the sequence number from the old pred-prey form used in the lab for quantitative analysis. Sequence number uniquely identified a record from a given stomach. These are currently not maintained. | |
100
|
HAUL | NUMBER | A 3-digit numeric field that does not allow null values representing the haul number from which the associated stomach data were collected. | |
100
|
PRED_SPECN | NUMBER | A 4-digit numeric field that does not allow null values. This is the predator specimen number assigned to the stomach when it was collected in the field. Prior to in-lab form data entry, this was a 2-digit number assigned in the lab at the time of analysis | |
100
|
PRED_NODC | NUMBER | A 10-digit numeric field that does not allow null values representing the NODC code for the predator from which the given data were collected. Consult REEM NODC code dictionary for definitions as some codes have been customized | |
100
|
PRED_LH | NUMBER | A 1-digit numeric field that allows null values representing the life history stage of the predator from which the stomachs were collected. Table 5 contains the acceptable values for this field. | |
100
|
PRED_LEN | NUMBER | A 4.1-digit numeric field that does not allow null values representing the fork length (cm) of the predator. | |
100
|
PRED_SEX | NUMBER | A 1-digit numeric field that allows null values representing the sex of the predator. Acceptable values are null, 1 indicating male, 2 indicating female or 3 indicating unsexed or juvenile. | |
100
|
PREY_NODC | NUMBER | A 10-digit numeric field that does not allow null values representing the NODC code for the prey item. Consult REEM NODC code dictionary for definitions as some codes have been customized | |
100
|
PREY_LH | CHAR | A 1-digit character field that allows null values representing the life history stage of the prey item. Table 6 contains the acceptable values for this field. | |
100
|
PREY_SZ1 | NUMBER | An 8.3-digit numeric field that does not allow null values representing the standard length (mm) of fish prey, carapace width (mm) of Majid crabs, or carapace length of Lithodid crabs. This is the primary prey size measurement | |
100
|
PREY_SZ2 | NUMBER | An 8.3-digit numeric field that allows null values representing the fork length (mm) of fish prey or carapace length (mm) of Majid crabs. This is a secondary prey size measurement. | |
100
|
PREY_SZ3 | NUMBER | An 8.3-digit numeric field that allows null values representing miscellaneous auxiliary prey size measurements. | |
100
|
EMPTY_1 | NUMBER | An 8.3-digit numeric field that allows null values. Unused. | |
100
|
PREY_SEX | NUMBER | A 1-digit numeric field that allows null values representing the sex of the prey. Acceptable values are null, 1 indicating male, 2 indicating female or 3 indicating unsexed or juvenile. A prey sex code of 5 may be used to indicate a fish length that was estimated with a method other than the Pollock otolith measurements as noted below. Values of 6-8 are used indicating the condition of walleye pollock otoliths used for estimating the length of the prey fish they were removed from. 6 indcating fair, 7 indicating good, and 8 indicating excellent. See the lab manual for a description of the protocol for using walleye pollock otoliths for estimating prey length. | |
100
|
HAULJOIN | NUMBER | A 12-digit numeric field that does not allow null values. Each hauljoin uniquely identifies a given vessel, cruise, haul combination. A foreign key to the haul table. | |
100
|
PREDJOIN | NUMBER | A 12-digit numeric field that uniquely identifies a given stomach sample. | |
100
|
PREYLENJOIN | NUMBER | A 12-digit numeric field that uniquely identifies a prey length record. |
Attribute Details
QUARTER
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is a one-digit numeric field with acceptable values of null, 1, 2, 3, 4. Quarter 1 represents January through March, quarter 2 represents April through June, quarter 3 represents July through September and quarter 4 represents October through December. |
Allowed Values: | 1 - 4 |
YEAR
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is a 4-digit numeric field that does not accept null values, acceptable values are any four-digit year |
Allowed Values: | 1981 - 2015 |
VESSEL
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 4-digit numeric field that does not accept null values, acceptable values are any vessel code. |
Allowed Values: | 1 - 7777 |
CRUISE
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 4-digit numeric field that does not accept null values, acceptable values are any cruise code. |
Allowed Values: | 11983 - 992009 |
TYPE
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 1-digit numeric field that does not accept null values indicating the stomach analysis type performed to generate the associated data. |
Allowed Values: | 2 - 9 |
STA_ID_LET
Data Storage Type: | CHAR |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 2-digit character field that allows null values or a station ID letter based on the RACE station grid. Bering Sea Data only. This field indicates the station ID letter from which the samples were collected. Not maintained, use Station_ID from the Haul table |
STA_ID_NUM
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 2-digit character field that allows null values or a station ID number based on the RACE station grid. Bering Sea Data only. This field indicates the station ID number from which the samples were collected. Not maintained, use Station_ID from the Haul table. |
Allowed Values: | 0 - 33 |
SEQ_NUM
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 4-digit numeric field that allows null values. This represents the sequence number from the old pred-prey form used in the lab for quantitative analysis. Sequence number uniquely identified a record from a given stomach. These are currently not maintained. |
Allowed Values: | 0 - 1242 |
HAUL
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 3-digit numeric field that does not allow null values representing the haul number from which the associated stomach data were collected. |
Allowed Values: | 1 - 3058 |
PRED_SPECN
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 4-digit numeric field that does not allow null values. This is the predator specimen number assigned to the stomach when it was collected in the field. Prior to in-lab form data entry, this was a 2-digit number assigned in the lab at the time of analysis |
Allowed Values: | 0 - 9880 |
PRED_NODC
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 10-digit numeric field that does not allow null values representing the NODC code for the predator from which the given data were collected. Consult REEM NODC code dictionary for definitions as some codes have been customized |
Allowed Values: | 8710010101 - 8857041901 |
PRED_LH
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 1-digit numeric field that allows null values representing the life history stage of the predator from which the stomachs were collected. Table 5 contains the acceptable values for this field. |
Allowed Values: | 0 - 8 |
PRED_LEN
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 4.1-digit numeric field that does not allow null values representing the fork length (cm) of the predator. |
Allowed Values: | 4.3 - 288 |
PRED_SEX
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 1-digit numeric field that allows null values representing the sex of the predator. Acceptable values are null, 1 indicating male, 2 indicating female or 3 indicating unsexed or juvenile. |
Allowed Values: | 1 - 3 |
PREY_NODC
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 10-digit numeric field that does not allow null values representing the NODC code for the prey item. Consult REEM NODC code dictionary for definitions as some codes have been customized |
Allowed Values: | 5.001e+09 - 9999999999 |
PREY_LH
Data Storage Type: | CHAR |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 1-digit character field that allows null values representing the life history stage of the prey item. Table 6 contains the acceptable values for this field. |
PREY_SZ1
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
An 8.3-digit numeric field that does not allow null values representing the standard length (mm) of fish prey, carapace width (mm) of Majid crabs, or carapace length of Lithodid crabs. This is the primary prey size measurement |
Allowed Values: | 0 - 710 |
PREY_SZ2
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
An 8.3-digit numeric field that allows null values representing the fork length (mm) of fish prey or carapace length (mm) of Majid crabs. This is a secondary prey size measurement. |
Allowed Values: | 0 - 570 |
PREY_SZ3
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
An 8.3-digit numeric field that allows null values representing miscellaneous auxiliary prey size measurements. |
Allowed Values: | 0 - 440 |
EMPTY_1
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
An 8.3-digit numeric field that allows null values. Unused. |
Allowed Values: | 0 - 49.5 |
PREY_SEX
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 1-digit numeric field that allows null values representing the sex of the prey. Acceptable values are null, 1 indicating male, 2 indicating female or 3 indicating unsexed or juvenile. A prey sex code of 5 may be used to indicate a fish length that was estimated with a method other than the Pollock otolith measurements as noted below. Values of 6-8 are used indicating the condition of walleye pollock otoliths used for estimating the length of the prey fish they were removed from. 6 indcating fair, 7 indicating good, and 8 indicating excellent. See the lab manual for a description of the protocol for using walleye pollock otoliths for estimating prey length. |
Allowed Values: | 0 - 8 |
HAULJOIN
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 12-digit numeric field that does not allow null values. Each hauljoin uniquely identifies a given vessel, cruise, haul combination. A foreign key to the haul table. |
Allowed Values: | 651234 - 11135973 |
PREDJOIN
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 12-digit numeric field that uniquely identifies a given stomach sample. |
Allowed Values: | 999996 - 11138912 |
PREYLENJOIN
Data Storage Type: | NUMBER |
---|---|
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A 12-digit numeric field that uniquely identifies a prey length record. |
Allowed Values: | 10873939 - 10991339 |
Catalog Details
Catalog Item ID: | 22161 |
---|---|
GUID: | gov.noaa.nmfs.inport:22161 |
Metadata Record Created By: | Angie Greig |
Metadata Record Created: | 2014-09-02 16:45+0000 |
Metadata Record Last Modified By: | SysAdmin InPortAdmin |
Metadata Record Last Modified: | 2022-08-09 17:11+0000 |
Metadata Record Published: | 2016-04-19 |
Owner Org: | AFSC |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2016-04-19 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2017-04-19 |