Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Request No. 2018-18
Date of RequestApril 26, 2018 
RequesterCCCCO / Craig Hayward 
Application(s)CCCApply Standard / International
Section / Page

Race & Ethnicity / Demographic Information 

Proposed Change to Download FileYes - Adjustments & New Data Field
Proposed Change to Residency LogicN/A 



Table of Contents


Problem and Business Need

Research conducted over the past two years by the Student Equity Planning workgroup and the Chancellor's Vision for Success  has resulted in a system-wide focus on closing equity gaps. Historical MIS data sets, however, do not include all ethnic groups that are relevant for the diverse and distinct communities served by the 115 California community colleges.

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) in CCCApply and make that data available via the statewide MIS. 

Info

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:

Expand
titleClick here to read Article 1.5. Student Equity Plans 78220....

Article 1.5. Student Equity Plans 78220.

(a) As a condition for receiving Student Success and Support Program funding, and in order to ensure equal educational opportunities and to promote student success for all students, regardless of race, gender, age, disability, or economic circumstances, the governing board of each community college district shall maintain a student equity plan that includes all of the following for each community college in the community college district:

(1) Campus-based research as to the extent of student equity by gender and for each of the following categories of students:

(A) Current or former foster youth.

(B) Students with disabilities.

(C) Low-income students.

(D) Veterans.

(E) Students in the following ethnic and racial categories, as they are defined by the United States Census Bureau for the 2010 Census for reporting purposes:

(i) American Indian or Alaska Native.

(ii) Asian.

(iii) Black or African American.

(iv) Hispanic or Latino.

(v) Native Hawaiian or other Pacific Islander.

(vi) White.

(vii) Some other race.

(viii) More than one race.

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

One of the primary objectives for this new implementation is to minimally impact the colleges with data field changes. The legacy race ethnicity section in CCCApply (and across all higher education) is a highly regulated data collection and set of questions - mandated by state and federal, and aligns to MIS and IPEDs reporting requirements. 
It is critical that this implementation:
  • 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)

Image Removed

In the International Application Today

(before new Race & Ethnicity implementation - 6.3.0)

Image Removed

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:

This system-wide need to close the equity gaps was the impetus for the Ethnicity-Ancestry Expansion Project 2018, and the foundation of this change request. 



Proposed Solution

In summary this proposal will expand the categories of ethnicity/ancestry collected in CCCApply, and includes a detailed set of requirements for a redesign to the layout and the specific ethnicity values and race groups that should be added.

According to one of the authors of the proposal, Craig Hayward, Dean of Institutional Research at Bakersfield College:

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.

Responding to the ethnicity question (will remain) optional, 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.

Click here: Ancestry proposal 2.43.xlsx


Info

Approval Information

This proposal was reviewed by the Chancellor’s Office Data, Evaluation and Research (CODER) group, which includes representatives from the Chancellor’s Office MIS and research units as well as other stakeholders from the Research and Planning Group, Education Results Partnership, and the Workforce and Economic Development Division of the Chancellor’s Office. The proposal was favorably reviewed and APPROVED to be advanced for adoption. One area of particular focus was the discussion of how students feel a sense of belonging when they see their ethnic background represented as an option. In particular, the discussion focused on whether to include all Native American tribes that are recognized by the state of California and if not, where to draw the line.



Additional Information

Ethnicity/Ancestry Expansion Proposal

This proposal was approved by the Chancellor's Office based on over two years of research and dialogue by the Student Equity Planning workgroup and the Chancellor's Vision for Success.  The proposal is clearly explained in the "Ethnicity-Ancestry Expansion Proposal".  See an excerpt below. 

"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."


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:

Expand
titleClick here to read Article 1.5. Student Equity Plans 78220....

Article 1.5. Student Equity Plans 78220.

(a) As a condition for receiving Student Success and Support Program funding, and in order to ensure equal educational opportunities and to promote student success for all students, regardless of race, gender, age, disability, or economic circumstances, the governing board of each community college district shall maintain a student equity plan that includes all of the following for each community college in the community college district:

