CCC Data Warehouse - Student Journey User Guide
Introduction
The Student Journey data model, introduced in the CCC Data Warehouse with the CCC Data 3.0.0 release, consolidates student information from multiple datasets into a unified view for CCC researchers. By integrating data from various sources, it streamlines access, eliminating the need to search through multiple databases and tables. Designed for analytics, this dataset enhances how researchers view, query, and utilize the CCC Data Warehouse.
The Student Journey dataset is only available through direct access and cannot be accessed via the Data Warehouse Report Server. If you don’t have access to the CCC Data Warehouse, contact your College Experience Manager (CEM) at cems@ccctechcenter.org for assistance in setting up a direct connection. For more information on direct access, see the Data Warehouse Direct Access User Guide.
Contents
Benefits for Researchers
The Student Journey dataset integrates data from CCCApply and CO-MIS (post-processed files), providing researchers with a more comprehensive and accessible view of student information.
With the CCC Data 3.0.0 release, this new database consolidates datasets and simplifies access permissions, eliminating the need to navigate multiple sources. Designed specifically for data analysis, it allows for the creation of optimized tables that improve query performance and usability.
The Student Journey model is built for adaptability, evolving to fit the needs of researchers. Future enhancements will be guided by user feedback, ensuring the dataset continues to support relevant and impactful research. To request a future enhancement, contact your ES College Experience Manager (CEM).
Note: Existing databases and tables outside the Student Journey dataset remain unchanged and will continue to be supported.
MIS (post-processed files): When MIS data is mentioned in this document, it refers to post-processed files, also known as referential data. This output data is referred to as “MIS (post-processed files)”.
Scope of this User Guide
This guide provides detailed information on the Student Journey dataset:
overview of the data model
data sources
instructions on how to use it
example queries
For information on how to use direct access to connect to the Data Warehouse see the Data Warehouse Direct Connect Access User Guide.
Student Journey Goals
The Student Journey dataset is designed to:
Improve the usability and accessibility of student data for researchers.
Establish clear correlations between CO-MIS (post-processed files) and CCCApply data, enabling more comprehensive analysis.
Data Model Explanation
The Student Journey data model uses a canonical modeling approach to unify data from multiple sources into a single, structured framework. Instead of maintaining separate, sparsely populated tables for different data sources, this model consolidates attributes into core tables with linked satellite tables, improving data consistency and usability.
Core TablesThese tables serve as the foundation of the model:
Satellite TablesEach core table is associated with satellite tables that store additional details:
Consult the Student Journey Database Data Dictionary to identify the source, table, description, and example values for each data field. |
Description of the Schema
Researchers can query the Student Journey dataset in the CCC Data Warehouse via direct access. The following tables are available:
Core Tables
ccc__district_vwccc__college_vwccc__needs_and_interests_vw
Application and Student Data Tables
apply__mis_associative_entity_vwapply__application_vwapply__college_attended_vwapply__contact_information_vwapply__education_vwapply__needs_and_interests_vwapply__personal_information_vwapply__personal_sociodemographic_vwstudent_journey__dictionary_mvw
These tables consolidate data from multiple sources and follow a canonicalized structure to ensure consistency and ease of use.
Using the Student Journey Data Model
This section provides guidance on interpreting and querying the tables within the Student Journey canonical model.
Example Query 1: Educational Attainment
To analyze educational attainment, researchers can use the apply__application_vw and apply__education_vwtables, as this attribute is linked to each student’s college application. The following examples demonstrate how to retrieve this information.
Figure 1: Application Table
college | tstmp_ | tstmp_ | tstmp_ | app_id | source | app_lang | status | ccc_id |
|---|---|---|---|---|---|---|---|---|
181 | 51:26.5 | 05:05.4 |
| 246163 | stnd_application | en |
| AAP |
181 | 58:30.4 | 05:05.4 |
| 246170 | stnd_application | en |
| AAP |
181 | 40:35.5 | 05:05.4 |
| 14308 | stnd_application | en |
| AAA |
181 | 04:30.1 | 05:06.7 |
| 766185 | stnd_application | en |
| AAA |
181 | 11:06.6 | 05:05.4 |
| 243283 | stnd_application | en |
| AAP |
181 | 43:57.4 | 05:05.4 |
| 244160 | stnd_application | en |
| AAP |
863 | 22:35.0 | 05:43.2 | 05:43.2 | 799145 | stnd_application | en | S | AAA |
863 | 16:01.8 | 09:35.5 |
| 799957 | stnd_application | en |
| AAB |
863 | 55:24.6 | 55:24.9 | 10:41.5 | 839913 | stnd_application | en | S | ABS |
863 | 32:53.0 | 32:53.1 | 33:19.3 | 785127 | stnd_application | en | S | ABK |
The application table includes fields common to all application data sources. The source field specifies the origin of each record, as shown in the table below.
Figure 2: Application Source
source | number_of_records |
|---|---|
bogfw_application | 75648 |
stnd_application | 801022 |
intl_application | 63459 |
The application_education table, linked to the source field, provides additional details on educational background and goals, as shown below.
Figure 3: Application Education Table
app_id | source | ccc_id | tstmp_create | field | value |
|---|---|---|---|---|---|
823812 | stnd_application | ABQ7872 | 29:06.4 | description | Apprenticeship: Electrical (Cert) |
823812 | stnd_application | ABQ7872 | 29:06.4 | highest_edu_level | 32013 |
827804 | stnd_application | ABR7662 | 40:17.0 | intended_major | 1491 |
827873 | stnd_application | ABR6671 | 01:56.5 | major_category | Behavioral Sciences |
823812 | stnd_application | ABQ7872 | 29:06.4 | major_category | Apprenticeship Education |
840738 | stnd_application | ABQ7872 | 36:43.0 | highest_edu_level | 0 |
840738 | stnd_application | ABQ7872 | 36:43.0 | description | ASL/English Interpreter Education |
840738 | stnd_application | ABQ7872 | 36:43.0 | edu_goal | A |
781669 | stnd_application | AAA3495 | 45:28.3 | intended_major | 84102 |
827873 | stnd_application | ABR6671 | 01:56.5 | edu_goal | F |
By querying the apply__education_vw view, researchers can access attributes related to a student's educational background and future goals. This table includes both valid values and unknown values (represented as 0), but does not contain null or blank values.
To determine how many submitted applications include an edu_goal, researchers can perform a left join between the application and application_education tables using the query below.
Figure 4: Example Query
SELECT count(*) as num_applications
FROM apply__application_vw ca
LEFT JOIN apply__education_vw cae
ON (ca.app_id = cae.app_id)
WHERE ca.source = 'stnd_application'
AND cae.field = 'hs_edu_level' ;Figure 5: Query Result
num_applications |
801022 |
To generate a report on educational attainment by student, use the following query:
Figure 6: Example Query
SELECT ccc_id,max(value) as hs_edu_level
FROM apply__application_vw ca
LEFT JOIN apply__education_vw cae
ON (ca.app_id = cae.app_id)
WHERE ca.source = 'stnd_application'
AND cae.field = 'hs_edu_level'
and ca.tstmp_create > '2025-01-01' group by ccc_id;To generate a report on student sociodemographic information, use the following query:
Figure 7: Example Query
SELECT ccc_id,max(value) as hs_edu_level
FROM apply__application_vw ca
LEFT JOIN apply__education_vw cae
ON (ca.app_id = cae.app_id)
WHERE ca.source = 'stnd_application'
AND cae.field = 'hs_edu_level'
and ca.tstmp_create > '2025-01-01' group by ccc_id;This requires data from the apply__application_vw and apply__personal_information_vw tables.
Figure 8: apply_personal_Information_vw view
app_id | source | ccc_id | lastname | firstname | middlename | tstmp_update |
|---|---|---|---|---|---|---|
855357 | bogfw_application | ABU2416 | Kimmy | Pamy |
| 46:12.1 |
855456 | bogfw_application | ABU3934 | Walsh | Esme | Shanon | 48:24.7 |
855588 | bogfw_application | ABU6936 | sreetest | suvtest |
| 07:16.8 |
855555 | bogfw_application | ABU6903 | sreetester | Suvtester |
| 52:16.4 |
855489 | bogfw_application | ABU6244 | Sreetester | Suvatester |
| 01:14.6 |
855522 | bogfw_application | ABU6245 | sreetest123 | suvtest12 |
| 17:02.4 |
855786 | bogfw_application | ABU6244 | Sreetester | Suvatester |
| 38:28.9 |
855852 | bogfw_application | ABU6245 | sreetest123 | suvtest12 |
| 50:40.4 |
855753 | bogfw_application | ABU6245 | sreetest123 | suvtest12 |
| 27:13.1 |
855423 | bogfw_application | ABU3934 | Walsh | Esme | Shanon | 44:48.3 |
Figure 9: apply_personal_sociodemographic_vw View
app_id | source | ccc_id | tstmp_create | field | value |
|---|---|---|---|---|---|
119389 | bogfw_application | ABS2569 | 28:30.7 | married_or_rdp | y |
119389 | bogfw_application | ABS2569 | 28:30.7 | homeless_youth_school | y |
119389 | bogfw_application | ABS2569 | 28:30.7 | cert_national_guard | y |
119389 | bogfw_application | ABS2569 | 28:30.7 | marital_status | M |
119389 | bogfw_application | ABS2569 | 28:30.7 | homeless_youth_other | y |
119389 | bogfw_application | ABS2569 | 28:30.7 | elig_police_fire | y |
119389 | bogfw_application | ABS2569 | 28:30.7 | parents_deceased | y |
119389 | bogfw_application | ABS2569 | 28:30.7 | reg_dom_partner | y |
119389 | bogfw_application | ABS2569 | 28:30.7 | us_veteran | y |
119389 | bogfw_application | ABS2569 | 28:30.7 | parents_assistance | y |
By querying these tables, researchers can access attributes related to a student's sociodemographic status. For example, to determine how many students indicated they were married when completing their application, use the following query:
Figure 10: Marriage Information Query
SELECT pi.app_id,sd.field,sd.value ,pi.value last_name FROM apply__personal_sociodemographic_vw sd inner join
apply__personal_information_vw pi on pi.app_id=sd.app_id where sd.field='married_or_rdp'
and pi.field='lastname';This query returns the following results:
Figure 11: Query Results
ABU2416 | married_or_rdp |
|
ABU6245 | married_or_rdp | n |
ABU6245 | married_or_rdp | n |
ABU6245 | married_or_rdp | n |
ABU6245 | married_or_rdp | n |
ABU6903 | married_or_rdp | n |
ABU6903 | married_or_rdp | n |
ABU3934 | married_or_rdp | n |
ABU3934 | married_or_rdp | n |
More Connection Info: DW Direct Access User Guide
For details on connecting to the Data Warehouse and accessing current datasets, refer to the Data Warehouse Direct Access User Guide.
Student Journey Application Database Name and Schema Format
When connecting to the Data Warehouse using the instructions in the Data Warehouse Direct Access User Guide, use the following details for the Student Journey dataset:
Database Name:
Student_JourneySchema:
public
All tables are stored in the public schema, eliminating the need to navigate to a specific schema based on your MIS code. Data access is automatically managed and protected.
For more details about tables and columns in the database, see the Student Journey Data Dictionary.
Data Access Validation and Testing for Student Journey
To validate your connection to the Student Journey dataset, follow the instructions in the Data Warehouse Direct Access User Guide and use the following SQL query to verify connection:
select * from student_journey.public.ccc_district_vw
limit 10;This query should return 10 rows, confirming successful connectivity.
Colleges are encouraged to perform additional data access tests, such as running:
select * from student_journey.public.apply__mis_associative_entity limit 10;Using the Student Correlation Views
In the Student Journey database, there are five views that help uniquely identify students even when multiple students may have the same name, birthday, and last four digits of their social security number. This helps ensure the correct student is matched with their application, and it also helps identify fraudulent accounts.
The match_strength column in each view indicates if there are multiple criteria that match, indicating a level of confidence that this student is correctly matched with their application.
The table below describes each view.
View Name | Description |
|---|---|
correlation__birthdate_ccid_vw | The birthdate and the CCID match what is on the application. |
correlation__birthdate_ssn_vw | The birthdate and full Social Security Number match what is on the application. |
correlation__firstname_ccid_vw | The First Name and CCCID match what is on the application. |
correlation__firstname_ssn4_ccid_vw | The First Name, last four digits of the Social Security Number, and the CCID match what is on the application. |
correlation__ssn4_ccid_vw | The last four digits of the Social Security Number and the CCID match what is on the application. |
General Data Warehouse Help
If you need assistance with the CCC Data Warehouse, visit the http://CCCTechnology.info support channel. There, you can receive help from the Enabling Services Support (ESS) team and collaborate with other colleges and districts on using the CCC Data Warehouse.
