...

Read the tech report. Exchange information. What's changed? What's broke? Is there anything outstanding that should be taken care of for laboratory readiness or shipboard operations for the new expedition? Swap war stories.

3. Courier duties

...

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

...

alter table lims.sample enable all triggers;

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

...

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]).

13. Replace

...

GEODESC catalog and projects with the latest definitions from shore

...

GEODCAT

...

Export a copy from LIMSHQ before the expedition. Bring it along (order of megabytes).

Code Block

-- LIMSHQ as your DBA account, from within SQL dp export -directory dmpdir -dumpfile to###-geodcat.dmpdp -logfile to###-geodcat.log -schemas geodcat -- pick up the output file from s1:/backup/export/ -- To restore on ship dp export -directory dmpdir -dumpfile geodcat-yyyymmdd.dmpdp -logifle geodcat-yyyymmdd.log -schemas geodcat -- Backup up the current state drop user geodcat cascade constraints; -- Delete the current schema dp import -directory dmpdir -dumpfile to###-geodcat.dmpdp -logfile to###-geodcat-import.log -schemas geodcat -- Restore from copy transported

GEODP###

If prior work was done on shore, bring a copy out.

Code Block
-- 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

If no prior work exists for the GEODESC project, create a new one per the scripts at Create New GEODESC Project (GEODPnnn) Schema – Ship

• Be sure to catalog the new schema password in the shipboard safe.
• Spotcheck newly created or imported schemas to confirm operability and access to existing data:

...

• Do templates load? Can new samples be added to DataCapture working sets?

...

14. Honor moratorium.

Assist other technical staff with expedition preparation.

...