First CHRONOS IT meeting
San Diego Supercomputer Center May 13, 2003
Participants:
CHRONOS: Bohling, Cervato, Diver, Fils, Koppers, Wardlaw
SDSC: Archbell, Baru, Bhatia, Kwon, Lin, Seber
NSF: Lane and Snyder
IT goals for first two years:
Three interlaced datasets (life, time and time scale)
Visualization and analytical tools
Portal construction
Key points discussed:
Statement
All data should be included
Task
This requires appropriate qualification
(metadata). More detailed metadata description
would indicate higher quality data. Paleostrat
database (GeoVision) has developed high
quality, detailed metadata that we could use to
start.
We need to develop standards for all data - the
challenge is to get people (scientists) to follow
the standards. Be as broad and inclusive as
possible. The task groups should achieve this.
The biostrat task group should convene asap to
determine how we should approach taxonomy.
Use a two-tier approach: use existing
technology (e.g., Webservices that GEON is
using - ‘wrap on top’ approach - JDBC to Data
sources) to make fast technological progress at
first, then push the creative IT development
(GRID services to GEON as Data Mediator;
open source software)
CHRONOS as one of the GRID nodes. Hardware
and software fully compatible (GEON POP Point Of Presence - with Rocks software at
Central Hub with GEON’s Certificate of
Authenticity -CA - to access tools). Purchase
WebCams to allow live and cheap visual
communication between CHRONOS IT
programmers (Fils, Diver, Bohling with
SDSC).
Use a combination of WebDAV (Web-based
There are cultural differences between IT and
geoscience people
Need to achieve integrated database system
CHRONOS fully compatible with GEON
CHRONOS Portal with persistent data storage
1
for individuals (own working space)
Distributed Authoring and Versioning), with
SSL (Secure Socket Layer for security), SQL
database and Servlet engine. This would allow
users to store their data, rules and
manipulations in their CHRONOS folder on their
“CHRONOS space” accessible from their
desktop and be able to return to them and work
on them locally while actually being connected
to the CHRONOS network. This could also be
one potential mechanism to allow people to
upload their data into the CHRONOS system
(through their “My CHRONOS” account.
Also investigate the option of using GridPort
(developed at SDSC) used for GEON.
Build an inventory of potential data sources
and identify depth and diversity for data. To
achieve this we would build a database and
interface accessible through CHRONOS Portal
that allows users (“I am interested in
participating and sharing my data”) to register
the existence of a stratigraphic/ chronologic
database or dataset. It would include generic
attributes (Name, affiliation, description of
data, quality, data type and format, age range,
URL, contact info etc)
CHRONOS workshops at AAAS, GSA, AGU,
AAPG, SEPM meeting, get advice from the
community, need to show willingness to
change and shift if the community requires it.
Write papers in Geotimes, EOS, GSA Today,
G3 after August retreat. Approach NAS to host
international conference for CHRONOS to start
global initiative to study interface issues with
different databases (Geoinformatics).
CHRONOS as community resource - how do we
find out what’s out there?
CHRONOS as community resource - PR aspects
How do we interface different databases?
 Obtain information on type of database, system, accessibility, data model (schema)
 Evaluate what it would take for connection - creating interface/wrapper (JDBC to data source
for first 2 years, GRID services later on)
 Decide on hosting (Central Hub, data replicated at SDSC through GRID), if necessary.
Automatic data duplication for federated databases (hosted elsewhere, ongoing, separately
funded database projects like USGS Paleodata and PaleoBiology db)
Time plan
Task
Deadline
Responsible
2
CHRONOS Hardware on line
Prototype CHRONOS Portal on
line (www.chronos.org)
Neptune db on line (in
PostgreSQL) with relations
and tools (expansion of
Neptune coordinated with
Huber and Leckie to concur
with IT development)
Ontology for radiometric db
August 1
August 15
Fils with SDSC
Fils, Cervato
End 2003
Fils, Diver, Cervato
End 2003
CHRONOS Interface available
to GEON
Visualization and analytical
applications
Metadata definition for
CHRONOS (bstrat first)
Full integration of EarthRef
and possibly second
radiometric db
Create schema for db in
thematic nodes
API for GeoVision and ODP
Janus
June 2004
Koppers, GEON (Ludaescher,
Kai Lin), and community
Fils
June 2005
Bohling, SDSC
June 2004
June 2005
Cervato, Huber, Leckie and
community (workshop)
Fils, Diver, SDSC
June 2005
Diver, Fils, Cervato
June 2005
Diver
Tidbits
 Check out WebMol, an open source 3D visualization and manipulation tool
(http://www.cmpharm.ucsf.edu/~walther/webmol.html) - we could adapt it for CHRONOS
needs (SDSC, Bohling, Fils)
 Interview and hire the second Central Hub programmer (Cervato, Fils)
 Move Visualization Tools workshop to year 1 to allow full integration with IT development
and identification of community requirements/wishes as early as possible (Bohling)
 Schedule Biostrat workshop as early as possible in fall 2003 with aim to lay out metadata,
ontology needs, and possibly tools required (Huber, Leckie)
3