Page Comparison

...

Pre Expedition Activities

• Work with the staff scientist expedition project manager to determine if any external data (such as previous expeditions from Janus) will need to be loaded is required in LIMS for use during the expedition. If so, pre-load the data to LIMS on shore and export it to take to the Extract the required content for transport to ship. 
• Work with the staff scientist and TAS expedition project manager and laboratory staff to determine if any third-party instruments will be used during the expedition. If so, determine how the data is to be captured and reported. If necessary (and possible) create any required parsing or loader routines before traveling to the ship and take them with you. 
• Work with Analytical Services to determine if any containers or other information needs to come from shore. If so, assist Analytical Services to pre-load the data to LIMS on shore and export it to take to the ship. 
• Review change management records from the ship to know what has been done recently.
• Work with laboratory staff. Transport container data to ship for moisture and density. Be aware of new or changed instrumentation being supported.
• Review the science prospectus to become aware of the expedition goals and plans.
• Review current technical reports and change management records to be aware of recent changes. 
• Check with the AD supervisor on the latest development projects you will be working on during the expedition. 
• Get the Prospectus for the expedition you are participating in. Read it.

Port Call – oncoming, early expedition

• Make sure Ensure your computing equipment will plug-in and that you can function on the shipboard network without having account and/or password issues. Make sure you still have the correct password for the ship dev account, password safe, and other required ship access. Get the current password(s) from the off-going developer(s) as needed. 
• Read the previous crew's expedition reports, thoroughly.
• Circulate through the labs. Talk to the off-going technical staff. What worked? What didn’t? What can be improved? 
• Repeat with any off-going scientists you can catch. What worked? What didn’t? What can be improved? powers up and successfully connects to ship and shore networks.
• Cross-over with offgoing staff regarding credential changes. Confirm your shipboard passwords and access: Oracle non-privileged and DBA accounts (test and production); ship and shore password safes; credentials for the storage network and email; credentials for build and dev resources, including software distribution credentials for the application servers.
• All personnel have responsibilities to ensure expedition data is returned to the shore warehouse. Review and confirm: data is backed up and ready for transport, we are clear to prepare the database for the new expedition.
• Prepare the database system for the new expedition.
• Cross-over with off-going developers. What happened? What changed? What’s changing? What worked? What didn’t? Where can we improve?
  • Review change management records
  with them to assist in the discussion of what has changed during
  • from the previous expedition. 
  Spot check and confirm that releases in the source code repository match deployments in production and that you have the correct source code for what is being used. 
  • Read the prior expedition reports, thoroughly.
  • Confirm that you have access to (current) source code for recently changed product.
  • Spot-check
  the normal
  • routinely used services to ensure they are functioning
  and available
  • :
  Web page, Web-Tabular Reports, Cumulus technical documents, Oracle databases, E-mail, Network & File services, Test database, Wiki. 
• Determine exactly what was copied / exported and is on the backup going to shore. Confirm contents if necessary. This is to prevent accidental “cleaning” of information that did not get sent to shore. 
• Review the developer’s end of expedition reports from the previous expedition. 
• Attend introductory meeting(s) or any other safety or training meeting(s)
  • sampling programs, LIMS reports, MUT uploaders, web pages, Confluence support pages. SQL Developer access, LIME data editor.
• The labs are being made ready for expedition use. What is changing? What needs improvement? Anything not working that requires your knowledge and support? Prioritize, advertise.
• Repeat with any off-going scientists you can catch. What worked? What didn’t? What can be improved? 
• Attend introductory meetings including required safety and/or training meeting sessions. 
• Assist with loading/unloading freight and other tasks as directed by the Lab Officer or Assistant Lab Officer. 
• Plug in the travel drive(s). Dump a copy of information being transferred to the ship to the network or another machine. Synchronize any change management, source control, or document content that needs to be updatedProvide courier services as-needed. If data was brought out, load it. If digital media were brought out, deliver it to those who requested it.
• You have expertise in software and code. Help others leverage that expertise.

General Activities during an expedition

• Cross-over at least once a day with the other developer on ship.
  • Ensure they are aware of what you are working on and any ongoing problems that you are aware of.
  • Update your activities in
  Trello and
  • the
  Google Site activity logs as appropriate
  • ship activity log. These are effective tools to communicate and support the first item.
  Cross-over at least twice weekly with your colleagues. What’s working? What’s not? What can be improved? Colleagues for this include the MCS, Curation, and TAS staff. 
• Be present at laboratory staff cross-overs (as your shift assignment allows). Be aware of staff and science participant software concerns. Learn about what they do.
• Spend at least 2 hours every shift up in the labs with the scientists and techs. Provide assistance in learning and using applications, capturing, managing, and reporting data, and general support for use of computing resources on ship. 
• Provide notifications to the change management team on ship and shore BEFORE modifying applications. This is done by sending an email to jr_developer when development work is begun. Keep appropriate records of changes as described in the Change Management Procedures. 
• Provide notifications of all changes to production applications and common libraries by email to jr_developer. Make sure to include the reason for the modification. 
• Keep the source code repository up to date so that releases in the repository match deployments on the ship. If it was deployed, it should have been checked in.

...