Review and Resolve Duplicate-Flagged Activity Registrations
When the Duplicate Detection Service flags a registration as a potential duplicate of an existing approved record, it appears in the approval queue with a distinct duplicate warning badge. When the coordinator opens the flagged item, a comparison panel is displayed showing the suspected duplicate alongside the current registration — including activity type, date, duration, submitter, and participants — allowing side-by-side review. The coordinator can: (1) approve the current registration and suppress the duplicate flag if the records are legitimately distinct; (2) reject the current registration as a duplicate; or (3) correct one and approve it. Any action taken on a duplicate-flagged record is recorded with the coordinator's resolution decision in the audit trail.
User Story
Acceptance Criteria
- Given a registration has been flagged as a potential duplicate, when it appears in the approval queue, then a distinct duplicate warning badge is displayed on the queue item
- Given the coordinator opens a duplicate-flagged registration, when the detail view loads, then a side-by-side comparison panel shows the suspected duplicate record with key fields highlighted for comparison
- Given the coordinator determines the records are legitimately distinct, when they approve with duplicate flag suppression, then both records proceed independently and the duplicate flag is cleared from the current registration's audit record
- Given the coordinator determines the current registration is a genuine duplicate, when they reject it with reason 'duplicate', then it is removed from the reporting pipeline and the original approved record is unchanged
- Given the coordinator resolves a duplicate, when the action completes, then the resolution decision (suppressed vs rejected) is stored in the correction history for audit purposes
Business Value
Duplicate activity registrations are a specific pain point called out by NHF — when multiple coordinators register the same activity or a peer mentor submits the same event twice, Bufdir reporting data is inflated, potentially triggering audits or requiring manual correction of submitted grant reports. Surfacing duplicates in the approval queue with contextual comparison data allows coordinators to resolve them at the source before they enter the reporting pipeline, protecting NHF's funding relationships with Bufdir.