<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.gmailsignatureprefix
{mso-style-name:gmail_signature_prefix;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:740270;
mso-list-template-ids:1025826766;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal">Rama.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Esip-preserve <esip-preserve-bounces@lists.esipfed.org>
<b>On Behalf Of </b>Megan Orlando via Esip-preserve<br>
<b>Sent:</b> Wednesday, November 29, 2023 11:46 AM<br>
<b>To:</b> elishawc@lbl.gov; esip-preserve@lists.esipfed.org<br>
<b>Subject:</b> [EXTERNAL] Re: [Esip-preserve] possible data stewardship idea<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hi Everyone,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">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. <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">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.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">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.<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">What do others think?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Megan<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span class="gmailsignatureprefix">--</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">Megan Orlando<o:p></o:p></p>
<div>
<p class="MsoNormal">ESIP Community Director<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:meganorlando@esipfed.org" target="_blank">meganorlando@esipfed.org<br>
</a><o:p></o:p></p>
<div>
<p class="MsoNormal">Please note my new last name.<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Wed, Nov 29, 2023 at 2:28 PM Elisha Wood-Charlson <<a href="mailto:emwood-charlson@lbl.gov" target="_blank">emwood-charlson@lbl.gov</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Aloha ESIP data stewardship committee!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">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. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I drafted some ideas into a G-doc <a href="https://docs.google.com/document/d/14rvBVGyr-KhnsiJFzhECU1Tgem-8Z3sqQCawQifxbM4/edit?usp=sharing" target="_blank">
here</a>. The main goal would be to <i>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).
</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><u>Proposed Scope of Effort</u><o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Identify ESIP groups, committees, members that work on use case topic (e.g., wildfires)<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Set up community interviews to learn about their Qs and data sources<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Establish small cross-data source teams to explore metadata required to support data integration/interoperability<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
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<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Draft report on process and finding and determine if useful/relevant to try to apply to other use cases, scale<o:p></o:p></li></ol>
</div>
<div>
<div>
<p class="MsoNormal">Happy to field any questions, ideas, thoughts. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Cheers, <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">-Elisha<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span class="gmailsignatureprefix">-- </span><o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Elisha M Wood-Charlson, PhD (she/her)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fkbase.us%2f&c=E,1,3CKWYbssJzyYqduHq8VnPP0E07uz3C6Eico3htB5qzCGt1KZ93kxbY8T97V8hI6DoyAWBQOtK1YPx5MCS5VU0_nT8a8PT2XTFKvZoXi2KJceV93q&typo=1" target="_blank">KBase</a> User Engagement
Lead; <a href="https://twitter.com/doekbase" target="_blank">@DOEKBase</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Lawrence Berkeley National Laboratory<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="http://www.linkedin.com/in/elishawc" target="_blank">LinkedIn</a>,
<a href="https://twitter.com/ElishaMariePhD" target="_blank">Twitter</a> (personal)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Want to get credit for more than just a publication? Check out our
<i><a href="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" target="_blank">10
simple rules on getting and giving credit for data</a></i>, and then let me know so we can help you publish data in KBase.
<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>