We wired up the enrollment sink a while ago, and should use that as the source of truth for (most?) enrollment data instead of the xAPI events, which are less robust and harder to backfill.
For some things like enroll/unenroll events over time this may be the wrong way to go since we won't have any historical data from before the sink started running. Same with backfills, it will only capture the current state. So we may need both going forward.
We wired up the enrollment sink a while ago, and should use that as the source of truth for (most?) enrollment data instead of the xAPI events, which are less robust and harder to backfill.
For some things like enroll/unenroll events over time this may be the wrong way to go since we won't have any historical data from before the sink started running. Same with backfills, it will only capture the current state. So we may need both going forward.