...

1. Make sure you are connected in your new home.
2. Relieve your counterpart. Take charge.
3. Courier duties: transfer and deliver any IT content in your possession.
4. Apply database and web-service updates.
5. Reset database defaults for expedition and projects.
6. Create user accounts, manage application roles & privileges.
7. Review what database accounts will be expiring soon. Let those folks know--set expectations.
8. Clean & preen the database. Includes summary data cache in OVERVIEW application.
9. Check that database triggers are enabled.
10. Programs to run.
    1. Remind the Publications specialist to start the Virtual Photo Table compositer.
    2. Start the iRIS Collector utility on the physical host in the MCS office. Or otherwise confirm it is running.
    3. Enquire with the Ops Manager and the Drillers that their iRIS interfaces are up and running.
11. Pull the current list of core catcher types LIST_ENTRY where LIST='CC_TYPE'. Chat with the Core Techs. - Do we still need this. Can we retire this?
12. Check with the DESC tech to see if DESC value list entries need to be made available to the SEM uploader. - Do we still need this. Can we retire this?
13. Replace GEODCAT with the latest definitions from shore (LIMSHQ.GEODCAT--under normal circumstances this is the primary catalog).
14. Honor moratorium. Assist other technical staff with this expedition preparation.
15. Expedition readiness. Assist other technical staff with expedition readiness concerns.

...

• Laptop connectivity to the network? Internet?
• Email account on ship active?
• Able to access file systems? Printers?
• Can you get to the password safe? The database?
• Can you get to your account on the BUILD box and DEV workstation? The dev account (for as long as we continue to do that).
• Can you get to Nexus and Subversion?
• Is the Subversion sync process still running? - BUILD (c:/srv/rsync/rsyncd.log)
• Are your software distribution credentials still functional? Development, Test, Production?
• Are you your database accesss access credentials still functional? Development, Test, Production? Can you reach shore too (in case required)?
• Can you access your Confluence accounts?

...

• If shore sends out desktop/server software distributions with you, ensure the media is turned over to the MCS.
• If you have Moisture and Density container information, make sure it is staged in a location you can find it when you are ready to process those containers.
• If the science party requested legacy data to be available for the on-coming expedition, you should have that data and a plan for making it available.
• If you have software updates for development or laboratory support, stage them under here: \\NOVARUPTA\VOL3\DML\

...

5. Reset database defaults for expedition and projects

Use SQLDeveloper SQL Developer to make these database changes for the newly started expedition. As soon as possible. Technical staff are running instrument and lab readiness procedures on the first day on-board. Laboratory standards (calibrations, checks, controls, blanks, etc.) do not follow a geophysical hierarchy so depend on some of these settings to be associated with the current expedition.

1. Set the default expedition for LIMS.

   Code Block
   update lims.lims_constants set constant_value='&currentExp' where name='EXPEDITION';

   
   

2. If legacy data has been loaded run the appropriate compute procedure to generate display content for the OVERVIEW report.
   
   In SQLDeveloper SQL Developer browse LIMS.LIST_ENTRY where LIST='MENU'. Edit the record with NAME set to the previous expedition. Change the expedition name in the NAME column from the previous expedition to the current expedition. Change all the instances in the VALUE column from the previous expedition to the current expedition.
   
   

3. Add a new project list entry for PROJECT.
   

   Code Block
   In SQL SQLDeveloperDeveloper browse LIMS.LIST_ENTRY where LIST='PROJECT'. Edit the existing record to reflect the current expedition or add a new record.

   
   

4. Auther privileges - requested by the LIME team, particularly
   • All scientist accounts are removed (just like with Oracle).
   • New scientist accounts are added.
   • No changes will be made to "tech" accounts.
   • New scientist accounts will have only the generic Scientist Role assigned.
     Any special roles needed are handled by Curator.
     
     
5. Are there any new personnel?
   • Do they have the necessary lab application access privileges?
     Curators manage Auther roles and privileges. Give a hand as-needed to new Curators.
   • Check-in with the individual(s), MCS, ALOs to ensure email, storage, Confluence resources have been allocated and are accessible.
     If there's an on-boarding check list, we should follow it.
   • Ensure appropriate GEODESC operator privileges are applied.
     
     
6. Changes in application authorization
   • SampleMaster
     • If a new ALO or Curator is participating, ensure they have the SampleMaster curatorial role.
     • If a new Driller is participating, ensure they have the SampleMaster driller role.
   • GEODESC
     • Participant roles for GEODESC users are managed by the GEODESC Admin.
     • If a new GEODESC Admin is participating, ensure they are setup with the necessary permissions and training.
   • Desclogik - This application is "not quite dead yet". The infrastructure will be maintained until the Thin Section Report Writer is brought current and confirmed to not need to be fed by any Desclogik worksheet constructions.
     • Participant roles for Desclogik users are managed by the Desclogik Admin.
     • If a new Desclogik Admin is participating, ensure they are setup with the necessary permissions and training.
   • Catwalk
     • If a new ALO or Curator is participating, ensure they have the CURATOR role. This ensures access to the Template Manager and Settings.
   • Other accounts - Crossover with off-going developers to verify if any significant access changes were made. See the development password safe for credentials . If you make any credential change relevant to development work, please update the safe to reflect the change.

...

Remove previous expedition content. Maybe remove 999 (play core content). Ask Technical Staff and ALOs first.

CONFIRM WITH THE OUTGOING DEVELOPER THAT WE HAVE A GOOD COPY OF THE PREVIOUS EXPEDITION EXPORT. Review the EOX export (and spot-check import) logs.
CONFIRM THAT THE MCS HAVE A GOOD COPY OF THE EXPEDITION EXPORT, ASMAN FILES (OLYMPUS), DATA1 content, and CONFLUENCE spaces on TAPE.

...

OVERVIEW. Review menus and content: remove items no longer carried on ship.
GEODESC. Remove prior project schema and associated authorizations, roles, permissions.
LIMS. Remove the one (or more) expedition(s) content not pertinent to current expedition work.
OPS. Remove IRIS related data from the previous expedition--on the order of 125 GiB for 60 65 days; ~5 million records.

...

This step is dependent on the completion of (7). Via SQLDeveloperSQL Developer, log into the LIMS account. Ensure that no triggers, functions, procedures, views are flagged by a red 'X' (indicates invalid or disabled content).

...

-- LIMSHQ as your DBA account, from within SQL
dp export -directory dmpdir -dumpfile to###-geodp.dmpdp -logfile to###-geodp.log -schemas geodp###

-- To restore on ship
drop user geodp### cascade constraints;                                                                          -- Delete the current schema
dp import -directory dmpdir -dumpfile to###-geodp.dmpdp -logfile to###-geodp-import.log -schemas geodp###        -- Restore from copy transported

...

2/13/2024: Removed constraints  from the end of the drop user geodcat  command. Was causing the script to fail. Left it on for the project schema because I did not have to run that command. - df Incorporated above for project too.

14. Honor moratorium.

Assist other technical staff with expedition preparation.

Typically this involves ensuring prior expedition content is removed from lab workstation and instrument host local hard drives.

15. Expedition readiness

Assist other technical staff with expedition readiness concerns.

If something worked the previous expedition, it is expected to work for you. Port call is the time to re-check / re-test. Do what you can early. Being on-site and scrambling isn't worth it when it can be readily and simply avoided.