Page Comparison

...

The fields "hispanic", "race_group", and "race_ethnic"(Apply)/"race_ethnicity" (Intl) are calculated from the user's selections and made available to the college using the same format as previous versions of the applications.

We understand that several of the existing race & ethnicity fields (race_group; race_ethnic) align to MIS data elements (and other derived data elements) and colleges have configured data files to map to those MIS requirements. Throughout this implementation, we made it a priority to maintain the existing data output formats and leave these fields unchanged for this purpose.

...

What’s changing in CCCApply?

The change to the user interface is changing. The existing Race & Ethnicity section in CCCApply has been designed so as to not impact the colleges. There is no required actions for colleges. All existing data field formats would remain unchanged; while the new expanded ethnicities would be collected optionally in a new, completely separate, data field.The idea is to add one additional high-level category (Middle Eastern/North African) which would roll up into "White" for federal IPEDS reporting (as it currently does). The other groups would only be made visible if someone selected a high level group like "Asian"; then they would see all of the possible sub-categories for Asian. Work on this proposal has been ongoing with various stakeholder groups around the state for the past year or so- the layout and format of the race groups and ethnicity sub-categories - that appears to students - is changing.

For colleges, the back-end data output is changing but you only have to take action when you want to start downloading the new values in the new field being added. Only the new data field is different from what you are currently collecting now. The existing race fields will continue to download the data without any action or change to your Format file - in the same format you are been downloading today. This will not change.

The only change is in the new data field being added. The new data field will capture all the new race groups and ethnicity values that align to the layout changes in the new implementation.

When your college is ready to download/collect all the new race groups and ethnicities you will then need to update your Download Format XML file and the Download Client jar file <transfer-client.6.3.0>

What impact will this new format have on your college?

Responding to the ethnicity question (will remain) optionalremains optional for the student, and the expanded number of categories will be unobtrusive as the detailed subgroups will only be seen when one of the higher-level categories is selected first. This proposal is compliant with federal reporting requirements as all subgroups can be easily rolled up into the required federal ethnicity and race reporting categories. For example, the new high-level group, Middle Eastern and North African (MENA) rolls up into the “White” category for federal reporting purposes. Most importantly, information gathered from the expanded categories will allow colleges and districts to identify equity gaps and work to alleviate them by allowing for enhanced targeting of resources and services—thereby empowering CCC stakeholders to rise the challenge, laid out in the Vision for Success, of reducing and eventually closing all equity gaps by 2027.

What's happing to the existing race/ethnicity fields?

The technical specifications summaries below pertain to the new Race & Ethnicity Implementation 2018.Colleges must opt-in to implement these data fields, otherwise they will not display to your students. Note: Display of questions and data field downloads must be turned on manually by the CCCApply development team.

The new Race & Ethnicity Implementation 2018 includes: one new, optional data field to collect that collects all the new response options included in the expansion (Race Ethnicity Full); a new streamline layout to the Race & Ethnicity section in the Standard & International applications; and 194 new race and ethnicity-ancestry checkbox options in an accordion-style format.

• One bullet

• Two bullet

• Three bullet

Onscreen Text: " "

Summary of Data Elements

Hispanic

Data Element: <hispanic>

Notes: No changes, this field is a boolean true/false field that continues to work as in previous version

Example Format: boolean (true/false/null)

Race Group

Data Element: <race_group>

Notes: No changes, this field was intentionally left unchanged

Example Format: Apply: "04, 05, 08, 09, 14, 15, 17, 19, 20, 21", International: "04,05,08,09,14,15,17,19,20,21" (note lack of spaces for Intl)

Maximum Expected Width: 78 characters (unchanged) (20 * 2 character long values + 18 commas + 18 spaces + 2 surrounding quote marks for CSV delimiting in the output format)

Race Ethnicity

Data Element: <race_ethnic> (Apply) / <race_ethnicity> (International)

Notes: No changes, this field was intentionally left unchanged

Example Format: YNYNNNNYNNNNNNNNNYNNN

Maximum Expected Width: 22 characters (unchanged) (22 character long string)

Race Ethnicity Full

Data Element: <race_ethnic_full>

Notes: race_ethnic_full is a new field that will store the CSV separated values for all the ethnicity section selections for both the higher level ethnic groups and the associated sub groups as listed above in the chart.

Example Format: "100,101,117,118,200,205,08,09,500,15,600,601,17,19,602,700,701,713,800,802,803"

Maximum Expected Width: 804 characters (201 * 3 character long values + 199 commas + 2 surrounding quote marks for CSV delimiting in the output format)