MEDIUM story-duplicate-activity-detection-coordinator-005 5 pts
5
Story Points
Medium
Priority
Duplicate Activity Detection
Feature

User Story

As a Coordinator
I want to view an audit history of all duplicate warnings that were triggered, dismissed, or resolved under my chapter
So that I can demonstrate to national administrators and Bufdir auditors that duplicate activity pairs were actively reviewed rather than silently ignored

Acceptance Criteria

  • Given a coordinator dismisses a duplicate warning by selecting 'Submit Anyway', When the activity is saved, Then a log entry is written with the coordinator ID, both activity IDs, resolution action 'PROCEED_WITH_DUPLICATE', and timestamp
  • Given a coordinator resolves a pair in the deduplication queue, When the resolution is saved, Then a log entry is written with resolution action, resolver ID, and timestamp
  • Given the coordinator opens the duplicate audit log, When they view the list, Then each entry shows a human-readable summary: date, peer mentor name (masked if sensitive), resolution action, and resolver name
  • Given the coordinator is preparing a Bufdir export, When they access the export configuration, Then they can optionally append the duplicate audit log as a supplementary CSV
  • Given a log entry exists for a record that was later deleted, When the coordinator views the audit log, Then the entry is preserved with a note that the referenced record was subsequently removed

Business Value

Bufdir audits require organizations to demonstrate data integrity practices, not just clean data. A persistent, exportable audit trail proves that duplicate resolution is a deliberate, documented process rather than an absence of duplicates by chance. This directly supports NHF's compliance posture during annual grant reporting cycles and reduces the risk of funding disputes arising from data quality questions.