The Community Garden of Data: Cultivating Accessible and Sustainable Archives

Last weekend, I found myself volunteering at my local community garden, hands deep in soil, wrestling with bindweed and marvelling at the sheer vitality of the volunteer potato plants that had sprung up from a previous year’s crop. As I worked, a thought took root: our efforts to manage open data and public archives have a lot to learn from the principles of community gardening. It’s not a perfect metaphor, but an organic one, and it offers a refreshing alternative to the more common—and more sterile—analogies of libraries or museums.

Consider the traditional approach to digital preservation: we often aim to create a curated, perfectly weeded collection, like a formal botanical garden. Every record is meticulously catalogued, every format is normalized, and access is controlled via neat, official pathways. This is a vital and necessary practice, especially for high-value, fragile assets. But it’s also resource-intensive and can inadvertently create barriers. It treats data as a finished exhibit rather than a living, evolving resource.

A community garden, by contrast, is a shared space for cultivation. The soil—the infrastructure, the storage, the core datasets—is maintained collectively. The success of the garden doesn't hinge on a single master gardener, but on the distributed efforts of many. In the world of open data, this translates to platforms that allow for user contributions, corrections, and annotations. It means accepting that a dataset, like a patch of soil, might be used in ways we never anticipated. Someone might plant tomatoes where we intended for flowers, and that’s not a failure of the garden, but a sign of its health and utility.

Tending the Soil, Not Just the Plants

The most crucial lesson is the focus on the commons. A community garden’s primary asset isn't the harvest of any single season; it's the quality of the soil that will support harvests for years to come. In our domain, this means focusing on sustainable infrastructure, clear and open licensing (the ‘rules of the garden’), and formats that resist obsolescence. It means prioritizing the health of the ecosystem over the immediate perfection of a single data ‘plant.’ A rusty PDF is like a struggling seedling; our goal shouldn't just be to prop it up, but to improve the ‘soil’ so the next version can be a more accessible, machine-readable format.

This model also embraces a certain kind of productive messiness. In the garden, a few ‘weeds’ can be beneficial, attracting pollinators or improving the soil. Similarly, in an archive, what we initially dismiss as ‘digital dust bunnies’—unstructured logs, informal comments, duplicate files—can provide crucial context or unexpected pathways for discovery. The goal isn't a pristine lawn, but a thriving, biodiverse plot where different ‘species’ of data can coexist and interact.

Adopting a community garden mindset shifts the archivist’s or data steward’s role from that of a solitary gatekeeper to a facilitator. We become the ones who test the soil’s pH, who ensure the water is connected, who provide the basic tools, and who welcome new gardeners. Our success is measured not by how perfectly controlled our plot is, but by how much nourishment the community derives from it. It’s a humbler, more collaborative, and ultimately more resilient approach to keeping our digital commons alive and growing.

Notes & further reading

A few pages I came back to while writing this: