Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Use SQLDeveloper 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 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.

...

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 that is under moratorium and not pertinent to current expedition work.
OPS. Remove IRIS related data from the previous expedition (on the order of 100 GiB for 60 days; ~4 million records).

Prior expedition content is to be removed to enforce moratorium. Use this detailed reference to go through the process.

...