Converting Recruiting and Admissions and Campus Community Data
This section provides an overview of conversion of recruiting and admissions and campus community data and discusses how to populate tables for recruiting and admissions and campus community data.
You should convert recruiting and admissions data first along with relevant Campus Community data such as personal data—names, addresses, or phone numbers.
It is up to you how much of this data you convert—for instance, how many addresses you convert for one individual—and how much history you take into consideration. Of course, if the student records team is converting 10 years of student records, make sure that there are 10 years of personal data elements in the system.
You should convert up to two years of recruiting and admissions data for your institution. Again, this may vary depending upon your practices and your needs. Regardless of how much history you do convert, it is important that you keep the prospect stacks of data and the Recruiting and Admissions stacks of data consistent. You do not want to end up with a year of recruiting and admissions data without the prospect data for the same year. This also ensures that the data required for institutional research reporting—for instance, cohort reporting and statistical reporting—remains consistent.
Aside from address and other information, there are some tables that are precursors to all application conversions in Campus Solutions. These tables represent the minimum to be converted.
Academic Organization Tables
Populate these tables in this order for academic organizations:
Level and Load and Term and Session Tables
Populate these tables in this order for level and load and term and sessions:
In addition to these tables, you must convert these tables as early in the process as possible in the sequence. Use the name and address load routines delivered with the system, to load data:
DISABILITY: required for PERS_DATA_EFFDT and PERSONAL_DATA to function properly.
DIVERSITY: required for PERS_DATA_EFFDT and PERSONAL_DATA to function properly.
ADDRESSES: to display and convert any address information, including those on PERSONAL_DATA.
GENL_MATERIALS: to track materials already received for applications.