Import events from Excel
As of v0.4.0 you are able to import an excel file containing a list of events. For the import to be successful there are a few conventions that Ontime expects
The workbook tab must be named either ontime or Event Schedule (non case sensitive)
Event Name, Event URL, Public Info, Backstage Info and End Message fields must have its data on the cell to its right
Any event data (Time Start / Time End / Event Title / Presenter Name / Event Subtitle/ Is Public / Notes) should be directly under field
Time Start and Time End should be Excel time fields
Any text under a field named Is Public will make the event public
You only need to define a single value per row to create an event
Field names as defined in the table below, any other fields in the table will be ignored
Event data
The event data can be imported through excel, this fields must have its data on the cell to its right
| Field Name | |
|---|---|
Event Name | All fields here are text |
Event URL | All fields here are text |
Public Info | All fields here are text |
Backstage Info | All fields here are text |
End Message | All fields here are text |
Event list
Field names are not case sensitive. Meaning: both Event Title and event title would be recognised on import
| Event Field | Possible Names | Type |
|---|---|---|
Event Name | Event Name | Text |
Event URL | Event URL | Text |
Time Start | Time Start, Start | Excel time |
Time End | Time End, End, Finish | Excel Time |
Title | Event Title, Title | Text |
Name | Presenter Name, Speaker, Presenter | Text |
Subtitle | Event Subtitle | Text |
Public | Is Public, Public | Text (any text means the event is public) |
Notes | Notes | Text |
Colour** | Colour | Text |
** Colour field adds a coloured indicator in the backstage views:
/backstage /studio /cuesheetThis feature allows for user colour coding of events.
User Fields
There are 10 custom fields available.
The excel importer would be looking for columns starting with any of the defined values above (ie. user0).
It is possible to add custom naming for in-app display by using a pattern such as user0:Video in the column header. This would import the data of user0 to any event and show it labeled as Video
user0 | Text |
user1 | Text |
user2 | Text |
user3 | Text |
user4 | Text |
user5 | Text |
user6 | Text |
user7 | Text |
user8 | Text |
user9 | Text |
Last updated
