...
3. Tech Congress Program. Sessions were briefly reviewed (see materials below). One comment was to add a session on course transcripts domain model, given current limitations (as documented in Tracker) on the model.
Addendum made on 1/21 - Eric's action from item #2 above
From consulting with the details of those involved in field projects, it seems that there are several cases where districts struggle to control rostering such that rostering can provide a consistent student identifier within the district ecosystem.
- State assessments are one case: in this case, the state only has the state-assigned student ID, which does not match the district student ID in usage. Yet districts would like to see the state assessments transferred via API into a local district context. One option would be to have the state also manage the local district IDs, but this was seen as a likely a fairly big lift.
- In some cases, districts are essentially dealing with systems with no formal rostering. In these cases, students often enter their "student number" into an application and may even in some cases self-roster. This student number may not match the SIS/district student identifier, creating a problem where two IDs can be resolved (and resolved prior to an API transaction).
- In some cases, vendors have pre-defined roster solutions and specifications, sometimes even without a student ID or with one that matches the wrong student identifier (e.g the state assessment use case above). There was no feedback on if the vendors would change their specs to accommodate IDs or multiple IDs, but it was regarded by those I consulted that there was likely a fair amount of inertia in this system, as those making the change would not be direct beneficiaries (i.e. they don't feel the current pain).
Based on this feedback, and looking at the Clever data specifications, it seemed that there were 3 main identifiers in the Ed-Fi ecosystem today (a SIS/district ID, a state ID, and a local student number), and that clarifying these was important. Also, it seems that the ability of a SIS to provide all 3 so that they can be resolved seems equally important. Based on this I raised
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Materials
| View file | ||||
|---|---|---|---|---|
|
...