Search Help Show/Hide Menu
Summary
Item Identification
Entity Info
Data Attributes
Catalog Details

Summary

Abstract

A snapshot of data. Used to freeze data so that the data can be used for NMFS reporting purposes such as status reviews and annual updates.

Description

A snapshot of data. Used to freeze data so that the data can be used for NMFS reporting purposes such as status reviews and annual updates.

Entity Information

Entity Type
Data Table

Data Attribute / Type Description
RECORD_NUMBER_OF_EDITS
NUMBER
The number of times that the particular record was modified. This count is dynamically incremented by 1 by the database trigger each time the record is edited.
RECORD_SOFT_DELETED
VARCHAR2
Flag whether or not this record has the "Deleted" status. Null means this record has NOT been deleted. "Y" means this record HAS been deleted. This flag allows "deleted" records to remain in the table for technical reasons. When the record is "Hard Deleted" it will be removed from this table and may or may not be placed in a historical table to preserve historical status.
RECORD_STEWARDSHIP
VARCHAR2
If a set of User-Roles are developed for these records, this allows a particular Role (which may be a collection of other Roles) to be assigned to steward individual records. When any user attempts to modify a record, a database procedure will then dynamically examine the user's Role to determine if they are authorized to edit particular records.
RECORD_CHANGE_COMMENT
CLOB
Unlimited narrative describing the last change/edit made to this particular record. In a post-edit summary, this text is intended to describe what was done by the latest edit job.
ARCHIVE_DB_ID
NUMBER
Database-generated primary key (unique identifier) for each SPS_ARCHIVE record, created by an internal sequence generator and used by the database to maintain referential integrity. This ID is not designed to be managed by users. This primary key constraint is named SPS_ARCHIVE_PK.
ARCHIVE_NAME
VARCHAR2
The name of the archive. Used to present the archive to end users. The name indicates the latest year for which data is available at time of archive creation. The name should indicate why the archive was created, for example to freeze data for a status review.
ARCHIVE_ACTION
VARCHAR2
The action performed on the archive either created or deleted.
ARCHIVE_NOTE
VARCHAR2
Any notes from the data providers. Indicates what the archive is to be used for.
ARCHIVE_AUDIENCE
VARCHAR2
The audience for the data. Either internal or public. If public the data is available through the SPS application interface.
RECORD_HISTORY
CLOB
An accumulated set of statements describing how THIS RECORD has been edited over time including WHEN and by WHOM.
RECORD_JOURNAL_NOTE
VARCHAR2
Short narrative describing the last change/edit made to this particular record. In a post-edit summary, this text is intended to describe what was done by the latest edit job.
RECORD_APPROVED_BY_PERSON
VARCHAR2
If there is a certification process for these records, name of person who certified approval of the particular record.
RECORD_APPROVED_ON_DATE
DATE
If there is a certification process for these records, date that the particular record was approved or officially certified.
RECORD_COMPUTER_LOAD_BY_USER
VARCHAR2
The username that loaded the record into the database. The username is dynamically captured by the database trigger when the record is inserted and saved to the database. This person may have no knowledge of content or meaning but ran the computer process that put the record into the database.
RECORD_COMPUTER_LOAD_ON_DATE
TIMESTAMP(4)
The date that the record was loaded into the database. This date is dynamically captured by the database trigger when the record is inserted and saved.
RECORD_CREATED_BY_PERSON
VARCHAR2
The name of the person who originated this record PRIOR to its being entered into the database. The name of the person to contact with administrative questions or an explanation of it content.
RECORD_CREATED_ON_DATE
TIMESTAMP(4)
The date, or approximate date, that the person with content knowledge originated this record PRIOR to its being entered into the database.
RECORD_EFFECTIVE_DATE
DATE
If necessary, the date that the individual record becomes effective. Prior to this date the record is not valid.
RECORD_EXPIRATION_DATE
DATE
If necessary, the date that the individual record ceases to be effective. To force a midnight expiration, this may be set by "Select to_date(to_char(sysdate +1 ,'mm/dd/yyyy')||' 23:59:59','mm/dd/yyyy hh24:mi:ss') from dual". After this date and time the record is not valid.
RECORD_LAST_EDITED_BY_USER
VARCHAR2
The username of the last person who modified this record. This username is dynamically captured by the database trigger any time the record is edited.
RECORD_LAST_EDITED_ON_DATE
TIMESTAMP(4)
The last date that the particular record was modified. This date is dynamically captured by the database trigger any time the record is edited.

