• Created by Unknown User (fackler), last modified on Mar 09, 2023

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

BOX - beginning of expedition
EOX - end of expedition

About EOX

The outgoing programmer(s) is(are) responsible for all EOX activities.

The first goal is to ensure a good copy of the data gets back to HQ.
An equally important goal is to leave laboratory and data management systems in an operational state for hand-off to your counterparts.

Please read this entire document and EOX - rationale and FAQ. Expect to take 3 to 4 hours to complete this exercise. While the database dump can occur in 20 min for 61 GiB--operational decisions and technical staff concerns with their portion of the data management will take time to address.

The process has been much simplified. Do not hurry. If you are "fried"--work together. 

Checklist / Overview

  1. Deliver the end-of-expedition report to the LO (that you have been writing throughout the expedition). Post a copy to the development team via Slack. See examples from prior technical reports for formats and variations.
  2. Establish with MCS, LOs, CoChiefs when the final database snapshot will be taken for EOX.
  3. Circulate through the labs. What data didn’t get into the database? Provide support and training to help get the data in or find an appropriate place for it. 
  4. Honor moratorium. Once content is uploaded to LIMS, and raw files have gone to data1, expedition-specific data may be cleaned off of instrument hosts and workstations. Good practice to confer with technical staff that manage this for their labs. There is variance between crews as to how these procedures are carried out.
  5. Conduct end of expedition procedures for backing up the database.
  6. Provide courier services if called upon to do so.
  7. Confirm with the MCS what is to be included in the backup going to shore and that it does cover all the information you are aware of that should go to shore.
  8. Ensure all your code changes are checked in.
  9. Clean the development office. Assist in the general cleaning efforts. 
  10. Be ready to move out. Your replacement will be here soon.
  11. Provide assistance and information to oncoming developers.
    Assist them to accomplish their oncoming duties.
    They may not have sailed for quite a while, plan to
    1. Review your changes.
    2. Review the current state of the labs.
    3. Review the current state of deployed applications.

Out of Scope

These checklist items are included to raise full process awareness. Other actors than the developers are responsible for these equally critical activities. The sooner done, the sooner accessible.

  1. Retrieve data content from tape. Distribute it to Publications, Data Librarian, DBA, Operations, and public access storage locations. - Systems
  2. Restore (routinely selected) database content from the full backup to the shore production transfer schema. - DBA
  3. Establish moratorium credentials and controls for the expedition data. - DBA
  4. Copy the content into the publicly accessible LIMS. - DBA
  5. Update the Database Overview configuration to summarize the added content. - DBA
  • No labels