32704 SPS_ARCHIVE Entity Published / External 17904 SPS Abundance - Salmon spawner abundance data compilation and database management Data Set Planned 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 Table Yes SPS 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. ARCHIVE_ACTION VARCHAR2 15 No No Active The action performed on the archive either created or deleted. VARCHAR2 RECORD_STEWARDSHIP VARCHAR2 40 No No Active 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. VARCHAR2 ARCHIVE_DB_ID NUMBER 22 Yes Yes Active 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. NUMBER ARCHIVE_NAME VARCHAR2 50 Yes No Active 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. VARCHAR2 ARCHIVE_NOTE VARCHAR2 4000 No No Active Any notes from the data providers. Indicates what the archive is to be used for. VARCHAR2 RECORD_APPROVED_BY_PERSON VARCHAR2 40 No No Active If there is a certification process for these records, name of person who certified approval of the particular record. VARCHAR2 RECORD_APPROVED_ON_DATE DATE 7 No No Active If there is a certification process for these records, date that the particular record was approved or officially certified. DATE RECORD_CHANGE_COMMENT CLOB 4000 No No Active 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. CLOB RECORD_COMPUTER_LOAD_BY_USER VARCHAR2 40 No No Active 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. VARCHAR2 RECORD_COMPUTER_LOAD_ON_DATE TIMESTAMP(4) 11 No No Active 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. TIMESTAMP(4) RECORD_CREATED_BY_PERSON VARCHAR2 40 No No Active 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. VARCHAR2 RECORD_CREATED_ON_DATE TIMESTAMP(4) 11 No No Active The date, or approximate date, that the person with content knowledge originated this record PRIOR to its being entered into the database. TIMESTAMP(4) RECORD_EFFECTIVE_DATE DATE 7 No No Active If necessary, the date that the individual record becomes effective. Prior to this date the record is not valid. DATE RECORD_EXPIRATION_DATE DATE 7 No No Active 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. DATE RECORD_HISTORY CLOB 4000 No No Active An accumulated set of statements describing how THIS RECORD has been edited over time including WHEN and by WHOM. CLOB RECORD_JOURNAL_NOTE VARCHAR2 4000 No No Active 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. VARCHAR2 RECORD_LAST_EDITED_BY_USER VARCHAR2 40 No No Active 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. VARCHAR2 RECORD_LAST_EDITED_ON_DATE TIMESTAMP(4) 11 No No Active The last date that the particular record was modified. This date is dynamically captured by the database trigger any time the record is edited. TIMESTAMP(4) RECORD_NUMBER_OF_EDITS NUMBER 22 No No Active 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. NUMBER RECORD_SOFT_DELETED VARCHAR2 1 No No Active 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. VARCHAR2 ARCHIVE_AUDIENCE VARCHAR2 30 No No Active The audience for the data. Either internal or public. If public the data is available through the SPS application interface. VARCHAR2 gov.noaa.nmfs.inport:32704 Jeffrey Cowen 2016-05-09T14:20:01 SysAdmin InPortAdmin 2022-08-09T17:11:00 2016-05-11 Northwest Fisheries Science Center NWFSC 2725 Montlake Boulevard East Seattle WA 98112 USA 206-860-3200 https://www.nwfsc.noaa.gov 1001 Public No 2016-05-11 1 Year 2017-05-11