Observational constraints on mergers creating magnetism in massive stars
Building a Community of Practice
1. Building a Community of Practice
Panel
Chelle Gentemann (she/her)
Farallon Institute
Twitter: @ChelleGentemann
2. Specifically, what lessons
can NOAA learn from other
communities?
Language matters, it sets the tone.
https://www.planetary.org/articles/10050900-finding-new-language
https://www.sapiens.org/column/wanderers/outer-space-and-gendered-language
Open science can advance community acceptance &
amplify investments in data collection.
3. How can NOAA leverage other agency or private
sector models and frameworks?
2017 Decadal Survey - focused on prioritized community
developed science
2007 Decadal Survey - focused on missions/instruments
Focus investments in community development around
science questions that advance NOAA priorities, building on
OceanObs19 and 2017DS results.
Agile development
4. Are regional approaches better or worse than
enterprise solutions?
It depends….it is all about implementation
Enterprise - data archive, re-imagined training as cohorts
Regional - FAA/operator/science for UAVs
Image credit: flyingmag.com
5. What about “All The Other
Stuff” NOAA should
appreciate as they
implement their strategy?
Data Archives - variety not
volume
Uncertainty estimates - build
trust
Data formats: a cohesive
strategy for updating formats
for multi-sensor / multi-
mission interdisciplinary
studies
Editor's Notes
I thought that on the 3rd day, we all might enjoy just looking at a beautiful image while tying into Eric Lindstrom’s island theme. I am going to go through the questions that NOAA posed to our workshop and talk about them with respect to building a community.
This is the panel on building a community… Language matters, it sets the tone. I’ve been learning a lot the past few days by attending this invitation only meeting and I wonder if others might have been included, because I’d like to hear more voices. Many of us are in positions of influence, that is in part why we were invited here today, and I would love to see a recommendation come out of this panel on inclusivity and language. Building a community starts with being considerate and thoughtful about communication and creating space for everyone to feel their voice will be welcomed. To me, the use of the term ‘Unmanned’ reinforced gender stereotypes. While this might not seem like a big deal, sometimes it is the small things that send ‘signals’ to communities that make them feel welcomed, this is why I include pronouns next to my name now, it sends a subtle message to communities I want to empower and support.
I’d also like to highlight open science - open instruments/software/data. As a funding agency, it is important to be aware of where ‘open’ can be applied to amplify the investment. When choosing where to invest in development, it may be useful to gather information on a particular solutions ‘openness’ and even perhaps consider requiring some form of openness as part of the RFP. As an agency, how you frame opportunities and how you set metrics for success can act to prioritize openness.
The 2017 learned from the 2007 DS - too much focus on mission/instruments locked in a decade of advancement that didn’t allow for disruptive technologies or changes in scientific priorities to adjust. By focusing on science, it encourages competition for the best solution and builds larger communities. Agile is important.
This is a developing space for research, with data formats and archive centers not quite caught up. If the data isn’t made freely available in formats and access points that are accessible to the broadest range of communities it undermines collecting the data at all.