Resolve sourcedId conflicts when the same logical user or class appears with different sourcedIds across multiple OneRoster providers

Steps

1. Establish a canonical identity layer in your system that maps provider sourcedIds to an internal entity ID; never use a provider sourcedId as your primary key.
2. Use demographic matching (given name + family name + date of birth + grade level) to detect probable duplicates across providers; flag matches above a configurable confidence threshold for human review.
3. Prefer the district SIS sourcedId (typically from a Clever or ClassLink roster) as the canonical anchor; treat LMS-originated sourcedIds as secondary references.
4. Store the full provenance set — provider name, sourcedId, last seen timestamp — for each entity so conflicts can be audited and manually overridden.
5. When a new provider introduces a sourcedId that fuzzy-matches an existing entity, emit a conflict event to an admin queue rather than automatically merging; auto-merge only when an exact shared external identifier (e.g., state student ID, NCES school ID) exists.
6. Publish a deduplication report after each sync cycle showing new conflicts detected, auto-merged records, and human-pending conflicts for governance sign-off.