The tables below pertain to the MMPS data fields collected in the CCCApply Standard application.
This document is intended to map the data fields in Banner with the fields in the College Adaptor for MMPS data.
Note that the "College Adaptor Payload Name" in the table below is the field name in the College Adaptor that receives data from CCC Tech Center and third-party systems. Conductor is the”SuperGlue” bridge between the Tech Center systems and any/all third-party systems.
For example, for the Multiple Measures Placement Service:
Conductor first passes CCCApply data fields (the submitted application data) to ERP.
Then ERP generates a placement using the application data along with Cal-PASS Plus (California Department of Education) or CCGI data.
Conductor then requests the placement data from ERP.
Once Conductor gets the ERP’s placement output, it then maps each of the placement’s output fields to a College Adaptor input field.
Note: Currently, the output field names (from ERP) match the input field names for the College Adaptor. This fact/implementation detail is by design, but purely by happenstance that we coordinate with each other; since there is a mapping process, the field names do not have to match. For instance, the placementStatus field is not currently part of ERP—it’s solely defined within Conductor and provided as input to College Adaptor.
For the MMPS mappings (and any other third-party system mappings), we ONLY document the mappings to the “payload” names (College Adaptor input field names) that College Adaptor uses. Conductor is responsible for then mapping College Adaptor fields to/from the other system’s names. Most of the time, Conductor does very simplistic mappings, attempting to keep the fields names the same.