...

Make sure we are getting as complete a copy of the data to be warehoused on shore as we can.goal is to ensure a good copy of the data gets back to HQ.

Please read this entire document and its companion. Expect to take 3 to 4 hours to complete this exercise. (I keep saying this only takes 15 minutes. But that really is just the individual database dump processes.) Do not hurry. If you are "fried"--work together. 

0. Readiness assessment.

0. Negotiate a time window

Work with Work the LO, ALOs, EPM, MCS, laboratory technical staffTechnical Staff. Three weeks before the end of the expedition you should have an (increasingly clear) idea how and when these activities will transpire.

...

It is Ok to ask repeatedly. It is an exercise in planning and preparation which helps us collectively focus and prioritize the tasks to be done.

1. Deliver the EOX tech report

Deliver the end-of-expedition technical report to the (place in Confluence specified by the) LO.
Please post a PDF export of it to jrso-developer on Slack.

See the Confluence Lab Notebook space for prior examples of the development technical report. Keeping a daily activity log throughout the expedition aids in the timely preparation of the report.

The report can be the basis of cross-over discussions. It is also a records of expedition activities and concerns that can provide context to future users of IODP data.

2. Establish when the final database snapshot will be taken

Recapitulation of 0. Continue talking to the LOs, ALOs, CoChiefsEPM, MCS, and laboratory Technical Staff to clarify this timing.

• It takes 20 minutes to run a full database export (for 61 GiB of data)--but we want it to be as complete as possible within the constraints of expedition activities.
• The MCS routinely stage expedition content for convenience of copying via Science Office and User Room workstations. Timing of that activity is a common communication at the end of the expedition.

3.

...

Spot check data copy efforts

Recapitulation of 0, 2. Be an additional set of eyes and ears.

...

Often there is both expedition-specific and individual variance. Much room for improvement in the current process.

4. Honor moratorium

...

If end-of-expedition activities are harried and crunched--don't do this step. Leave the data for the (fresh) oncoming developers and technical staff to accomplish. 

Once content is uploaded to LIMS, and raw files have gone to data1, and routine backup cycles have occurred: expedition-specific data may (in-general) be cleaned off of instrument hosts and workstations.

These activities are the purview of laboratory technical staff. Often assistance is welcome.

There is precedent for this activity to be pushed to the (fresh) oncoming crew. Totally depending on timing of last core on deck and timing of arrival in portIt is good practice to assist technical staff in this activity: both to raise awareness of its complexity, and to consider opportunities for automation and improvement. At busy times it can help reduce individual workload. Well managed labs will have staging areas where expedition-specific data is placed so it can be readily managed in this context.
Good practice to confer with technical staff that manage this for their labs. There is variance between crews as to how and when these procedures are carried out. It is possible to do these activities on a site-by-site basis rather than just EOX.

5. Conduct EOX database backup

...

1. Establish with MCS, LOs, CoChiefs when the final database snapshot will be taken for EOX.
2. Circulate through the labs. 
3. 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.
4. Conduct end of expedition procedures for backing up the database.
5. Provide courier services if called upon to do so.
6. 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.
7. Ensure all your code changes are checked in.
8. Clean the development office. Assist in the general cleaning efforts. 
9. Be ready to move out. Your replacement will be here soon.
10. Provide assistance and information to oncoming developers.
    The goal of all oncoming personnel is to ensure the function of laboratory and computing systems to support the successful execution of the new expedition.
    Assist with those goals.
    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.