BOX - beginning of expedition
EOX - end of expedition

About BOX

The incoming developerprogrammer(s) is(are) always responsible for all BOX activities. And for some of the EOX activities. 

Ship-based activities are described. In many cases pre-expedition preparation is required.

For a repository of shipboard developer programmer resources see the Developer space on shipboard Confluence:  http://confluence.ship.iodp.tamu.edu:8090/display/RAADND/Random+Access%3A+Application+Developer+Notes+and+Documentation+Home.  

Checklist / Overview

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. Clean & preen the database. Includes summary data cache in OVERVIEW application.
8. Check that database triggers are enabled.
9. Programs to run.
   1. Remind the Publications specialist to start the Virtual Photo Table compositer.
   2. Start the IRIS-Collector.exe on the Ops office engineering station.
10. Pull the current list of core catcher types LIST_ENTRY where LIST='CC_TYPE'. Chat with the Core Techs.
11. Check with the DESC tech to see if DESC value list entries need to be made available to the SEM uploader.
12. Replace GEODCAT with the latest definitions from shore (RTLIMS.GEODCAT, or Blum source spreadsheet).

...

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.
   

   Code Block
   In SQLDeveloper 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 SQLDeveloper 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.
     
     
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.

...