Child Items

No Child Items for this record.

Contact Information

No contact information is available for this record.

Please contact the owner organization (NWFSC) for inquiries on this record.

Item Identification

Title: SPS_ARCHIVE
Short Name: SPS_ARCHIVE
Status: Planned
Abstract:

A snapshot of data. Used to freeze data so that the data can be used for NMFS reporting purposes such as status reviews and annual updates.

Entity Information

Entity Type: Data Table
Active Version?: Yes
Schema Name: SPS
Description:

A snapshot of data. Used to freeze data so that the data can be used for NMFS reporting purposes such as status reviews and annual updates.

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
RECORD_NUMBER_OF_EDITS NUMBER The number of times that the particular record was modified. This count is dynamically incremented by 1 by the database trigger each time the record is edited.
100
RECORD_SOFT_DELETED VARCHAR2 Flag whether or not this record has the "Deleted" status. Null means this record has NOT been deleted. "Y" means this record HAS been deleted. This flag allows "deleted" records to remain in the table for technical reasons. When the record is "Hard Deleted" it will be removed from this table and may or may not be placed in a historical table to preserve historical status.
100
RECORD_STEWARDSHIP VARCHAR2 If a set of User-Roles are developed for these records, this allows a particular Role (which may be a collection of other Roles) to be assigned to steward individual records. When any user attempts to modify a record, a database procedure will then dynamically examine the user's Role to determine if they are authorized to edit particular records.
100
RECORD_CHANGE_COMMENT CLOB Unlimited narrative describing the last change/edit made to this particular record. In a post-edit summary, this text is intended to describe what was done by the latest edit job.
100
Primary Key ARCHIVE_DB_ID NUMBER Database-generated primary key (unique identifier) for each SPS_ARCHIVE record, created by an internal sequence generator and used by the database to maintain referential integrity. This ID is not designed to be managed by users. This primary key constraint is named SPS_ARCHIVE_PK.
100
ARCHIVE_NAME VARCHAR2 The name of the archive. Used to present the archive to end users. The name indicates the latest year for which data is available at time of archive creation. The name should indicate why the archive was created, for example to freeze data for a status review.
100
ARCHIVE_ACTION VARCHAR2 The action performed on the archive either created or deleted.
100
ARCHIVE_NOTE VARCHAR2 Any notes from the data providers. Indicates what the archive is to be used for.
100
ARCHIVE_AUDIENCE VARCHAR2 The audience for the data. Either internal or public. If public the data is available through the SPS application interface.
100
RECORD_HISTORY CLOB An accumulated set of statements describing how THIS RECORD has been edited over time including WHEN and by WHOM.
100
RECORD_JOURNAL_NOTE VARCHAR2 Short narrative describing the last change/edit made to this particular record. In a post-edit summary, this text is intended to describe what was done by the latest edit job.
100
RECORD_APPROVED_BY_PERSON VARCHAR2 If there is a certification process for these records, name of person who certified approval of the particular record.
100
RECORD_APPROVED_ON_DATE DATE If there is a certification process for these records, date that the particular record was approved or officially certified.
100
RECORD_COMPUTER_LOAD_BY_USER VARCHAR2 The username that loaded the record into the database. The username is dynamically captured by the database trigger when the record is inserted and saved to the database. This person may have no knowledge of content or meaning but ran the computer process that put the record into the database.
100
RECORD_COMPUTER_LOAD_ON_DATE TIMESTAMP(4) The date that the record was loaded into the database. This date is dynamically captured by the database trigger when the record is inserted and saved.
100
RECORD_CREATED_BY_PERSON VARCHAR2 The name of the person who originated this record PRIOR to its being entered into the database. The name of the person to contact with administrative questions or an explanation of it content.
100
RECORD_CREATED_ON_DATE TIMESTAMP(4) The date, or approximate date, that the person with content knowledge originated this record PRIOR to its being entered into the database.
100
RECORD_EFFECTIVE_DATE DATE If necessary, the date that the individual record becomes effective. Prior to this date the record is not valid.
100
RECORD_EXPIRATION_DATE DATE If necessary, the date that the individual record ceases to be effective. To force a midnight expiration, this may be set by "Select to_date(to_char(sysdate +1 ,'mm/dd/yyyy')||' 23:59:59','mm/dd/yyyy hh24:mi:ss') from dual". After this date and time the record is not valid.
100
RECORD_LAST_EDITED_BY_USER VARCHAR2 The username of the last person who modified this record. This username is dynamically captured by the database trigger any time the record is edited.
100
RECORD_LAST_EDITED_ON_DATE TIMESTAMP(4) The last date that the particular record was modified. This date is dynamically captured by the database trigger any time the record is edited.

