Community Data Hubs Co-Design Partnership Opportunity

We recently received this message from the State Water Resources Control Board regarding The Open Environmental Data Project:

“The Open Environmental Data Project (OEDP) is opening a call for community partners to co-design a Community Data Hub (CDH) prototype. The co-design process aims to

  • Identify and solve data stewardship challenges, 
  • Provide a workshopping space for community partners to work through environmental data governance
  • questions, challenges, and find new opportunities within the CDH prototype, and
  • Inform the design and content of a playbook that will detail different approaches and potential blueprints for addressing those questions and challenges for the benefit of both the community partner and other community data stewards.

More information on the CDH prototype: we are interested in modeling a networked infrastructure for storing and sharing environmental data between communities, government, and researchers. With this prototype, we aim to increase data usability in environmental governance by: (1) providing frameworks for communities to make collective decisions about their own data while also (2) modeling complementary data governance structures for sharing between communities and other sectors. This work explores challenges and possibilities with partners in order to understand how the CDH model can address challenges in existing environmental governance settings. 

We’re looking to partner with a community-based organization that is already collecting environmental data and is interested in examining challenges related to data governance including privacy, consent, ownership, or accessibility.

Partners can expect to receive a stipend, a tailored workshop facilitated by OEDP, a co-designed set of resources, and two post-workshop check-ins. 

For more information on the process, eligibility, and timeline, please see our website. For more detailed information on our conceptual and strategic groundwork for this project, please see our documentation blogs.