Table: TALS_GCANV6071
Southeast Fisheries Science Center
Entity
(ENT)
| ID: 5442
| Published / External
Created: 2007-10-16
|
Last Modified: 2022-08-09
Data Set (DS) | ID: 1917
ID: 5442
Entity (ENT)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | Table: TALS_GCANV6071 |
---|---|
Short Name | TALS_GCANV6071 |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | |
* » Abstract |
This table contains historical annual landings data from 1962 through 1971. Please remember that this data are also available in fsrayg.gencan_r45@shark (on the SHARK on the DC machine.) |
* Purpose | |
Notes |
Loaded by batch 1723, 10-16-2007 04:06. |
Other Citation Details | |
• Supplemental Information |
These landings are reported on forms which contain pre-printed species. Generally the species listed on the form reflect the species of interest of the State Agency as well as NMFS and they vary from state to state. Space is generally provided for 'write-in' species; however, it is probable that bias exists favoring the entry of the pre-printed species. |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
None | annual data |
None | landings |
Temporal Keywords
Thesaurus | Keyword |
---|---|
None | 1962-1971 |
* Spatial Keywords
Thesaurus | Keyword |
---|---|
None | alabama |
None | florida |
None | georgia |
None | louisiana |
None | mississippi |
None | north carolina |
None | south carolins |
None | texas |
Stratum Keywords
Thesaurus | Keyword |
---|---|
None | county |
None | gear |
None | species |
None | state |
None | waterbody |
Instrument Keywords
Thesaurus | Keyword |
---|---|
Platform Keywords
Thesaurus | Keyword |
---|---|
Physical Location
• » Organization | Southeast Fisheries Science Center |
---|---|
• » City | Miami |
• » State/Province | FL |
• Country | USA |
• » Location Description |
75 Virginia Beach Drive Miami, FL 33149 |
Entity Information
Entity Type | Data Table |
---|---|
Active Version? | Y |
Alias | |
Schema Name | ALS |
» Description |
This table contains historical annual landings data from 1962 through 1971. Please remember that this data are also available in fsrayg.gencan_r45@shark (on the SHARK on the DC machine.) |
Change Summary |
Data Attributes
Attribute Summary
Score | Req'd? | PKey? | » Name | Data Storage Type | Description |
---|---|---|---|---|---|
100 | No | No | MONTHLAND | VARCHAR2 | In this table there are no monthly data. The code '13' is used to indicate annual landings. |
100 | No | No | YEARLAND | VARCHAR2 | The Year Landed. |
100 | No | No | ALSSTATE | VARCHAR2 | The NMFS State Code of where the fish was landed. Florida has coastal codes of '10' (Atlantic), '11' (Gulf), '12' (Interior). |
100 | No | No | ALSCTYIN | VARCHAR2 | The three character county code. |
100 | No | No | NMFSCOUNTY | VARCHAR2 | The two character NMFS County Code. |
100 | No | No | WATERBODY | VARCHAR2 | The Water Body Code. Has been updated from the old state-dependent system to the Gulf grid / South Atlantic shrimp system coding. Previous code contained in the old_waterbody column. |
100 | No | No | NMFSGEAR | VARCHAR2 | The NMFS Gear Code. |
100 | No | No | NMFS_CODE | VARCHAR2 | The NMFS Species Code. |
100 | No | No | POUNDS | NUMBER | The whole weight in pounds except for Florida which lists the landed weight in pounds. For non-shrimp species weights are rounded to nearest even hundreds of pounds. |
100 | No | No | VALUE | NUMBER | The Value (in Dollars) |
100 | No | No | XPRICE | VARCHAR2 | The ex-vessel price. This column has an implied decimal in the second position. The price 0100 should read 0.100. |
100 | No | No | COMMON | VARCHAR2 | The common name of the species landed. Names are not consistent within this column. It is recommended that the table be joined by NMFS_CODE to the SPECIES_CODE_NMFS table for consistent reporting by name. |
100 | No | No | DISTANCE | VARCHAR2 | The Distance From Shore Code. Distance codes of '0' are supposed to represent inshore waters; however, it appears from examination of the catch that code of '0' was used as a place-holder in many instances. |
100 | No | No | STATECAUGHT | VARCHAR2 | This column is not to be used. |
100 | No | No | HOWFIGURED | VARCHAR2 | A code to indicate how the price was figured for Florida data. This column is null in this table. |
100 | No | No | WHICHONE | VARCHAR2 | Gives the source of the data. Codes are alpha-state initials except for 'GS' which stands for 'Gulf Shrimp' and indicates records originating from the Gulf Shrimp Survey data set. |
100 | No | No | REGION | VARCHAR2 | The Region Code. Indicates general region of landing. '4' is for Southern US Atlantic Waters (NC - Florida East Coast). '5' is for Gulf of Mexico. |
100 | No | No | OLD_WATERBODY | VARCHAR2 | Waterbody Code that originally was on the record prior to the comprehensive water code update. See ALS_WATERBODY_OLD_NEW_XREF for details. |
100 | No | No | UNFACTORED_WEIGHT_FDEP | NUMBER | Unfactored Weight From FLorida. This column had been added for compatibility purposes with other Landings Tables, but is not used in this table. |
100 | No | No | PRICE | NUMBER | This column is null. |
100 | No | No | CONVERSION | NUMBER | Conversion Factor Between Unfactored Weight From Florida and NMFS Species Weight. Provided for compatbility purposes with other tables. This column is not used for this application |
Attribute Details
Attribute Name | MONTHLAND |
---|---|
Seq. Order | 1 |
Data Storage Type | VARCHAR2 |
Max Length | 2 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
In this table there are no monthly data. The code '13' is used to indicate annual landings. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | YEARLAND |
---|---|
Seq. Order | 2 |
Data Storage Type | VARCHAR2 |
Max Length | 4 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
The Year Landed. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | ALSSTATE |
---|---|
Seq. Order | 3 |
Data Storage Type | VARCHAR2 |
Max Length | 2 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
The NMFS State Code of where the fish was landed. Florida has coastal codes of '10' (Atlantic), '11' (Gulf), '12' (Interior). |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | ALSCTYIN |
---|---|
Seq. Order | 4 |
Data Storage Type | VARCHAR2 |
Max Length | 3 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
The three character county code. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | NMFSCOUNTY |
---|---|
Seq. Order | 5 |
Data Storage Type | VARCHAR2 |
Max Length | 2 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
The two character NMFS County Code. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | WATERBODY |
---|---|
Seq. Order | 6 |
Data Storage Type | VARCHAR2 |
Max Length | 4 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
The Water Body Code. Has been updated from the old state-dependent system to the Gulf grid / South Atlantic shrimp system coding. Previous code contained in the old_waterbody column. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | NMFSGEAR |
---|---|
Seq. Order | 7 |
Data Storage Type | VARCHAR2 |
Max Length | 3 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
The NMFS Gear Code. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | NMFS_CODE |
---|---|
Seq. Order | 8 |
Data Storage Type | VARCHAR2 |
Max Length | 4 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
The NMFS Species Code. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | POUNDS |
---|---|
Seq. Order | 9 |
Data Storage Type | NUMBER |
Max Length | 22 |
Min Length | |
Required | No |
Primary Key | No |
Precision | 9 |
Scale | 0 |
Status | Active |
Description |
The whole weight in pounds except for Florida which lists the landed weight in pounds. For non-shrimp species weights are rounded to nearest even hundreds of pounds. |
General Data Type | NUMBER |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | VALUE |
---|---|
Seq. Order | 10 |
Data Storage Type | NUMBER |
Max Length | 22 |
Min Length | |
Required | No |
Primary Key | No |
Precision | 9 |
Scale | 0 |
Status | Active |
Description |
The Value (in Dollars) |
General Data Type | NUMBER |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | XPRICE |
---|---|
Seq. Order | 11 |
Data Storage Type | VARCHAR2 |
Max Length | 4 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
The ex-vessel price. This column has an implied decimal in the second position. The price 0100 should read 0.100. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | COMMON |
---|---|
Seq. Order | 12 |
Data Storage Type | VARCHAR2 |
Max Length | 21 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
The common name of the species landed. Names are not consistent within this column. It is recommended that the table be joined by NMFS_CODE to the SPECIES_CODE_NMFS table for consistent reporting by name. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | DISTANCE |
---|---|
Seq. Order | 13 |
Data Storage Type | VARCHAR2 |
Max Length | 1 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
The Distance From Shore Code. Distance codes of '0' are supposed to represent inshore waters; however, it appears from examination of the catch that code of '0' was used as a place-holder in many instances. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | STATECAUGHT |
---|---|
Seq. Order | 14 |
Data Storage Type | VARCHAR2 |
Max Length | 2 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
This column is not to be used. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | HOWFIGURED |
---|---|
Seq. Order | 15 |
Data Storage Type | VARCHAR2 |
Max Length | 2 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
A code to indicate how the price was figured for Florida data. This column is null in this table. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | WHICHONE |
---|---|
Seq. Order | 16 |
Data Storage Type | VARCHAR2 |
Max Length | 2 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
Gives the source of the data. Codes are alpha-state initials except for 'GS' which stands for 'Gulf Shrimp' and indicates records originating from the Gulf Shrimp Survey data set. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | REGION |
---|---|
Seq. Order | 17 |
Data Storage Type | VARCHAR2 |
Max Length | 2 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
The Region Code. Indicates general region of landing. '4' is for Southern US Atlantic Waters (NC - Florida East Coast). '5' is for Gulf of Mexico. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | OLD_WATERBODY |
---|---|
Seq. Order | 18 |
Data Storage Type | VARCHAR2 |
Max Length | 4 |
Min Length | |
Required | No |
Primary Key | No |
Precision | |
Scale | |
Status | Active |
Description |
Waterbody Code that originally was on the record prior to the comprehensive water code update. See ALS_WATERBODY_OLD_NEW_XREF for details. |
General Data Type | VARCHAR2 |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | UNFACTORED_WEIGHT_FDEP |
---|---|
Seq. Order | 19 |
Data Storage Type | NUMBER |
Max Length | 22 |
Min Length | |
Required | No |
Primary Key | No |
Precision | 9 |
Scale | 0 |
Status | Active |
Description |
Unfactored Weight From FLorida. This column had been added for compatibility purposes with other Landings Tables, but is not used in this table. |
General Data Type | NUMBER |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | PRICE |
---|---|
Seq. Order | 20 |
Data Storage Type | NUMBER |
Max Length | 22 |
Min Length | |
Required | No |
Primary Key | No |
Precision | 7 |
Scale | 3 |
Status | Active |
Description |
This column is null. |
General Data Type | NUMBER |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | CONVERSION |
---|---|
Seq. Order | 21 |
Data Storage Type | NUMBER |
Max Length | 22 |
Min Length | |
Required | No |
Primary Key | No |
Precision | 9 |
Scale | 5 |
Status | Active |
Description |
Conversion Factor Between Unfactored Weight From Florida and NMFS Species Weight. Provided for compatbility purposes with other tables. This column is not used for this application |
General Data Type | NUMBER |
Unit of Measure | |
Case Restriction | |
Display Example | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | |
---|---|
Seq. Order | |
Data Storage Type | |
Max Length | |
Precision | |
Scale | |
Required | |
Primary Key | |
Status | |
Description | |
General Data Type | |
Case Restriction | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Min Length | |
Unit of Measure | |
Display Example | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | |
---|---|
Seq. Order | |
Data Storage Type | |
Max Length | |
Precision | |
Scale | |
Required | |
Primary Key | |
Status | |
Description | |
General Data Type | |
Case Restriction | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Min Length | |
Unit of Measure | |
Display Example | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Attribute Name | |
---|---|
Seq. Order | |
Data Storage Type | |
Max Length | |
Precision | |
Scale | |
Required | |
Primary Key | |
Status | |
Description | |
General Data Type | |
Case Restriction | |
Format Mask | |
Null Value | |
Null Value Meaning | |
Min Length | |
Unit of Measure | |
Display Example | |
Allowed Values | |
Default Value | |
Foreign Key Relations | |
Derivation | |
Validation Rules |
Support Roles
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area
* » W° Bound | |
---|---|
* » E° Bound | |
* » N° Bound | |
* » S° Bound | |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame
* » Time Frame Type | |
---|---|
* » Start | |
End | |
Alternate Start as of Info | |
Alternate End as of Info | |
Description |
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 |
Confidential data are not to be released in any publication, report, oral presentation, or other means to the public. |
Metadata Access Constraints |
Non-published Metadata access is restricted. Published Metadata is available to the public. |
Metadata Use Constraints |
Only published metadata are to be used. |
Distribution Information
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Activity Log
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | 2011-06-10 |
---|---|
Author | Joshua E. Bennett |
Issue |
Shrimp gear is NULL in table for Gulf of Mexico region. Neither is it present in source table GSS.GSS_GULF_SHRIMP_56_83. |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 5442 |
---|---|
Metadata Record Created By | Lee M Weinberger |
Metadata Record Created | 2007-10-16 04:06+0000 |
Metadata Record Last Modified By | SysAdmin InPortAdmin |
» Metadata Record Last Modified | 2022-08-09 17:10+0000 |
Metadata Record Published | 2021-05-06 |
Owner Org | SEFSC |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2021-05-06 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2022-05-06 |
Tags |
---|