There are strict requirements to import events into 25Live using the events.csv service. Please ensure that your CSV file meets all the requirements below.
Consider using the following attachments as a starting or reference point for creating a properly formatted CSV file:
The Excel template is formatted as text to avoid issues with automatic date/time formatting. Be sure to save it in .csv format before uploading.
Warning: Check Your Date Format
When opening the CSV file in Microsoft Excel, it is likely that the date and time columns will be automatically converted to a different format. If that is the case, please updated the format to YYYY-MM-DD and HH:MM:SS format as described below before saving your changes.
- All data column headers found in the attached template must be included, with no omissions or change in order.
- Enter your data with one row per event with its own EVENT_ID, unless the event has multiple segments (also known as "profiles" or "meeting patterns").
- Each profile needs its own row with the same EVENT_ID and a different PROFILE_ID.
- All values must be in text format between the commas which separate the columns. If you need to use a comma in the data itself (such as part of an event description), you may surround the text with double quotes.
- Some columns (marked in bold) are required. You may omit data in any other column by not putting anything between the commas.
Example: 34621,2022 Commencement Address,,,,Ceremony...
- Some columns (such as categories and locations) allow multiple values. These must be separated with the vertical bar character ("|"). You may not use a vertical bar as part of an event name or any other data.
Example: Academic|Calendar|Open to the Public
- Location sharing is supported by specifying
:sharedafter the location name (no spaces around the colon)
- Some columns (such as event type, categories, and locations) must match 25Live data. Spelling must be an exact match. (It is not case-sensitive.)
- Start and end time may be on different dates (for events that span midnight) but may not be separated by more than 24 hours.
- Unless otherwise noted, text fields don't have character limits.
- Required date format is YYYY-MM-DD, e.g. 2021-01-18
- Required time format is HH:MM:SS in 24-hour time, e.g. 14:30:00
- Beware of "helpful" automatic date/time formatting in applications like Excel. Format columns as plain text to ensure you are using YYYY-MM-DD and HH:MM:SS.
Click below to see an example that contains two events, each with two segments.
Working With Spreadsheets (Excel)
You can use Microsoft Excel or a similar application to read and write CSV files. Click File > Save as... and choose a CSV extension when saving your work.
Be careful when you do this, as some applications (especially Excel) may not convert the file format in ways you expect. After you save, open your CSV file in a plain text editor to make sure it looks okay.
Some things to look out for:
- Make sure that the date and time are written in the correct format.
- Make sure that double quotes have not been added or removed unexpectedly.
Previous Template Versions
The original version of the import process only allowed events to have a single segment. The current version (with the template linked above) supports events with multiple segments, but has additional columns that are not found in the original.
If you previously downloaded the original template then uploading CSV files in that format is still supported, but we recommend you begin using the new template as soon as possible.
Data Column Headers
- Fields marked in BOLD are required.
- Multiples Allowed - Multiple data elements may be uploaded at once. Each data element must be separated by a vertical bar (|).
- Must Match - The data in this field must match existing 25Live data.
Unique identifier of the event. If the imported event has an ID you can enter it here and it will be used in 25Live as an alien event identifier. The Event ID will be given a "CSV-" prefix to indicate the source of the imported event, and to guarantee uniqueness in 25Live.
If you use an ID value that already exists for an event in 25Live, the import will overwrite that event rather than creating a new one.
Imported value: ID-23441A
25Live ALIEN UID value:
|EVENT_NAME||Short name of the event (40 character limit).||Sailing Lesson - Level IV|
|EVENT_TITLE||Long name of the event (120 character limit per database and testing).||Sailing Lesson IV: USCG Master Inland / Mate Near Coastal|
|DESCRIPTION||Description of the event. The description is most commonly displayed on public calendars and accepts HTML & CSS.||Learn the ins and outs of inland and coastal cruising with the Jonas Grumby Skipper (aka the Skipper from Gilligan's Island)|
|INTERNAL_NOTES||Internal communication between schedulers; not meant to be read by outside parties.||Last time these lessons happened, Jonas had a bit of trouble navigating. Let's make sure we assign a GPS Resource and that Jonas has this on the boat prior to leaving.|
|EVENT_TYPE||Type of event. See Event Types in 25Live||X|
Academic event type: Section
Special Events event type: Meeting
Any department, campus group, community organization, or other entity that uses 25Live for scheduling or event planning, or that sponsors campus events. This field is used to route imported events to the correct folder in your 25Live event structure.
PRIMARY_ORGANIZATION value must be the 25Live Organization Name.
The PRIMARY_ORGANIZATION becomes a required import data field if the 25Live Cabinet-Folder event structure has multiple folders (for example, a "Special Events" Cabinet with "Administrative Events," "External Events," and "Student Events" folders, and the 25Live Organizations are attached to specific folders).
|REG_HEADCOUNT||Number of attendees registered for the event. This is most commonly used for academic courses.||7|
|EXP_HEADCOUNT||Number of expected attendees for the event.||30|
|CATEGORIES||Event groupings that apply to the event. Categories allow for easy searching and grouping of events.||X||X||Academic|Calendar|Open to the Public|
|INSTRUCTOR||Email address of the instructor of the event. Most commonly, events with an instructor are being imported from an SIS.||Xfirstname.lastname@example.org|
|SCHEDULER||Email address of the person scheduling the event. To match, there must be a 25Live contact with (at minimum) last name and same email address.||Xemail@example.com|
|REQUESTOR||Email address of the person requesting the event. To match, there must be a 25Live contact with (at minimum) last name and same email address.||Xfirstname.lastname@example.org|
Unique identifier of the event profile (aka "segment"). Each event has at least one segment in 25Live.
To create an event with multiple segments, use a separate row for each segment with its own PROFILE_ID and the same EVENT_ID.
This may not match any other PROFILE_ID in the 25Live database.
|PROFILE_NAME||Short name for the segment (40 character limit). If this is not specified, the event ID is used.||Welcome Speech, Breakfast, Registration Table|
First date the event takes place. Use YYYY-MM-DD format.
If importing events with ad hoc dates, this field is NOT required and should not be used. Events with only a single occurrence (ie, final exams) should be treated as ad hoc.
|PRE_EVENT_TIME||Time prior to the event. This time is often used to gather attendees or to set expectations for the event. Must be entered as an integer representing minutes (for example 90 for 1.5 hours).||90|
|START_TIME||Time when the event starts. Use HH:MM:SS in 24-hour format.|
For 8 am: 08:00:00
For 8 pm: 20:00:00
Time when the event ends. Use HH:MM:SS in 24-hour format.
Note: If the END_TIME is before the START_TIME we assume that the END_DATE occurs on the next calendar date, i.e. the event spans midnight.
For 11 am: 11:00:00
For 11 pm: 23:00:00
|POST_EVENT_TIME||Time after the event. This time is often used to clean up or to allow attendees to comfortably exit. Must be entered as an integer representing minutes (for example, 90 for 1.5 hours).||120|
Tells 25Live how to build an event that repeats in a regular pattern. Uses a subset of standard repeating rule nomenclature. If using Ad Hoc Dates, this field should be left blank. Repeating rules are defined as follows:
Common Repetition Types:
Days of the Week Abbreviations:
Ending the Repetition:
Every Day for 5 Days...
Every Third Day, repeated 10 times...
Weekly on Sunday until Dec. 23, 2021...
Weekly on Monday/Wednesday/Friday for 16 Weeks...
Every other Tuesday/Thursday until Oct. 1, 2016...
Every Second Tuesday Every Month for 12 Months...
Monthly on the 2nd and 15th for 6 Months...
Tells 25Live how to build an event that repeats on ad hoc dates.
If both the ADHOC_DATES field and the FIRST_OCCURENCE_DATE field are used, the first occurrence date is treated as an additional ad hoc date.
Location(s) where the event will be held.
Indicate that a location assignment should be shared by entering
You may also use
|BOUND_PROFILE_ID||Profile ID's of segments on other events that are required to have the same location(s) as the current segment/profile. If indicated, these segments will be bound, meaning that location assignments are the same for all of them.||X||ID-12345|
|RELATED_EVENT_ID||Event ID's of related events. 25Live Related Events functionality lets you specify that certain events are related by “content” in a way that is significant to your school’s business practices, but not enforced by the system. Related events must be indicated by EVENT_ID from among other events imported via this process. See Creating Related Events in 25Live||X||ID-44811C|ID-14401J|
Additional data elements you want to track about events. Different data types are allowed depending on the data source. Multiple custom attributes may be added, but all must be included between their respective commas, then separated by a vertical bar, e.g. ...,"High Risk?:Y|Past Attendance:45|Send Calendar?:N",...
For more information about the data types allowed, see Adding and Editing Custom Attributes In 25Live
High Risk?:Y|Past Attendance:45