Transition from Email to Person_ID as Unique Identifier - Now Allows Bulk Email Update
We transitioned from using email addresses to Person_IDs as the unique identifier for people in the system. This change enhances data accuracy and ensures a more reliable and consistent identification process.
Key Updates:
- Person_IDs as Primary Identifier: Person_IDs will now serve as the unique identifier, providing stability and consistency compared to emails, which can change over time.
- Email Updates via Data Import: System Administrators can bulk update email addresses through the people.csv file, with changes reflected across all integrated systems.
- Person_ID Updates Restricted to UI: Bulk updates of Person_IDs will no longer be possible through the people.csv file. Future updates must be made manually via the UI.
- No Changes to Other CSV Imports: Basic Person Attributes, Student Term Attributes, and Enrollment files will continue using email as the unique identifier.
- Email as Unique Identifier for Login: Email will remain the unique identifier for login purposes related to Navigator.
- Validation for Unique Emails: Each institution will be allowed only one unique email address per person, with validation errors thrown for duplicates.
- Validation for Unique Person_IDs: Each institution will be allowed only one unique Person_ID per person, with validation errors thrown for duplicates.
Improved Front-End User Experience for Cohorts
Improvements are shown in the image below:
- Cohorts is now seen in the left hand navigation
- Cohorts has a new search and filter area
- Cohorts has an updated main listing page.
The Bulk Imports tab in Data Transaction to be removed
The 'Bulk Imports' tab that tracks logs will now be captured under ‘Transactions Log’
- For institutions that import data through ZIP and/or API
- Transactions Log will now be the only area to track data import statuses