...

Read the tech report. Exchange information. What's changed? What's broke? Swap war stories.

3. Courier duties

Deliver all transported media and equipment to their responsible parties. Stage any software-related components and tools in the appropriate locations. Make sure our own content survived the trip by connecting the media.

...

Use SQLDeveloper to make these database changes for the newly started expedition.1.

1. Set the default expedition for LIMS.

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

...

1. 
   

   
   

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.

...

1. 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.

   
   
   
2. Auther privileges

...

1. - requested by the LIME team

...

1. , 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.

...

1. • 
     Any special roles needed are handled by Curator.

...

1. • 
     
     
2. Are there any new personnel

...

1. ?
   • Do they have the necessary lab application access privileges?
     Curators manage Auther roles and privileges. Give a hand as-needed to new Curators

...

1. • .
   • 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.
     
     
2. Changes in

...

1. 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

...

1. • - 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

...

1. • • ensures access to the Template Manager and Settings.
   • Other accounts

...

1. • - 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.

6.

...

Manage laboratory application accounts

See Subversion for the last created versions of the script: https://build.ship.iodp.tamu.edu/svn/wapps/Database/DbScript/participants

Best source of user names: the expedition science party email list maintained by the staff scientist EPM (expedition project manager) for on-going project communications. The MCS will have a list of the accounts the created and since we use the same names get their list when they are done.Obtain the list from the MCS as they routinely receive it before we do. The expedition participant list may also be retrieved from the Crew N Cruise application. Requires permission.

• Create accounts for new participants--
• Delete the accounts for those who are leaving or have left the ship. Use - participants_remove.sql.

7. Clean the database

Previous Expedition. Maybe play core data (999)Remove previous expedition content; maybe remove 999 (play core content) too--ask technical staff and ALOs first.

CONFIRM WITH THE OUTGOING DEVELOPER THAT WE HAVE A GOOD COPY OF THE PREVIOUS EXPEDITION EXPORT.
CONFIRM THAT THE MCS HAVE A GOOD COPY OF THE EXPEDITION EXPORT, ASMAN FILES (OLYMPUS), DATA1 content, and CONFLUENCE spaces on TAPE.

DO NOT PROCEED UNTIL CONFIRMATION RECEIVED.

OVERVIEW. Review menus & and content: remove items no longer carried on ship.

...