Talk:Data Summit Workspace

From Earth Science Information Partners (ESIP)

Other Discussions:

Decision Support Schematic -- RScheffe 20:31, 16 January 2008 (EST)


Below is the WRAP DSS Architecture slide Neil and I were discussing during last week's call. The idea is that it conveys in a simple means the steps from raw data to inteegration/manipultaion and finally tro decision making. We would use this as a guide for the braek outs to focus on the left and center portions of the diagram. Anyawy...I'd like to use today's call to flesh out soem specifics/questions/gyuidance for the day 1 breakout groups. Rudy/Terry...and all.(David, Phil...Nick, ...) ..join if you can...originally just Joe and I were going to workk with Louis behind the scenes on some of these steps...but chime in if you can...if nothing else, it will keep you apprised of what is going on...

Re: Decision Support Schematic -- Rhusar 12:56, 24 January 2008 (EST)

Yes! See On Decision Support System Architectures

Data Summit Table-- Tesh Rao 17 January 2008 (EST)

Data Summit Table - Word Doc
I expanded the table a bit, but not too much. I mainly look at it as link, that definitely needs to be maintained from am day one to pm day one to day two. It can be polished a bit as needed.

This could be one of the items handed to the breakout sessions for completion during its individual discussion. The (my kind of half-baked) idea it to use this to "tie" things together. Under each "business topic" category, the groups would identify which raw data systems and which data processing centers are most important via this table. Then, the group would discuss, theoretically, which of the chosen attributes are most important in summation when we begin talking about a "system of systems." {There may need to be more than one of those depending on application...which is what we want to discuss and best to streamline that :-) ). Those thought would go in the colored row at the bottom of each of the table subsections. Talk could even be focused on whether any data processing center that is existent and mature now can handle many of the attributes that we arrive at for each "business topic." Then the discussion can expand, as possible and do-able, to streamlining techniques across all the business topics. Beyond that, a few other points:

  • In the 8 minute presentations in the morning of the 1st day, on top of the items we gave to Lou Sweeny as topics for each speaker to cover, I would add something that describes the maturity of the system in question (as well as perceived user community). Only after today's RSIG meeting did I realize that it has advanced so far in terms of implementation (though the number of users is probably small in that case). Also covered should be issue of sustainability for each of the systems. If the presenters have examples/papers/reports/policy related work that has been done using their system (this wouldn't really apply to some of them like AQS), it would be good to identify those briefly.
  • We are addressing 4 very broad "business topics"--and the ones chosen are good--but we should think about anything we are missing (as far as future importance for OAQPS) under the umbrella of topics we have. Climate Change, for example, comes to mind.
  • I am sure there will be discussion items that come up that aren't directly related to any of the structured discussion items, but may be important to the overall big picture. I would have the note-takers keep track of those in a "parking lot" list.
  • When Tsirigotis/Curran were here, we had a discussion about how a data analyst spends 80% of any given project on data assimilation, data reduction, and general data readying. Only 20% of his/her time is spent on actual visualization/interpretation. The idea as we think about approaching a "system of systems" is for being able to reduce the 80% number for a data analyst. One of Airquest's initial goals was to do this. This could be framed as a discussion item for the breakout sessions. Even though we have a proliferation of tools now for accessing (ambient) data now compared to say 6-7 years ago, this 80/20 split hasn't gone down a great deal.
  • Again, after today's RSIG meeting, we need to manage time very effectively, otherwise we could get caught in a very narrow discussion of relatively few topics. Need the facilitator to keep track of time well. And, you have it on the agenda, but next steps should be clearly delineated both at the beginning of the first day and especially at the end of the second day.
  • To me, this is a very needed discussion and it needs to be done efficiently and well. There just seems to be so much overlap between systems that exist now (AQ, RSIG, etc.) and funds seems to be used for duplicative items. I'll stop here for now.

Data Summit Workspace -- Stefan Falke (Sfalke) 28 January 2008 (EST)

Joe, As we discussed on the phone this morning, the wiki has been updated with links to the "modular" wiki pages containing the Data Summit content. Please take a look at the wiki and workspace to see if this is what you envisioned.

