...

Your duties require information technology connectivity. A lot of change happens in our environment between expeditions. Verify your tools and access:

• 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).
• Are your software distribution credentials still functional? Development, Test, Production?
• Are you database accesss credentials still functional? Development, Test, Production?
• Can you access your Confluence accounts?

2. Relieve your counterpart

...

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.

Examples

• 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: \\
CLEVELAND
• NOVARUPTA\VOL3\
AD
• DML\
dml

4. Apply database and web-service updates

...

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

   
   
   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.

...

Best source of user names: the expedition science party email list maintained by the EPM (expedition project manager) for on-going project communications. 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 permissionPermission and authorization required.

• Create accounts for new participants - - participants_add.sql
• Delete the accounts for those who are leaving or have left the ship. Use
• Adapt the script in Subversion to our current needs - participants_remove.sql.

7. Clean the database

Remove previous expedition content; maybe . Maybe remove 999 (play core content) too--ask technical staff . 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.

...

Prior expedition content is to be removed to enforce moratorium. Use this reference until you are comfortable with detailed reference to go through the process.

8. Check that database triggers are enabled

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

A pattern to enable all triggers for a table. Must have appropriate privilege for the target tables.

alter table lims.sample enable all triggers;

This pattern is applicable to SAMPLE, TEST, RESULT, GEOD_DATA, etc.

If invalid triggers exist, track down why. Look for the Oracle-specific errors via SQL Developer. Give another DBA a holler.

9. Programs to Run

Start the Virtual Photo Generator

If not already present, help set it up on the Publications Specialist host. This should be the ONLY location that runs it.

Start the IRIS-Collector

If not already present, help set it up on the Ops Engineer station. This should be the ONLY location that runs it.

...

1. In SQL Developer, look at the table, sorted by HIER_KEY.  At the bottom, you might find one or more expedition-specific entries (they'll have an expedition number in their names).  Delete these.
2. This documentation describes the process of adding new values for your expedition:  SEM uploader X_SEM_HIERARCHY table.
3. If the above documentation is confusing, here are some notes:
   1. The data in this table represents a hierarchy, and the PARENT value for each record links back to the HIER_KEY of that item's parent.   
   2. For example, "igneous rock names", "sediment names" and "metamorphic rock names" (HIER_KEY = 80, 90, 100) all link back to "LITHOLOGY" (HIER_KEY = 10).  On expedition 396, we added three entries, with each one linking back to one of the three lithology items just mentioned, so their PARENT values were 80, 90, 100.
   3. If you've done this properly, you should be able to run the SEM uploader and (after selecting an image, which can be anything), see the name(s) you added when you pick the parents (e.g. Category = LITHOLOGY → General subcategory = igneous rock names → Exp. specific subcategory = [your entry or entries]).

12. Replace GEODCAT with the latest definitions from shore

TBD - RTLIMS.GEODCAT, or Blum source spreadsheet?
This needs to become routine (as does catalog merging and updates of taxonomies.

13. Honor moratorium.

Assist other technical staff with expedition preparation.

14. Expedition readiness

Assist other technical staff with expedition readiness concerns.