Minneapolis Must Decide How to Handle Thousands of Duplicate Archive Images

Minneapolis city officials are weighing a set of consequential options after an internal audit identified a significant backlog of duplicate digital images clogging the municipal records system — redundant files spread across departments from the Department of Public Works to the Minneapolis Park and Recreation Board. The review, completed late last month, found the duplication problem severe enough to affect storage costs, records retrieval times, and compliance with Minnesota's Government Data Practices Act.

The timing matters. The city is already mid-cycle on a broader technology modernization push tied to the Minneapolis Digital Infrastructure Initiative, a multi-year program that has been reallocating IT resources since 2024. Allowing duplicate image files to pile up unchecked creates downstream problems: longer search times for public records requests, inflated cloud storage bills, and the risk that different versions of the same document end up in the public record — creating legal exposure for the city in litigation.

What the Audit Found and Where the Problem Lives

The duplication issue is not uniform across city hall. According to city technology staff familiar with the review, the heaviest concentrations of redundant image files appear in two areas: the Planning Department's permit and zoning image libraries, where scanned documents from projects along corridors like Central Avenue NE and Lake Street have been stored in multiple formats without a consistent naming protocol, and the City Clerk's office, which manages official photographic records tied to council proceedings and licensing. The Minneapolis Community Planning and Economic Development office, which handles development reviews for neighborhoods from Whittier to the Near North, also flagged its own internal file management gaps during the review process.

Each duplicate image costs money. Municipal cloud storage rates for government entities in Minnesota typically run between $0.02 and $0.05 per gigabyte per month under state-negotiated contracts, and when tens of thousands of redundant files accumulate across multiple departments, the annual waste adds up to real budget line items. City IT staff have not yet published a final figure, but the scale of the identified duplicates points to costs that could reasonably run into six figures annually if left unresolved.

The city has three realistic options. It can pursue automated deduplication — software that identifies and flags matching files for deletion or consolidation — which carries a one-time licensing cost but requires staff time to verify results before permanent deletions. It can assign staff from each affected department to conduct manual reviews, a slower process but one that gives department heads more direct control over what gets removed. Or it can contract the work out to a vendor, an approach the city used in 2021 when it outsourced a similar cleanup of legacy GIS data inherited from older mapping systems.

The Decisions That Will Define the Outcome

Three choices in particular will determine whether this cleanup actually sticks. First, the City Clerk's office and the Department of Technology and Innovation need to agree on a unified image naming and storage protocol before any deletion work begins — without that, departments will recreate the duplication problem within months. Second, the city council's Ways and Means Committee will need to decide whether to fund the cleanup through existing IT budget reserves or request a supplemental allocation, a question likely to surface during the next budget review cycle in September. Third, officials need to determine which version of a duplicated file becomes the authoritative record under the Data Practices Act, since deleting the wrong copy could constitute an improper records disposal under Minnesota statute.

Community groups that regularly file data requests with the city — including housing advocacy organizations in the Phillips neighborhood and legal aid groups that rely on permit records from the Ventura Village area — have a direct stake in how quickly the city resolves this. Slower retrieval times hit them hardest. City IT staff are expected to present a recommended approach to the council's Technology and Innovation Committee before the end of July. That presentation will be the first real public test of whether the city has a coherent plan or is still working one out.