Page Comparison

...

1. the NMFS employee who received the portal portable media will return to the office, login, and run start a data import processprogram.
2. the The data import process will program will present the operator with fields to record where and when the portable media was delivered, who delivered it and who received it. The NMFS data import program will record require this information before proceeding, and will institute appropriate data checks to ensure the most accurate data possible.  The data import program will record these fields as well as the login name of the operator, the time that the data import was run, and the raw uninterpreted contents of the submitted e-logbook file(s), into a NMFS database.
3. These audit trail data items should be written to audit trail tables by the data import 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.)
4. after After the this audit trail information is recorded the data import program can proceed to interpret the e-logbook data stream and insert the data into NMFS operational database(s).

Providing an Electronic Receipt or Acknowledgment of a Successful Submission

The system proposed is not online and does not provide a user interface directly to the customer.  As proposed the electronic signature is executed by certified (trusted) software onboard the vessel, but, since the data is being submitted to satisfy NMFS record keeping and reporting regulations, it seems appropriate that any receipt be provided by NMFS and not by the e-logbook software vendor.  Accordingly, the proposed receipt process is as follows:

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 an exact recapitulation of the submitted data with the following additions:
   1. a "ReceiptMessages" element will be added to the XML as a child element of the top level "LogbookReport" element
      1. the ReceiptMessages element will contain one or more messages documenting success or failure(s) in the interpretation of the e-logbook submission; in the best case, the returned message might consist of the text "ok"
   2. for each element in the returned XML which consists of a code, for example, gear code, the XML schema will provide an optional attribute for a name; when the XML is submitted from the vessel these optional attributes will not be present (and if they are present they will be ignored); when the XML is returned from the agency as a receipt, these optional attributes will be populated by the agency to indicate that the code was recognized and to confirm what the code represents
2. The receipt file will be written back onto the portable media if that media is to be returned to the vessel operator
3. Assuming that the data import was successful, or at least successful enough that the e-logbook'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
4. 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