(1) Campus-based research as to the extent of student equity by gender and for each of the following categories of students:

(A) Current or former foster youth.

(B) Students with disabilities.

(C) Low-income students.

(D) Veterans.

(E) Students in the following ethnic and racial categories, as they are defined by the United States Census Bureau for the 2010 Census for reporting purposes:

(i) American Indian or Alaska Native.

(ii) Asian.

(iii) Black or African American.

(iv) Hispanic or Latino.

(v) Native Hawaiian or other Pacific Islander.

(vi) White.

(vii) Some other race.

(viii) More than one race.



Legacy 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 Legacy - Before 6.3.0

CCCApply Standard Application

Current Database Values

International Application
(Before new Race & Ethnicity implementation - 6.3.0)(Before new Race & Ethnicity implementation 6.3.0)(Before new Race & Ethnicity implementation - 6.3.0)
Image Added

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

Native
17: Pacific Islander: Guamanian
18: Pacific Islander: Hawaiian
19: Pacific Islander: Samoan
20: Pacific Islander: Other
21: White

Image Added




General Requirements

One of the primary objectives for this new implementation is to minimally impact the colleges with data field changes. The legacy race ethnicity section in CCCApply (and across all higher education) is a highly regulated data collection and set of questions - mandated by state and federal, and aligns to MIS and IPEDs reporting requirements. 
It is critical that this implementation:
  • Backward Compatibility - No change to data downloads:  Implement the new expanded race and ethnicity categories without changing the existing formats and data output; keeping the download files unchanged and seamlessly backwards compatible.
  • Minimal impact on 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



Screenshots: New Layout Design

Expand
titleClick here to see more screenshots of the new Race/Ethnicity layout designs:

New Hispanic Question & Race Groups - Auto-populated


New Hispanic Question Expanded


Asian Category Expanded


More Groups Expanded


  • 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

Image RemovedImage Added


Zoom Demo: New Race & Ethnicity Layout 

Info
titleNew 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.  

New Race Group 
Name & Value
(race_group)
Legacy Race Group ValueNew Race Group Value
New Race Ethnicity Full Values 
(race_ethnic_full)
Add metadata to the new race_group and race_ethnicity that will map/aligns to the legacy race/ethnicities
Hispanic, Latino 01100

