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 |
Steering Hearing Date | TBD |
Proposed Change to Download File | See Notes |
Proposed Change to Residency Logic | N/A |
Info |
---|
This is an approved 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. See Change Request 2018-18: Expand Race & Ethnicity Section with New Categories |
Table of Contents |
---|
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 is 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
View file | ||||
---|---|---|---|---|
|
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 | ||
---|---|---|
| ||
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. |
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)
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
Proposed Solution
Update the Race & Ethnicity section of the Demographic Information page to include a new section and revise the 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.
View file | ||||
---|---|---|---|---|
|
Zoom Demo
Info | ||
---|---|---|
| ||
New Race & Ethnicity Changes - User Interface Demo Zoom recording 09.14.18: https://cccconfer.zoom.us/recording/play/rJbSJXM0v3OcWtJaPncPnvSBB1LB7J_dxsSBF7JoEj4OdMLGWgT8hXWidv_LNxSz?continueMode=true |
NEW Layout Screenshots
New Hispanic Question & Race Groups Collapsed
New Hispanic Question & Race Groups - Auto-populated
New Hispanic Question Expanded
New Groups Expanded
More Groups Expanded
Requirements for New Design and Functionality
Section 1 Requirements - Hispanic/Latino Section
- The first section should ask the following question: "Are you Hispanic or Latino?"
- If user clicks on the checkbox, then the box next to Hispanic or Latino should become automatically checked and the subgroup list expands and becomes visible to display 19 subcategories (race_ethnicity).
- If user does not click on the checkbox, then the box next to Hispanic or Latino should not systematically expand and the user should not see the 19 subcategories race_ethnicity).
Race Group (race_group) | Current Value / Mapping | NEW Associated Subgroup (race_ethnicity) | Notes | |||||
---|---|---|---|---|---|---|---|---|
Hispanic or Latino - New DB Value of 100 | 01 | 100 = New DB Value
| Hispanic, Latino - (From ‘Are you Hispanic / Latino?’ Check the box to open the sub-ethnicities 10.12.18: Per Craig Hayward, Bakersfield College - Brazil is intentionally omitted from this implementation. | |||||
Mexican, Mexican-American, Chicano | 02 |
| ||||||
Central American | 03 |
| ||||||
South American | 04 |
| 10.12.18: Per Craig Hayward, Brazil is not included on purpose. | |||||
Hispanic, Other | 05 |
|
Section 2 Requirements
- The following instructions should fall below the Hispanic/Latino Section.
- 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 and then click on the button that says "Continue".
- The system should then show the following ethnic groups with a checkbox next to each group:
- Asian
American Indian or Alaska Native
- Black or African American
- Native Hawaiian or Other Pacific Islander
- Middle Eastern or North African
- White
- Applicants who select one or more of the Ethnic Groups should then see the subset of more detailed associated subgroups. Multiethnic applicants are able to select as many ethnic groups and ethnic 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.
- The following table shows a breakdown of the subgroups tied to each ethnic group, as well as the DB value associated in parenthesis.
Ethnic Group (race_group) | Current Value / Mapping | NeW Associated Subgroup (race_ethnicity) | Notes |
---|---|---|---|
Asian | 200 - - New DB Value of 200 | ||
Asian: Indian | 06 |
| Note: All responses from this group will map back to the original 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 |
| |
American Indian or Alaska Native | 300 -- New DB Value of 300 | ||
NOTE: All the new American Indian / Alaskan Native responses will map back to original DB value "16" | 16 |
| NOTE: All new American Indian / Alaskan Native responses will map back to original DB value "16" |
Black or African American | 15 | 500 -- New DB Value of 500 | |
Note: All of these responses will map back to the original value for Black or AfricanAmerican = 15 | 15 |
| Note: All of these responses will map back to the original value for Black or AfricanAmerican = 15 |
Native Hawaiian or Other Pacific Islander | 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 | 700 - - New DB Value of 700 | ||
Note: All of these new responses will map to the original value for White = 21 | 21 |
| Note: All of these new responses will map to the original value for White = 21 |
White | 800 - - New DB Value of 800 | ||
Note: All of these new responses will map to the original value for White = 21 | 21 |
| Note: All of these new responses will map to the original value for White = 21 |
In Progress Applications
There will be no database value mappings for In Progress applications. 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 To Colleges (Updated Oct. 25th 2018)
Backwards Compatibility
If a user has added Race/Ethnicity data on their in-progress application before this update goes live, then the system attempts to map it to data in the new set. However, if the user has un-mappable choices (such as the old "South American" choice now being split out among many individual countries), then the user will receive a validation message upon attempting to submit the application that will direct them back to the Demographic Page to update their Race/Ethnicity choices. This should be fairly seamless to the colleges and should cause no backwards compatibility issues.
New Data Formats
Colleges should be able to continue using their old format file with no issues; however, 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 Ethnic Group values, so that will store values such as "100,200,300,500,600,700,800".
The actual data stored in these fields is changing as follows:
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: race_group now stores only the Ethnic Group mappings as CSV content with no spaces, as opposed to the old format which was 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 they do need to remove the spaces between the values - which is consistent with other CSV formats)
race_ethnic (Apply) / race_ethnicity (International)
Notes: No changes, this field was intentionally left unchanged
Example Format: YNYNNNNYNNNNNNNNNYNNN
Maximum Expected Width: 22 characters (22 character long string)
race_ethnic_full
Notes: race_ethnic_full in a new field that will store the CSV separated values of the subgroups. 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)
Articulating Changes by Section
(Note - corresponds to (01)
Checkboxes
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)
Duplicate use of values
Storing the YNX block (YNNNNYN)
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
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
But the individual
Release Information To Colleges
- The system does not store names; maps to numerical values. DB is a text field which has unlimited length. When we store the choice user makes, we save code value - no names are stored.
- Colleges will need to absorb the new options and replace their DLC jar file for the categories added to the response options for the Race & Ethnicity download field(s).
- No changes are needed to the Download client from Unicon's side. Colleges will need to adjust their format file. If a college is using a fix width columns, they may need to adjust based on a student selecting multiple groups and ethnicities.
3 Existing Fields =
Hispanic
race_group (repurposed - no commas)
CCCApply: race_ethnic (giving the college this same field) still has the MIS format - no change
IA: race_ethnicity (now)
IA: race_ethnic_full (future)
NEW full version - Adding - race_ethnic_full (the new format)
Backwards Compatibility
If a user has added Race/Ethnicity data on their in-progress application before this update goes live, then those users will receive a validation message upon attempting to submit that will force them to return to the Demographic Page and update their choices. The end user will not be able to submit their application until they have returned to the Demographic Page and saved their updated data. For the colleges, this means there will be a sharp divide between old and new data, and they should not encounter a time when they can expect to receive both formats. So once this update is deployed, then they can immediately switch to whatever process they put into place to accept the new data into their systems.
New Data Formats
From a download client perspective, colleges using a fixed-width output will need to update their format file for the possible output of the new Race Ethnicity selections, and the new usages of the race_group and race_ethnicity fields.
'race_group' used to store the Hispanic Race Group choices, but it would store them in a comma delimited format with the values, such as "02, 03, 04". 'race_ethnicity' stored the chosen values of both the Hispanic and the original Race Ethnicity in a block of values such as "XNNNNNYYYYNN..." with each character denoting the individual checked or unchecked answer in series.
Now, race_group is being re-purposed to store the value of the "super groups" such as Asian, American Indian or Alaska Native etc., and race_ethnicity is storing the values for the "sub groups" of these choices. Colleges will need to be aware of these new uses and adjust how they process this data into the final destination for these submitted applications.
If a college is using a delimited output for their format file, then they should not need to change their format file. While there will be a greater number of values the user can choose, since it is a delimited output it will simply print the values out as it always has between the chosen delimiter.
If the college is using a fixed width output, they will need to adjust their format file to compensate for the new number of values that can possibly be output.
race_group has up to 8 values a user can choose, and is output as "100, 200, 300...(etc.)". The colleges will need to adjust their fixed width output to accept 36 characters for the race_group field (8 values * 3 characters per value + 6 commas + 6 spaces = 36 characters)
race_ethnicity has up to 194 values the user can choose, and is output as "101, 102, 103, 201, 202, 306...(etc.)".
The colleges will need to adjust their fixed width output to accept 966 characters for the race_ethnicity field (194 values * 3 characters each + 192 commas + 192 spaces = 966 characters)
Updated Data Dictionary Elements & Data Field Information
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
Release Information To Colleges (Updated Oct. 25th 2018)
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.
New Data Formats
Colleges should be able to continue using their old format file with no issues; however, 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 Ethnic Group values, so that will store values such as "100,200,300,500,600,700,800".
The actual data stored in these fields is changing as follows:
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)
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
Notes: race_group now stores only the Ethnic Group mappings as CSV content with no spaces, as opposed to the old format which was 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 they do need to remove the spaces between the values - which is consistent with other CSV formats)
race_ethnic (Apply) / race_ethnicity (International)
Notes: No changes, this field was intentionally left unchanged
Example Format: YNYNNNNYNNNNNNNNNYNNN
Maximum Expected Width: 22 characters (22 character long string)
race_ethnic_full
Notes: race_ethnic_full in a new field that will store the CSV separated values of the subgroups. 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)
Articulating Changes by Section
Section | Field | Original Implementation | Original Backend | Change to UI | Change to Back-End | 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 | Pertains only to Hispanic / Latino Checkboxes | Varying length Storing actual value | Changed to map to the Ethnicity Groups rather than just the Hispanic/Latino options | Now stores the Ethnic Group data in CSV Format | Account for the different meaning of the data coming through, also adjust fixed-width delimited download client format as needed |
race_ethnic | 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) | Added additional options in checkboxes as subgroups | Stores the YNNNYNNYN... format | Nothing, No Change | ||
Race / Ethnicity | race_ethnic | Checkbox | Duplicate use of values Storing the YNX block (YNNNNYN) | |||
Race / Ethnicity Full | race_ethnic_full | N/A | N/A | Maps from the same checkboxes as the race_ethnic field | Stores the raw value for each of the Ethnic Subgroups selected on the page | New Download Client Column, optional for the colleges if they want to download these fields |
Values that weren't a clear 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 screwed up logic as before (combined use of YN) | ||||||
NOTE: If the college does nothing - they don't update their Download Format file (XML) then: 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 But the individual | ||||||
Release Information To Colleges
- The system does not store names; maps to numerical values. DB is a text field which has unlimited length. When we store the choice user makes, we save code value - no names are stored.
- Colleges will need to absorb the new options and replace their DLC jar file for the categories added to the response options for the Race & Ethnicity download field(s).
- No changes are needed to the Download client from Unicon's side. Colleges will need to adjust their format file. If a college is using a fix width columns, they may need to adjust based on a student selecting multiple groups and ethnicities.
3 Existing Fields =
Hispanic
race_group (repurposed - no commas)
CCCApply: race_ethnic (giving the college this same field) still has the MIS format - no change
IA: race_ethnicity (now)
IA: race_ethnic_full (future)
NEW full version - Adding - race_ethnic_full (the new format)
Backwards Compatibility
If a user has added Race/Ethnicity data on their in-progress application before this update goes live, then those users will receive a validation message upon attempting to submit that will force them to return to the Demographic Page and update their choices. The end user will not be able to submit their application until they have returned to the Demographic Page and saved their updated data. For the colleges, this means there will be a sharp divide between old and new data, and they should not encounter a time when they can expect to receive both formats. So once this update is deployed, then they can immediately switch to whatever process they put into place to accept the new data into their systems.
New Data Formats
From a download client perspective, colleges using a fixed-width output will need to update their format file for the possible output of the new Race Ethnicity selections, and the new usages of the race_group and race_ethnicity fields.
'race_group' used to store the Hispanic Race Group choices, but it would store them in a comma delimited format with the values, such as "02, 03, 04". 'race_ethnicity' stored the chosen values of both the Hispanic and the original Race Ethnicity in a block of values such as "XNNNNNYYYYNN..." with each character denoting the individual checked or unchecked answer in series.
Now, race_group is being re-purposed to store the value of the "super groups" such as Asian, American Indian or Alaska Native etc., and race_ethnicity is storing the values for the "sub groups" of these choices. Colleges will need to be aware of these new uses and adjust how they process this data into the final destination for these submitted applications.
If a college is using a delimited output for their format file, then they should not need to change their format file. While there will be a greater number of values the user can choose, since it is a delimited output it will simply print the values out as it always has between the chosen delimiter.
If the college is using a fixed width output, they will need to adjust their format file to compensate for the new number of values that can possibly be output.
race_group has up to 8 values a user can choose, and is output as "100, 200, 300...(etc.)". The colleges will need to adjust their fixed width output to accept 36 characters for the race_group field (8 values * 3 characters per value + 6 commas + 6 spaces = 36 characters)
race_ethnicity has up to 194 values the user can choose, and is output as "101, 102, 103, 201, 202, 306...(etc.)".
The colleges will need to adjust their fixed width output to accept 966 characters for the race_ethnicity field (194 values * 3 characters each + 192 commas + 192 spaces = 966 characters)
Updated Data Dictionary Elements & Data Field Information
Expand below to see the OLD and the NEW Data Dictionary data field tables for Race & Ethnicity Section. (before 6.3.0)
Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Race/Ethnicity
Hispanic/Latino
Race Group
This field has been "re-purposed" in the new implementation. All ethnic groups are optional
|
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
- The following instructions should fall below the Hispanic/Latino Section and above the next set of race/ethnicity sections:
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.
- The UI should display the following ethnic groups with a disabled checkbox next to each group:
- Asian
- American Indian or Alaska Native
- Black or African American
- Native Hawaiian or Other Pacific Islander
- Middle Eastern or North African
- White
- Applicants who select one or more of the Ethnic Groups should then see the subset of more detailed associated subgroups (race_ethnicity).
- When a race_group option is checked/selected, the system should reveal/display the associated subgroups (race_ethnicity). Users should have the ability to select as many race_groups and race_ethnicities options as applicable.
- When an option is unchecked/deselected, the race_group expansion should roll up/no longer show the subgroups (race_ethnicity).
- Multiethnic applicants should be able to choose as many ethnic groups and ethnic subgroups as needed.
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
- Postman can be used to get database values.
- The UI can be used for testing.