[Esip-discovery] [EXTERNAL] use case collection form

Wed May 6 17:14:38 EDT 2020

Jonathan,

I think that is a great mission statement for the Discovery Cluster!

I think the next thing we would want to elicit from the Community Resilience Cluster is an example of a specific practitioner, what their specific application is, and then an imagining of how they would *like* to find the most likely-to-be-useful datasets by looking at what similar practitioners used.
—
Christopher Lynnes   NASA/GSFC    mobile: 410-231-4573
“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.” A. de St. Exupery

On 5/6/20, 17:02, "Blythe, Jonathan N" <Jonathan.Blythe at boem.gov<mailto:Jonathan.Blythe at boem.gov>> wrote:

Hi Chris,

  The Community Resilience Cluster would like to collaborate with the discovery cluster on a use case.  Here is a blurb from our problem statement that is still in draft, but feel free to use it for your survey.  Maybe we could make it more concrete with precipitation data use stories?  I'm open to suggestions and any constructive feedback.

Thank you,
Jonathan

from the community resilience problem statement (draft language, please excuse typos, please do not distribute outside the decision cluster)

"Are data fit for use?
The presentation of earth science may be one particular cause of knowledge challenges, since it may be difficult to know when you have found the data that are needed to address your question.  Different communities have their own specific needs and it may be difficult to ascertain whether a dataset that is generally useful for answering a question is useful in the particular case. The earth sciences have developed keywords to tag dataset according to their anticipated uses (citation), which satisfies federal agencies’ needs to demonstrate applicability of their research products, but it prescribes uses for datasets that often go unverified. These keywords fit within the earth science’s ontology of data uses, but place based communities often need to know about more specific aspects of those applications.

A novel application of discovery metadata is to append previous exemplars of a dataset’s usage.  Here, secondary users of data annotate how data have been applied in specific scenarios, using a technology called knowledge graphing.  Therefore, instead of searching across characteristics of datasets and their primary uses, examples of actual use in derived and more applied scenarios may highlight how data were able to be applied by secondary users to elucidate a challenge to very particular questions to solve specific problems.  Therefore, discovery of data based on derived and applied uses of the data may be particularly helpful to practitioners who don’t have enough training in the originating scientific discipline to anticipate how data that are generally useful for a question is applicable to their own questions.

The usage of data is not a characteristic of that data, and it becomes added value to that data that may append to catalogs and websites where the data may be made discoverable and accessible to a broader audience.  This functionality may not be all that useful to scientists working in the originating field, because they have a good grasp of a dataset’s utility, and can rather easily assess the particular scenarios where a dataset may be useful in application.  However, practitioners don’t have this facility with the originating scientific discipline, and are not going to research primary literature in order to find datasets that may be useful to their questions. Access to a library of scenarios where datasets have been applied to specific societal problems may help practitioners identify the relevance of data to their own questions.  A resilience genome has been proposed to address knowledge challenges in the agriculture and climate decision-making space (Wee and Piña, 2019), and knowledge graphing technology may provide the needed infrastructure to bring these initiatives for particular societal issues  and problem spaces to bear."
________________________________
From: Esip-discovery <esip-discovery-bounces at lists.esipfed.org> on behalf of Lynnes, Christopher S. (GSFC-5860) via Esip-discovery <esip-discovery at lists.esipfed.org>
Sent: Monday, April 27, 2020 10:04 AM
To: esip-discovery at lists.esipfed.org <esip-discovery at lists.esipfed.org>
Subject: [EXTERNAL] [Esip-discovery] use case collection form

Dear ESIP Discoverers,

I’d like to propose the following template for collecting use cases from some of the other clusters. I’ve gone with the bare minimum of information I think we need to identify use case. As we need more detail for particular use cases, we can go back to respondents to get it. (In fact, having that kind of dialogue is in some respects as important as the information itself.)

1.       Who am I? – I’m a state highways engineer

2.       What am I trying to do?  Predict where I’m most likely to have landslides in the next month.

3.       What do I want/need? – I want rainfall data for the last 3 months over my state. And some soil moisture wouldn’t go amiss.

4.       How do you solve this problem now? – I surf around a bunch of landslide portals, trying to suss out what kind of rainfall datasets they use.

5.       What would the Easy Button for this look like? – I go to a single applications portal, click on “Data for Landslide Prediction” and get a list of all the datasets used by a variety of landslide models and other applications.

Comments?  It would be great if we could initiate a dialogue with other clusters interested in our effort by, say, Thursday.

—

Christopher Lynnes   NASA/GSFC    mobile: 410-231-4573
“Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that’s creativity.” - C. Mingus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.esipfed.org/pipermail/esip-discovery/attachments/20200506/384be15e/attachment-0001.htm>