Why a digital portal feels like repair — and why it can also repeat harm

When I first encountered a community-run digital repatriation portal, it felt like a small miracle: images, recordings and documents that had been separated from families and communities for generations were being gathered, contextualised and shared according to the wishes of those to whom they mattered most. The portal made visible stories that had been flattened in museum catalogues. It allowed elders, artists and youth to access material that might otherwise remain siloed in distant archives.

Yet very quickly I began to notice the tension at the heart of many well-intentioned digital repatriation projects. A portal can restore access and agency, but if it simply re-houses objects within a new, extractive architecture—owned and controlled by funders, platforms or non-community institutions—it risks reproducing the same dynamics that caused the dispossession in the first place. The form of repatriation matters as much as the fact of repatriation.

What do people mean by “digital repatriation”?

At its simplest, digital repatriation refers to the return of cultural material—photographs, sound recordings, documents, artefact records—in digital form. For communities geographically removed from the institutions that hold their heritage, digital access can be transformative. But it’s not a substitute for physical return when that is necessary, nor is it a neutral technical fix.

People ask me: isn a digital copy enough? Who decides what gets digitised and who can see it? Who controls the metadata and the stories attached to objects? These are the right questions. A portal that ignores them will likely echo the colonial practices of control, classification and commodification it aims to undo.

Core principles for portals that don’t repeat colonial extraction

From conversations with archivists, community leaders and makers of platforms like Mukurtu CMS, several recurring principles stand out. They’re practical, social and technical at once.

  • Community governance: The community whose heritage is at stake must have formal decision-making powers over what is digitised, how it’s presented and who may access it. Token consultation is not enough.
  • Consent and provenance: Digitisation must be accompanied by careful provenance research and consent processes—ideally iterative and revocable. Consent is a process, not a checkbox.
  • Access controls and cultural protocols: Not all material should be public. Community-run portals need robust, flexible access controls so that sacred, gendered or restricted materials remain within defined circles.
  • Data sovereignty: Communities should control their data, ideally hosting it under legal and technical frameworks that respect Indigenous data sovereignty. That may mean local hosting, or clear contractual terms that prevent platform-level exploitation.
  • Ethical metadata: Descriptive practice matters. Instead of imposing Western taxonomies, portals should enable community-driven vocabularies and contextual narratives that reflect local meanings.
  • Capacity building and reciprocity: Funding and training must prioritise community capacity—digital skills, archiving knowledge, curatorial practice—so that the portal is sustained by, and for, the community.

    • Practical architecture: what the portal should do

    Technically, a community-run portal should be both usable and protective. Here are features I look for and recommend.

  • Tiered access: Multiple layers of visibility—public, community-only, restricted—managed by community-appointed stewards.
  • Embedded storytelling: Spaces for community voices to contextualise materials: oral histories, annotations, translations and counter-narratives.
  • Interoperability with safeguards: The portal should use standards that allow exchange with museums and research repositories, but always with policy gates that prevent unconsented harvesting.
  • Modular and portable data: Data should be exportable in community-owned formats. Avoid vendor lock-in. If the platform dies, the community must still be able to migrate their archive.
  • Offline and low-bandwidth options: Many communities have intermittent internet. The portal should support local copies and sync solutions (Rsync, USB packages, or offline site exports).

    • Who pays—and how to prevent new dependencies?

    Funding is the most brittle part of the setup. External grants often come with strings: reporting cycles that tilt priorities toward donor metrics, or ownership clauses that make long-term community control precarious.

    In projects I’ve seen work well, funding models combine short-term grants for setup with community-driven sustainability plans: sliding paywalls for non-community users, partnerships with cultural institutions that provide in-kind support (storage, training) under clear agreements, and small revenue-generating services such as reproduction requests whose proceeds flow back to the community.

    Public and philanthropic funders must be asked to accept governance frameworks that place control firmly with communities, even if that complicates their reporting. That’s where advocacy and patient relationship-building are essential.

    Common pitfalls to avoid

    A few recurring mistakes keep cropping up:

  • Centralising control under an external platform: It’s tempting to use a managed service for convenience. But if the platform’s terms allow reuse, sale or aggregation, the portal can become a new vector of extraction.
  • Over-digitising without context: Dumping high-resolution images online without narratives, or stripping community knowledge into neutral metadata, reproduces erasure.
  • Ignoring intergenerational flows: A portal that serves only elders or only researchers misses how communities live with their heritage. Youth outreach, co-creation and teaching resources are vital.
  • Treating digital as a substitute for physical return: Digital access is rarely sufficient restitution. It should complement, not replace, advocacy for physical repatriation where appropriate.

    • Examples and inspirational models

    Platforms like Mukurtu show what a culturally responsive CMS looks like: built with Indigenous communities, prioritising cultural protocols and layered access. Elsewhere, community archives in Aotearoa/New Zealand, parts of Scandinavia where Sámi groups manage digital collections, and projects in North America demonstrate how local governance and legal frameworks (including Indigenous data declarations) can be integrated into technical design.

    These examples aren’t perfect; they face resourcing and legal headaches. But they provide templates: governance charters, consent forms designed with elders, hybrid hosting strategies and pedagogies that teach community members to be archivists.

    What I ask when I’m invited to help

    When communities invite me into these conversations I start by listening. I ask:

  • Who should govern the archive, and how do we formalise that?
  • What materials are sensitive, and how should they be described and accessed?
  • What local skills exist, and what training will be needed?
  • What is the long-term plan for sustainability and for physical repatriation where that’s required?

    • Designing a portal is as much political work as technical work. It’s about shifting power, not just building a prettier interface.

    Small interventions that make a big difference

    Some low-cost, high-impact practices I’ve learned from practitioners:

  • Use community-controlled vocabularies instead of library subject headings.
  • Include oral-history permissions alongside digitisation consent—people may change their minds, so enable updating and withdrawal.
  • Build local mirroring: a copy on a community server or even on encrypted physical drives stored locally.
  • Create learning modules so young people can contribute and contest narratives.

    • These measures keep the archive alive, relevant and accountable.

    The hard truth I keep returning to

    A community-run digital repatriation portal can restore access and dignity—but only if it dismantles the logic that created the harm. That means real control over data, meaningful governance, flexible access, investment in local capacity and funding structures that resist extractive pressures. Done well, a portal becomes a living commons: a place where heritage is not owned by institutions but cared for by people. Done badly, it simply re-bottles colonial knowledge for a new audience.