Release Summary

CCCData v3.0.10 introduces several independent enhancements for DW Direct Connect users:

1. Near Real-Time Data Ingestion for several datasets

2. New Consolidation Database cornucopia

3. Expanded datasets

Near Real-Time Data Ingestion

For certain datasets, the Data Warehouse’s behind-the-scenes ETL processes now utilize AWS’s Zero-ETL Technology to stream data from upstream data sources into the Data Warehouse in near real time.

The CCCApply Submitted Applications, CVCOEI Shared Applications, Student Fraud Scores, and the Multiple Measures Placement Services datasets are streamed into the warehouse with a maximum lag time of 1 hour. This near-real-time data is available via a brand new cornucopia database. The existing application and mmps databases will continue to be refreshed on a nightly basis.

New Consolidation Database

A brand new database, named cornucopia, has been added to the Data Warehouse. This new database contains a series of schemas to support viewing both near-real-time (ongoing) data and snapshot (mostly nightly-refreshed) data. This database provides a centralized entry point to accessing common datasets from around the Data Warehouse.

Expanded datasets

MMPS

Five new tables are now available:

1. academic_record

   • Provides the self-reported and CCGI HS transcript summary data used by the MMPS to generate a placement recommendation record

   • Includes the class_of_year field

   • Includes the last_school_attended_name and last_school_attended_ceeb_code fields

2. academic_record_course

   • Provides a row per each HS course that was pulled from upstream academic record data-sources such as CCGI. Note: self-reported academic_records do not support listing individual courses.

   • Includes the organization_name and organization_ceeb_code fields

3. placement

   • Provides a listing of all generated placements per student application. a given student application may have more than one placement generated over time.

4. placement_academic_record

   • Provides a connection/mapping to show all the academic_records that were considered and taken into account when generating a placement record

5. placement_delivery_log

   • Provides a row per successful delivery of the placement into a given college’s staging table via superglue.

CCCApply Submitted Applications

Two new tables are now available:

1. shared_application_log

   • Provides a history of which applications where shared from a given home College to a teaching College per normal CVC-OEI application transfer requests.

   • As a new feature of Superglue v5.2.5; data is available to when such tracking began; on October 2nd, 2025

2. ipqs_fraud_score

   • Provides additional application fraud scoring insight for some of the metrics that were considered when determining an application’s final fraud_score field value.

   • Data is available back to May 5th, 2023

Enhancements to the submitted_application table:

Five new fields have been added:

1. fraud_status_last_updated_timestamp

   • Provides a timestamp in which the fraud_status value was last updated

2. fraud_status_last_updated_by

   • Provides the system-based user which made the update; be it superglue, or a spam filter user, or the behind-the-scenes 30-day cron job.

3. tstmp_delivered

   • Initially this field will be null for all records. In a future SuperGlue release, this field will be populated when an application is delivered either via SuperGlue’s college adaptor integration to a college staging table or by downloading the application via a SuperGlue API.

4. delivered_by

   • Initially this field will be null for all records. In a future SuperGlue release, this field will be populated when an application is delivered either via SuperGlue’s college adaptor integration to a college staging table or by a college downloading the application via a SuperGlue API.

5. military_jst_optin

   • This field has been added to the upstream CCCApply application. Reference the CCCApply Data Dictionaries for available values.

The following fields have been marked as deprecated and no longer provide values. Querying these columns will solely give null results:

• salt

• cryptokeyid

• signature

• orientation_encrypted_backup, orientation_encrypted

  • Note: the orientation field is still supported and should be used instead

• transgender_encrypted_backup, transgender_encrypted

  • Note: the transgender field is still supported and should be used instead

• tstmp_processing_finished

• ssid_rematched

Student Account Fraud Scores

When a student signs up for an OpenCCC account, and any time they make a change to their account, the OpenCCC system uses the account data to determine a fraud_score at the account level which is not tied to any given application nor college. This account-level fraud_score is then used in determining a submitted application’s fraud_score and fraud_status values. However, the account level fraud_score value is distinct and different from a given application’s fraud_score as the available data in making such determinations are different.

There is now a new database named student_account available to internal CCCTC staff and Chancellor’s Office DW Direct connect users.

There are four new tables added:

1. primary_fraud_profile

   • Provides a row per openCCC account (per ccc_id) to capture the current fraud_score for that account.

   • Note: the intent to to score each openCCC account going forward. Several accounts have been back-scored, but not all accounts.

2. override_history

   • Provides a row anytime the primary_fraud_profile.fraud_score field is overridden; to record the history of each change.

3. model_score_history

   • Provides multiple rows per OpenCCC account detailing the various models used in determining the final account-level fraud_score

4. business_rule_history

   • Provides a history of the changes to the business rule used in determining an OpenCCC accounts fraud_score value.

Known Issues

• There are no known issues in this release.