Table of content
| Table of Contents | ||||
|---|---|---|---|---|
|
Purpose
The GEODESC application tool set was designed and built in 2019-2022 to support geological core description and micropaleontological data capture on the scientific drilling vessel JOIDES Resolution (JR). The GEODESC system includes five browser-based user applications backed by an Oracle database. The application features were designed to optimize the workflow on the JR based on decades of experience with coring projects all over the worlds' oceans, recovering a broad spectrum of Earth materials.
Design concepts
GEODESC is based on the user-approved concept of observational data capture in spreadsheets, whereby a row represents a description interval or domain, the first set of fixed columns defines the scope of description (sample identity and interval, etc.), and any number of configurable columns define observables. Observers can use existing templates configured based on corporate experience 'out of the box', modify existing templates, or create completely new templates.
System architecture
Figure 1: Schematic overview of GEODESC users, user applications, and database 'backbone'.
Limitations for external use
The GEODESC tool set is taking advantage of existing tools and resources on the JR for efficient data gathering and reporting, and therefore cannot easily be used outside the JR computing infrastructure. Most importantly, GEODESC is using
- the sophisticated sample registry that evolved over decades to accommodate user needs, and
- depth computation business rules for standard depths and alternate depths
If GEODESC was to be fully used in another organization, these resources would have to be replicated or replaced.
However, external projects can take advantage of the GEODESC catalog resources and final product data files, all available in tab-delimited text format, and use them in commercial spreadsheet programs with or without adding sample registry and data validation functions.
System architecture
Figure 1: Schematic overview of GEODESC users, user applications, and database 'backbone'.
Section 2