Attribute Details

RECORD_NUMBER_OF_EDITS

CC ID: 324433
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Status: Active
Description:

The number of times that the particular record was modified. This count is dynamically incremented by 1 by the database trigger each time the record is edited.

General Data Type: NUMBER

RECORD_SOFT_DELETED

CC ID: 324434
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Flag whether or not this record has the "Deleted" status. Null means this record has NOT been deleted. "Y" means this record HAS been deleted. This flag allows "deleted" records to remain in the table for technical reasons. When the record is "Hard Deleted" it will be removed from this table and may or may not be placed in a historical table to preserve historical status.

General Data Type: VARCHAR2

RECORD_STEWARDSHIP

CC ID: 324435
Data Storage Type: VARCHAR2
Max Length: 40
Required: No
Primary Key: No
Status: Active
Description:

If a set of User-Roles are developed for these records, this allows a particular Role (which may be a collection of other Roles) to be assigned to steward individual records. When any user attempts to modify a record, a database procedure will then dynamically examine the user's Role to determine if they are authorized to edit particular records.

General Data Type: VARCHAR2

RECORD_CHANGE_COMMENT

CC ID: 324436
Data Storage Type: CLOB
Max Length: 4000
Required: No
Primary Key: No
Status: Active
Description:

Unlimited narrative describing the last change/edit made to this particular record. In a post-edit summary, this text is intended to describe what was done by the latest edit job.

General Data Type: CLOB

ARCHIVE_DB_ID

CC ID: 324437
Data Storage Type: NUMBER
Max Length: 22
Required: Yes
Primary Key: Yes
Status: Active
Description:

Database-generated primary key (unique identifier) for each SPS_ARCHIVE record, created by an internal sequence generator and used by the database to maintain referential integrity. This ID is not designed to be managed by users. This primary key constraint is named SPS_ARCHIVE_PK.

General Data Type: NUMBER

ARCHIVE_NAME

CC ID: 324438
Data Storage Type: VARCHAR2
Max Length: 50
Required: Yes
Primary Key: No
Status: Active
Description:

The name of the archive. Used to present the archive to end users. The name indicates the latest year for which data is available at time of archive creation. The name should indicate why the archive was created, for example to freeze data for a status review.

General Data Type: VARCHAR2

ARCHIVE_ACTION

CC ID: 324439
Data Storage Type: VARCHAR2
Max Length: 15
Required: No
Primary Key: No
Status: Active
Description:

The action performed on the archive either created or deleted.

General Data Type: VARCHAR2

ARCHIVE_NOTE

CC ID: 324440
Data Storage Type: VARCHAR2
Max Length: 4000
Required: No
Primary Key: No
Status: Active
Description:

Any notes from the data providers. Indicates what the archive is to be used for.

General Data Type: VARCHAR2

ARCHIVE_AUDIENCE

CC ID: 324441
Data Storage Type: VARCHAR2
Max Length: 30
Required: No
Primary Key: No
Status: Active
Description:

The audience for the data. Either internal or public. If public the data is available through the SPS application interface.

General Data Type: VARCHAR2

