How Canberra's Digital Archives Ended Up Full of Duplicate Images — and What It Took to Get Here

Canberra's public sector holds one of the densest concentrations of digital image archives in the southern hemisphere. Decades of scanning programs, website refreshes, and agency restructures have left a trail of duplicated, misnamed, and redundant image files sitting across shared drives, content management systems, and cloud storage buckets — many of them funded by taxpayers more than once.

The problem did not appear overnight. It accumulated through a series of decisions that each made sense in isolation but compounded into something unwieldy. Understanding how that happened matters now because several ACT government departments and at least two federal agencies headquartered in the parliamentary triangle are midway through major digital asset audits, with remediation contracts either tendered or under active procurement.

The Road to Duplication

The earliest seeds were planted during the Howard-era push to digitise government records in the late 1990s and early 2000s. Agencies working independently — often without shared metadata standards — scanned the same source materials multiple times. The National Archives of Australia, based on Queen Victoria Terrace in Parkes, and the National Library on Parkes Place both built substantial digital collections during this period using different file naming conventions and different resolution standards. When staff moved between agencies, as is common in Canberra's tight public service labour market, they often brought copies of images with them on portable media or personal network folders.

The problem accelerated sharply after the 2011 machinery-of-government changes under the Gillard government, which reshuffled dozens of departments and merged functions that had previously sat separately. Digital assets — photographs, maps, diagrams, infographics — migrated between systems without any systematic deduplication. A 2014 review by the Australian Government Information Management Office flagged the issue in general terms, but no binding cross-agency standard for image asset management followed.

At the ACT government level, the expansion of service delivery websites after 2015 created its own version of the same problem. The Chief Minister, Treasury and Economic Development Directorate, which oversees digital government policy from its offices in London Circuit in Civic, began logging duplicate image complaints from internal users around 2017. By the time the ACT's whole-of-government cloud migration accelerated in 2021, the duplication rate across some legacy systems was estimated internally — though no public figure has been released — to be significant enough to affect storage costs and search reliability.

Why It Is Harder to Fix Than It Sounds

Replacing or removing duplicate images is not simply a matter of running a deduplication script. Many images exist in multiple versions because different departments cropped, colour-corrected, or resized the originals for specific purposes. Deleting one version without checking its usage across live web pages, intranet portals, and printed publications risks breaking content that the public or staff rely on. The Australian National University's digitisation team in Acton, which manages image assets for several research collections, encountered exactly this problem during a 2023 repository consolidation — discovering that what appeared to be identical files carried different rights metadata, meaning automated removal could have stripped licensing information from published academic content.

Federal procurement records show that contracts for digital asset management and content auditing services in the ACT region have grown steadily. The Digital Transformation Agency, located on Mort Street in the city, has published updated guidance on metadata standards for Commonwealth entities, with the most recent version released in late 2024 setting clearer expectations around image provenance and deduplication before any new content management system goes live.

For agencies currently mid-audit, the practical path forward involves three steps that specialists in this field consistently recommend: a full inventory using hash-based matching tools to identify true duplicates versus near-duplicates, a usage crawl across all active digital properties to flag which versions are referenced in live content, and a staged replacement process that substitutes canonical versions before retiring redundant copies. That last step — the actual replacement — is where most projects stall, because it requires coordination across communications, IT, and records management teams that rarely share a reporting line. Agencies that have set internal deadlines for completion before the end of the 2026-27 financial year will need to move quickly to meet them.