DELETE_FROM_SPS

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.

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

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.

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.

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.

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.

Database-generated primary key (unique identifier) for each DELETE_FROM_SPS 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 DELETE_FROM_SPS_PK.

The foreign key to pull in the Population Name for the source database.

The year that adults enter the river to spawn.

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

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.

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

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

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.

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.

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.

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

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

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.