Apr. 9, 2004

Thetus project

What interaction do we want to have with Thetus Inc.?
Do we need to further investigate Thetus
Do we want to enter a 'live' workflow into Thetus
Can we learn from this architecture and how they solve metadata capture/management/query problems
I don't think we answered any of these questions at this meeting. Tell me if this is not so.

ES3 architecture

Debbie has come up with some 'must have' metadata items for ES3
Debbie will create xml files for MODIS ingest and Mike's DEM and will help to determine:
- what metadata ES3 should capture automatically
- what is the minimum set of required metadata
what data is transfered between ES3 clients and server:
- lineage
- metadata (i.e. for transformations, file objects)
- profile information (name of person responsible for data product)
- annotation information
ES3 should support capturing a 'grab bag' of info
- user may have a bunch of files and just wants ES3 to remember them
- lineage links between items supported but not required
- like a manually entered single workflow invocation
- could be accomplished with just drag and drop (i.e. drag and drop and IDL script and data file)

Example workflows

Peter will be responsible for providing AVHRR product needed by Walter and creating/recording workflow metadata for this

Other