Each individual wiki page (e.g., participants, agenda, etc.) should now be "shared" between the Workspace and Wiki so any changes to those pages are reflected in what people see whether they're coming from the workspace or wiki. The particpants page would need to be updated with your latest list. The documents listed on the wiki page are not yet all reflected on the workspace but will be.

Re: Data Summit Workspace -- joe tikvart (Jtikvart) 28 January 2008 (EST)

Stefan, Thanks! This looks good. I especially like the new "front page" with links to all the workshop components. Couple of comments:

  1. I don't see a link from the "workspace" back to "documents" on the main page. Related, it seems to me that "Manual Resources", "Harvested Resources", and "Documents" are all of the same ilk in terms of resource materials; all could be lumped together on the "workspace".
  2. The telecon notes under "What's New" and "Background" are the same; we probably only need one link.
  3. We will resolve the issue of a participant e-mail list on tomorrow's conference call.

Notes for the Jan 29 Data Summit Telecon -- Rhusar 13:51, 29 January 2008 (EST)

  • Data system profiles have been prepared to aid the classification, intercomparison of the various data systems. If these data system profile forms are filled out prior to the Feb. 12 meeting, Louis, Rich and others could (1) analyze the profiles, (2) present the outcome at the meeting, and (3) support the breakout session discussions.
  • Following the call to "chime in", a wiki page has been prepared on the topic of On Decision-Support System Architectures, highlighting the differences between 'stovepipe', networked, and user/market-driven architectures.
  • Prepared a collage 'Perspectives on GEOSS, Air Quality, IT' consisting of excerpts from presentations by Foley, Scheffe, Keating, Szykman, Niebert, Percivall and Husar. Would you spare an idea, yours or someone else's? e-mail ideas to and we will add it to the collage.
  • Data Summit participants may be interested in the GEOSS Architecture Implementation Pilot. Contributions for defining and reviewing the 'smoke scenario' would be particularly welcome.

Monday Pre-Meeting before Data Summit -- NFrank 29 January 2008 (EST)

Rudy is working on a project for me and I have invited him to make a few 90 minute data-summit related presentations to EPA on Monday Feb 11. Topics will include DataFed - indepth overview; and Exceptional Events analysis, as a DataFed application.

I am also thinking that a more substantive presentation to EPA about RSIG and maybe VIEWS would also be good to include that day.

Rich was going to send out an preliminary announcement last week but it apparently didnt happen. :-)

Just wanted you to know in case you want to come a day early and to tentatively block time on your calendar. I will send out more details later.

Re: Monday Pre-Meeting before Data Summit -- NFrank 30 January 2008 (EST)

Here is a summary of the scheduled meetings for Monday Feb 11 in class room C112. For those who cannot attend, we are seeing if the sessions can be recorded for subsequent viewing on the web.

  • Environmental Geo Web Services, Ravi Nair and Gary Walter, (9-9:45) Environmental Geoweb involves geospatial technologies for accessing and visualization of earth science information (focus on satellite data and “layering” capability).
  • DataFed (Husar): (10a-11:30a) DataFed is Web services-based software that non-intrusively mediates between autonomous, distributed data providers and users. DataFed is designed in accordance with the GEOSS architecture, so that it provides standard interfaces to heterogeneous distributed data, fosters data integration and use with processing services and tools, and collects metadata and user-feedback on datasets. DataFed provides access to over 50 distributed, air-quality relevant datasets which can be explored and analyzed by tools for processing and visualization.
  • RSIG Demo/training (1230-2p) The Remote Sensing Information Gateway (RSIG) provides a way for users to get the multi-terabyte, environmental dataset they want via an interactive, Web browser-based application. With RSIG users are able to download and parse files (environmental data and models) in minutes, and to integrate selected datasets into a unified visualization.
  • Exceptional Event(2:30-4) --Technical Analyses , as application of DataFed Illustrative Air Pollution Event Analyses in accordance with EPA's Exceptional Events Rule.

