[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[CONDUIT #YAW-321892]: Let's add data to CONDUIT!

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [CONDUIT #YAW-321892]: Let's add data to CONDUIT!
  • Date: Thu, 17 Jul 2014 08:54:43 -0600
Hi Becky,

I apologize for the very slow response to your email below!

re:
> We are finally ready to start adding new model data to the CONDUIT
> system here in College Park.  We have a nice, large LDM queue, so I'd
> like to finally start providing some new data to the users.
> 
> We had done the survey a few years ago and I can dig out those results.
> And then hopefully we've done a few new things since then.
> 
> How would you like to move forward?

I agree with you that it is time to move forward with additions to
CONDUIT.  The items that will come up from the CONDUIT user community
are:

- what products are currently in CONDUIT

  Duh!?  In reality, folks forget what they are already receiving
  _and_ using on a day-to-day basis.  The delivery of data via the
  IDD has become like the deliver of power by a utility: the data
  comes in with essentially no interaction; processing of the data
  proceeds with no interaction; etc.  The only time a user thinks
  about the data they are getting is when the data flow stops for
  whatever reason.

  We need to remind users of everything that is available in CONDUIT
  and their associated volumes.

- what data could be added to CONDUIT

  This needs to be a comprehensive list of data sets that could be
  made available and a list of "pie in the sky" (i.e., not so easily
  made available) items

- a good idea of the time frame for surveying the community, compiling
  users' responses, deciding which data sets should be added, informing
  the end-users of the decisions made and then implementation

I say let's start working on the items above (and any that I have forgotten)!

BTW, the Unidata User's Committee needs to be involved in some of the
items above.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: YAW-321892
Department: Support CONDUIT
Priority: High
Status: Closed