Run the learning platform
Keep the learning history when records overlap.
Duplicate-account handling includes target selection, collision review and an audit record. This example stops at review.
Record A · keep
- Name
- Taylor Quinn
- Classroom
- Python Lab
- Submitted versions
- 4
- Published reviews
- 3
Record B · reconcile
- Name
- Taylor Quinn
- Classroom
- Python Lab
- Submitted versions
- 2
- Published reviews
- 1
These are hypothetical duplicate records outside the program totals. No merge is executed; no original learner history is accessed.
What this part of Arc does
- Find possible duplicate students and choose a target
- Inspect a merge plan and resolve data collisions
- Transactional execution with preserved history and absorbed-account records
- Review previous merges and reference coverage
This is a browsable portfolio interpretation of Arc’s workflows with fictional examples. Navigation, filtering and theme previews work here; editing, execution and platform services belong to the original application.
Inside the original application.
This demo view is grounded in Arc’s source. Explore the recorded workflows for a look at the original interface.
Source references & review notes
app/Platform/Portals/Admin/Controllers/AdminAccountMergeController.phpapp/Platform/Domain/AccountMerge/MergePlanner.phpapp/Platform/Domain/AccountMerge/MergeExecutor.php
Source reviewed at development revision 5549bf96. Original captures have their own pinned revisions; the live platform has a separate release.