Logo for N.C. Cooperative Extension N.C. Cooperative Extension Homepage

EIT Redistricting Checklist

Things that EIT needs to do when changing Districts:

2012

  • Update the CED email lists –> ** have file to update after 1/1/12
  • Update tables in XEMP (districts, counties, locations). The districts and counties table have been updated and named …_2008. The new tables just need to be named appropriately at the correct time: The following SQL needs to be run on the locations table: update locations, counties set locations.dist_id = counties.district_id where locations.dist_id != 0 and locations.name = concat(counties.county_name, " County")
  • Update tables in other applications (LMS, calendar, others?)

The following databases have counties/districts tables

√ xemp (master table to be updated after jan 1)
√ ncce
√ phoenix
√ xcal
√ xlms
√ xrdb
√ xvacancy

The following SQL was executed against the databases above to make their county tables point to the master xemp county table. When the xemp county table is updated for the new year the others will automatically be updated as well.

  • newton.ncce

create view ncce.counties_latlon_vw as select county_id, ind, county_name, district_id, gateway, latitude, longitude from xemp.counties; rename table ncce.counties_latlon to ncce.counties_latlon_SAVE; rename table ncce.counties_latlon_vw to ncce.counties_latlon;

  • newton.phoenix

create view phoenix.counties_vw as select county_id, ind, county_name, district_id, gateway, latitude, longitude, ‘Y’ as use_new_url from xemp.counties where ind = 0; rename table phoenix.counties to phoenix.counties_SAVE; rename table phoenix.counties_vw to phoenix.counties;

  • newton.xcal

create view xcal.counties_vw as select county_id, county_name, district_id from xemp.counties where ind = 0; rename table xcal.counties to xcal.counties_SAVE; rename table xcal.counties_vw to xcal.counties;

  • newton.xlms

create view xlms.counties_vw as select county_id, county_name, district_id from xemp.counties where ind = 0; rename table xlms.counties to xlms.counties_SAVE; rename table xlms.counties_vw to xlms.counties;

  • newton.xrdb

create view xrdb.counties_vw as select county_id, county_name, district_id from xemp.counties where ind = 0; rename table xrdb.counties to xrdb.counties_SAVE; rename table xrdb.counties_vw to xrdb.counties;

  • newton.xvacancy

create view xvacancy.counties_vw as select county_id, county_name, district_id from xemp.counties where ind = 0; rename table xvacancy.counties to xvacancy.counties_SAVE; rename table xvacancy.counties_vw to xvacancy.counties;


Not sure about changes to ERS — (RK: ERS does not use districts and is unaffected by redistricting.)

Most of these will not cause a problem once we remap counties and change district names as appropriate.
The following paragraph may apply… One potential issue is if we delete district 8 (formerly Southwest) from the database we will need to make sure to update any records (wherever they may be in each db) that reference it. This will require us to analyze the data in each program and come up with the appropriate SQL to fix the problem and/or mark them as “Non-District” and let the changes be performed manually within the program.

  • Update phoenix.counties table. Maybe use xemp.counties?
  • Update XEMP entries for DEDs and AAs
  • Change district web sites
    • DNS changes
    • rewrite rules
  • Update County Centers page
  • Replace District Map with new map (obtained new map from Ext Admin)
  • Farm Income in NC (FINC) program (RK:ANCIENT program – no longer active – no changes needed)
  • Update CES Organizational Chart
  • Update map images on district web pages –> *** copy /loc/htdocs/ncce/map2012map.php over map.php
  • Update descriptive text on district web pages (District AAs should do this)

2008

  • Update the CED email lists
  • Update tables in XEMP (districts, counties, locations). The districts and counties table have been updated and named …_2008. The new tables just need to be named appropriately at the correct time: The following SQL needs to be run on the locations table: update locations, counties set locations.dist_id = counties.district_id where locations.dist_id != 0 and locations.name = concat(counties.county_name, " County")
  • Update tables in other applications (LMS, calendar, others?)

The following databases have counties/districts tables

copubs_import not used
copubs_import_dorner not used
finc
ncce
√phoenix
program_evaluation not used
√ xcal
xemp
√xlms
xlrp not used
√ xrdb
√ xvacancy

Not sure about changes to ERS/POD

Most of these will not cause a problem once we remap counties and change district names as appropriate.

One potential issue is if we delete district 8 (formerly Southwest) from the database we will need to make sure to update any records (wherever they may be in each db) that reference it. This will require us to analyze the data in each program and come up with the appropriate SQL to fix the problem and/or mark them as “Non-District” and let the changes be performed manually within the program.

  • Update phoenix.counties table. Maybe use xemp.counties?
  • Update XEMP entries for DEDs and AAs
  • Change district web sites
    • √ DNS changes
    • √ rewrite rules
  • Update County Centers page
  • Replace District Map with new map (obtained new map from Ext Admin)
  • √ Farm Income in NC (FINC) program
  • Update CES Organizational Chart
  • Update map images on district web pages
  • Update descriptive text on district web pages (District AAs should do this)

This page has value for future changes in districts and should be archived.

Written By

Photo of Rhonda ConlonRhonda ConlonDirector, Extension Information Technology (919) 515-5893 rhonda_conlon@ncsu.eduExtension Information Technology - NC State University
Was the information on this page helpful? Yes check No close