[Esip-preserve] [EXTERNAL] Re: possible data stewardship idea

[Yuhan Douglas Rao]

Hi Elisha,

Echoing Rama's comment - I think it is a great idea. I would also encourage
to think beyond just earth system data and bring in other types of data
into the project.
As people start to look at integrating earth science data, socioeconomic
data, and other data like citizen science data and community data, the
process becomes more complex.
ESIP community has groups that are very interested in aspects like
community resilience and the impact side of physical phenomena.

Cheers!
-Douglas

[image: NCICS] <http://ncics.org/> Yuhan (Douglas) Rao
*Research Scientist*
Pronoun: he/him/his
North Carolina State University <http://ncsu.edu/>
North Carolina Institute for Climate Studies (NCICS) <https://ncics.org/>
151 Patton Ave, Asheville, NC 28801
e: yrao5 at ncsu.edu
o: +1 828 271 4903


On Wed, Nov 29, 2023 at 5:44 PM Hampapuram Ramapriyan via Esip-preserve <
esip-preserve at lists.esipfed.org> wrote:

> I think this is a great idea. In fact, in the Information Quality Cluster
> meeting yesterday, Ge Peng was suggesting that we should take on the
> discussion of provenance and implementation issues to make provenance
> visible to users. The ideas presented by Elisha fit very well to accomplish
> that and I believe are worth pursuing. I see that it will be a challenge to
> bring the various interested parties to gehter and coordinate, but the Data
> Stewardship Committee is the right place to do that! All the best.
>
> Rama.
>
>
>
> *From:* Esip-preserve <esip-preserve-bounces at lists.esipfed.org> *On
> Behalf Of *Megan Orlando via Esip-preserve
> *Sent:* Wednesday, November 29, 2023 11:46 AM
> *To:* elishawc at lbl.gov; esip-preserve at lists.esipfed.org
> *Subject:* [EXTERNAL] Re: [Esip-preserve] possible data stewardship idea
>
>
>
> Hi Everyone,
>
>
>
> For a little more context, the current Chair of Data Stewardship has
> needed to step out of the role. The Program Committee will appoint a new
> Chair and Elisha may agree to be that person, but first wanted to determine
> whether other Committee participants share her enthusiasm for the direction
> she is interested in going in.
>
>
>
> From my perspective, this sounds like a great and very concrete direction
> to head in that will involve cross-collaboration area connections with a
> number of other ESIP groups.
>
>
>
> Anyone on this mailing list is invited to speak up if this idea resonates
> with them, regardless of whether or not you have the energy to
> contribute in a major way. Questions are also welcome. All input is
> especially invited before next Wednesday Dec. 6.
>
>
>
> What do others think?
>
>
>
> Thanks,
>
> Megan
>
>
>
> --
>
> Megan Orlando
>
> ESIP Community Director
>
> meganorlando at esipfed.org
>
> Please note my new last name.
>
>
>
> On Wed, Nov 29, 2023 at 2:28 PM Elisha Wood-Charlson <
> emwood-charlson at lbl.gov> wrote:
>
> Aloha ESIP data stewardship committee!
>
> As I often ask too many questions about data and the research process
> during ESIP calls, Megan asked me if I would be willing to present a
> possible project to this group - as something we could consider working on
> for the rest of the year's term.
>
>
>
> I drafted some ideas into a G-doc here
> <https://docs.google.com/document/d/14rvBVGyr-KhnsiJFzhECU1Tgem-8Z3sqQCawQifxbM4/edit?usp=sharing>.
> The main goal would be to *explore what is necessary to link ESIP data
> streams in meaningful ways that support accurate navigation across the data
> landscape, by humans and machines (AI/ML). *
>
>
>
> *Proposed Scope of Effort*
>
>    1. Identify ESIP groups, committees, members that work on use case
>    topic (e.g., wildfires)
>    2. Set up community interviews to learn about their Qs and data sources
>    3. Establish small cross-data source teams to explore metadata
>    required to support data integration/interoperability
>    4. Prep a ESIP summer meeting session to report out, get feedback -
>    what are we missing to make connection, what data sources would others need
>    to address additional Qs
>    5. Draft report on process and finding and determine if
>    useful/relevant to try to apply to other use cases, scale
>
> Happy to field any questions, ideas, thoughts.
>
> Cheers,
>
> -Elisha
>
>
>
> --
>
> Elisha M Wood-Charlson, PhD (she/her)
>
> KBase
> <https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fkbase.us%2f&c=E,1,3CKWYbssJzyYqduHq8VnPP0E07uz3C6Eico3htB5qzCGt1KZ93kxbY8T97V8hI6DoyAWBQOtK1YPx5MCS5VU0_nT8a8PT2XTFKvZoXi2KJceV93q&typo=1>
> User Engagement Lead; @DOEKBase <https://twitter.com/doekbase>
>
> Lawrence Berkeley National Laboratory
>
> LinkedIn <http://www.linkedin.com/in/elishawc>, Twitter
> <https://twitter.com/ElishaMariePhD> (personal)
>
>
>
> Want to get credit for more than just a publication? Check out our *10
> simple rules on getting and giving credit for data
> <https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fjournals.plos.org%2fploscompbiol%2farticle%3fid%3d10.1371%2fjournal.pcbi.1010476&c=E,1,aCH8GjHcnz7iZb_STFteziE-OnzSN55SF3Fb6cyTROXr4XvTk-9vwVfnGG-Mlt4APKG__HMWOsKGL38LQwu4r1io3eepZc8cKBJ_UIr7x9RX&typo=1>*,
> and then let me know so we can help you publish data in KBase.
>
>
>
>
> _______________________________________________
> Esip-preserve mailing list
> To start a new topic: Esip-preserve at lists.esipfed.org
> To unsubscribe and manage prefs:
> https://lists.esipfed.org/mailman/listinfo/esip-preserve
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.esipfed.org/pipermail/esip-preserve/attachments/20231204/0378c804/attachment.htm>