Delhi's Digital Archives Crisis: Government Drive to Purge Duplicate Images From Public Records Hits a Critical Week

Municipal Corporation of Delhi officials confirmed this week that a systematic sweep of duplicate and redundant image files stored across the corporation's internal digital repositories has flagged more than 40,000 files as potential duplicates — a backlog that has quietly accumulated over nearly a decade of uncoordinated data uploads from ward offices spread across all 12 zones. The audit, running since late June, marks the most aggressive attempt yet to clean up a records infrastructure that civic technology managers have privately described as increasingly unmanageable.

The timing is not accidental. Delhi's government has been pushing hard to digitise citizen-facing services ahead of the next cycle of the Delhi e-District portal upgrades, scheduled for the third quarter of 2026. With the Aam Aadmi Party administration under Arvind Kejriwal having staked significant political capital on paperless governance and transparent civic services, disorganised back-end databases undercut that message directly. Images attached to building permits, property records, and encroachment documentation — many of them filed by residents in neighbourhoods like Rohini, Dwarka, and Shahdara — have in some cases been uploaded three or four times under different file names, creating verification problems for frontline officers.

What the Audit Found This Week

The duplicate image problem cuts across at least three separate systems: the MCD's internal grievance management portal, the Delhi Development Authority's land records database, and the heritage documentation files held by the Delhi Urban Art Commission, which covers monuments and registered structures in areas including Shahjahanabad and the Mehrauli Archaeological Park. Officials working on the audit told The Daily Delhi that the DUAC's archive alone contains image folders where individual photographs of protected structures appear to have been uploaded by different departments without any cross-referencing system in place, some files dating to 2017.

Storage is not a trivial concern here. Government cloud contracts for civic data in Delhi are typically renewed on an annual basis, and redundant image files inflate both storage costs and retrieval times. A 2024 Central Government Digital India report noted that unmanaged duplication across state-level portals was contributing to measurable slowdowns in citizen service response times in metro regions. Delhi, with its population of roughly 32 million and the corresponding volume of civic documentation, sits at the sharper end of that problem.

This week's audit push has also put a spotlight on the Integrated Command and Control Centre at Indraprastha Estate, which coordinates data flows between multiple city agencies. Technical staff there have been working since Monday to build a de-duplication script that can cross-match image files by hash value rather than by file name alone — a method that catches duplicates even when a file has been renamed or slightly compressed during upload. The process is expected to take another two to three weeks to complete across all ward-level feeds.

What Comes Next for Citizens and Officers

For Delhi residents who have submitted documents through the e-District portal — particularly those with pending property mutation cases or building plan approvals — the practical advice from civic technology advisers is to retain original copies of all photographs submitted, along with submission reference numbers. If a case has been dormant for more than 60 days without a status update, resubmission of image files may be advisable once the audit concludes, expected by late July 2026.

Ward offices in East Delhi's Laxmi Nagar and South Delhi's Saket district have been specifically mentioned in internal memos as locations where the duplicate file count is highest, likely because both areas saw intensive building permit activity during 2022 and 2023. Officers at those offices are being asked this week to manually verify at least 200 flagged records each before the automated script takes over.

The broader lesson the corporation seems to be drawing is structural: without a mandatory image-naming protocol tied to a unique case ID at the point of upload, the duplication problem will simply rebuild itself. Whether the MCD formalises such a protocol before the next major portal upgrade is the question civic administrators are now trying to answer fast.