Info |
---|
The purpose of this data element crosswalk is for colleges to interpret the IDme Verification Status Change notifications data across multiple formats. |
Table of Contents | ||
---|---|---|
|
About IDme Status Changes
In order to keep colleges informed of these post-submission status changesThe ID.me identity verification process is displayed to students following the creation of their OpenCCC Account and before they submit their CCCApply application. Completing the verification process at that time is strongly encouraged; however, students are able to opt-out at this point and return later to complete the process. When this happens, null values are stored and passed to the college with their application data.
To keep colleges informed of a student’s current IDme verification status, event-driven notifications can now be delivered to the college to colleges in a new Events table via Superglue, and/or colleges may request access to a daily or weekly report detailing change information configured to their college MIS code. These notifications will allow colleges to always have the student’s current IDme verification status to support their eligibility to financial aid and other financial assistance.
Why Would A Status Change?
While our current process strongly encourages students to verify their identity using IDme at the time they create their OpenCCC account and submit a CCCApply application, it is not required and students can choose to opt-out of the process before they submit their application. When this happens a Null value (or no value/blank) is delivered to the college with their application data. These values are stored with the application data even if the student returns to verify their identity post-submission at a later time or if a change to their status is triggered from a change to the student’s account profile (see Understanding Status Changes below).
IDme Status Change Report Data Fields
Both of these formats deliver the same change notifications using different variations of the same master data fields.
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
IDme Verification Data Fields & Values
There are three key data fields that are initially collected during the ID.me Verification process (http://ID.me) and passed to the college with the student’s CCCApply submitted application data.
Data Dictionary Name | Data Field Name | Description |
---|---|---|
IDme Opt-in Timestamp | <idme_optin_timestamp> | Indicates the date and time that the student opted in to the ID.me verification process. |
IDme Confirmation Timestamp | <idme_confirmation_timestamp> | Indicates the date and time that the student’s identity is successfully verified by the ID.me vendor. |
IDme Workflow Status | <idme_workflow_timestamp> | Indicates the current status of the student's ID.me identity verification. |
Info |
---|
The ID.me data fields that are collected with the student’s submitted application are documented in the CCCApply Standard & Noncredit Application Data Dictionary (v.2024.4 or higher). |
IDme Workflow Status Field Values
The IDme Workflow Status field indicates the student’s ID.me (verification) workflow status at the time the student’s CCCApply Application is submitted. Changes to the status are indicated and delivered through variations of the field.
If/when the student’s IDme (verification) workflow status changes…
the college can track the change in this vehicle… | …through this field |
---|---|
Status Change Report | <current_idme_workflow_status> |
Events Table | <idme_status> |
The values for the IDme Workflow Status field are the same for all variations of the workflow status field:
Value | Definition |
---|---|
blank/null | = the student has never verified their identity through the IDme process. (Blank/Null would only appear in the <previous_idme_status> field in the Events table.) |
verified | = the student’s IDme verification was successfully Verified and is current. |
staff_verified | = the student’s identity was verified by a college staff member at the time the student’s OpenCCC account was created. |
unverified | = the student’s identity was previously verified but has become Unverified due to a change made by the student in their OpenCCC account profile. |
expired | = one year (365 days) has elapsed since the student’s previous Verified or Staff Verified status. |
Valid Workflow Status Changes
A valid workflow status change will be one of the following:
Never Verified (Null/Blank) to Verified
Verified to Unverified
Unverified to Verified
Verified to Expired
Staff Verified to Unverified, Verified or Expired
IDme Status Change Report Data
The IDme Status Change Report provides status change notifications in a user-friendly format geared for college staff such as Admissions & Records and Financial Aid officers. The report will include rows/instances where an IDme workflow status has changed in relation to the student’s CCCID and their last application submitted. Applications submitted where the IDme Workflow Status is null (blank) will not be included in the report. Only valid workflow changes will be included in the report.
See More:
Data Dictionary Name | Field Name | Description | Type | Max Length | Field Values | Allows Null |
---|---|---|---|---|---|---|
College MIS Code | mis_code | The CCCCO MIS identification code for the California Community College. | text | 3 | 3-digit code | No |
California Community College ID (CCCID) | ccc_id | The unique identifier for a single California Community College student. | text | 8 | No | |
Latest Application ID | latest_app_id | The Application ID <app_id> of the latest (most recent) CCCApply application submitted to the college. | number | 16 | No | |
Latest Application | latest_app_tstmp_submit | The date and time of the latest (most recent) CCCApply application submitted to the college. | date time | 16 | No | |
Latest Application | latest_app_idme_workflow_status | Indicates the IDme Workflow Status at the date and time of the student’s latest (most recently) submitted CCCApply application to the college. | text | 16 | See the IDme Workflow Status for values. | Yes |
Latest Application | latest_app_idme_optin_timestamp | Indicates the IDme Opt-In Timestamp (date and time) of the student’s latest (most recent) submitted CCCApply application submitted to the college. | date time | 16 | Yes | |
Latest Application | latest_app_idme_confirmation_timestamp | Indicates the IDme Confirmation Timestamp (date and time) of the student’s latest (most recent) submitted CCCApply application to the college. | date time | 16 | Yes | |
Current IDme Workflow Status | current_idme_workflow_status | Indicates the student’s current IDme Workflow Status at the date/time the report is run or an IDme workflow status change is set. | date time | 16 | See the IDme Workflow Status for values. | Yes |
Current IDme Opt-In Timestamp | current_idme_optin_timestamp | Indicates the student’s current IDme Opt-In Timestamp at the date/time that the report is run or an IDme workflow status change is set. | date time | 16 | Yes | |
Current IDme Confirmation Timestamp | current_idme_confirmation_timestamp | Indicates the student’s IDme Confirmation timestamp at the date/time that the report is run or an IDme workflow status change is set. | date time | 16 | Yes | |
Current IDme Workflow Status Change Timestamp | current_idme_workflow_status_change_timestamp | Indicates the date and time of the most recent change made to the student’s IDme Workflow Status at the time the report is run or status change is made. | date time | 16 | See the IDme Workflow Status for values. | Yes |
Events Table Fields & Payload Data
...
(
...
Superglue)
The Events table delivers the following event-driven data fields to college staging tables and/receives change notifications in a staging table or directly to your college SIS systems, including system. These are the same ID.me (verification) workflow status changes that occur post -CCCApply application status changes submission or when a student makes a change is made to the user’s their account profile that changes their identity verification.
Despite the optional eventType values of ‘UPDATE_PROFILE’ and ‘FEDERATED_IDENTITY_LINK’, CCCTC systems will solely deliver this event payload to college staging tables if or when the previous_idme_status field contains a different value from the idme_status current value. It is theoretically possible that a student modifies the first name (or other field) in such a way that does not change their verification status. In that case, no event would be sent to the college.
Table: Events
Table Field Name | Data Element Dictionary Name | Field Name | Description | Type | Length | Field Values | Allows Null |
---|---|---|---|---|---|---|---|
Event ID | Event ID | eventId | The unique id of an event. | Text | 32 | No | |
Event Type | Event Type | eventType | The coded identifying name used to identify the schema of the Event Payload. | Text | 50 |
| No |
Event Payload | Event Payload | eventPayload | The Json Payload containing various fields based on the Event Type | Text | 2000 | No | |
Event Timestamp | Event Timestamp | eventTimestamp | The date and time is which this event was triggered. | Date with UTC | 24 | No | |
MIS Code | MIS Code | misCode | The unique three-digit code for the California Community College. | 3 | No | ||
CCCID | cccid | The unique California Community Colleges identifier for the user. | String | 9 | No | ||
First Name | firstName | The updated first name of the user. | String | 100 | Yes | ||
Previous First Name | previous_firstName | The previous first name of the user, if applicable. | String | 100 | Yes | ||
Last Name | lastName | The updated last name of the user. | String | 100 | Yes | ||
Previous Last Name | previous_lastName | The previous last name of the user, if applicable. | String | 100 | Yes | ||
The updated email address for the user. | String | 256 | Yes | ||||
Previous Email | previous_email | The previous email address for the user, if applicable. | String | 256 | Yes | ||
IDme Verification Status | idme_status | The current status of the user's ID verification. | String | 50 |
| No | |
Previous IDme Verification Status | previous_idme_status | The previous status of the user’s ID verification, if applicable. | String | 50 |
| Yes | |
IDme Confirmation Timestamp | idme_confirmation_timestamp | Date with UTC time the user’s current ID verification was confirmed, if applicable. | Date with UTC Time | Yes |
About Verification Status Changes
...
Valid current IDme workflow status change values reported are:
...
Never Verified (Blank) to Verified
...
Verified to Unverified
...
Unverified to Verified
...
Verified to Expired
...
Unverified to Expired
...