Citizen science & data

Open Data and Community Data: How to Share Participatory Research Results Responsibly

Citizen science & data · · Published 2026-10-26

Two young people outdoors, one shading her eyes as she looks up, during a water monitoring field day
Students taking part in a volunteer water monitoring programme in Iowa. US government photo (USDA Natural Resources Conservation Service), public domain.

Participatory research produces data that belong, in a moral sense at least, to the people who provided them and often helped collect them. Sharing those data openly can multiply their value; sharing them carelessly can harm the very people they describe. This guide sets out the main choices a project faces, from giving results back to participants to publishing a dataset in a public repository.

Three audiences, three formats

A participatory project usually has to share data in at least three ways:

Each audience needs a different level of detail, and each raises different risks.

Returning results to participants

"Report-back" is the practice of giving participants their own results and the study's overall findings. Environmental health researchers have studied it closely. A 2007 article by Julia Green Brody and colleagues in the American Journal of Public Health, "Is it safe? New ethics for reporting personal exposures to environmental chemicals", argued that participants generally have a right to know their own results, even when the health meaning is uncertain, and that report-back should be planned with community partners. Practical lessons from that literature include:

Collective results can be shared through "data walks", in which residents move between posters of findings in small groups and discuss what they see. Co-interpretation sessions often catch errors and add explanations that researchers missed.

What "open" means

Open data are data that anyone can freely access, use, modify and share, subject at most to requirements to attribute the source and keep the same openness. In practice, publishing open data means choosing a licence. Common choices are Creative Commons Attribution (CC BY), the CC0 public domain dedication, and, for databases, the Open Database Licence (ODbL). Without a licence, others cannot be sure what they are allowed to do.

The UNESCO Recommendation on Open Science (2021) supports open data, but it also endorses the idea that data should be as open as possible and as closed as necessary, recognising legitimate reasons to restrict access, including privacy, security and the rights of Indigenous peoples. The FAIR principles (findable, accessible, interoperable, reusable) do not require data to be open either: data can be FAIR and still restricted.

Protecting people in published data

Community research often concerns small areas and small groups, which makes re-identification easier than in a national survey. Standard precautions include:

Where data cannot be safely anonymised, controlled-access repositories let approved researchers use them under agreements. In the UK, the UK Data Service, funded by the Economic and Social Research Council, offers open, safeguarded and controlled access levels and guidance on preparing qualitative and quantitative data for archiving.

When data should not be open

Repositories and documentation

For data that can be shared, a recognised repository is better than a project website, which may disappear when funding ends. Options include discipline repositories (for example, biodiversity records through the Global Biodiversity Information Facility), national data archives, university repositories and general-purpose services that issue persistent identifiers (DOIs). Whatever the choice, publish documentation with the data: the protocol, a codebook explaining every variable, the quality checks applied (see data quality in citizen science), known limitations, and a clear licence and citation.

Write a data agreement early

Disputes about data are among the most common reasons partnerships break down. A short agreement, signed before data collection, should cover:

  1. Ownership and stewardship. Who owns the data, who looks after them, and where they are stored.
  2. Access. Who can see raw data during and after the project.
  3. Use and reuse. What the data may be used for, and whether new uses need approval.
  4. Publication. Whether community partners review outputs before publication, and how disagreements are resolved.
  5. Retention. How long data are kept, and whether they are archived, returned or destroyed.

These questions apply equally to large citizen science platforms, where volunteers should be able to find a clear statement of how their contributions are licensed and used.

Sources