Response to question "Are you Hispanic or Latino?"

  • Argentinean - should map back to DB value of 04
  • Bolivian should map back to DB value of 04
  • Chilean should map back to DB value of 04
  • Colombian - should map back to DB value of 04
  • Costa Rican should map back to DB value of 03
  • Cuban - should map back to DB value of 05
  • Dominican (Dominican Republic) should map back to DB value of 05
  • Ecuadorian - should map back to DB value of 04
  • Guatemalan - should map back to DB value of 03
  • Honduran - should map back to DB value of 03
  • Mexican  - should map back to DB value of 02
  • Nicaraguan - should map back to DB value of 03
  • Panamanian - should map back to DB value of 03
  • Peruvian - should map back to DB value of 04
  • Puerto Rican - should map back to DB value of 05
  • Salvadoran - should map back to DB value of 03
  • Spanish - should map back to DB value of 05
  • Venezuelan - should map back to DB value of 04
  • Other Hispanic or Latino - should map back to DB value of 05

    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.  Response to question "Are you Hispanic or Latino?"

    New Race Group 
    Name & Value
    (race_group)
    Legacy Race Group ValueNew Race Group Value
    New Race Ethnicity Full Values 
    (race_ethnic_full)
    Add metadata to the new race_group and race_ethnicity that will map/aligns to the legacy race/ethnicities
    Hispanic, Latino 01100

    Response to question "Are you Hispanic or Latino?" = 100


    Mexican, Mexican-American, Chicano02
    • Mexican  - New DB Value of 111 

    Central American03
    • Costa Rican - New DB Value of 105
    • Guatemalan - New DB Value of 109
    • Honduran - New DB Value of 110
    • Nicaraguan - New DB Value of 112
    • Panamanian - New DB Value of 113
    • Salvadoran - New DB Value of 116

    South American04
    • Argentinean - New DB Value of 101
    • Bolivian - New DB Value of 102
    • Chilean - New DB Value of 103
    • Colombian - New DB Value of 104
    • Ecuadorian - New DB Value of 108
    • Peruvian - New DB Value of 114
    • Venezuelan - New DB Value of 118

    Hispanic: Other05
    • Cuban - New DB Value of 106
    • Dominican (Dominican Republic) - New DB Value of 107
    • Puerto Rican - New DB Value of 115
    • Spanish - New DB Value of 117 
    • Other Hispanic or Latino - New DB Value of 119 


    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. 

    Legacy Race Group 
    Name

    Legacy Race Group Value
    (race_group)
    New Race Group Value in Race Ethnicity Full
    New Race Ethnicity Full Name & Values 
    (race_ethnic_full)
    Mapping Notes:

    Asian

    06200
    • Afghan - New DB Value of 201
    • Bangladeshi - New DB Value of 202
    • Burmese/Myanmar - New DB Value of 203
    • Indian - ((Stays as 06)
    • Pakistani - New DB Value of 206
    • Sri Lankan - New DB Value of 207

    The following ethnicity subgroups should map back to DB value = 06

    • Afghan 
    • Bangladeshi 
    • Burmese/Myanmar 
    • Indian 
    • Pakistani 
    • Sri Lankan
  • Chinese should map back to Asian:Chinese 07
  • Japanese should map back to Asian: Japanese 08
  • Korean should map back to Asian: Korean 09
  • Laotian should map back to Asian: Laotian 10
  • Cambodian should map back to Asian: Cambodian
  • Vietnamese should map back to Asian: Vietnamese
  • Filipino should map back to Asian: Filipino
  • Homng, Indonesian, Other Asian, Taiwanese and Thais should map back to Asian: Other 14.  

    Asian

    06200
    • Afghan - New DB Value of 201
    • Bangladeshi - New DB Value of 202
    • Burmese/Myanmar - New DB Value of 203
    • Indian - ((Stays as 06)
    • Pakistani - New DB Value of 206
    • Sri Lankan - New DB Value of 207



    Asian: Chinese07
    • Chinese - (Stays as 07)

    Asian: Japanese08
    • Japanese - (Stays as 08)

    Asian: Korean09
    • Korean - (Stays as 09)

    Asian: Laotian10
    • Laotian -  (Stays as 10)

    Asian: Cambodian11
    • Cambodian - (Stays as 11)

    Asian: Vietnamese12
    • Vietnamese - (Stays as 12)

    Asian: Filipino13
    • Filipino - (Stays as 13)

    Asian: Other14
    • Hmong - New DB Value of 204
    • Indonesian - New DB Value of 205
    • Taiwanese - New DB Value of 208
    • Thai - New DB Value of 209
    • Other Asian - (Stays as 14)

    American Indian or Alaska Native

    16300
    • Agua Caliente Band of Cahuilla Indians of the Agua Caliente Indian Reservation - New Value of 301
    • Alturas Indian Rancheria - New DB Value of 302
    • Augustine Band of Cahuilla Indians - New DB Value of 303
    • Aztec or Mixtec - New DB Value of 304
    • Bear River Band of the Rohnerville Rancheria - New DB Value of 305
    • Berry Creek Rancheria of Maidu Indians of California - New DB Value of 306
    • Big Lagoon Rancheria - New DB Value of 307
    • Big Pine Band Paiute Tribe of the Owens Valley - New DB Value of 308
    • Big Sandy Rancheria of Western Mono Indians of California - New DB Value of 309
    • Big Valley Band of Pomo Indians of the Big Valley Rancheria - New DB Value of 310
    • Bishop Pauite Tribe (previously listed as Paiute-Shoshone Indians of the Bishop Community of the Bishop Colony) - New DB Value of 311
    • Blue Lake Rancheria - New DB Value of 312
    • Bridgeport Indian Colony - New DB Value of 313
    • Buena Vista Rancheria of Me-Wuk Indians of California - New DB Value of 314
    • Cabazon Band of  Mission Indians - New DB Value of 315
    • Cachil DeHe Band of Wintun Indians of the Colusa Indian Community of the Colusa Rancheria - New DB Value of 316
    • Cahuilla Band of Mission Indians of the Cahuilla Reservation - New DB Value of 317
    • Cahto Indian Tribe of the Laytonville Rancheria - New DB Value of 318
    • California Valley Miwok Tribe - New DB Value of 319
    • Campo Band of Diegueño Mission Indians of the Campo Indian Reservation - New DB Value of 320
    • Capitan Grande Band of Diegueño Mission Indians of California:Barona Group of Capitan Grande Band of Mission Indians of the Barona Reservation; Viejas (Baron Long) Group of Capitan Grande Band of Mission Indians of the Viejas Reservation - New DB Value of 321
    • Cedarville Rancheria - New DB Value of 322
    • Chemehuevi Indian Tribe of the Chemehuevi Reservation - New DB Value of 323
    • Cher-Ae Heights Indian Community of the Trinidad Rancheria - New DB Value of 324
    • Cherokee - New DB Value of 325
    • Chicken Ranch Rancheria of Me-Wuk Indians of California - New DB Value of 326
    • Chippewa - New DB Value of 327
    • Cloverdale Rancheria of Pomo Indians of California - New DB Value of 328
    • Cold Springs Rancheria of Mono Indians of California - New DB Value of 329
    • Colorado River Indian Tribes of the Colorado River Indian Reservation (Arizona and California) - New DB Value of 330
    • Cortina Indian Rancheria of Wintun Indians of California - New DB Value of 331
    • Coyote Valley Band of Pomo Indians of California - New DB Value of 332
    • Death Valley Timbi-Sha Shoshone Tribe - New DB Value of 333
    • Dry Creek Rancheria of Pomo Indians - New DB Value of 334
    • Elem Indian Colony of Pomo Indians of the Sulphur Bank Rancheria - New DB Value of 335
    • Elk Valley Rancheria - New DB Value of 336
    • Enterprise Rancheria of Maidu Indians of California - New DB Value of 337
    • Ewiiaapaayp Band of Kumeyaay Indians - New DB Value of 338
    • Federated Indians of Graton Rancheria - New DB Value of 339
    • Fort Bidwell Indian Community of the Fort Bidwell Reservation of California - New DB Value of 340
    • Fort Independence Indian Community of Paiute Indians of the Fort Independence Reservation - New DB Value of 341
    • Fort Mojave Indian Tribe (Arizona, California and Nevada) - New DB Value of 342
    • Greenville Rancheria - New DB Value of 343
    • Grindstone Indian Rancheria of Wintun-Wailaki Indians of California - New DB Value of 344
    • Guidiville Rancheria of California - New DB Value of 345
    • Habematolel Pomo of Upper Lake - New DB Value of 346
    • Hoopa Valley Tribe - New DB Value of 347
    • Hopland Band of Pomo Indians - New DB Value of 348
    • Inaja Band of Diegueño Mission Indians of the Inaja and Cosmit Reservation - New DB Value of 349
    • Ione Band of Miwok Indians of California - New DB Value of 350
    • Jackson Band of Miwuk Indians - New DB Value of 351
    • Jamul Indian Village of California - New DB Value of 352
    • Karuk Tribe  - New DB Value of 353
    • Kashia Band of Pomo Indians of the Stewart’s Point Rancheria - New DB Value of 354
    • Koi Nation of Northern California - New DB Value of 355
    • La Jolla Band of Luiseño Indians  - New DB Value of 356
    • La Posta Band of Diegueño Mission Indians of the La Posta Indian Reservation - New DB Value of 357
    • Lone Pine Paiute-Shoshone Tribe - New DB Value of 358
    • Los Coyotes Band of Cahuilla & Cupeno Indians  - New DB Value of 359
    • Lytton Rancheria of California - New DB Value of 360
    • Manchester Band of Pomo Indians of the Manchester Rancheria - New DB Value of 361
    • Manzanita Band of Diegueño Mission Indians of the Manzanita Reservation - New DB Value of 362
    • Mechoopda Indian Tribe of Chico Rancheria - New DB Value of 363
    • Mesa Grande Band of Diegueño Mission Indians of the Mesa Grande Reservation - New DB Value of 364
    • Middletown Rancheria of Pomo Indians of California - New DB Value of 365
    • Mooretown Rancheria of Maidu Indians of California - New DB Value of 366
    • Morongo Band of Cahuilla Mission Indians - New DB Value of 367
    • Navajo - New DB Value of 368
    • Northfork Rancheria of Mono Indians of California - New DB Value of 369
    • Pala Band of Luiseño Mission Indians of the Pala Reservation - New DB Value of 370
    • Paskenta Band of Nomlaki Indians of California - New DB Value of 371
    • Pauma Band of Luiseño Mission Indians of the Pauma & Yuima Reservation - New DB Value of 372
    • Pechanga Band of Luiseño Mission Indians of the Pechanga Reservation - New DB Value of 373
    • Picayune Rancheria of Chukchansi Indians of California - New DB Value of 374
    • Pinoleville Pomo Nation (formerly the Pinoleville Rancheria of Pomo Indians of California) - New DB Value of 375
    • Pit River Tribe (includes XL Ranch, Big Bend, Likely, Lookout, Montgomery Creek and Roaring Creek Rancherias) - New DB Value of 376
    • Potter Valley Tribe (formerly the Potter Valley Rancheria of Pomo Indians of California) - New DB Value of 377
    • Quartz Valley Indian Community of the Quartz Valley Reservation of California - New DB Value of 378
    • Quechan Tribe of the Fort Yuma Indian Reservation (Arizona and California) - New DB Value of 379
    • Ramona Band of Cahuilla - New DB Value of 380
    • Redding Rancheria - New DB Value of 381
    • Redwood Valley or Little River Band of Pomo Indians of the Redwood Valley Rancheria California - New DB Value of 382
    • Resighini Rancheria - New DB Value of 383
    • Rincon Band of Luiseño Mission Indians of the Rincon Reservation - New DB Value of 384
    • Robinson Rancheria - New DB Value of 385
    • Round Valley Indian Tribes, Round Valley Reservation - New DB Value of 386
    • San Manual Band of Serrano Mission Indians of the San Maual Reservation - New DB Value of 387
    • San Pasqual Band of Diegueño Mission Indians of California - New DB Value of 388
    • Santa Rosa Indian Community of the Santa Rosa Rancheria - New DB Value of 389
    • Santa Rosa Band of Cahuilla Indians (formerly the Santa Rosa Band of Cahuilla Mission Indians of the Santa Rosa Reservation) - New DB Value of 390
    • Santa Ynez Band of Chumash Mission Indians of the Santa Ynez Reservation - New DB Value of 391
    • Lipay Nation of Santa Ysabel (Previously listed as the Santa Ysabel Band of Diegueño Mission Indians of the Santa Ysabel Reservation) - New DB Value of 392
    • Scotts Valley Band of Pomo Indians of California - New DB Value of 393
    • Sheep Ranch Rancheria of Me-Wuk Indians - New DB Value of 394 
    • Sherwood Valley Rancheria of Pomo Indians of California - New DB Value of 395
    • Shingle Springs Band of Miwok Indians, Shingle Springs Rancheria (Verona Tract) - New DB Value of 396
    • Sioux - New DB Value of 397
    • Soboba Band of Luiseño Indians - New DB Value of 398
    • Susanville Indian Rancheria - New DB Value of 399
    • Sycuan Band of the Kumeyaay Nation (formerly the Sycuan Band of Diegueno Mission Indians of California) - New DB Value of 401
    • Table Mountain Rancheria of California - New DB Value of 402
    • Tejon Indian Tribe - New DB Value of 403
    • Tolowa Dee-ni' Nation - New DB Value of 404
    • Torres-Martinez Desert Cahuilla Indians - New DB Value of 405
    • Tule River Indian Tribe of the Tule River Reservation - New DB Value of 406
    • Tuolumne Band of Me-Wuk Indians of the Tuolumne Rancheria of California - New DB Value of 407
    • Twenty-Nine Palms Band of Mission Indians of California - New DB Value of 408
    • United Auburn Indian Community of the Auburn Rancheria of California - New DB Value of 409
    • Upper Lake Band of Pomo Indians - New DB Value of 410
    • Utu Utu Gwaitu Paiute Tribe of the Benton Paiute Reservation - New DB Value of 411
    • Washoe Tribe (Carson Colony, Dresslerville Colony, Woodfords Community, Stewart Community and Washoe Ranches) (California and Nevada) - New DB Value of 412
    • Wilton Rancheria - New DB Value of 413
    • Wiyot Tribe (formerly the Table Bluff Reservation-Wiyot Tribe) - New DB Value of 414
    • Yocha Dehe Wintun Nation  - New DB Value of 415
    • Yurok Tribe of the Yurok Reservation - New DB Value of 416
    • Zapotec - New DB Value of 417
    • Other American Indian - New DB Value of 418
    • Other Alaska Native - New DB Value of 419
    • All new American Indians and Alaskan Native ethnicity sub-groups should map back to legacy American Indian / Alaskan Native value of 16.

    Black or African American

    15500
    • African American - Stays as 15
    • Subsaharan African: Ethiopian - New DB Value of 501
    • Subsaharan African: Kenyan - New DB Value of 502
    • Subsaharan African: Nigerian - New DB Value of 503
    • Subsaharan African: Somali - New DB Value of 504
    • Subsaharan African: South African - New DB Value of 505
    • Subsaharan African: Other Subsaharan African - New DB Value of 506
    • West Indian: Belizean - New DB Value of 507
    • West Indian: Haitian -  New DB Value of 508
    • West Indian: Jamaican - New DB Value of 509
    • West Indian: Other West Indian - New DB Value of 510
    • All Black or African American ethnicity subgroups should map back to Black or African American which has a current DB value of 15.

    Native Hawaiian or Other Pacific Islander 


    600

    Pacific Islander: Other20
    • Fijian - New DB Value of 601
    • Other Pacific Islander - Stays as 20

    Pacific Islander: Guamanian17
    • Guamanian or Chamorro - Stays as 17

    Pacific Islander: Hawaiian18
    • Native Hawaiian - Stays as 18

    Pacific Islander: Samoan19
    • Samoan - Stays as 19
    • Tongan - New DB Value of 602

    Middle Eastern or North African


    700
    • Assyrian, Syriac or Chaldean - New DB Value of 701
    • Egyptian - New DB Value of 702
    • Iranian or Persian - New DB Value of 703
    • Iraqi - New DB Value of 704
    • Israeli - New DB Value of 705
    • Jordanian - New DB Value of 706
    • Lebanese - New DB Value of 707
    • Moroccan - New DB Value of 708
    • Palestinian - New DB Value of 709
    • Syrian - New DB Value of 710
    • Turkish - New DB Value of 711
    • Other Middle Eastern - New DB Value of 712
    • Other
    North African - New DB Value of 713
    • North African - New DB Value of 713
    • Middle Eastern or North African is a NEW Race Group value - was not in the legacy section.  Therefore, all responses in this section roll up to "White" = 21
    • All Middle Eastern or North African ethnicity subgroups should map back to DB value of 21.
    White - New DB Value of 80021800
    • Armenian - New DB Value of 801
    • Australian - New DB Value of 802
    • Basque - New DB Value of 803
    • British Isles (UK or Ireland) - New DB Value of 804
    • Canadian - New DB Value of 805
    • European  - New DB Value of 806
    • Russian - New DB Value of 807
    • Ukrainian - New DB Value of 808
    • Other White - New DB Value of 809  
    • All White ethnicity subgroups
    should
    • map back to DB value of 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. Provide colleges with the same data fields and formats they were getting in the original (legacy) implementation.
    2. Provide a new field with all the new race groups and ethnicity/ancestry subcategories collected in the new layout and disaggregation categories.


    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. 


    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 (layout and data) is designed so as to not require colleges to make any changes to their jar file/download client and should be seamlessly backwards compatible. 

    The current database is set up to support 21 specific race groups and race ethnicities. With the addition of more and new race_groups and race_categories, we needed to assign new database values to the new race groups and race ethnicities while maintaining the integrity of the existing race_group and race_ethnicity values.

    The fields "hispanic", "race_group", and "race_ethnic" (Apply)/"race_ethnicity" (Intl) will remain unchanged. We are adding an additional database column called "race_ethnic_full" which will store the values the user selects for both higher level ethnic groups and the associated sub groups presented in the new UI and in the chart above.  From   From a download file perspective, colleges should only have to touch their download files if they want to add the new field <race_ethnic_full>, capturing all the new groups and sub-category values.


    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.

    Detailed Field Notes

    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

    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_ethnic (Apply) / race_ethnicity (International)

    NotesNo changes, this field was intentionally left unchanged

    Example Format: YNYNNNNYNNNNNNNNNYNNN

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

    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)


    College Adaptor Data Element

    For SuperGlue colleges, the new race_ethnic_full data element is called "raceEthnicFull"



    Changes by Section

    SectionFieldOriginal ImplementationOriginal BackendChange to UIChange to Back-End What colleges need to do
    Hispanic / Latino QuestionhispanicYes / No radio buttonsBoolean Y/N or T/F
    (Note - corresponds to (01)
    NoneNoneNothing, No Change
    Race Grouprace_groupPertains only to Hispanic / Latino
    Checkboxes

    Varying length 

    In-Progress Side: Stored the Hispanic/Latino checked values in CSV

    Submitted Side: Stored the raw values in CSV for both the Hispanic/Latino section as well as the Ethnicities section

    Changed to map to the Ethnicity Groups, new optionsNow stores the Ethnic Group data in CSV FormatAccount for the different meaning of the data coming through, also adjust fixed-width delimited download client format as needed
    Race / Ethnicityrace_ethnic (Apply) / race_ethnicity (Intl)Checkboxes

    Varying length 

    In-Progress Side: Stored the Ethnicities section checked values in CSV

    Submitted Side: stored the YNX MIS Reporting format

    UI no longer maps directly to this fieldNow a calculated value that always stores the MIS Reporting format (both in-progress and submitted side)Nothing, No Change
    Race / Ethnicity Fullrace_ethnic_fullN/AN/AAdded new Ethnicity subgroup options, changed to map subgroups to this columnNow stores the values for all subgroups in CSV (combines Hispanic/Latino section and other Ethnicities)New Download Client Column, optional for the colleges if they want to download these values
    Values that weren't a clear a one-to-one map, we had to change





    The only option to keeping the columns the same would be to have implemented ALL 190+ race ethnicities and groups with the same formatting as the odd logic as before (combined use of YN)


    MIS Data Elements 

    MIS Data Element

    MIS Derived Data Element
    SB29 - Multi-EthnicitySTD10 - Student -Ethnicity (Derived Data Element) 
    Used for IPEDs reporting
    View file
    nameSB29 - Multi-Ethnicity.pdf
    height400
    View file
    nameMIS STD10 IPEDS Ethnicity.pdf
    height400



    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:

    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

    XNYNNNNYNNNNNNNNNYNNN

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


    race_ethnic (Apply) / race_ethnicity (International)

    NotesNo changes, this field was intentionally left unchanged

    Example Format: YNYNNNNYNNNNNNNNNYNNN

    Maximum Expected Width: 22 characters (unchanged) (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:

    2018: 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 Group/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

    Maximum Expected Width: 78 characters (unchanged) (20 * 2 character long values +

    6

    18 commas + 18 spaces  + 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”

    No changes made in 2018; 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)


    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:

    commas




    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
    [checkbox] American Indian or Alaska Native
    [checkbox] Black or African American
    [checkbox] Native Hawaiian or Other Pacific Islander
    [checkbox] Middle Eastern or North African
    [checkbox] White

    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.