Import Events (Hot Folder)

Use the Import/Native hot folder to automatically ingest events, in CSV format, directly onto your TelVue Princeton™ server instead of having to import them via the user interface. Successfully imported CSV files are moved to the CSV subfolder.

  1. Make sure your CSV file has valid content. Many software packages export CSV files a spreadsheet. Use a simple text editor to edit your CSV file and be sure to save it in CSV format.
  2. Navigate to the drive you use for your uploads (typically vol1 or upload). (If you will use the hot folder often you might want to map the /upload drive.) A window pops up showing the import/native hot folder. In this example, the mapped drive is named R: (Windows) or native (Mac).Screenshot: Native Hot Folder on OS X
  3. Open a new window and show the contents of the folder where your CSV file is. Find the CSV file.
  4. Drag the CSV file onto the /import/native folder.Screenshot: CSV Upload on PC
    Screenshot: CSV Upload on OSX
  5. Refresh the Content screen on the Digital Broadcaster UI and look for the file. When the CSV file has been successfully imported, the /import/native folder will be empty and the original source CSV file will appear in /import/native/csv on servers running software versions before 3.10.0. Additionally, a summary CSV will be created in the /import/native/summary folder that is similar to the source CSV but adds a summary column for the status each entry. If the import failed, a CSV file is created with only the failed records in /import/native/failed. This acts as a sort of “bump list” in case the reason for the error is corrected and only the failed events need to be re-imported. On versions starting with 3.10.0 and greater, these three folders are located in /import/native_complete/ (/import/native/ is still the folder you place incoming CSV files into).
    Screenshot: CSV, Failed, and Summary Folders on Mac

You can also use the Schedule Config setting in the Web Application called “Delete Overlapping Events On Import” to specify whether overlapping events on import take precedence and delete any conflicts, or to ignore imported events that conflict with existing events.

To understand the TelVue Princeton™ native CSV format, schedule a few sample events in the web application, and then from Classic Programming view, select those events and export in Native format.



  1. Kevin Reynen says:

    It’s important to note that short .csv require a header row. Long .csv do not. It would be great to either know how long, long is or just make this consistent for all .csv.

  2. dpisarski says:


    Great to see you here! We are excited to finally have this up and available.

    To clarify, all CSVs are expected to have a header row today, long or short. So a file that contains 1000 rows, all events, will only import 999 because the first row is skipped as a header row. This is also true of a 1 row file and a 1500 row file.

    As you discovered, the error message returned, via the hot folder and also in the UI, is a bit cryptic on this, as it skips over the valid row without counting that as an error. Thus your summary file will have only 999 entries, with no mention of the missing row. If your input file is only 1 row, there will be no error (but no import) in the hot folder, or in the UI, you will get an error stating that the file was empty.

    After your issues with this, we have added this for future development consideration – its unfortunate it works this way today, as it should be pretty straightforward to detect that a row looks an event entry and not a header. In the interim though, anyone importing CSVs of events should include a header row in the file.

    I will also update these docs to make this clear.