1<!doctype html> 2 3 4 5 6<html 7 dir="ltr" 8 lang="en" 9 10> 11 <head> 12 <meta charset="utf-8"> 13 <meta name="viewport" content="width=device-width, initial-scale=1"> 14 <meta name="theme-color" content=#ffffff> 15 <link rel="stylesheet" href="/assets/css/app.css"> 16 <link rel="shortcut icon" type="image/png" 17 href="/favicon.png" 18 /> 19
19<script src="https://cdn.jsdelivr.net/gh/alpinejs/[email protected]/dist/alpine.min.js" defer></script>
19 20 <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@5/css/all.min.css"> 21 22 <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/bulma-social@1/bin/bulma-social.min.css"> 23 24 <!-- Begin Jekyll SEO tag v2.8.0 --> 25<title>Data Management | ESS_CIWG</title> 26<meta name="generator" content="Jekyll v3.10.0" /> 27<meta property="og:title" content="Data Management" /> 28<meta property="og:locale" content="en_US" /> 29<meta name="description" content="Building Community Cyberinfrastructure for Environmental System Science" /> 30<meta property="og:description" content="Building Community Cyberinfrastructure for Environmental System Science" /> 31<link rel="canonical" href="https://ess-community.github.io/working-groups/data-management/" /> 32<meta property="og:url" content="https://ess-community.github.io/working-groups/data-management/" /> 33<meta property="og:site_name" content="ESS_CIWG" /> 34<meta property="og:type" content="website" /> 35<meta name="twitter:card" content="summary" /> 36<meta property="twitter:title" content="Data Management" />
37<script type="application/ld+json"> 38{"@context":"https://schema.org","@type":"WebPage","description":"Building Community Cyberinfrastructure for Environmental System Science","headline":"Data Management","url":"https://ess-community.github.io/working-groups/data-management/"}</script>
38 39<!-- End Jekyll SEO tag --> 40<!-- head scripts --></head> 41 42 <body> 43 44 <nav class="navbar is-primary " x-data="{ openNav: false }"> 45 <div class="container"> 46 <div class="navbar-brand"> 47 <a href="/" class="navbar-item"> 48 ESS_CIWG 49 </a> 50 <a role="button" class="navbar-burger burger" aria-label="menu" aria-expanded="false" data-target="navMenu" 51 :class="{ 'is-active': openNav }" x-on:click="openNav = !openNav"> 52 <span aria-hidden="true"></span> 53 <span aria-hidden="true"></span> 54 <span aria-hidden="true"></span> 55 </a> 56 </div> 57 58 <div class="navbar-menu" id="navMenu" :class="{ 'is-active': openNav }"> 59 <div class="navbar-start"> 60 61 62 63 64 <a href="/about/" 65 class="navbar-item "> 66 About 67 </a> 68 69 70 71 <div class="navbar-item has-dropdown is-hoverable "> 72 <a href="" 73 class="navbar-link "> 74 Working Groups 75 </a> 76 77 <div class="navbar-dropdown"> 78 79 <a href="/working-groups/data-management" 80 class="navbar-item "> 81 Data Management 82 </a> 83 84 85 86 <a href="/working-groups/integration" 87 class="navbar-item "> 88 Model Data Integration 89 </a> 90 91 92 93 <a href="/working-groups/software-engineering" 94 class="navbar-item "> 95 Software Engineering and Interoperability 96 </a> 97 98 99 100 <a href="/working-groups/computing-infrastructure" 101 class="navbar-item "> 102 Computing Infrastructure 103 </a> 104 105 106 107 <a href="/working-groups/ai-ml" 108 class="navbar-item "> 109 AI/ML 110 </a> 111 112 113 114 </div> 115 </div> 116 117 118 119 <a href="/events/" 120 class="navbar-item "> 121 Events 122 </a> 123 124 125 126 <div class="navbar-item has-dropdown is-hoverable "> 127 <a href="" 128 class="navbar-link "> 129 Community Resources 130 </a> 131 132 <div class="navbar-dropdown"> 133 134 <a href="/resources/reports" 135 class="navbar-item "> 136 Reports 137 </a> 138 139 140 141 <a href="/resources/webinars" 142 class="navbar-item "> 143 Webinars 144 </a> 145 146 147 148 </div> 149 </div> 150 151 152 153 154 </div> 155 </div> 156 </div> 157</nav> 158 159 <section class="hero is-small is-bold is-primary" style="background: url('/img/ess-ciwg-banner.png') no-repeat center center; background-size: cover;" > 160 <div class="hero-body "> 161 <div class="container"> 162 <p class="subtitle is-3"> </p> 163 <p class="subtitle is-3"> </p> 164 <h1 class="title is-2" style="color:#FFFFFF;">Data Management</h1> 165 <h1 class="subtitle is-3" style="color:#FFFFFF;"></h1> 166 167 </div> 168 </div> 169</section> 170 171 172 173 174 <section class="section"> 175 <div class="container"> 176 <div class="columns is-multiline"> 177 178 <div class="column is-12"> 179 180 181 182 183 184 185 186 187 188<div class="content"> 189 <p><strong>Data Management (DM) Working Group</strong> addresses data needs of the ESS Community:</p> 190 191<ul> 192 <li>Data Preservation, Sharing, and Publication</li> 193 <li>Common Data and Metadata Standards</li> 194 <li>Data Citation and Attribution</li> 195 <li>Data Federation across different data catalogs</li> 196 <li>Data Synthesis across ESS and other relevant data sources</li> 197 <li>Development of common Tools for data usage</li> 198 <li>QA/QC, processing, analysis, mining and visualizing data to prepare them for use, especially in new research applications such as AI.</li> 199</ul> 200 201<p>The <strong>Data Management Working Group</strong> collaborates with members of the ESS Community 202by providing opportunities to interact with each other through quarterly and annual 203meetings to ensure their short and long-term needs are met at ESS-DIVE and other DOE 204data type specific repositories (i.e. ESGF, EMSL, JGI, AmeriFlux). The opportunity for 205cross-project/institution/discipline interaction of our many forward-looking members 206is invaluable since data management is central to virtually all aspects of Environmental 207System Science and the ModEx cycle. By establishing shared, standard tools and workflows, 208the archival of the rapidly-growing, diverse data is facilitated. These archived data 209will inform model representations of environmental systems, and the model results and 210analyses should guide future data collections. Towards these goals, ESS-DIVE is the primary 211repository for archiving data generated by ESS projects following the guidance and 212requirements of the <a href="https://doi.org/10.11578/2023DOEPublicAccessPlan">2023 DOE Public Access Plan</a> 213and the DOE Office of Science <a href="https://science.osti.gov/Funding-Opportunities/Digital-D
213ata-Management">Statement on Digital Management</a>.</p> 214 215<h1 id="data-management-leads">Data Management Leads</h1> 216 217<table> 218<tbody> 219<tr> 220<td><img class="alignleft" src="/img/people/christianson.jpeg" alt="Danielle Svehla Christianson" width="150" height="150" /></td> 221<td valign="top"><strong>Danielle Svehla Christianson</strong><br /> 222<a href="mailto: [email protected]">[email protected]</a><br /> 223<em>Lawrence Berkeley National Laboratory</em></td> 224</tr> 225<tr> 226<td><img class="alignleft" src="/img/people/velliquette.jpeg" alt="Terri Velliquette" width="150" height="150" /></td> 227<td valign="top"><strong>Terri Velliquette</strong><br /> 228<a href="mailto: [email protected]">[email protected]</a><br /> 229<em>Oak Ridge National Laboratory</em></td> 230</tr> 231</tbody> 232</table> 233 234<p>Want to contribute? Ask the leads to join the Google Group: [email protected]</p> 235 236<h1 id="quarterly-meetings">Quarterly Meetings</h1> 237 238<p>The DM WG holds quarterly meetings in the 2nd month of the business quarter on 239the 4th Thursday at 12:00 PT / 3:00 ET (unless rescheduled due to holidays/conflicts).</p> 240 241<p>Past meeting topic and session leaders:</p> 242 243<h3 id="fy2026">FY2026</h3> 244<p>Q1: What is AI-Ready Data? Part 2 245<br />Charuleka Varadharajan and ESS-DIVE team (LBNL)</p> 246 247<h3 id="fy2025">FY2025</h3> 248<p>Q4: What is AI-Ready Data? 249<br />Douglas Rao (NOAA National Centers for Environmental Information)</p> 250 251<p>Q3: ML/LLM/AI/Agentic-AI Working Group discussion 252<br />David Moulton (LANL)</p> 253 254<p>Q2: Experiences & Improvements to Archiving Model Data Products 255<br />Zhi Li (PNNL), Rosemary Carroll (Desert Research Institute)</p> 256 257<p>Q1: ESS-DIVE Annual Data Workshop: Needs for ESS data discovery & use 258<br />Danielle Christianson (LBNL), Terri Velliquette (ORNL)</p> 259 260<h3 id="fy2024">FY2024</h3> 261<p>Q4: Tools for implementing Reporting Formats (continued) 262<br />Tom Ruggles, Terri Velliquette, (ORNL), Sigrid Dengel (LBNL) , Dylan OâRyan (LBNL)</p> 263 264<p>Q3: Tools for implementing Reporting Formats 265<br />Gilberto Pastorello, Valerie Hendrix (LBNL), Brieanne Forbes, Amy Goldman (PNNL)</p> 266 267<p>Q2: BERAC Unified Data Report & ESS-DIVE proposal input 268<br />Pamela Weisenhorn (ANL), Kjiersten Fagnan, Charu Varadharajan (LBNL)</p> 269 270<p>Q1: NMDC submission portal & EMSL metadata template 271<br />Montana Smith (PNNL)</p> 272 273<h3 id="fy2023">FY2023</h3> 274<p>Q4: Data integration brainstorming for BERAC Unified Data RFI 275<br />Kjiersten Fagnan, Danielle Christianson (LBNL)</p> 276 277<p>Q3: ESS CI Annual Mtg follow up / BERAC Unified Data RFI 278<br />Kjiersten Fagnan (LBNL)</p> 279 280<p>Q2: Valuing Data and Software as Scientific Products 281<br />Pamela Weisenhorn (ANL), Tim Scheibe (PNNL)</p> 282 283<p>Q1: ESS-DIVE Community Reporting Formats 284<br />Charuleka Varadharajan, Joan Damerow, Emily Robles (LBNL)</p> 285 286<h3 id="fy2022">FY2022</h3> 287<p>Q4: Kickoff! Planning & topic selection</p> 288 289</div> 290 </div> 291 292 </div> 293 </div> 294 </section> 295 296 <footer class="footer"> 297 <div class="container"> 298 299 300 <div class="columns is-multiline"> 301 302 </div> 303 304 <p style="text-align:center;"> 305 <!-- <a href="https://ideas-watersheds.github.io"><img src="/img/IDEAS_watershed-logo_blueText.png" alt="IDEAS-Watersheds" width="150"></a> 306 </p> --> 307 <div class="content is-small has-text-centered"> 308 <p><a href="https://science.osti.gov/ber/Research/eessd">Earth and Environmental Systems Sciences Division</a> of the U.S. Department of Energyâs <a href="https://science.osti.gov/ber">Office of Biological and Environmental Research</a>.</p> 309 </div> 310 311 <!-- <div class="content is-small has-text-centered"> 312 <p class="">Theme built by <a href="https://www.csrhymes.com">C.S. Rhymes</a></p> 313 </div> --> 314 </div> 315</footer> 316 317
317<script src="/assets/js/app.js" type="text/javascript"></script>
317<!-- footer scripts --> 318</body> 319</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.