RECORD_HISTORY

CC ID: 324442
Data Storage Type: CLOB
Max Length: 4000
Required: No
Primary Key: No
Status: Active
Description:

An accumulated set of statements describing how THIS RECORD has been edited over time including WHEN and by WHOM.

General Data Type: CLOB

RECORD_JOURNAL_NOTE

CC ID: 324443
Data Storage Type: VARCHAR2
Max Length: 4000
Required: No
Primary Key: No
Status: Active
Description:

Short narrative describing the last change/edit made to this particular record. In a post-edit summary, this text is intended to describe what was done by the latest edit job.

General Data Type: VARCHAR2

RECORD_APPROVED_BY_PERSON

CC ID: 324444
Data Storage Type: VARCHAR2
Max Length: 40
Required: No
Primary Key: No
Status: Active
Description:

If there is a certification process for these records, name of person who certified approval of the particular record.

General Data Type: VARCHAR2

RECORD_APPROVED_ON_DATE

CC ID: 324445
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

If there is a certification process for these records, date that the particular record was approved or officially certified.

General Data Type: DATE

RECORD_COMPUTER_LOAD_BY_USER

CC ID: 324446
Data Storage Type: VARCHAR2
Max Length: 40
Required: No
Primary Key: No
Status: Active
Description:

The username that loaded the record into the database. The username is dynamically captured by the database trigger when the record is inserted and saved to the database. This person may have no knowledge of content or meaning but ran the computer process that put the record into the database.

General Data Type: VARCHAR2

RECORD_COMPUTER_LOAD_ON_DATE

CC ID: 324447
Data Storage Type: TIMESTAMP(4)
Max Length: 11
Required: No
Primary Key: No
Status: Active
Description:

The date that the record was loaded into the database. This date is dynamically captured by the database trigger when the record is inserted and saved.

General Data Type: TIMESTAMP(4)

RECORD_CREATED_BY_PERSON

CC ID: 324448
Data Storage Type: VARCHAR2
Max Length: 40
Required: No
Primary Key: No
Status: Active
Description:

The name of the person who originated this record PRIOR to its being entered into the database. The name of the person to contact with administrative questions or an explanation of it content.

General Data Type: VARCHAR2

RECORD_CREATED_ON_DATE

CC ID: 324449
Data Storage Type: TIMESTAMP(4)
Max Length: 11
Required: No
Primary Key: No
Status: Active
Description:

The date, or approximate date, that the person with content knowledge originated this record PRIOR to its being entered into the database.

General Data Type: TIMESTAMP(4)

RECORD_EFFECTIVE_DATE

CC ID: 324450
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

If necessary, the date that the individual record becomes effective. Prior to this date the record is not valid.

General Data Type: DATE

RECORD_EXPIRATION_DATE

CC ID: 324451
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

If necessary, the date that the individual record ceases to be effective. To force a midnight expiration, this may be set by "Select to_date(to_char(sysdate +1 ,'mm/dd/yyyy')||' 23:59:59','mm/dd/yyyy hh24:mi:ss') from dual". After this date and time the record is not valid.

General Data Type: DATE

RECORD_LAST_EDITED_BY_USER

CC ID: 324452
Data Storage Type: VARCHAR2
Max Length: 40
Required: No
Primary Key: No
Status: Active
Description:

The username of the last person who modified this record. This username is dynamically captured by the database trigger any time the record is edited.

General Data Type: VARCHAR2

RECORD_LAST_EDITED_ON_DATE

CC ID: 324453
Data Storage Type: TIMESTAMP(4)
Max Length: 11
Required: No
Primary Key: No
Status: Active
Description:

The last date that the particular record was modified. This date is dynamically captured by the database trigger any time the record is edited.

General Data Type: TIMESTAMP(4)

Catalog Details

Catalog Item ID: 32704
GUID: gov.noaa.nmfs.inport:32704
Metadata Record Created By: Jeffrey W Cowen
Metadata Record Created: 2016-05-09 14:20+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+0000
Metadata Record Published: 2016-05-11
Owner Org: NWFSC
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2016-05-11
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2017-05-11