Difference between revisions of "Talk:AQ Data Summit Agenda"

From Earth Science Information Partners (ESIP)
Line 18: Line 18:
 
# Planned enhancements/data system trajectory
 
# Planned enhancements/data system trajectory
 
# Data System Issues or perceived weaknesses
 
# Data System Issues or perceived weaknesses
 +
 +
===Re: Clarification on 1st Plenary Session -- [[User:Erinmr|Erinmr]] 16:37, 31 January 2008 (EST)===
 +
We want instructions to presenters to be clear, and we want presentations to naturally support subsequent discussions. I think we can do this by having presenters reference a standard information value chain (and accompanying diagram which I will draft, based on views tss/and distribute tomorrow) based on the following "value added" stages from the profile:
 +
# Data collection,
 +
# primary data storage/management, (e.g. system is a primary/official storage site for some type of some data..e.g AQS)
 +
# data aggregation/processing/integration/sourcing, (system stores
 +
copies of data from external sources and/or manages links to them, ELT
 +
tools, and data warehouses fall in here)
 +
# analysis/visualization/reporting
 +
# decision support (some level of integration into a business process
 +
decision)
 +
 +
Here is how I would propose we instruct presenters.
 +
 +
'''Session Objective:'''  Explain what the system does and does not do.
 +
 +
Each Presenter Will Address:
 +
 +
# Summary description of System and Usage
 +
## Data types and spatial, temporal and compositional attributes
 +
## primary user and/or supplier groups
 +
## Overview and elaboration of major functions of the system per our standard value chain, is it end to end or is it focused on some part of the chain. What are most important functions?
 +
### We can cover "connections to other systems as part of stage 3 (data aggregation/processing ect). I recommend that these be active/managed connection to the system, not            passive uses.
 +
# Planned enhancements/data system trajectory
 +
# Data System Issues or  perceived weaknesses not covered in the planned enhancements (does this still make sense?)
 +
 +
I'd propose we discuss "Gaps" during the group session, i.e. are there major functions or domains we have missed.

Revision as of 15:37, January 31, 2008

Other Discussions:

Clarification on 1st Plenary Session -- RScheffe 01:28, 30 January 2008 (EST)

Nick [Mangus], thanks for pointing out the greyness of the session objectives for the first plenary...does this help?..

Session Objective: Explain what the sustem does and does not do. Each Presenter Will Address:

  1. Summary description of System and Usage
    1. Data types and spatial, temporal and compositional attributes
    2. primary user and/or supplier groups
    3. connections to other systems?? Louis/Rob/Rudy…what is meant here?
    4. Primary Storage???...Louis/Rob/Rudy…what is meant here?
  2. Planned enhancements/data system trajectory
  3. Data System Issues or perceived weaknesses

Re: Clarification on 1st Plenary Session -- Erinmr 16:37, 31 January 2008 (EST)

We want instructions to presenters to be clear, and we want presentations to naturally support subsequent discussions. I think we can do this by having presenters reference a standard information value chain (and accompanying diagram which I will draft, based on views tss/and distribute tomorrow) based on the following "value added" stages from the profile:

  1. Data collection,
  2. primary data storage/management, (e.g. system is a primary/official storage site for some type of some data..e.g AQS)
  3. data aggregation/processing/integration/sourcing, (system stores

copies of data from external sources and/or manages links to them, ELT tools, and data warehouses fall in here)

  1. analysis/visualization/reporting
  2. decision support (some level of integration into a business process

decision)

Here is how I would propose we instruct presenters.

Session Objective: Explain what the system does and does not do.

Each Presenter Will Address:

  1. Summary description of System and Usage
    1. Data types and spatial, temporal and compositional attributes
    2. primary user and/or supplier groups
    3. Overview and elaboration of major functions of the system per our standard value chain, is it end to end or is it focused on some part of the chain. What are most important functions?
      1. We can cover "connections to other systems as part of stage 3 (data aggregation/processing ect). I recommend that these be active/managed connection to the system, not passive uses.
  2. Planned enhancements/data system trajectory
  3. Data System Issues or perceived weaknesses not covered in the planned enhancements (does this still make sense?)

I'd propose we discuss "Gaps" during the group session, i.e. are there major functions or domains we have missed.