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

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

Additional Information:  https://www.diffen.com/difference/Ethnicity_vs_Race

Supporting Documentation

Ethnicity/Ancestry Expansion Proposal

Ethnicity-Ancestry Expansion Proposal Digest-Draft v 1.4.docx

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:

Current Race/Ethnicity 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.

CCCApply Application Today

(Before new Race & Ethnicity implementation - 6.3.0)

Image Added

International Application Today

(before new Race & Ethnicity implementation - 6.3.0)

Image Added

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

Proposed Solution

Update the Race & Ethnicity section of the Demographic Information page to include a revised layout and conditional formatting functionality to hide certain sub-categories until a student selects the high level category.  

Note: If a new category is added to the response options for the Race & Ethnicity download field(s), colleges will be required to implement the changes to absorb the new options and replace their DLC jar file.

General  Requirements

• Requirements below apply to both the Apply and international applications.
• Data Dictionary for both Apply and International applications should be updated to reflect new Database values and mappings.
• No changes to the current DB size limit.

Functional Mock Up for New Design and Functionality

Attached is a functional excel mockup for how this new layout and functionality should be in both the CCCApply and International Application.

Zoom Demo 

NEW Layout Screenshots

New Hispanic Question & Race Groups Collapsed

Image Added

New Hispanic Question & Race Groups - Auto-populated

Image Added

New Hispanic Question Expanded

Image Added

New Groups Expanded

Image Added

More Groups Expanded

Image Added

Specifications for New Layout Design and Database Values

Section 1: Hispanic/Latino Section

Similar to the current version, the new Race & Ethnicity implementation layout has two sections: 1) The 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. 

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> 

Hispanic/Latino Database Values

Section 2: Race Groups & Ethnicities

Below the Hispanic/Latino section, the following instructive text is displayed and a set of high-level Race Groups with checkboxes are displayed. 

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

New Data Formats & Downloads

The new Race & Ethnicity implementation requires some changes to your existing download file in order to collect the new race groups and ethnicity values, but still maintain a format that is as close to the output you are getting now for MIS reporting purposes. 

New "Race & Ethnicity Full" Data Field

A new data field has been added to the database that is dedicated specifically to the new Race & Ethnicity responses, added in this implementation.

Colleges that want to collect these new values should add this new field to their CCCApply Format Definition XML file: <race_ethnic_full>.

Adjustments to Existing Download Files

From a download file perspective, colleges using a fixed-width output now will need to update their Format Definition files for the output of the repurposed fields.

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.

The actual data stored in these fields is changing as follows:

Hispanic/Latino

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

Field: race_group

Notes:  'race_group' used to store 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, 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").  

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

Field:  race_ethnic (Apply) / race_ethnicity (International)

Notes: No changes, this field was intentionally left unchanged. Null is allowed.

Example Format: YNYNNNNYNNNNNNNNNYNNN

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

NEW! Race Ethnicity Full

Field:  race_ethnic_full

Notes: New field added to capture all new race groups and ethnicities in 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

Release Information for Colleges

The new Race & Ethnicity Disaggregation implementation is a revision to the existing, highly regulated Race & Ethnicity section in CCCApply which is protected by federal law, the Office of Civil Rights, and aligns to MIS reporting requirements (SB29). The new implementation will be in place before the MIS requirements are updated in Fall 2019.  Our goal for this roll-out is twofold:

1) implement the new layout and data format changes, including new high-level race groups and extensive, corresponding ethnicity values (race_ethnic_full), so that researchers can start collecting and benefiting from this data; and

2) while still providing colleges with legacy data formats so that colleges can continue to get the format required for MIS reporting (race_ethnic). Colleges that want to collect the new data values must add the new data field to their Format XML files and update the Download Client with the v.6.3.0 jar file.

In-Progress Applications

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

For In-Progress applications, there will be no database value mappings. If an application is in-progress and a student selected a race/ethnicity and their choice is in the list of obsolete values post the release, we should display a server side validation error message during the pre-submission validation 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 need to store the new value.

Release Information for Colleges

The new Race & Ethnicity Disaggregation implementation is a revision to the existing, highly regulated Race & Ethnicity section in CCCApply which is protected by federal law, the Office of Civil Rights, and aligns to MIS reporting requirements (SB29). The new implementation will be in place before the MIS requirements are updated in Fall 2019.  Our goal for this roll-out is twofold:

1) implement the new layout and data format changes in a new, additional field (race_ethnic_full), which includes all the new high-level race groups and associated ethnicity values being implemented for research purposes; and

2) Continue to provide colleges with the legacy data formats required for MIS reporting (race_ethnic). 

Colleges that want to collect the new data values must add the new data field to their Format XML files and update the Download Client with the v.6.3.0 jar file.

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.

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

Adjustments to Existing Download Files

From a download file perspective, colleges using a fixed-width output now will need to update their Format Definition files for the output of the repurposed fields.

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.

The actual data stored in these fields is changing as follows:

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)

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:
hispanic will give them the same as getting now. 

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 SB29 - Multi-Ethnicity

Updated Data Dictionary Elements

Expand below to see the OLD and the NEW Data Dictionary data field tables for Race & Ethnicity Section. (before 6.3.0)

Race/Ethnicity

Data Element:

race_ethnic

Description:

Combination of all responses to Ethnicity and Race questions

Format, Length:

bpchar, 21

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:

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. The race subcategories such as 'Asian: Chinese' and 'Pacific Islander: Hawaiian' are defined by MIS at the Chancellor's Office (data element SB29).

personal_info table

Xap Field:

raceEthnicity

Revision Log:

~~

Char

Race/Ethnicity

Values

1

Hispanic, Latino

