Recruit supports the importing of data unique to your campus, with a few rules.
Data feed ground rules
Data feeds require special handling in order for UC Recruit to properly find the uploaded file and import it into the system.
When UC Recruit encounters an error, an email is sent to the data feed contact(s) at the customer campus. It is critical that the email address(es) on file are monitored by at least one person with the authority and operational responsibility to quickly resolve data errors, as they could lead to a negative impact on the user experience or inhibit full use of UC Recruit for your campus.
UC Recruit applies two passes of validation during data load:
- Valid CSV file: UC Recruit uses a fairly strict definition of CSV taken directly from the RFC. When UC Recruit encounters a CSV file that does not adhere to the RFC definition, the import process is aborted without changing any data and an error report is emailed to the data feed contacts, including the problematic line in the file.
- Valid contents: UC Recruit maintains strict data types and foreign key relationships for all underlying data models. When UC Recruit encounters a CSV file with invalid rows, those rows are skipped; all other valid rows are imported. An email is sent to the data feed contacts with an error message and a reference to the invalid row(s).
File upload sequence
It is important to upload files in order because later files build upon earlier ones—Schools contain Departments, which have many Users, who may have User Roles, etc. Trying to put faculty into a department not yet defined would result in an error, and transferring files in the order listed below will avoid such errors.”
Formatting a data feed SCP destination
UC Recruit accepts data feeds for all environments: QA, Training, and Production. Each data feed’s SCP destination must follow the format for the intended environment as described below.
Each campus has a unique username that you’ll need to form a data feed request; refer to the table below for your campus’s username.
Valid SCP destination values
Using the username from the table above, build the SCP destination for your data feed by choosing the corresponding option from each of the columns below. For example, an SCP destination for a UC Irvine departments CSV data feed to Training would look like: