Talk:AQ Data Summit Agenda

Other Discussions:

• Data Systems
• Data Summit
• Data System Profile Development

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 -- NMangus

Rich, My concern is just to make sure each speaker knows exactly what to cover so that we get comparable views of each system.

I'm going to ask questions to clarify what info is desired for each system....

On connections to other systems: Does this mean on the front end (incoming data) or on the back end (outgoing data)? Does it include passive connections (Rudy asks for my data once per year) as well as active connections (I'm networked into DataFed).

On primary storage: Is this data elements (specific data fields), type of data (measured, reduced, modeled, projected, etc.), format (netCDF vs. Oracle), technical architecture (SAN array at EPA), or simply the question of whether this data system represents the primary storage repository for particular data. Like, AQS would be primary storage for PM2.5 species measurements, the HEI database would be secondary storage, and something further downstream would be tertiary, etc. Thanks,

Re:Re: Clarification on 1st Plenary Session -- Louis Sweeny (Louis) 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)
4. analysis/visualization/reporting
5. 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.

Here are answers to Nicks good questions: On connections to other systems: Does this mean on the front end (incoming data) or on the back end (outgoing data)? Does it include passive connections (Rudy asks for my data once per year) as well as active connections (I'm networked into DataFed). Active connections, managed by on the source system end. So yes for DataFed (since I assume you manage that connection) but NO to periodic passive request

On primary storage: Is this data elements (specific data fields), type of data (measured, reduced, modeled, projected, etc.), format (netCDF vs. Oracle), technical architecture (SAN array at EPA), or simply the question of whether this data system represents the primary storage repository for particular data. Like, AQS would be primary storage for PM2.5 species measurements, the HEI database would be secondary storage, and something further downstream would be tertiary, etc. the latter, is the system the primary/official repository for particular data (and which)

Re: Re:Re: Clarification on 1st Plenary Session -- NMangus

Louis, Thanks for the clarifications - makes sense to me.