Page Comparison

...

Panel
title Registration Terms and Conditions
Dave or Dayna needs to fill this in

Terms and conditions presented during the signing ceremony (when the processor has entered fish ticket data into the program and is submitting the data to NMFS) includes the following statement just above the required signature block:

...

The proposed design implements the following audit trail controls for submission of e-tickets via email:

Panel
Dave or Dayna needs to re-write section below to describe how you actually get submissions through email or web

1. The NMFS email interface program will run periodically (perhaps every 5 minutes), login to the postoffice, and open the inbox.
2. The email interface program will consider every message currently in the inbox, and for each message:
   1. Log receipt of the email message into audit trail tables.
   2. If the email message is recognized (recognized messages were generated by e-ticket software and submitted by registered permit holders).
      1. Generate a unique e-ticket message identier.
      2. Handle possible return-receipt-requested.
      3. Extract e-ticket message payload(s) (zip attachments)
         1. For each e-ticket payload:
         2. Log receipt of payload into audit trail tables.
         3. Unzip and unmarshall the payload, creating an e-ticket object; if payload cannot be unzipped or unmarshalled the receipt is formed from the raw input data and unzip/unmarshall errors are noted and logged.
         4. Process the e-ticket object, inserting into the database (if possible) and creating a receipt (appropriate data checks are applied in this step and any errors noted in the receipt.)
         5. Return the receipt to the appropriate party.
         6. Log the result into audit trail tables.
3. These audit trail data items should be written to audit trail tables by the email interface application using a database account which has insert privileges to the database but does not have update or delete privileges. (And update and delete privileges on the audit trail tables should be carefully controlled by the database administrator.)

...

1. After the data import program has interpreted (or attempted to interpret) the submitted e-logbook data, the data import program writes a receipt file. The proposed receipt will consist of note

   Panel
   Dave or Dayna needs to describe the receipt and check that the statements below are accurate

2. Assuming that the data import was successful, or at least successful enough that the e-logbookticket's permit could be ascertained, the receipt file will also be emailed directly by the data import program to the address of record for the permit holder
3. If the receipt file cannot be emailed directly to the address of record for the permit holder the operator executing the data import program is notified so that they can take steps to inform the submitter

...

The guidance document section 4.2 states "for a record to remain reliable, authentic, with its integrity maintained, and usable for as long as the record is needed, it is necessary to preserve its content, context, and sometimes its structure."

Panel
Dave or Dayna needs to check that the statements below are accurate

The proposed e-signature enabled system preserves content (ticket data), context (audit trail data and permit data), and structure (links among related tables) by maintaining a historical record of all changes to its database tables. Updates to the data result in inserts into history tables, leaving the prior values intact in the history records. Deletions of data result in insertions into history tables that indicate that the prior data is no longer valid. But in all cases, the history records allow reconstruction of a point-in-time view of the data.

...