<?xml version="1.0" encoding="UTF-8"?>
<inport-metadata xmlns:xs="http://www.w3.org/2001/XMLSchema"
                 version="1.11"
                 source="https://www.fisheries.noaa.gov">
   <item-identification>
      <catalog-item-id>5446</catalog-item-id>
      <title>Table: ALS_TEMP_LAND_PUERTO_RICO</title>
      <short-name>ALS_TEMP_LAND_PUERTO_RICO</short-name>
      <catalog-item-type>Entity</catalog-item-type>
      <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
      <parent-catalog-item-id>1919</parent-catalog-item-id>
      <parent-title>Puerto Rico Commercial Landings Statistics 1983 and more recent in Accumulated Landings System (ALS) Compatible Format</parent-title>
      <parent-catalog-item-type>Data Set</parent-catalog-item-type>
      <status>Completed</status>
      <abstract>Pre-validation table for processing the load of Puerto RIco landings data.</abstract>
      <notes>Loaded by batch 1725, 10-16-2007 05:43</notes>
   </item-identification>
   <keywords>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>landings</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>staging table</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Spatial</keyword-type>
         <keyword>puerto rico</keyword>
      </keyword>
   </keywords>
   <physical-location>
      <organization>Southeast Fisheries Science Center</organization>
      <city>Miami</city>
      <state-province>FL</state-province>
      <country>USA</country>
      <location-description>75 Virginia Beach Drive
Miami, FL 33149</location-description>
   </physical-location>
   <entity-information>
      <entity-type>Data Table</entity-type>
      <active-version>Yes</active-version>
      <schema>ALS</schema>
      <description>Pre-validation table for processing the load of Puerto RIco landings data.</description>
   </entity-information>
   <data-attributes>
      <data-attribute cc-id="17260">
         <seq-order>1</seq-order>
         <name>MONTH_LANDED</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>2</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Two Character Month Landed</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17259">
         <seq-order>2</seq-order>
         <name>YEAR_LANDED</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>4</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>4 character Year Landed</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17258">
         <seq-order>3</seq-order>
         <name>STATE_LANDED</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>2</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>State Code Landed.  This is laways loaded with the NMFS STate Code For Puerto Rico.</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17257">
         <seq-order>4</seq-order>
         <name>FISHING_CENTER</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>3</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Fishing Center Code.</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17256">
         <seq-order>5</seq-order>
         <name>DEALER</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>9</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Dealer Code. Added For compatibility with other ALS Tables.  This is column is always filled with all 9s as the Dealer is unknown.</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17255">
         <seq-order>6</seq-order>
         <name>WATER_BODY</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>4</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Water Body Code</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17254">
         <seq-order>7</seq-order>
         <name>GEAR</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>3</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>NMFS Gear Code (If One exists. It is generated between a cross table Of Erdman Gear Codes to NMFS Gear Code)</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17253">
         <seq-order>8</seq-order>
         <name>SPECIES</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>4</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>NMFS Species Code (If One exists. It is generated between a cross table Of Erdman Species Codes to NMFS Species Codes)</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17252">
         <seq-order>9</seq-order>
         <name>SHELL_OR_FINFISH</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>1</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Finfish or shell fish code.</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17251">
         <seq-order>10</seq-order>
         <name>POUNDS</name>
         <data-storage-type>NUMBER</data-storage-type>
         <max-length>22</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <precision>9</precision>
         <scale>0</scale>
         <status>Active</status>
         <description>Pounds Caught. (Whole weight)</description>
         <general-data-type>NUMBER</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17250">
         <seq-order>11</seq-order>
         <name>VALUE</name>
         <data-storage-type>NUMBER</data-storage-type>
         <max-length>22</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <precision>9</precision>
         <scale>0</scale>
         <status>Active</status>
         <description>Value in dollars</description>
         <general-data-type>NUMBER</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17249">
         <seq-order>12</seq-order>
         <name>SECTION</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>1</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Section Code,  Added for compatibility with ALS.ALS_LANDINGS</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17248">
         <seq-order>13</seq-order>
         <name>PRICE</name>
         <data-storage-type>NUMBER</data-storage-type>
         <max-length>22</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <precision>7</precision>
         <scale>3</scale>
         <status>Active</status>
         <description>Price payed for fish. (In dollars)</description>
         <general-data-type>NUMBER</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17247">
         <seq-order>14</seq-order>
         <name>DISTANCE</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>1</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Distance From Shore Code. Added for compatibility with ALS.ALS_LANDINGS.</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17246">
         <seq-order>15</seq-order>
         <name>STATE_CAUGHT</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>2</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>State Caught.  Added For compatibility WIth ALS.ALS_LANDINGS</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17245">
         <seq-order>16</seq-order>
         <name>LANDING_DATE</name>
         <data-storage-type>DATE</data-storage-type>
         <max-length>7</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Actual Date animal was landed.</description>
         <general-data-type>DATE</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17244">
         <seq-order>17</seq-order>
         <name>PR_ID_CODE</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>6</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Identification Code asigned to Record by Puerto Rico data manager</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17243">
         <seq-order>18</seq-order>
         <name>PR_GEAR</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>3</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Erdman Gear Code</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17242">
         <seq-order>19</seq-order>
         <name>NUMBER_OF_TRIPS</name>
         <data-storage-type>NUMBER</data-storage-type>
         <max-length>22</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <precision>2</precision>
         <scale>0</scale>
         <status>Active</status>
         <description>Number Of Trips</description>
         <general-data-type>NUMBER</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17241">
         <seq-order>20</seq-order>
         <name>PR_SPECIES</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>3</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Erdman Species Code</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17240">
         <seq-order>21</seq-order>
         <name>GEAR_QTY</name>
         <data-storage-type>NUMBER</data-storage-type>
         <max-length>22</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <precision>4</precision>
         <scale>0</scale>
         <status>Active</status>
         <description>Number Of Gear</description>
         <general-data-type>NUMBER</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17239">
         <seq-order>22</seq-order>
         <name>GEAR_HOURS</name>
         <data-storage-type>NUMBER</data-storage-type>
         <max-length>22</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <precision>3</precision>
         <scale>0</scale>
         <status>Active</status>
         <description>Soak Time</description>
         <general-data-type>NUMBER</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17238">
         <seq-order>23</seq-order>
         <name>DAY_LANDED</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>2</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Day landed. Derived from landing date</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17237">
         <seq-order>24</seq-order>
         <name>RNUMBER</name>
         <data-storage-type>NUMBER</data-storage-type>
         <max-length>22</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <precision>6</precision>
         <scale>0</scale>
         <status>Active</status>
         <description>Record Number of Record In Question In file loaded</description>
         <general-data-type>NUMBER</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17236">
         <seq-order>25</seq-order>
         <name>USERID</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>30</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Oracle Id Of The Person Loading The Data</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17235">
         <seq-order>26</seq-order>
         <name>SOURCE_FILE</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>20</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Source File used to load data.</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17234">
         <seq-order>27</seq-order>
         <name>MINIMUM_DEPTH</name>
         <data-storage-type>NUMBER</data-storage-type>
         <max-length>22</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <precision>4</precision>
         <scale>0</scale>
         <status>Active</status>
         <description>Minimum Depth Fished</description>
         <general-data-type>NUMBER</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17233">
         <seq-order>28</seq-order>
         <name>MAXIMUM_DEPTH</name>
         <data-storage-type>NUMBER</data-storage-type>
         <max-length>22</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <precision>4</precision>
         <scale>0</scale>
         <status>Active</status>
         <description>Maximum Depth Fished</description>
         <general-data-type>NUMBER</general-data-type>
      </data-attribute>
      <data-attribute cc-id="17232">
         <seq-order>29</seq-order>
         <name>TRIP_TICKET_NUMBER</name>
         <data-storage-type>VARCHAR2</data-storage-type>
         <max-length>11</max-length>
         <required>No</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>Trip Ticket Number</description>
         <general-data-type>VARCHAR2</general-data-type>
      </data-attribute>
   </data-attributes>
   <access-information>
      <security-class>Confidential</security-class>
      <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-classification-system>
      <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.
