Versions Compared

Old Version 9

changes.mady.by.user jr_fackler

Saved on

compared with

New Version 10

changes.mady.by.user jr_fackler

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Ensure your computing equipment powers up and successfully connects to ship and shore networks.
  • Cross-over with off-going 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. See BOX checklist, detail, rationale (TBD include link).
    • Moratorium enforcements.
      • Expunge the previous expeditionsexpedition's database content. Note that some information may need to be retained from the previous expedition--for example play cores for JR Academies and Schools of Rock. As-needed confirm with the staff scientist.
      • Clean out archived files on all logger systems. Confirm with off-going and on-coming Physical Properties, Paleomagnetics, and Imaging staff what has been done.
    • Conduct beginning-of-expedition setups. 
  • Setup Manage laboratory accounts for scientists and techs. This includes: creating or enabling accounts for oncoming scientists and staff as well as ; and removing accounts for off-going scientists. Sometimes intervention is required with Auther permissions.
  • Cross-over with off-going developers. What happened? What changed? What’s changing? What worked? What didn’t? Where can we improve?
    • Read the prior expedition reports, thoroughly.
    • Review change management records from the previous expedition. Read the prior expedition reports, thoroughly.
    • Confirm that you have access to (current) source code for recently changed product.
    • Spot-check routinely used services to ensure they are functioning: 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.
  • 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. 
  • Provide 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.

...

  • Ensure the current copy of the shore code and dependency repositories are available to your preferred workstations. If not, update it. Merge in any changes you may need from shore for this expedition and rebuild those applications. Remember to notify jr_developer when you start work and jr_developer for deployments. 
  • Work with TAS and curation staff to identify and handle any special data requests. Everyone is working to get the new expedition off the ground (stores and supplies inventories and staged, equipment function and readiness reviewed). The questions you receive will lean that way, including but not limited to: 
    • Containers or vials to be entered in preparation for the new expedition. 
    • Sample request or sample planning data and content. 
    • Do any of the samples from the previous expedition carry over? Keep them in the database and flag them appropriately. 
    • Do any standard materials need new labels and database records created? 
    • Are repository samples being carried with the new expedition that will be analyzed? Do they need to be entered into the system? 
    • Have new pieces of equipment come on board that require software or data services to assist in configuration, automation? 
  • Cross-over with the technicians in each of the labs. 
    • Are the laboratory instrument systems up and functioning? 
    • Are the Sample Entry sample entry systems up and functioning? 
    • Are the Correlation correlation systems up and functioning? 
    • Are the Description description systems up and functioning? 
    • Are the Label Printing label printing and  engraving systems up and functioning? 
    • Start any required changes through the change management process.
    • Check with the Underway technician: are the Navigation and Bathymetry data feeds running Ok?
    • Ensure the video overlay feed is still connected to the RigWatch master and functioning. (Ops and MCS concern.)
    • Ensure iRIS data feeds are connected and running. (Ops and MCS concern)

...

  • Deliver the end-of-expedition report to the LO (that you have been writing throughout the expedition; send ). Post a copy to the AD Supervisor; copy it where the LO and ALOs can pick it up in Confluence. What worked? What didn’t? What’s changed? What can be improved?development team via Slack. See examples from prior technical reports for formats and variations.
  • Establish with MCS, LOs, etc. CoChiefs when the final database snapshot will be taken for EOX.
  • Circulate through the labs. What data didn’t get into the database? Provide support and training to help get the data in or find another an appropriate place for it. 
  • Is moratorium access being honored? Clean out archived files on all logger systems—collaborate/confirm with off-going Physical Properties, Paleomagnetics, and Imaging staff. Technical staff responsible for each lab take care of this for their instruments and workstationsHonor 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.
  • Conduct end of expedition procedures for backing up the database. You may be
  • Provide courier services if called upon to provide courier servicesdo so.
  • 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.
  • Ensure all your code changes are checked in.
  • Clean the development office. Assist in the general cleaning efforts. 
  • Be ready to move out. Your replacement will be here soon.

...