Column Notes for Striped Marlin Hardparts and Gonads Collected by the Hawaii LOP.
Entity (ENT) | Pacific Islands Fisheries Science Center (PIFSC)GUID: gov.noaa.nmfs.inport:11761 | Updated: August 9, 2022 | Published / External
Item Identification
Title: | Column Notes for Striped Marlin Hardparts and Gonads Collected by the Hawaii LOP. |
---|---|
Status: | In Work |
Abstract: |
Column Notes describing what is included in the striped marlin (Tetrapturus audax) hardparts and gonad database, Collected by the PIRO Hawaii Longline Observer Program (LOP). |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
UNCONTROLLED | |
None | Dorsal Spines |
None | EFL |
None | Gender |
None | Gonads |
None | Hawaiian Longline Observer Program |
None | Histology |
None | Otoliths |
None | PIRO |
None | Striped Marlin |
None | tetrapturus audax |
Spatial Keywords
Thesaurus | Keyword |
---|---|
UNCONTROLLED | |
None | central North Pacific |
None | Hawaii |
Physical Location
Organization: | Pacific Islands Fisheries Science Center |
---|---|
City: | Honolulu |
State/Province: | HI |
Country: | USA |
Location Description: |
The Life History Program has relocated to the Honolulu IRC facility on Ford Island hence; most data sets are stored there. |
Entity Information
Entity Type: | Data Table |
---|---|
Description: |
Striped Marlin (Tetrapturus audax) Hardparts and Gonads Collected by the PIRO Hawaii Longline Observer Program. |
Data Attributes
Attribute Summary
Name | Type | Description | ||
---|---|---|---|---|
100
|
LONGLINE_TRIP_NUM | VARCHAR | The longline trip number the specimen was caught during; this should be written onto the specimen identification tag as part of the fish data num. | |
100
|
SET | NUMBER | The set number of a particular trip the specimen was caught during; this should be written onto the specimen identification tag as part of the fish data num. | |
100
|
PAGE | NUMBER | The catch event page number; this should be written onto the specimen identification tag as part of the fish data num. | |
100
|
LINE | NUMBER | The catch event line number; this should be written onto the specimen identification tag as part of the fish data num. | |
100
|
SPECIMEN_NUM_COMMENTS | VARCHAR | Any comments about the specimen number. There were a lot of discrepancies between the written specimen tag numbers and what was entered into Data Trawler. Identified differences between hand-written tag and what was entered into Data Trawler is noted here. | |
100
|
FISH_DATA_NUM | VARCHAR | AKA the SPECIMEN_ID, it is a combination of the Longline Trip Num, Set, Page, and Line Number. This is the unique identifier for the specimen, if there are discrepancies or uncertainties about the integrity of the Longline Trip Num, Set, Page, or Line, the data may be unreliable. | |
100
|
DATA_MISSING_OR_INCORRECT_YN | CHAR | Were there discrepancies between what was written on the specimen tag and what was entered into Data Trawler? Is there important information about a particular specimen missing? Yes (Y) or no (N)? | |
100
|
COLLECTION_DATE_BEGIN_HAUL | DATE | The begin haul date of the set the specimen was caught is used for the collection date. If not available on the specimen tag, the collection date/begin haul date is found by looking up the specimen ID in Data Trawler. | |
100
|
LENGTH_EFL_CM | NUMBER | The EFL (eye to fork length) measured at sea by an observer recorded in centimeters. If not available on the specimen tag, the EFL can be found by looking up the SPECIEMN_ID in Data Trawler. | |
100
|
LENGTH_COMMENTS | VARCHAR | Comments about the length of the specimen such as differences between the value written on the tag and the value entered into Data Trawler. | |
100
|
CATCH_LOCATION_BEG_HAUL_LAT_DEC_DEG | NUMBER | The latitude of the begin haul of the set the specimen was caught is recorded for the catch location in decimal degrees. The catch location begin haul latitude is found by looking up the SPECIMEN_ID in Data Trawler. | |
100
|
CATCH_LOCATION_BEG_HAUL_LONG_DEC_DEG | NUMBER | The longitude of the begin haul of the set the specimen was caught is recorded for the catch location in decimal degrees. The catch location begin haul longitude is found by looking up the specimen ID in Data Trawler. | |
100
|
4TH_DORSAL_SPINE_EXTRACTED_YNU | CHAR | Was the 4th dorsal spine from this specimen extracted and brought to the Aiea lab for processing, yes (Y), no (N), or unknown (U)? | |
100
|
5TH_DORSAL_SPINE_EXTRACTED_YNU | CHAR | Was the 5th dorsal spine from this specimen extracted and brought to the Aiea lab for processing, yes (Y), no (N), or unknown (U)? | |
100
|
DF_RAYS_GIVEN_TO_KOPF_YN | CHAR | Were the 4th and/or 5th dorsal spines sent to Dr. Keller Kopf for age and growth work, yes (Y), no (N), or unknown (U)? | |
100
|
SAGITTAE | NUMBER | The number of sagittae successfully extracted from the specimen. | |
100
|
LAPILLAE | NUMBER | The number of lapillae successfully extracted from the specimen. | |
100
|
ASTERI | NUMBER | The number of asteri successfully extracted from the specimen. | |
100
|
VISUAL_GENDER_ID_MFU | CHAR | The gender of the fish determined visually either male (M), female (F), or unknown (U) should be entered here. | |
100
|
TOTAL_GONAD_WEIGHT_G | NUMBER | The weight of the whole gonad in grams. | |
100
|
TOTAL_GONAD_WEIGHT_KG | NUMBER | The weight of the whole gonad in kilograms. | |
100
|
RIGHT_LOBE_GONAD_WEIGHT_G | NUMBER | The weight of the right lobe of the gonad in grams. | |
100
|
LEFT_LOBE_GONAD_WEIGHT_G | NUMBER | The weight of the left lobe of the gonad in grams. | |
100
|
DATE_FIXED_IN_FORMALIN | DATE | The date that the gonads were fixed in formalin by the Life History Program (LHP) staff at the Aiea lab. | |
100
|
FROZEN_TO_FORMALIN_FIXED_YN | CHAR | The date that the gonads were fixed in formalin by the Life History Program (LHP) staff at the Aiea lab after they were stored frozen at sea. | |
100
|
GLYO_FIXX_AT_SEA_YNU | CHAR | Were the gonads fixed in Glyo Fixx by an observer at sea, yes (Y), no (N), or unknown (U)? | |
100
|
HISTO_SLIDE_CREATED_YNU | CHAR | Was a cross sectioned fragment of the collected gonad sent to John Burns Medical School for creation of a histological microscope slide, yes (Y), no (N), unknown (U)? | |
100
|
HISTO_GENDER_ID_MFU | CHAR | If a histological slide was created, the gender determined using the information found on the slide, male (M), female (F), unknown (U). | |
100
|
GENERAL_COMMENTS | VARCHAR | Any comments about the specimen. There were a lot of discrepancies between what was recorded on the specimen tag and the data entered into Data Trawler, these difference are noted here. |
Attribute Details
LONGLINE_TRIP_NUM
Seq. Order: | 1 |
---|---|
Data Storage Type: | VARCHAR |
Max Length: | 10 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The longline trip number the specimen was caught during; this should be written onto the specimen identification tag as part of the fish data num. |
Null Value: | Yes |
Null Value Meaning: |
There is a discrepancy in the data and the longline trip number written on the specimen tag does not match what was entered into Data Trawler or no information was recorded. |
SET
Seq. Order: | 2 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The set number of a particular trip the specimen was caught during; this should be written onto the specimen identification tag as part of the fish data num. |
Null Value: | Yes |
Null Value Meaning: |
There is a discrepancy in the data and the set number written on the specimen tag does not match what was entered into Data Trawler or no information was recorded. |
PAGE
Seq. Order: | 3 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The catch event page number; this should be written onto the specimen identification tag as part of the fish data num. |
Null Value: | Yes |
Null Value Meaning: |
There is a discrepancy in the data, the page number written on the specimen tag does not match what was entered into data trawler, or no information was recorded. |
LINE
Seq. Order: | 4 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The catch event line number; this should be written onto the specimen identification tag as part of the fish data num. |
Null Value: | Yes |
Null Value Meaning: |
There is a discrepancy in the data, the line number written on the specimen tag does not match what was entered into Data Trawler, or no information was recorded. |
SPECIMEN_NUM_COMMENTS
Seq. Order: | 5 |
---|---|
Data Storage Type: | VARCHAR |
Max Length: | 100 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Any comments about the specimen number. There were a lot of discrepancies between the written specimen tag numbers and what was entered into Data Trawler. Identified differences between hand-written tag and what was entered into Data Trawler is noted here. |
Null Value: | Yes |
Null Value Meaning: |
There were no comments or discrepancies about the specimen number worth noting. |
FISH_DATA_NUM
Seq. Order: | 6 |
---|---|
Data Storage Type: | VARCHAR |
Max Length: | 20 |
Required: | No |
Primary Key: | Yes |
Status: | Active |
Description: |
AKA the SPECIMEN_ID, it is a combination of the Longline Trip Num, Set, Page, and Line Number. This is the unique identifier for the specimen, if there are discrepancies or uncertainties about the integrity of the Longline Trip Num, Set, Page, or Line, the data may be unreliable. |
Null Value: | Yes |
Null Value Meaning: |
This is the unique identifier for all specimens, but some specimens don't have a valid fish data number, if this is the case, there will be a note in the SPECIMEN_NUM_COMMENTS. |
DATA_MISSING_OR_INCORRECT_YN
Seq. Order: | 7 |
---|---|
Data Storage Type: | CHAR |
Max Length: | 1 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Were there discrepancies between what was written on the specimen tag and what was entered into Data Trawler? Is there important information about a particular specimen missing? Yes (Y) or no (N)? |
Null Value: | No |
Null Value Meaning: |
The data is either in good shape or variations exist between what is written on the specimen tag and what has been entered into Data Trawler, if the answer to this is yes (Y), the data may be unreliable. |
Allowed Values: | Y, N |
COLLECTION_DATE_BEGIN_HAUL
Seq. Order: | 8 |
---|---|
Data Storage Type: | DATE |
Max Length: | 8 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The begin haul date of the set the specimen was caught is used for the collection date. If not available on the specimen tag, the collection date/begin haul date is found by looking up the specimen ID in Data Trawler. |
Null Value: | Yes |
Null Value Meaning: |
The date is unknown or was not recorded. |
LENGTH_EFL_CM
Seq. Order: | 9 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 6 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The EFL (eye to fork length) measured at sea by an observer recorded in centimeters. If not available on the specimen tag, the EFL can be found by looking up the SPECIEMN_ID in Data Trawler. |
Null Value: | Yes |
Null Value Meaning: |
The EFL is unknown or was not recorded. |
LENGTH_COMMENTS
Seq. Order: | 10 |
---|---|
Data Storage Type: | VARCHAR |
Max Length: | 100 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Comments about the length of the specimen such as differences between the value written on the tag and the value entered into Data Trawler. |
Null Value: | Yes |
Null Value Meaning: |
No comments on the length are worth noting. |
CATCH_LOCATION_BEG_HAUL_LAT_DEC_DEG
Seq. Order: | 11 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 10 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The latitude of the begin haul of the set the specimen was caught is recorded for the catch location in decimal degrees. The catch location begin haul latitude is found by looking up the SPECIMEN_ID in Data Trawler. |
Null Value: | Yes |
Null Value Meaning: |
The Fish Data Number is invalid, the latitude of the catch location wasn't recorded, or the latitude is unknown. |
CATCH_LOCATION_BEG_HAUL_LONG_DEC_DEG
Seq. Order: | 12 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 10 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The longitude of the begin haul of the set the specimen was caught is recorded for the catch location in decimal degrees. The catch location begin haul longitude is found by looking up the specimen ID in Data Trawler. |
Null Value: | Yes |
Null Value Meaning: |
The Fish Data Number is invalid, the longitude of the catch location wasn't recorded, or is unknown. |
4TH_DORSAL_SPINE_EXTRACTED_YNU
Seq. Order: | 13 |
---|---|
Data Storage Type: | CHAR |
Max Length: | 1 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Was the 4th dorsal spine from this specimen extracted and brought to the Aiea lab for processing, yes (Y), no (N), or unknown (U)? |
Null Value: | No |
Null Value Meaning: |
It is either known or unknown if the 4th dorsal spine was collected. |
Allowed Values: | Y, N, U |
5TH_DORSAL_SPINE_EXTRACTED_YNU
Seq. Order: | 14 |
---|---|
Data Storage Type: | CHAR |
Max Length: | 1 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Was the 5th dorsal spine from this specimen extracted and brought to the Aiea lab for processing, yes (Y), no (N), or unknown (U)? |
Null Value: | No |
Null Value Meaning: |
It is either known or unknown if the 5th dorsal spine was collected. |
Allowed Values: | Y, N, U |
DF_RAYS_GIVEN_TO_KOPF_YN
Seq. Order: | 15 |
---|---|
Data Storage Type: | CHAR |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Were the 4th and/or 5th dorsal spines sent to Dr. Keller Kopf for age and growth work, yes (Y), no (N), or unknown (U)? |
Null Value: | No |
Null Value Meaning: |
It is either known or unknown if the dorsal spines were sent to Dr. Keller Kopf. |
Allowed Values: | Y, N, U |
SAGITTAE
Seq. Order: | 16 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The number of sagittae successfully extracted from the specimen. |
Null Value: | No |
Null Value Meaning: |
Either 0, 1, or 2 sagittae can be extracted. |
Allowed Values: | 0, 1, 2 |
LAPILLAE
Seq. Order: | 17 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The number of lapillae successfully extracted from the specimen. |
Null Value: | No |
Null Value Meaning: |
Either 0, 1, or 2 lapillae can be extracted. |
Allowed Values: | 0, 1, 2 |
ASTERI
Seq. Order: | 18 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The number of asteri successfully extracted from the specimen. |
Null Value: | No |
Null Value Meaning: |
Either 0, 1, or 2 asteri can be extracted. |
Allowed Values: | 0, 1, 2 |
VISUAL_GENDER_ID_MFU
Seq. Order: | 19 |
---|---|
Data Storage Type: | CHAR |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The gender of the fish determined visually either male (M), female (F), or unknown (U) should be entered here. |
Null Value: | No |
Null Value Meaning: |
The gender is either male, female, or unknown. |
Allowed Values: | M, F, U |
TOTAL_GONAD_WEIGHT_G
Seq. Order: | 20 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 6 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The weight of the whole gonad in grams. |
Null Value: | Yes |
Null Value Meaning: |
The gonad weight was not taken or was not recorded. |
TOTAL_GONAD_WEIGHT_KG
Seq. Order: | 21 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 6 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The weight of the whole gonad in kilograms. |
Null Value: | Yes |
Null Value Meaning: |
The gonad weight was not taken or was not recorded. |
RIGHT_LOBE_GONAD_WEIGHT_G
Seq. Order: | 22 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 6 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The weight of the right lobe of the gonad in grams. |
Null Value: | Yes |
Null Value Meaning: |
The gonad weight of the right lobe was not taken or was not recorded. |
LEFT_LOBE_GONAD_WEIGHT_G
Seq. Order: | 23 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 6 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The weight of the left lobe of the gonad in grams. |
Null Value: | Yes |
Null Value Meaning: |
The gonad weight of the left lobe was not taken or was not recorded. |
DATE_FIXED_IN_FORMALIN
Seq. Order: | 24 |
---|---|
Data Storage Type: | DATE |
Max Length: | 8 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The date that the gonads were fixed in formalin by the Life History Program (LHP) staff at the Aiea lab. |
Null Value: | Yes |
Null Value Meaning: |
No gonads were collected from this specimen, the gonads were not fixed in formalin, or the date was not recorded. |
FROZEN_TO_FORMALIN_FIXED_YN
Seq. Order: | 25 |
---|---|
Data Storage Type: | CHAR |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The date that the gonads were fixed in formalin by the Life History Program (LHP) staff at the Aiea lab after they were stored frozen at sea. |
Null Value: | Yes |
Null Value Meaning: |
No gonads were collected from this specimen, the gonads were not fixed in formalin, previously stored frozen, or the date was not recorded. |
GLYO_FIXX_AT_SEA_YNU
Seq. Order: | 26 |
---|---|
Data Storage Type: | CHAR |
Max Length: | 1 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Were the gonads fixed in Glyo Fixx by an observer at sea, yes (Y), no (N), or unknown (U)? |
Null Value: | No |
Null Value Meaning: |
The gonads either were or were not fixed in Glyo Fixx at sea or it is unknown if the gonads were fixed in Glyo Fixx. |
Allowed Values: | Y, N, U |
HISTO_SLIDE_CREATED_YNU
Seq. Order: | 27 |
---|---|
Data Storage Type: | CHAR |
Max Length: | 1 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Was a cross sectioned fragment of the collected gonad sent to John Burns Medical School for creation of a histological microscope slide, yes (Y), no (N), unknown (U)? |
Null Value: | No |
Null Value Meaning: |
A histological slide either was or was not created or it is not known if a slide was created. |
Allowed Values: | Y, N, U |
HISTO_GENDER_ID_MFU
Seq. Order: | 28 |
---|---|
Data Storage Type: | CHAR |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
If a histological slide was created, the gender determined using the information found on the slide, male (M), female (F), unknown (U). |
Null Value: | Yes |
Null Value Meaning: |
Could be blank if a histological slide was not created. |
Allowed Values: | M, F, U |
GENERAL_COMMENTS
Seq. Order: | 29 |
---|---|
Data Storage Type: | VARCHAR |
Max Length: | 500 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Any comments about the specimen. There were a lot of discrepancies between what was recorded on the specimen tag and the data entered into Data Trawler, these difference are noted here. |
Null Value: | Yes |
Null Value Meaning: |
There were no additional comments about the specimen. |
Catalog Details
Catalog Item ID: | 11761 |
---|---|
GUID: | gov.noaa.nmfs.inport:11761 |
Metadata Record Created By: | Meagan A Sundberg |
Metadata Record Created: | 2012-02-13 22:42+0000 |
Metadata Record Last Modified By: | SysAdmin InPortAdmin |
Metadata Record Last Modified: | 2022-08-09 17:11+0000 |
Metadata Record Published: | 2019-07-23 |
Owner Org: | PIFSC |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2019-07-23 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2020-07-23 |