</security-handling-description>
      <data-access-policy>See NOAA Administrative Order 216-100
NOAA ADMINISTRATIVE ORDER SERIES
Date of Issuance: July 26, 1994</data-access-policy>
      <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-procedure>
      <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-access-constraints>
      <data-use-constraints>NOAA/SEFSC Internal use only.
</data-use-constraints>
      <metadata-access-constraints>Non-published Metadata access is restricted.  Published Metadata is available to the public.
</metadata-access-constraints>
      <metadata-use-constraints>Only use Published Metadata</metadata-use-constraints>
   </access-information>
   <activity-logs>
      <activity-log cc-id="355832">
         <activity-date-time>2016-11-02</activity-date-time>
         <activity-type>Change column POUNDS format</activity-type>
         <responsible-party>Bennett, Joshua </responsible-party>
         <description>Pounds column re-formatted to NUMBER (9,3) from Number (9,0).  No more rounding of imports from Caribbean Commercial Landings.</description>
      </activity-log>
   </activity-logs>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:5446</guid>
      <metadata-record-created-by pers-id="1279">Lee Weinberger</metadata-record-created-by>
      <metadata-record-created>2007-10-16T05:43:40</metadata-record-created>
      <metadata-record-last-modified-by pers-id="0">SysAdmin InPortAdmin</metadata-record-last-modified-by>
      <metadata-record-last-modified>2022-08-09T17:10:59</metadata-record-last-modified>
      <record-published>2021-05-06</record-published>
      <owner-organization>Southeast Fisheries Science Center</owner-organization>
      <owner-organization-acronym>SEFSC</owner-organization-acronym>
      <owner-organization-address>75 Virginia Beach Drive</owner-organization-address>
      <owner-organization-address-city>Miami</owner-organization-address-city>
      <owner-organization-address-state>FL</owner-organization-address-state>
      <owner-organization-address-zip>33149</owner-organization-address-zip>
      <owner-organization-address-country>USA</owner-organization-address-country>
      <owner-organization-phone>(305)361-5761</owner-organization-phone>
      <owner-organization-url>www.sefsc.noaa.gov</owner-organization-url>
      <owner-organization-business-hours>8:00 a.m. - 4:30 p.m. EST</owner-organization-business-hours>
      <owner-organization-group-id>1001</owner-organization-group-id>
      <publication-status>Public</publication-status>
      <is-do-not-publish>No</is-do-not-publish>
      <metadata-last-review-date>2021-05-06</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2022-05-06</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
