Review and Resolve Deduplication Queue

Coordinators need a structured interface to manage the backlog of flagged duplicate pairs. The deduplication queue screen should display each suspected pair with key metadata, allow the coordinator to expand a pair for a full side-by-side comparison, and provide clear resolution actions: merge (keep one, discard the other), mark as distinct (both are legitimate and separate), or escalate to a national admin. The queue should show a count badge on the navigation so coordinators notice pending items without having to open the screen proactively.

HIGH story-duplicate-activity-detection-coordinator-002 8 pts

Story Points

High

Priority

Duplicate Activity Detection

Feature

User Story

As a Coordinator

I want to access a dedicated deduplication queue screen that lists all suspected duplicate activity pairs requiring my review

So that I can systematically work through unresolved conflicts rather than discovering them only at export time or when Bufdir questions the data

Acceptance Criteria

Given the coordinator opens the deduplication queue screen, When there are unresolved duplicate pairs, Then each pair is listed with participant name, activity type, date, and the names of both registrants
Given the coordinator taps a pair in the queue, When they expand it, Then a full duplicate-comparison-panel is shown with all fields of both records visible
Given the coordinator reviews a pair, When they choose 'Mark as Distinct', Then both records remain, the duplicate flag is cleared, and the pair is removed from the queue
Given the coordinator reviews a pair, When they choose 'Merge — Keep Newest', Then the older record is soft-deleted and the newer record's duplicate-reviewed flag is cleared
Given there are unresolved items in the deduplication queue, When the coordinator views the navigation bar, Then a numeric badge on the relevant tab reflects the count of pending pairs
Given the queue is empty, When the coordinator opens the deduplication queue screen, Then an empty state is displayed confirming no pending duplicates

Business Value

Without a queue-based workflow, duplicate resolution becomes an ad hoc, error-prone process where some conflicts are never resolved. A structured queue ensures every flagged pair is explicitly decided upon before it enters Bufdir export pipelines. This is especially critical for NHF, which has 1,400 local chapters where cross-coordinator registration overlap is statistically frequent during shared group events.

Components

Duplicate Activity Detection

Related Feature

Coordinator

User Role