Cook Inlet and Kenai Peninsula, Alaska ESI: FISH (Fish Polygons)
Office of Response and Restoration
Data Set
(DS)
| ID: 40275
| Published / External
Created: 2017-04-05
|
Last Modified: 2023-05-30
Project (PRJ) | ID: 46671
ID: 40275
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | Cook Inlet and Kenai Peninsula, Alaska ESI: FISH (Fish Polygons) |
---|---|
Short Name | Cook_Inlet_FISH |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2002-07 |
* » Abstract |
This data set contains biological resource data for herring spawning areas in Cook Inlet and Kenai Peninsula, Alaska. Vector polygons in this data set represent locations of herring concentration areas. Abundance, seasonality, status, life history, and source information are stored in relational data tables (described below) designed to be used in conjunction with this spatial data layer. See also the FISHL (Fish Lines) data layer, part of the larger Cook Inlet and Kenai Peninsula ESI database, for additional fish information.This data set comprises a portion of the Environmental Sensitivity Index (ESI) data for Cook Inlet and Kenai Peninsula. ESI data characterize the marine and coastal environments and wildlife by their sensitivity to spilled oil. The ESI data include information for three main components: shoreline habitats, sensitive biological resources, and human-use resources. |
* Purpose |
The ESI data were collected, mapped, and digitized to provide environmental data for oil spill planning and response. The Clean Water Act with amendments by the Oil Pollution Act of 1990 requires response plans for immediate and effective protection of sensitive resources. |
Notes |
1687 |
Other Citation Details |
Prepared by Research Planning, Inc., Columbia, South Carolina for the National Oceanic and Atmospheric Administration (NOAA), National Ocean Service, Office of Response and Restoration, Hazardous Materials Response Division, Seattle, Washington |
• Supplemental Information |
Resource Description - ESI Atlas for Cook Inlet and Kenai Peninsula, Alaska |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | environment |
ISO 19115 Topic Category | oceans |
NOS Topic Category | Environmental Monitoring |
None | Coastal resources |
None | Coastal Zone Management |
None | ESI |
None | Fish |
None | Oil spill planning |
None | Sensitivity maps |
None | Wildlife |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
None | Alaska |
None | Cook Inlet |
None | Kenai Peninsula |
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Platform Keywords
Thesaurus | Keyword |
---|---|
Physical Location
• » Organization | Office of Response and Restoration |
---|---|
• » City | Silver Spring |
• » State/Province | MD |
• Country | |
• » Location Description |
Data Set Information
* Data Set Scope Code | Data Set |
---|---|
• Data Set Type | |
• Maintenance Frequency | None Planned |
Maintenance Note | |
» Data Presentation Form | Digital vector data |
• Entity Attribute Overview |
In addition to the geographic data layers, six relational attribute or data tables, BIORES, BREED, SEASONAL, SOURCES, SPECIES, and STATUS, are used to store the complex biological data in the ESI data structure. The geographic data layer containing biological resource information (in this case, FISH) is linked to the Biological Resources table (BIORES) using the unique ID and the lookup table BIO_LUT, or it can be linked directly using RARNUM. The ID is a unique combination of the atlas number (for Cook Inlet and Kenai Peninsula, the number is 11), an element/layer specific number (BIRDS are layer 1, FISH are layer 2, etc.), and a unique record number. The RARNUM represents a unique combination of species, seasonalities, concentrations, and source information. For each of these groupings, a number is generated. That number is concatenated with the atlas number to create a "resource at risk" number that is unique across atlases. BIORES and the other relational data tables are described below in detail. See the Browse_Graphic section for a link to the entity-relationship diagram, which describes the way these tables relate to the geographic data layers and other attribute tables in the ESI data structure.Due to the complexity of the relational database model, the data items are also post-processed into a flat file format. This table, called BIOFILE, may be used in place of the relational files described below to ease simple data queries. The items in the flat file are ELEMENT, SUBELEMENT, NAME, GEN_SPEC, S_F, T_E, NHP, DATE_PUB, CONC, JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC, BREED1, BREED2, BREED3, BREED4, BREED5, RARNUM, G_SOURCE, S_SOURCE, and BREED. All of these items are the same as their counterparts in the individual data tables described below, except the BREED1-BREED5 and BREED items. BREED is a newly generated variable used to link to the BREED_DT data table, a modified, more compact version of the relational BREED data table. BREED1-BREED5 give a text summary of when each life stage occurs within the associated map object. The life stages referred to are the same as those listed in the Detailed_Description of the BREED data table. The link to the BIOFILE may be made through the BIO_LUT, using ID to link to RARNUM, or BIOFILE may be linked directly to the RARNUM in each of the geographic layer's attribute data tables. As mentioned, BREED_DT is an auxiliary support data table to the flat file structure, which allows the user to do searches based on month for seasonal breeding activities. The link from the flat file to BREED_DT is the BREED item.A second supporting data table is SOURCES. This is the same as the source file described above, and the link from the flat file is both G_SOURCE and S_SOURCE. It should be noted that although the flat file eases data query, it is not a normalized database structure, and actual updates performed by the states and other responsible agencies should be done using the relational data tables. The entity-relationship diagram, describing relationships between attribute tables in the ESI data structure, does NOT include the BIOFILE data table, and this data table is NOT described in detail below. |
Entity Attribute Detail Citation |
Unknown |
Entity Attribute Detail URL | |
Distribution Liability |
Although these data have been processed successfully on a computer system at the National Oceanic and Atmospheric Administration, no warranty, expressed or implied, is made by NOAA regarding the utility of the data on any other system, nor shall the act of distribution constitute any such warranty. NOAA warrants the delivery of this product in computer-readable format, and will offer a replacement copy of the product when the product is determined unreadable by computer-input peripherals, or when the physical medium is delivered in damaged condition. |
Data Set Credit | This project was supported by the National Oceanic and Atmospheric Administration (NOAA), National Ocean Service, Office of Response and Restoration, Hazardous Materials Response Division, Seattle, Washington |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2002-07 |
Date Effective To | |
Position | ESI Program Manager |
Address |
7600 Sand Point Way NE Seattle, WA 98115 |
Email Address | orr.esi@noaa.gov |
Phone | |
Fax | |
Mobile | |
URL | |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2002-07 |
Date Effective To | |
Position | ESI Program Manager |
Address |
7600 Sand Point Way NE Seattle, WA 98115 |
Email Address | orr.esi@noaa.gov |
Phone | |
Fax | |
Mobile | |
URL | |
Business Hours | |
Contact Instructions |
* » Support Role | Metadata Contact |
---|---|
* » Date Effective From | 2002-07 |
Date Effective To | |
Position | ESI Program Manager |
Address |
7600 Sand Point Way NE Seattle, WA 98115 |
Email Address | orr.esi@noaa.gov |
Phone | |
Fax | |
Mobile | |
URL | |
Business Hours | |
Contact Instructions |
* » Support Role | Point of Contact |
---|---|
* » Date Effective From | 2002-07 |
Date Effective To | |
Position | ESI Program Manager |
Address |
7600 Sand Point Way NE Seattle, WA 98115 |
Email Address | orr.esi@noaa.gov |
Phone | |
Fax | |
Mobile | |
URL | |
Business Hours | |
Contact Instructions |
* » 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 | The biological data were compiled during 2002. The currentness dates for these data range from 1980 to 2002 and are documented in the Source_Information section. |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -154.69 |
---|---|
* » E° Bound | -148.476 |
* » N° Bound | 61.881 |
* » S° Bound | 58.643 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Discrete |
---|---|
* » Start | 2002 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | |
Horizontal Distance Units | |
Vertical Distance | |
Vertical Distance Units | |
Equivalent Scale Denominator | |
Level of Detail Description |
Spatial Representation
Grid Representation Used? | |
---|---|
Vector Representation Used? | Yes |
Text / Table Representation Used? | |
TIN Representation Used? | |
Stereo Model Representation Used? | |
Video Representation Used? |
Grid Representation
Dimension Count | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | |||||||||||||
Transformation Parameter Available? | |||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | Yes |
Complex Object Count | 81 |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | Yes |
Curve Object Count | 12473 |
Point Object Present? | Yes |
Point Object Count | 81 |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | Yes |
Surface Object Count | 97 |
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | |
Complex Object Count | |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | |
Curve Object Count | |
Point Object Present? | |
Point Object Count | |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | |
Surface Object Count |
Reference Systems
Reference System
EPSG Code | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Access Information
Data License | |
---|---|
Data License URL | |
Data License Statement | |
* » Security Class | Unclassified |
* Security Classification System | |
Security Handling Description | |
• Data Access Policy | |
» Data Access Procedure |
Contact NOAA for distribution options (see Distributor). ESI data are processed into multiple formats to make them useful to a wider community of GIS/mapping users. Distribution formats include ARC export, MOSS and Shape files, and MARPLOT map folders. An ArcView ESI project and ESI_Viewer product are also included on the distribution CDs for ease of use of the ESI data. The database files are distributed both in the NOAA standard relational database format (see NOAA Technical Memorandum NOS ORCA 115) and in a simplified desktop flat file format. This metadata document includes information on both of these database formats.; |
• » Data Access Constraints |
None |
• Data Use Constraints |
DO NOT USE MAPS FOR NAVIGATIONAL PURPOSES.Besides the above warning, there are no use constraints on these data. Note that the ESI database should not be used to the exclusion of other pertinent data or information held by state or federal agencies or other organizations. Likewise, information contained in the database cannot be used in place of consultations with environmental, natural resource, and cultural resource agencies, or in place of field surveys. Recognize that the information contained in the ESI database represents known concentration areas or occurrences of natural, cultural, and human-use resources, but does not necessarily represent the full distribution or range of each species or resource. This is particularly important to recognize when considering potential impacts to protected resources, such as endangered species, wetlands, etc. Acknowledgment of the originators, publishers, contributors, and sources listed would be appreciated in products derived from these data. |
Metadata Access Constraints | |
Metadata Use Constraints |
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 |
Archive Information
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
URLs
URL | http://response.restoration.noaa.gov/esi |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Activity Log
Activity Time | 2002-09 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Date that the source FGDC record was last modified. |
Activity Time | 2017-04-05 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Converted from Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details. |
Activity Time | 2017-09-13 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload of Spatial Info section only. |
Activity Time | 2017-11-01 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Replaced entire Lineage section to populate new Source Contribution field. |
Activity Time | 2018-02-08 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload of Positional Accuracy fields only. |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Technical Environment
Description |
The software packages used to develop the atlas are Environmental Systems Research Institute's ARC/INFO(r) (version 8.0.2) and ORACLE(r) RDBMS (version 8.0.5.0.0). The hardware configuration is Hewlett Packard workstations (models 715/50 and 712/80i with 4 X-terminals) with UNIX operating system (HP-UX Release A.10.20), and PC's with Windows Operating System (NT4.0/2000).The Spatial_Data_Organization_Information section refers only to the source files in the ARC export format. The following files are included in that data set: birds.e00, esi.e00, fish.e00, fishl.e00, hydro.e00, ice.e00, index.e00, invert.e00, m_mammal.e00, m_mampt.e00, mgt.e00, nests.e00, rips.e00, road_mrk.e00, socecon.e00, volcanos.e00. Associated relational and desktop data tables provided in Arc export and text format are bio_lut, biofile, biores, breed, breed_dt, seasonal, soc_dat, soc_lut, sources, species, and status. |
---|
Data Quality
Representativeness | |
---|---|
Accuracy |
A multi-stage error checking process is used to verify both attribute accuracy and logical consistency throughout data production. The process includes a standardized data entry methodology, hardcopy data review by in-house and external resource experts, a final Quality Assurance/Quality Control (QA/QC) process, and multiple automated logical consistency checks. Quantitative data (such as densities, counts, abundances, or concentrations) provided by resource experts for inclusion in the data set may vary widely in attribute accuracy, depending upon the methodology used to collect and compile such data. For a more detailed evaluation of source data attribute accuracy, contact the sources listed in the Lineage section. |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Some of the spatial components of the biological data sets are developed using regional experts who estimate concentration areas. It is difficult to estimate the positional accuracy of such data, except to state that they are compiled on hardcopy basemaps with a scale of 1:250,000. Note that biological resource data by their very nature are considered "fuzzy", and this should be understood when considering the positional accuracy of vector digital objects representing these resources. |
Vertical Positional Accuracy | |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
These data represent a synthesis of expert knowledge and available hardcopy reports and digital data on herring spawning concentration areas. Refer to the FISHL (Fish Lines) data layer for additional anadromous fish information. These data do not necessarily represent all fish occurrences in Cook Inlet and Kenai Peninsula. The following species are included in this data set (Species_ID, Common Name, Scientific Name, if applicable): 66, Pacific herring, Clupea pallasi. |
Conceptual Consistency |
A multi-stage error checking process, described in the above Attribute_Accuracy_Report, is used to verify both attribute accuracy and logical consistency throughout data production. This process includes multiple automated logical consistency checks that test the files for missing or duplicate data, rules for proper coding, GIS topological consistencies (such as dangles, unnecessary nodes, etc.), and ORACLE(r) to ARC/INFO(r) consistencies. A final review is made by the GIS manager, where the data are written to CD-ROM and the metadata are written.After the data are delivered to NOAA, they are again subjected to a number of quality and consistency checks. In the process of checking for topological and database consistencies, new ID's and RARNUM's or HUNUM's are also generated. The new ID's are a combination of atlas number, element number, and record number. In addition, the value used to represent the element is modified to reflect the type of feature being mapped. In the case of an element that is normally represented by a point or polygon, a value of 20 is added to the standard element value for mapping of linear features. In the case where an element usually mapped as a polygon is represented by a point, a value of 30 is added to the regular element value. The RARNUM's are also modified to include the atlas number, so multiple atlases can be combined and RARNUM's remain unique. RARNUM's are redefined on an element basis, so "resource at risk" groupings will contain only a single element. HUNUM's are also modified to include the atlas number. |
» Quality Control Procedures Employed |
Data Management
» Have Resources for Management of these Data Been Identified? | |
---|---|
» Approximate Percentage of Budget for these Data Devoted to Data Management | |
» Do these Data Comply with the Data Access Directive? | |
» Is Access to the Data Limited Based on an Approved Waiver? | |
» If Distributor (Data Hosting Service) is Needed, Please Indicate | |
» Approximate Delay Between Data Collection and Dissemination | |
» If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed |
|
» Actual or Planned Long-Term Data Archive Location | |
» If World Data Center or Other, Specify | |
» If To Be Determined, Unable to Archive, or No Archiving Intended, Explain |
|
» Approximate Delay Between Data Collection and Archiving | |
» How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive? |
|
Lineage
» Lineage Statement |
---|
Sources
Citation Title | Habitat Management Guide |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | Alaska Department of Fish and Game (ADFG) |
Publish Date | 1982-01-01 |
Extent Type | Discrete |
Extent Start Date/Time | 1980 |
Extent End Date/Time | |
Scale Denominator | 250000 |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
Fish information | Source Geospatial Form: Hardcopy map | Type of Source Media: paper |
Citation Title | Herring Spawning Areas |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | Mark Fink (ADFG) |
Publish Date | |
Extent Type | Discrete |
Extent Start Date/Time | 2001 |
Extent End Date/Time | |
Scale Denominator | 250000 |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
Fish information | Source Geospatial Form: Hardcopy map | Type of Source Media: paper |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Process Steps
Process Step Number | 1 |
---|---|
» Description |
Sources of data used to depict fish distribution for this data layer came from (1) personal interviews with resource experts from Alaska Department of Fish and Game in Anchorage and (2) Alaska Dept. of Fish and Game's Most Environmentally Sensitive Areas maps. Information gathered from the interviews and other maps were compiled onto 1:250,000 scale USGS topographic maps. Following the data compilation phase, several sets of completed maps were sent out to the resource agencies for review, and edits were made based on recommendations by the resource experts. |
Process Date/Time | 2002-07-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Acquisition Information
Instruments
Instrument Unavailable Reason |
---|
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Platforms
Platform Unavailable Reason |
---|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Entity (ENT) | BIORES | |
Entity (ENT) | BIO_LUT | |
Entity (ENT) | BREED | |
Entity (ENT) | FISH.PAT | |
Entity (ENT) | SEASONAL | |
Entity (ENT) | SOURCES | |
Entity (ENT) | SPECIES | |
Entity (ENT) | STATUS | |
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 40275 |
---|---|
Metadata Record Created By | Tyler Christensen |
Metadata Record Created | 2017-04-05 14:50+0000 |
Metadata Record Last Modified By | SysAdmin InPortAdmin |
» Metadata Record Last Modified | 2023-05-30 18:09+0000 |
Metadata Record Published | 2018-02-08 |
Owner Org | ORR |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2018-02-08 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2019-02-08 |
Tags |
---|