Introduction
In order to build and send out candidate itineraries for a given Interview Weekend, data about various topics must first be uploaded, one of them being Events. This is done via uploading a properly formatted CSV file containing details about the events and who should attend.
File Upload Template (with Header Row): events.csv
| NOTE: The uploaded file needs to follow a very specific format (as specified below). It is required that there be a header row. Each row after will be assumed to contain all the necessary information for each event. Once uploaded, the file will be checked for compliance to this format; if any errors are found, the entire upload is cancelled -- the errors must be corrected in the CSV file, and the file re-uploaded. Once there are no errors, the file will be accepted by the system and its contents recorded in the database. |
Instructions
Required Format (with examples):
|
EVENT_TYPE |
CANDIDATE_UMID |
DEP-INT |
DESCRIPTION |
LOCATION |
PHONE |
DATE |
START_TIME |
END_TIME |
DELETE_RECORD |
|---|---|---|---|---|---|---|---|---|---|
|
Individual |
12345678 |
|
Description goes here |
2955 Taubman Health Science Library |
(123) 456-7890 |
2/5/2018 |
8:00PM |
9:00PM |
|
|
Dep-Int |
|
Bioinformatics |
Description goes here |
Research Auditorium, Med Sci II |
|
2/6/2018 |
9:00AM |
10:00AM |
|
|
PIBS |
|
|
Description goes here |
Cafeteria, NCRC |
|
2/6/2018 |
11:00AM |
1:00PM |
delete |
Notes about uploading, changing, and deleting:
- Uploads can contain as many or as few rows as desired; once uploaded, the information will stay in the database (i.e. the CSV file you uploaded does not need to be preserved).
- More events can be added to the weekend by either creating and uploading a new list, or adding the new events to your previously uploaded CSV file and reuploading.
- When an event is already found in the database, the system will do one of two things:
- if the location, phone, description, and end time are the same, it will skip this row
- if the location, phone, description, or end time are different, it will replace the event with the new values from the file
- An existing record (identified by the event type, candidate UMID, department/interest, date, and start time) can be deleted by typing 'delete' in the Delete_Record column for that row in your spreadsheet and uploading the file.
- If you do not have an existing CSV file with the record you want to delete, you must first recreate the file with the record identified by the event type, candidate UMID, department/interest, date, and start time.
Field Definitions
|
Name |
Length |
Rule |
Notes |
|---|---|---|---|
|
EVENT_TYPE |
10 |
Required |
Acceptable values: 'Individual', 'PIBS', or 'Dep-Int' |
|
CANDIDATE_UMID |
8 |
Required (if Individual type) |
8 digit UMID/Emplid; only necessary for Individual events. |
|
DEP-INT |
50 |
Required (if Dep-Int type) |
Must exactly match the departments/interests entered during Season setup; only necessary for Dep-Int events. |
|
DESCRIPTION |
100 |
Required |
Describe the event in a few words (~20 or fewer). |
|
LOCATION |
100 |
Optional |
Be specific, such as Building and Room Number. Remember that acronyms or slang terms for buildings may not be understandable to candidates. |
|
PHONE |
14 |
Optional |
Format: flexible (hyphens, dots, or spaces are allowed) |
|
DATE |
14 |
Required |
Format: MM/DD/YYYY (allows single digit day and month and two digit year) |
|
START_TIME |
14 |
Required |
Format: HH:MMPM |
|
END_TIME |
14 |
Required |
Format: HH:MMPM |
|
DELETE_RECORD |
6 |
Optional |
Must be used in conjunction with an existing record, identified by event type, candidate UMID, department/interest, date, and start time. |