Detect Duplicates in Proxy and Bulk Registrations
Coordinators frequently use proxy registration to log activities for peer mentors who lack digital access, and bulk registration for recurring group activities (e.g., weekly training sessions). Both flows must trigger the same duplicate detection logic as individual self-registration. For bulk registration, the system should check each participant individually and present a consolidated duplicate summary rather than interrupting the flow with one dialog per conflict. Coordinators should be able to resolve all conflicts in a single review screen before confirming the bulk submission.
User Story
Acceptance Criteria
- Given a coordinator submits a proxy registration on behalf of a peer mentor, When the submitted activity matches an existing record for that peer mentor, Then a duplicate-warning-dialog appears with the same comparison interface as self-registration
- Given a coordinator submits a bulk registration for 10 peer mentors, When 3 of the 10 have conflicting existing records, Then a consolidated duplicate summary shows all 3 conflicts grouped in one review screen before the batch is saved
- Given the consolidated duplicate summary is shown, When the coordinator resolves each conflict (mark distinct or skip), Then only the non-conflicting records plus the explicitly approved duplicates are saved
- Given a bulk registration is completed with some conflicts skipped, When the coordinator views the confirmation screen, Then it displays a count of successfully saved records and a count of skipped records
- Given a recurring bulk registration template is applied, When any participant in the template already has an activity within the same date/time window, Then those participants are highlighted before the coordinator submits
Business Value
Coordinators who manage large groups are most exposed to accidental duplicate creation because they submit high volumes of records rapidly. A coordinator running weekly group activities for 20 peer mentors across 52 weeks could inadvertently create hundreds of duplicate entries per year without automated detection. Catching these at bulk submission time eliminates the most statistically likely source of duplicate contamination in Bufdir data.
Components
- Duplicate Activity Warning Dialog ui
- Proxy Duplicate Detection Service service
- Proxy Duplicate Detector service
- Duplicate Detection Service service
- Duplicate Resolution Handler service
- Proxy Registration Service service
- Bulk Registration Service service
- Duplicate Detection BLoC infrastructure
- Proxy Registration Screen ui
- Bulk Registration Screen ui