Request No. | 2018-18 |
---|---|
Date of Request | April 26, 2018 |
Requester | CCCCO / Craig Hayward |
Application(s) | CCCApply Standard / International |
Section / Page | Race & Ethnicity / Demographic Information |
Proposed Change to Download File | Yes - Adjustments & New Data Field |
Proposed Change to Residency Logic | N/A |
Problem and Business Need
There is a business need to expand the categories of race and ethnicity that are collected via CCCApply and in the International application. The current Student Equity Plan (SEP) guidelines do not include all ethnic groups that are relevant for distinct and diverse local communities served by the 114 colleges. For example, State Center College has a sizable Hmong population in its service area. However, their ability to conduct research, identify equity gaps, and direct resources in ways that will effectively close those gaps has been impeded because “Hmong” is not an ethnicity category that is collected on the standard application. We need to expand the ethnicity group data collected via the standard CCC application (CCCApply) and make that data available via the statewide MIS.
This is an approved change request coming from the Chancellor's Office to revise the overall layout and expand the race and ethnicity values to better provide disaggregated data for research. UAT checklist and detailed implementation steps are published in the CCCApply public documentation section.
Additional Information
Ethnicity/Ancestry Expansion Proposal
"Currently, the CCC system collects information on 21 distinct ethnicity or ancestry categories. For comparison purposes, consider that the CSU system collects data on 113 categories while the UC system collects data on 73 categories. CCCApply collects ethnicity information by first asking applicants if they are Hispanic or Latino. Respondents who select “Yes” then see an expanded set of more specific options to choose from. This the same mechanism that the proposed expansion will use to ensure that the collection of the additional, more specific ethnic groups is minimally disruptive to the application process."
Ethnicity-Ancestry Expansion Proposal Digest-Draft v 1.4.docx
Additional Information: https://www.diffen.com/difference/Ethnicity_vs_Race
Additional Info: SSSP Memo Excerpt
Excerpts from Student Success and Support Program re Student Equity SEC. 6. Article 1.5 (commencing with Section 78220) is added to Chapter 2 of Part 48 of Division 7 of Title 3 of the Education Code, to read:
Proposed Solution
Update the Race & Ethnicity section of the Demographic Information page to include an enhanced, expanded layout, with conditional expand/collapse formatting to hide certain sub-categories until a student selects the high level category.
Proposed by Craig Hayward, Bakersfield College, on April 26, 2018:
This is a proposal for expanding the categories of ethnicity that are collected via CCCApply. 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.
General Requirements
- Implements all new data fields & formats as close to the original formats as possible for minimal impact on the colleges
- Ensures that the <race_ethnic> field is particularly unchanged; this is the field that aligns to the MIS reporting requirement
- Rolls up all the new data values, especially the new race groups & ethnicities values (over 200 in all) into one new, additional field - that colleges can choose to add to their downloads or not;
- Encourages all colleges to add the new Race Ethnicity Full data field and fully update their download files, making all necessary adjustments to existing fields and run the new Download Client Jar file
Functional Mock Up for Proposed New Design
Attached is a functional Excel spreadsheet mockup for how this new layout and functionality should be in both the CCCApply and International Applications.
Click here: Ancestry proposal 2.43.xlsx
Current Design and Functionality
CCCApply Standard and International applications collect race and ethnicity information by first asking applicants if they are Hispanic or Latino. Respondents who select “Yes” then see an expanded set of more specific options to choose from. From there, applicants are asked what their race is and they are given limited high level categories to choose from.
Race & Ethnicity Section in Standard Application Today
(Before new Race & Ethnicity implementation - 6.3.0)
In the International Application Today
(before new Race & Ethnicity implementation - 6.3.0)
Current Database Values
(Before new Race & Ethnicity implementation 6.3.0)
Hispanic/Latino (hispanic_latino):
Race Group (race_group):
01: Hispanic, Latino - (From ‘Are you Hispanic / Latino?’
drop-down menu selection)
02: Mexican, Mexican-American, Chicano
03: Central American
04: South American
05: Hispanic: Other
Race Ethnicity (race_ethnicity):
06: Asian: Indian
07: Asian: Chinese
08: Asian: Japanese
09: Asian: Korean
10: Asian: Laotian
11: Asian: Cambodian
12: Asian: Vietnamese
13: Asian: Filipino
14: Asian: Other
15: Black or African American
16: American Indian / Alaskan Native
17: Pacific Islander: Guamanian
18: Pacific Islander: Hawaiian
19: Pacific Islander: Samoan
20: Pacific Islander: Other
21: White
Screenshots: New Layout Design
- Hispanic/Latino Question Auto-populated
- Hispanic/Latino Question Expanded Showing All Hispanic/Latino Subcategory Values
- Asian Race Group Expanded Showing All Asian Subcategory Values
- More Race Groups Expanded Showing Subcategory Values
New Race/Ethnicity Section
Zoom Demo: New Race & Ethnicity Layout
New UI Layout Demo
New Race & Ethnicity Changes - User Interface Demo
Zoom recording 09.14.18: https://cccconfer.zoom.us/recording/play/rJbSJXM0v3OcWtJaPncPnvSBB1LB7J_dxsSBF7JoEj4OdMLGWgT8hXWidv_LNxSz?continueMode=true
Change Specifications: New Layout Design and Database Values
Consistent with the original version, the new Race & Ethnicity section includes two sub-sections: 1) Hispanic/Latino section, which includes a Yes/No question: "Are you Hispanic or Latino?" question, which also serves as the high-level race group, and a sub-set of more specific ethnicities to choose from, and 2) Six high-level race groups, which when selected expand to display a set of more specific options, or ethnicities, to choose from.
Race/Ethnicity Section Header
The Race & Ethnicity section heading label is Race/Ethnicity that displays above the Hispanic/Latino ssection on the "Demographic Information" page. This did not change from the original (legacy) layout.
Hispanic/Latino Section
The following instruction text appears above the Hispanic/Latino Yes/No question. Respondents that answer Yes will see an expanded set of 19 Hispanic/Latino ethnicities to choose from. Many of these ethnicity options are new and can be downloaded in the new field: <race_ethnic_full>
"Per U.S. Department of Education guidelines, colleges are required to collect this racial and ethnic data.
Check the box below if you identify as Hispanic or Latino. If you indicate that you are Hispanic or Latino, you will have the option to select more specific ancestry groups."
Hispanic/Latino Database Values
There is no change to the Hispanic/Latino database values or data format.
Race Group (race_group) | Legacy Race Ethnicity Value / Mapping | NEW Associated Ethnicities Subgroup Values | Notes |
---|---|---|---|
Hispanic or Latino | 01 | 100 = New DB Value | This race group aligns to the Hispanic question:‘Are you Hispanic / Latino?’ |
Mexican, Mexican-American, Chicano | 02 |
| Map to existing value = 02 |
Central American | 03 |
| All these ethnicity values map to the original "Central American" race group = 03 in the existing "race_ethnic" field which is still used for MIS (SB29) reporting. |
South American | 04 |
| 10.12.18: Per Craig Hayward, Bakersfield College - Brazil is intentionally omitted from this implementation. |
Hispanic, Other | 05 |
| New value approved for "Other Hispanic or Latino" = 119, but maps to Hispanic, Other = 05 in race_ethnic for MIS (SB29) reporting. |
Section 2: Race Groups & Ethnicities
Below the Hispanic/Latino section, display the following additional instructive text and display the following set of high-level Race Groups adjacent to corresponding checkboxes.
"Check all of the ethnicity and ancestry groups that you identify with. When you select a major ethnicity group, you will have the option to select more specific ancestry groups. Select all that apply."
- Asian
- American Indian or Alaska Native
- Black or African American
- Native Hawaiian or Other Pacific Islander
- Middle Eastern or North African
- White
Respondents who select one or more of the Race Groups checkboxes will then see the expanded associated subgroups. Respondents may select as many race groups and ethnicity subgroups as needed. When a box is checked an accordion expansion should reveal the associated subgroups. When a box is unchecked, the accordion expansion should roll up to no longer show the subgroups.
Race Groups & Ethnicities Database Values
The following table shows a breakdown of the subgroups tied to each ethnic group, as well as the DB value associated in parenthesis.
Race Groups (race_group) | Current (Legacy) Value | NEW Associated Ethnicities Subgroup Values | Notes |
---|---|---|---|
Asian | n/a | 200 - - New DB Value of 200 | |
Asian: Indian | 06 |
| Note: All of the following Asian: Indian ethnicity responses from this group will map back to the legacy <race_ethnic> value for "Asian: Indian" = 06 |
Asian: Chinese | 07 |
| |
Asian: Japanese | 08 |
| |
Asian: Korean | 09 |
| |
Asian: Laotian | 10 |
| |
Asian: Cambodian | 11 |
| |
Asian: Vietnamese | 12 |
| |
Asian: Filipino | 13 |
| |
Asian: Other | 14 |
| All of these Asian: Other ethnicity responses will map back to the legacy <race_ethnic> value "Asian: Other" = 14 |
American Indian or Alaska Native | 16 | 300 -- New DB Value of 300 | |
NOTE: All of the following Native American Indian / Alaskan Native nations responses will map back to the legacy database value = "16" | 16 |
| All of the following American Indian / Alaskan Native responses will map back to the legacy <race_ethnic> value for American Indian or Alaska Native = "16" |
Black or African American | 15 | 500 -- New DB Value of 500 | |
Note: All of the following ethnicity responses will map back to the legacy value for "Black or AfricanAmerican" = 15 | 15 |
| Note: All of the following ethnicity responses will map back to the legacy <race_ethnic> value for "Black or AfricanAmerican" = 15 |
Native Hawaiian or Other Pacific Islander | n/a | 600 - - New DB Value of 600 | |
Pacific Islander: Guamanian | 17 |
| |
Pacific Islander: Hawaiian | 18 |
| |
Pacific Islander: Samoan | 19 |
| |
Pacific Islander: Other | 20 |
| |
Middle Eastern or North African | n/a | 700 - - New DB Value of 700 | |
Note: All of these new ethnicity responses will be mapped to the legacy value for "White" = 21 | 21 |
| Note: All of these new ethnicity responses will map back to the legacy <race_ethnic> value for "White" = 21 |
White | 800 - - New DB Value of 800 | ||
Note: All of these new ethnicity responses will be mapped to the legacy value for "White" = 21 | 21 |
| Note: All of these new ethnicity responses will map back to the legacy <race_ethnic> value for "White" = 21 |
Release Information for Colleges
The Race & Ethnicity Implementation 2018 is a significant revision to the current, highly-regulated Race & Ethnicity section in CCCApply which is protected by federal law, the Office of Civil Rights, and aligns to various MIS (SB29) and IPEDs (STD10) reporting requirements. The new implementation will be in place before the MIS requirements are updated in Fall 2019.
CCCApply's objective for this implementation is twofold:
1) Whenever possible, provide colleges with the same data fields and formats implemented in the current implementation.
2) Provide all new fields, response options, and values in new data fields, as opposed to revising or reconfiguring existing fields and formats.
We understand that several of the existing race & ethnicity fields align to MIS data elements (and other derived data elements) and colleges have configured their data mappings to those MIS requirements. Whenever possible, we have kept the existing data formats unchanged for this purpose. Please see a summary of changes for each data field used in this new implementation.
In-Progress Applications
For In-Progress applications, there will be no database value mappings. If an application is in-progress at the time of release - and a student had already selected a race/ethnicity, the user will be presented with a client-side error validation message upon resuming that application that advises them of the following:
The Race and/or Ethnicity you have selected is no longer valid. Please go back to the Demographic Information tab and select a new value.
The user should not be able to submit the Apply or International application unless they have chosen a valid database value(s) for race_group and race_ethnicities. Once the new value is chosen, we will store the new value.
Data Formats & Downloads
The new Race & Ethnicity implementation is a combination of existing questions, values, and data fields - with one new additional data field and upwards of 200+ new ethnicity values.
We have designed this transition from the legacy formats to the new full implementation such that IF colleges want to implement the new race groups and ethnicity values they will need to make some minor changes to their download files and run the updated Download Client jar file in Pilot and Production, following each release. Below is a list of the changes that need to be made to each of the existing fields and the new, optional, full implementation data field.
Required Adjustments to Download Files
From a download file perspective, all colleges should review the new data configuration for this implementation to ensure they understand and identify any changes that could affect your current data output file.
Colleges using a fixed-width output format may need to adjust their race_group column width to account for the way this data is being used now. Originally, this would store the raw data mappings in CSV format for both the Hispanic sections and the other Race Ethnicity choices, so it would download as a format like : "02, 05, 06, 07, 21" and so on. This is now changing to map only the Race Group values, which will store in the following format: "100,200,300,500,600,700,800".
- The system does not store names; maps to numerical values. DB is a text field which has unlimited length. When we store the user's response option, we save code value - no names are stored.
- If the college wants to add the new <race_ethnic_full> column, they will need to download a 6.3.0 version of the transfer-client.jar file
- If the colleges keep their old transfer clients in place and do not upgrade, they should be fine with regard to the R/E update. Since we are keeping the <race_ethnic> column the same, no changes are necessary for that.
- Since we are re-purposing the data in the race_group column, however, the colleges, regardless of any download client changes, will start receiving the repurposed data since that is what is now being stored in that column.
Colleges that want to collect the new Race & Ethnicity Full data values will need to add the new data element to your Format Definitions XML files and update the Download Client with the v.6.3.0 jar file.
Reminder: CCCApply Standard and International applications must be updated separately using your application-specific Format Definition XML files. This is only relevant if your college has implemented the CCCApply International application.
Hispanic/Latino
Description: This is an existing data field <hispanic> that will continue to align to the Hispanic/Latino question and provides the first character of the Race Ethnicity field (race_ethnic).
Field: hispanic
Notes: No changes, this field is a boolean true/false field that continues to work as in the previous version
Example Format: boolean (true/false/null)
Historical Notes: The basic two-question format, the Hispanic ethnicity and race categories, and certain other aspects such as not requiring responses are IPEDS requirements. The race subcategories such as 'Asian: Chinese' and 'Pacific Islander: Hawaiian' are defined by MIS at the Chancellor's Office (data element SB29).
Race Group
Description: This is an existing data field <race_group> that has been repurposed slightly to capture the old race groups (mapped to new values) and the new race groups.
Field: race_group
Notes: 'race_group' originally stored the Hispanic Race Group choices in a comma delimited format with the values, such as "02, 03, 04". Now, the 'race_group' field stores only the new Race Group mappings as CSV content with no spaces. See the table of values for all new mappings.
Example Format: "100,200,300,500,600,700,800"
Maximum Expected Width: 30 characters (7 * 3 character long values + 6 commas + 2 surrounding quote marks for CSV delimiting in the output format). The college's parsing library should make this possible - but the spaces need to be removed between the commas and values - which is consistent with other CSV formats.
Race Ethnicity
Description: This is an existing field <race_ethnic> that remains in its original format for continued reporting to MIS (SB29).
Field: race_ethnic (Apply) / race_ethnicity (International)
Notes: No changes, this field was intentionally left unchanged. Null is allowed.
International Application: Please note that this field and format has a different data element name in the International Application: <race_ethnicity>
Example Format: YNYNNNNYNNNNNNNNNYNNN
Maximum Expected Width: 22 characters (22 character long string)
New "Race & Ethnicity Full" Data Field
Description: A new data field collecting a combination of all the new Ethnicities added in the 2018 implementation.
Field: race_ethnic_full
Notes: New field added to capture all of the new ethnicities added with the new 2018 implementation. 'race_ethnic_full' will store the CSV separated values of all selected ethnicities (subcategories). Colleges will need to add this to their format file and the download client to receive this field.
Example Format: "101,102,203,07,392,394,401,15,503,601,17,701,713,801,809"
Maximum Expected Width: 776 characters (194 * 3 character long values + 192 commas + 2 surrounding quote marks for CSV delimiting in the output format)
Changes by Section
Section | Field | Original (Legacy) Implementation | Original Backend | NEW Race & Ethnicity Changes to User Interface | NEW Race & Ethnicity Changes to Data Fields & Formats | What colleges need to do |
---|---|---|---|---|---|---|
Hispanic / Latino Question | hispanic | Yes / No radio buttons | Boolean Y/N or T/F (Note - corresponds to (01) | None | None | Nothing, No Change |
Race Group | race_group | Combination of the Race Groups | Varying length Storing actual value In-progress side, race_group would only save the 02, 03, 04, 05 Submitted side, race_group stored ALL values (hispanic and non-hispanic choices) | This field has been repurposed but remains mostly the same as the legacy format. Now, user interface shows all the unchanged and new high-level race groups in checkboxes. The format now saves the new race group values (hispanic and non-hispanic groups). Added additional options in checkboxes as subgroups | New format stores the Race Groups data in CSV Format. NOTE: No longer saves spaces between comma separated values. Spaces need to be removed from delimited and fixed width formats. Changes to the outputs: Delimited Format: Remove spaces, but no change is required to your Format XML. Will save and download new race groups. Fixed Width Format: Requires adjustment to your existing Format XML. Account for removed spaces. | Account for the different meaning of the data coming through, also adjust fixed-width delimited download client format as needed |
Race / Ethnicity (Original, legacy data output) | race_ethnic | Combination of 21 values: Hispanic/Latino Y/N question & all ethnicities checkboxes | Duplicate use of values Storing the YNX block (YNNNNYN) | Slight change to the user interface. No change to the Hispanic/Latino question (which doubles as the Hispanic/Latino race group). All new configuration of hispanic/latino question, race groups, and race ethnicities with map to the original values/format. The new race groups serve as the high-level categories to all new ethnicities. When a respondent selects a race group, the corresponding ethnicity subcategories values display. | There is no change to the original data output. The new layout and values will map to the original legacy format. This field will continue to store values in the legacy YNNNYNNYN... format. Null is still allowed in the first character position. Example Format: XNYNNNNYNNNNNNNNNYNNN Maximum Expected Width: 22 characters (22 character long string) | Nothing. This field is intentionally left unchanged for MIS SB29 reporting purposes. This is the field that gets reported to MIS SB29. This will not change. |
Race / Ethnicity Full | race_ethnic_full | N/A | N/A | Full display of all new ethnicity values (subcategories) added in new Race & Ethnicity implementation (2018). There are a total of 194 possible values for the data field. Each race group contains one or more ethnicities, which are displayed as checkboxes when selected by a respondent. | This is a new data field dedicated to storing CSV separated values of all new ethnicity responses (subcategories). Colleges that want to download this new data - in addition to the original legacy Race/Ethnicity data will need to add this field to their Format Definitions XML file and update the Download Client Jar file to download this data. Example Format: "101,102,203,07,392,394,401,15,503,601,17,701,713,801,809" Maximum Expected Width: 776 characters (194 * 3 character long values + 192 commas + 2 surrounding quote marks for CSV delimiting in the output format) | New download field. Optional. Colleges should add this field if they want to download all the new race & ethnicities values for research purposes. |
NOTE: If the college does nothing - they don't update their Download Format file (XML) then: Values that weren't a clear one-to-one map, were changed. See the list of new ethnicities for details. CHANGE: race_group will give them the new values regardless of whether they update the downloads or not Doesn't require a jar file update But the Race Group will come down with the new values - still comma separated values but map to the new super groups |
MIS Data Elements
MIS Data Element | MIS Derived Data Element |
---|---|
SB29 - Multi-Ethnicity | STD10 - Student -Ethnicity (Derived Data Element) Used for IPEDs reporting |
Updated Data Dictionary Tables
Hispanic/Latino
Data Element: | hispanic |
Description: | Applicant’s response to ‘Are you Hispanic or Latino?’ |
Format, Length: | boolean, 1 |
Values: | 1 = True/Yes, 0 = False/No If Null, the value will appear as blank in the downloads and Report Center. |
Allows Null: | Yes (see above) |
Default: | None |
Usage: | New 12.07.18: This element and "race_group' are used to derive 'race_ethnic" (Apply) and 'race_ethnicity' (International), which is still used for MIS (SB29) reporting. NOTE: MIS will update SB29 to match new configuration in Fall 2019. |
Notes: | Ethnicity is sensitive information, protected by federal law and the Office of Civil Rights. Any change to the text, prompt, access, or transmission of this data item must be approved by the Legal Counsel of the CCC Chancellor’s Office and the Office of Civil Rights. |
This information may not be provided to staff in the capacity of making a decision to admit an applicant until after the applicant is admitted—that is, uniformly enabled to register for classes. | |
Xap Field: | hispanicLatino |
Revision Log: | December 2018 (v.6.3.0) |
Question Text: | Are you Hispanic or Latino? Yes [radio button, clearable] No [radio button, clearable] |
Conditions: | Always |
Additional Text: | "Per U.S. Department of Education guidelines, colleges are required to collect this racial and ethnic data. Check the box below if you identify as Hispanic or Latino. If you indicate that you are Hispanic or Latino, you will have the option to select more specific ancestry groups." |
Response Options: | Yes No or X = No response |
Pop-Up Help: | None |
Field Error Check: | None |
Page Error Check: | None; optional response per IPEDS and CCCCO. |
Notes: | Ethnicity is sensitive information, protected by federal law and the Office of Civil Rights. Any change to the text, prompt, access, or transmission of this data item must be approved by the Legal Counsel of the CCC Chancellor’s Office and the Office of Civil Rights. This information may not be provided to staff in the capacity of making a decision to admit an applicant until after the applicant is admitted—that is, uniformly enabled to register for classes. |
Data Element: | hispanic |
Race/Ethnicity
Data Element: | race_ethnic (CCCApply Standard) | |
Description: | Combination of responses to legacy Hispanic/Latino question and ethnicities, and all original race groups and ethnicities, as per MIS (SB29) reporting requirements. | |
Format, Length: | bpchar, 22 No changes were made to this field, it was intentionally left unchanged. Null is allowed in first character position to represent Hispanic/Latino question response. Example Format: XNYNNNNYNNNNNNNNNYNNN Maximum Expected Width: 22 characters (22 character long string) | |
Values: | See Table | |
Allows Null: | No | |
Default: | None | |
Usage: | Correlates to MIS SB29. Ethnicity is used primarily by agencies affiliated with state reporting and evaluation of educational programs. This set of questions/data was based on specifications by the U.S. Dept. of Education in effect for all applicants beginning with the Summer 2009 term. | |
Notes: | This field is intentionally left unchanged for MIS SB29 reporting purposes. Example Format: YNYNNNNYNNNNNNNNNYNNN Maximum Expected Width: 22 characters (22 character long string) Note: Regarding new Race & Ethnicity implementation (v.6.3.0), colleges should continue to use this field to comply with the legacy MIS SB29 reporting requirements This field remains dedicated to the original (legacy) combined format. Per CCCCO Management Information Systems Division, SB29 will be revised to align with the new race and ethnicity values in Fall 2019. All the new Ethnicities added in December 2018 (v.6.3.0) are available in the new field <race_ethnic_full>. Ethnicity is sensitive information, protected by federal law and the Office of Civil Rights. Any change to the text, prompt, access, or transmission of this data item must be approved by the Legal Counsel of the CCC Chancellor’s Office and the Office of Civil Rights. This information may not be provided to staff in the capacity of making a decision to admit an applicant until after the applicant is admitted—that is, uniformly enabled to register for classes. The basic two-question format, the Hispanic ethnicity and race categories, and certain other aspects such as not requiring responses are IPEDS requirements. Any changes to race groups (categories) or ethnicities (sub-categories) implemented in the new implementation will map back to the original values specified by MIS at the Chancellor's Office (data element SB29). | |
Revision Log: | December 2018 | |
Char | Race/Ethnicity | Values |
1 | Hispanic, Latino | From ‘Are you Hispanic / Latino?’ radio button format: ‘Y’ if ‘Yes’; ‘N’ if ‘No’; otherwise ‘X’ |
2 | Mexican, Mexican-American, Chicano | ‘Y’ if box is checked; otherwise ‘N’ |
3 | Central American | ‘Y’ if box is checked; otherwise ‘N’ |
4 | South American | ‘Y’ if box is checked; otherwise ‘N’ |
5 | Hispanic Other | ‘Y’ if box is checked; otherwise ‘N’ |
6 | Asian Indian | ‘Y’ if box is checked; otherwise ‘N’ |
7 | Asian Chinese | ‘Y’ if box is checked; otherwise ‘N’ |
8 | Asian Japanese | ‘Y’ if box is checked; otherwise ‘N’ |
9 | Asian Korean | ‘Y’ if box is checked; otherwise ‘N’ |
10 | Asian Laotian | ‘Y’ if box is checked; otherwise ‘N’ |
11 | Asian Cambodian | ‘Y’ if box is checked; otherwise ‘N’ |
12 | Asian Vietnamese | ‘Y’ if box is checked; otherwise ‘N’ |
13 | Asian Filipino | ‘Y’ if box is checked; otherwise ‘N’ |
14 | Asian Other | ‘Y’ if box is checked; otherwise ‘N’ |
15 | Black or African American | ‘Y’ if box is checked; otherwise ‘N’ |
16 | American Indian / Alaskan Native | ‘Y’ if box is checked; otherwise ‘N’ |
17 | Pacific Islander Guamanian | ‘Y’ if box is checked; otherwise ‘N’ |
18 | Pacific Islander Hawaiian | ‘Y’ if box is checked; otherwise ‘N’ |
19 | Pacific Islander Samoan | ‘Y’ if box is checked; otherwise ‘N’ |
20 | Pacific Islander Other | ‘Y’ if box is checked; otherwise ‘N’ |
21 | White | ‘Y’ if box is checked; otherwise ‘N’ |
Race Group
Data Element: | race_group |
Description: | Combination of all responses to the new race groups (high-level categories) implemented in December 2018. |
Format, Length: | Varchar, 30 characters (7 * 3 character long values + 6 commas + 2 surrounding quote marks for CSV delimiting in the output format). Database stores as text string Notes: 'race_group' originally stored the Hispanic/Latino Race Group choices in a comma delimited format with the values, such as "02, 03, 04". Now, the 'race_group' field stores only the new Race Group mappings as CSV content with no spaces, as opposed to the old format which stored the raw values for the Ethnicity choices separated by a comma and a space (e.g. "02, 05, 06, 07, 21"). No longer saves spaces between comma separated values. Example Format: “100,200,300,500,600,700,800” |
Values: | String of codes indicating all new race group checkboxes that are checked, delimited by comma with no spaces between each code. New race_group codes are: |
100 – Hispanic or Latino 200 – Asian 300 – American Indian or Alaskan Native 500 – Black or African American 600 – Native Hawaiian or Other Pacific Islander 700 – Middle Eastern or North African 800 - White | |
Allows Null: | Yes |
Default: | None |
Usage: | This data element was repurposed in the new Race & Ethnicity implementation of 2018. The element now only stores the new high-level race groups (categories), including Hispanic/Latino. It is no longer used to derive the ‘race_ethnic’ data (which is still used as the primary element for MIS SB29 reporting). |
Notes: | Ethnicity is sensitive information, protected by federal law and the Office of Civil Rights. Any change to the text, prompt, access, or transmission of this data item must be approved by the Legal Counsel of the CCC Chancellor’s Office and the Office of Civil Rights. This information may not be provided to staff in the capacity of making a decision to admit an applicant until after the applicant is admitted—that is, uniformly enabled to register for classes. The basic two-question format, the Hispanic ethnicity and race categories, and certain other aspects such as not requiring responses are IPEDS requirements.. 12.07.18: This field has been repurposed as part of the new Race & Ethnicity implementation of 2018; however remains mostly the same as the legacy format. Now, user interface shows all the unchanged and new high-level race groups in checkboxes. The format now saves the new race group values (hispanic and non-hispanic groups). Added additional options in checkboxes as subgroups |
Xap Field: | raceGroup |
Revision Log: | 12.07.18 (v.6.3.0) |
Question Text: | "Check all of the ethnicity and ancestry groups that you identify with. When you select a major ethnicity group, you will have the option to select more specific ancestry groups. Select all that apply." [checkbox] Asian |
Conditions: | Always |
Response Options: | Any combination of checkboxes can be checked, from none to all. · Asian · American Indian or Alaska Native · Black or African American · Native Hawaiian or Other Pacific Islander · Middle Eastern or North African · White |
Field Error Check: | None |
Page Error Check: | None; optional response per IPEDS and CCCCO. |
Notes: | See note for Hispanic/Latino (previous table). |
Data Element: | race_group |
Race & Ethnicity Full
Data Element: | race_ethnic_full |
Description: | Combination of all responses of new ethnicities (subcategories) added in 2018 implementation. |
Format, Length: | Stores CSV separated values of all selected ethnicities (subcategories). Maximum Expected Width: 776 characters (194 * 3 character long values + 192 commas + 2 surrounding quote marks for CSV delimiting in the output format) Example Format: "101,102,203,07,392,394,401,15,503,601,17,701,713,801,809" |
Values: | String of codes indicating all new ethnicity checkboxes that are checked, delimited by commas with no spaces between each code. See table of full ethnicity values below. |
Allows Null: | Yes |
Default: | None |
Usage: | New data field added to collect all new ethnicities (subcategories) implemented in 2018. Colleges that want to collect and download these new values must add this field to their Format XML file and run the new Download Client v.6.3.0 jar file. |
Notes: | Ethnicity is sensitive information, protected by federal law and the Office of Civil Rights. Any change to the text, prompt, access, or transmission of this data item must be approved by the Legal Counsel of the CCC Chancellor’s Office and the Office of Civil Rights. This information may not be provided to staff in the capacity of making a decision to admit an applicant until after the applicant is admitted—that is, uniformly enabled to register for classes. |
Revision Log: | New 12.07.18 (v.6.3.0) |
Question Text: | "Check all of the ethnicity and ancestry groups that you identify with. When you select a major ethnicity group, you will have the option to select more specific ancestry groups. Select all that apply." |
Conditions: | Always |
Response Options: | Any combination of checkboxes can be checked, from none to all. See full list of ethnicities in table below. Complete list of ethnicities are displayed (expand) when race group category is selected. |
Field Error Check: | None |
Page Error Check: | None; optional response per IPEDS and CCCCO. |
Notes: | New data field to capture full combination of all new ethnicity values (subcategories). There are a total of 194 possible values for the data field. Each race group contains one or more ethnicities, which are displayed as checkboxes when selected by a respondent. |
Data Element: | race_ethnic_full |
Story
As a college researcher, I need the ability to disaggregate API data of the college/system race and ethnicity demographical data collected in CCCApply and International application so the data is captured in a more detailed manner for federal IPEDs reporting on ethnicity data.