Post-Summit wiki maintenance -- Erinmr 13:21, 21 February 2008 (EST)

Hi Joe, We would like to add the reports from the Data Summit Breakout Sessions to the wiki workspace. Could you ask the note takers to send me ( a word doc or to post their notes directly to the breakout session pages they belong to? Thanks - Erin

Re: Post-Summit wiki maintenance -- JTikvart 13:23, 26 February 2008 (EST)

Erin, After discussing your suggestion with Rich and a couple of the notetakers, we think that it would be best to wait for the Ross report for the breakout session summaries. The major points were captured on extensive flipcharts which are being summarized by Louis/Rob and will be a much better representation of those sessions than the somewhat scattered other notes that were taken. We hope that those summaries will be available in about two weeks. Thanks for staying ahead of the curve! The wiki site looks really good.

Jon Miller found an error in his original presentation and provided a correction. Please place the corrected attached file on the wiki. Also, I noted that the indicated participants for the breakout groups are from earlier draft lists. The second attached file contains the lists that we posted at the meeting; so an update to the wiki would be appreciated. Thanks!

Finally, I note that there isn't a presentation for the DAAC's since the folks from NASA couldn't make it to the meetiing and the replacement presentation was ad hoc. I will see if I can get something to fill in.

Re: Re: Post-Summit wiki maintenance -- Erinmr 13:25, 27 February 2008 (EST)

Hi Joe, all of the updates that you asked for have been made. The new AQS presentation is uploaded and linked to the presentations/agenda, the participant list for each breakout session have been modified and the presentation for DAAC has been added to the presentation/agenda as well.

How do we keep the wiki going? -- David McCabe (Davidmccabe) 25 February 2008 (EST)

Rudy, Stefan, Looking at the wiki pages that were generated for the AQ data summit, there has been ~0 activity since the summit. Actually, I have tweaked the Airnow page, but that it is it. This is not surprising, but it demonstrates that we certainly don't have much momentum on building a wiki that helps users figure out what is there, etc.

Here are my questions:

  • any way to keep people going on this?
  • I made a bit of an effort to generalize the wiki pages developed for the AQ summit so they no longer appear to exist only for the data summit. I think we should port these pages to make them more general, and open the formatting so users can do what they want with the wiki pages. (As opposed to the current form-based pages.) Thoughts?

Might we discuss these issues on Friday's call?

Re: How do we keep the wiki going? -- Stefan Falke (Sfalke) 26 February 2008 (EST)

David, Yes, the post-workshop lull. It is a usually a challenge to maintain the energy involved in coming together for a workshop. The workshop raised some common themes (community-driven activity, metadata creation/use, move toward standard SOA interactions, ...) that could serve as rallying points for at least subsets of the Summit participants. Some of the Summit breakouts had suggested meetings to move forward (e.g., identify the core standards a data provider needs to join the network). While those meetings are being organized, perhaps initiating the discussion through wiki/email/other could help maintain the momentum.

The profiles were one of the Summit successes created by most, if not all, of the participants. One possible next step is to begin capturing the interaction among the projects. We started this through a matrix ( but it has proven difficult to edit and is not "community friendly." Google Spreadsheet has added some features since we last looked at it that may make it more attractive. Perhaps there is a better way than an online spreadsheet but, in any case, it seems trying to define those connections as they are now and then assess how they might be improved would be useful in maintaining the community energy and preparing for a response in anticipation of Terry's AMI RFP.

I agree, the wiki material created for the Summit should be reconfigured so that it doesn't appear to only pertain to the Summit. A combination of form-based and free form pages might be a good approach to accommodate both content input as well as content discovery. How that mix is defined would need some thought.

Yes, please raise these for discussion Friday. Please add to the topic list/agenda on the telecon page:

Re: Re: How do we keep the wiki going? -- Erinmr 01:00, 28 February 2008 (EST)

In response to David's comment about how to keep people going on the wiki I have added a new page on general wiki resistances. I have started it with some of my own issues, please add others.

Data Summit WorkspaceTalk:Data Summit Workspace