From ‘Are you Hispanic / Latino?’ drop-down menu selection:

‘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

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

. 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

MIS SB29 - Multi-Ethnicity

Updated Data Dictionary Tables

Hispanic/Latino

Old: This element and ‘race_group’ are used to derive ‘race_ethnic’, which is used for MIS reporting.

Also used for part of personal_info: race_ethnic, which correlates to MIS SB29.

Race/Ethnicity

Database currently has ‘text, 2147483647’

Values:

String of codes indicating all checkboxes that are checked, delimited by comma and space between each code. Codes are:

This field has been "re-purposed" in the new implementation. 
The Race Group identifies the high-level ethnic groups displayed onscreen 

All ethnic groups are optional

02  = Mexican, Mexican-American, Chicano

03  = Central American

04  = South American

05  = Hispanic Other

06  = Asian Indian

07  = Asian Chinese

08  = Asian Japanese

09  = Asian Korean

10  = Asian Laotian

11  = Asian Cambodian

Allows Null:

No

Default:

None

Usage:

This element and ‘hispanic’ are used to derive ‘race_ethnic’, which is used for MIS reporting.

Notes:

This field has been "re-purposed" in the new implementation. 
The Race Group identifies the high-level ethnic groups displayed onscreen 

All ethnic groups are optional

Xap Field:

raceGroup

Revision Log:

~~

Question Text:

What is your race? Check one or more:

[checkbox] Asian: Indian [checkbox] Asian: Chinese [checkbox] Asian: Japanese [checkbox] Asian: Korean [checkbox] Asian: Laotian [checkbox] Asian: Cambodian [checkbox] Asian: Vietnamese [checkbox] Asian: Filipino [checkbox] Asian: Other

[checkbox] Black or African American [checkbox] American Indian / Alaskan Native

[checkbox] Pacific Islander: Guamanian [checkbox] Pacific Islander: Hawaiian [checkbox]

Pacific Islander: Samoan [checkbox] Pacific Islander: Other [checkbox]  White

Conditions:

Always

Additional Text:

Asian -- A person having origins in any of the original peoples of the Far East, Southeast Asia, or the Indian Subcontinent.

Black or African American -- A person having origins in any of the black racial groups of Africa.

American Indian / Alaskan Native -- A person having origins in any of the original peoples of North and South America (including Central America) who maintains cultural identification through tribal affiliation or community attachment.

Pacific Islander -- A person having origins in any of the original peoples of Hawaii, Guam, Samoa, or other Pacific Islands.

White -- A person having origins in any of the original peoples of Europe, the Middle East, or North Africa.

Response Options:

Any combination of checkboxes can be checked, from none to all.

Pop-Up Help:

Field Error Check:

None

Page Error Check:

None; optional response per IPEDS and CCCCO.

Notes:

See note for Hispanic/Latino (previous table).

Data Element:

personal_info:  race_group

Also used for part of personal_info: race_ethnic, which correlates to MIS SB29

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.

Request

• This is a high-priority change request coming from the Chancellor's Office to revise, expand, and add conditional formatting to the Race & Ethnicity section in both CCCApply and the International Application.
• We have a challenge 
• Business requirements can be found here: https://cccnext.jira.com/wiki/spaces/OPENAPPLY/pages/692486171. The developer should be implementing off these requirements.
• The change request form can be found here: https://cccnext.jira.com/wiki/spaces/PD/pages/731381767/2018-18R+Race+Ethnicity+Section+-+Expand+With+New+Options+and+Conditional+Formatting

Requirements
UI Requirements - Design and Functionality

• Re-design the Race/Ethnicity section of the Apply and International application to match the Functional Mockup. The mockup that has been provided is meant to convey the general idea of what the UI could look like. The design does not have to match exactly as the mockup. The UI designer has the liberty to redesign as long as the core functional requirements are covered. The functional requirement should include the following:

Hispanic/Latino Section

• The following text must be present and in place as it is today: "Per U.S. Department of Education guidelines, colleges are required to collect this racial and ethnic data."
• The first section should ask the following question: "Are you Hispanic or Latino?"
• Change the Hispanic checkbox to a Yes/No/Clearable input so that we can allow the user to input a Null choice for that field.

Other Race/Ethnicity Section

Race Group

Database Values and In Progress Application Mapping Requirements
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 need 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.

• Add and assign the new race_groups, race_ethnicities and database values based on the breakdown here: https://cccnext.jira.com/wiki/spaces/OPENAPPLY/pages/692486171/Race+Ethnicity+Section+-+Expand+With+New+Options+and+Conditional+Formatting
• For In Progress applications In Progress Applications, there will be no database value mappings. If an application is in-progress and a student selected a race/ethnicity and their choice is in the list of obsolete values post the release, we should display a server side validation error message during the pre-submission validation 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 need to store the new value.

Database Storage Scheme and Column Name Requirements

• Change the database storage scheme so values are saved with no spaces between the CSV Values (e.g. save values as “100,200,300…” for race_group and “101,102,301,302…” for race_ethnic_full).
• Change the DB column name of race_ethnicity_full to race_ethnic_full so that it is consistent with the naming of the other race_ethnic column that will be used for the MIS Reporting format.

Additional Requirements as of Sept 27, 2018

• Add metadata to the new race_group and race_ethnicity that will map/aligns to the old (current) race/ethnicities. Approved mappings are documented here: https://cccnext.jira.com/wiki/spaces/OPENAPPLY/pages/692486171
• Store the mapped record and exact format that is in place today so that colleges don't have to adjust their jar file and so that MIS can still get the format that is in place today.
• Add a new DL client field(s) with all the new race_group and race_ethnicity fields so the colleges could utilize this if they wanted.

Testing Approach

Race & Ethnicity Full