Support for Multiple Systems of Identifiers

Work on DATASTD-1301 suggested a new PersonIdentity entity associated with Person that would record additional identifiers consisting of an IdentificationCode and a Namespace. This would replace the existing StudentEducationOrganizationAssociation.StudentIdentficationCode common type collection.

The feedback was that requiring vendors to implement Person to use this feature was overreaching. Analysis for DATASTD-997 recommended defining new entities specific for the Student and EducationOrganization instead of using the Person entities.

The recommendations to be implemented by this ticket are as follows:

1. Create a new entity StudentIdentity consisting of:

• Student reference, required, key value – reference to the Student record in the ODS
• IdentificationCode, required, key value – the alternate identifier from another system being recorded
• Namespace, required, key value – the namespace of the source system for the alternate identifier being recorded
• SourceSystem - optional, string - Name and/or kind (SIS, LMS, etc) of the source system
• SourceSystemUserName - optional, string - Username of student in source, if different from the IdentificationCode
• StudentIdentificationSystem - optional, descriptor - the coding schema for identification

2. Create new entity EducationOrganizationIdentity consisting of:

• EducationOrganization - reference, required, key value – reference to the * EducationOrganization record in the ODS
• IdentificationCode - required, key value – the alternate identifier from another system being recorded
• Namespace, required, key value – the namespace of the source system for the alternate identifier being recorded
• SourceSystem - optional, string - Name and/or kind of the source system writing the identification code
• EducationOrganizationIdentificationSystem - optional, descriptor - The designated name of the system of identification (e.g., NCES, Tax ID, etc)

3. A new Entity StaffIdentity, following the StudentIdentity pattern above, is deferred until there is greater demand for interoperability of staff data between systems and applications.

4. Deprecate in the future the common type records:

• StudentEducationOrganizationAssociation.StudentIdentificationCode
• EducationOrganization.EducationOrganizationIdentificationCode

The details for the recommended additional entities (in Handbook format) is provided in Student EdOrg Identity Entities.xlsx