BOX - beginning of expedition
EOX - end of expedition

The DBA is responsible for shore EOX processing. In a pinch programmers and systems personnel can fill in (they just don't know it yet).

This expedition is ended. Within two weeks, science participants expect to have moratorium access to LIMS content. DBA, Systems/MCS, and sometimes Programmers need to coordinate to help this happen. The Database Librarian needs to know when these changes occur too.

Make sure we are getting as complete a copy of the data to be warehoused on shore as we can.

0. Notify that the data load is in progress

Lot's of folks want to know: Systems, Data Librarian, Programmers, EPMs, Managers, selected TAS staff.

1. Retrieve data content from tape

Distribute it to Publications, Data Librarian, DBA, Operations, and public access storage locations. - Systems

2. Restore

Restore routinely selected database content from the full backup to the shore production transfer schema. - DBA

3. Establish moratorium credentials and controls

For the new expedition data. - DBA

4. Copy the content

Into the publicly accessible LIMS. - DBA

5. Update the Database Overview

Configuration updates provide summary of the expedition data for participants and future users. - DBA

To be worked in. The scripts below are applicable to steps 2. thru 5.

EOX load and merge - rci_work/exp

The collection of scripts in this location is used to automate the shore components of EOX processing: retrieve last expedition content from the database dump, create and apply moratorium supports, merge the data into production; provide statistics which give quality assurance/quality control on the process.

These are the scripts (in-order) that are typically used

Other script

tbd