Blogs

Tips & Tricks: Keeping race/ethnicity changes in sync

By Matt Nuttall posted 06-02-2009 01:45 PM

  

The most recent bundle (CS 12 for v9.0 and CS 19 for v8.9) delivered the first wave of race/ethnicity changes, and with it has come a flurry of conversation on the Campus Community forum regarding the need to keep CS and HCM in sync.  While there will be a similar HCM bundle released this year, there seems to be some consensus on the value of a nightly script to keep everything straight in the interim. We’d like to highlight approaches taken by a couple of the contributors to the conversation.

 

Larry Roux from Syracuse University said they’re using three scripts:

  1. Populates the ETHNICITY_DTL rows for anything in DIVERS_ETHNIC and not in ETHNICITY_DTL
  2. Sets the HISP_LATINO flag for historical records
  3. Sets the ETHNIC_PCT_DENMRTR = 100 for historical records

And, Meg Fryling from the University at Albany has passed along the SQL they're using.

 

Background:

Campus Solutions support for the new IPEDS Ethnicity Data Collection and Reporting is being released in three phases.
 
Phase 1:  The Administrative pages updates and the TS189 updates are covered in the April bundle doc (links provided in email below - thanks, Debbie!)
Phase 2:  Updates for the self-service data collection are targeted for the June 2009 bundle.
Phase 3:  Updates for producing the content for the IPEDS reports is targeted for the second half of 2009.

 
0 comments
10 views

Permalink