CSV / Excel

Localist can import a CSV (.csv) or Excel (.xls) file that is hosted on your servers as a feed. The file must adhere to the same CSV format used for bulk uploading.

Need information on one-time bulk adds? Check out: +Bulk Add Events

In this article you’ll find:

  • Retrieving a CSV/XLS Template
  • CSV/XLS Import Data
  • Importing a CSV/XLS Feed
  • Important Feed Import Details

Retrieving a CSV/XLS Template

1. In your admin dashboard, navigate to Events > +Bulk Add Events

2. Select Bulk Event CSV to download a template that is pre-populated with the appropriate headers.

XLS

If using Excel, the Bulk Event CSV template will open as an XLS file in Excel. Important Note: Previously, Localist’s bulk uploader accepted only CSV files, but now Excel spreadsheets can be uploaded without exporting to CSV.


CSV Import Data

By default your CSV template will include these headers:

    1. Title
    2. Description
    3. Date From (Start Date): 2014-10-01
    4. Date To (End Date): 2014-10-01
    5. Recurrence: Su,M,T,W,Th,F,Sa
    6. Start Time: 7:00 AM
    7. End Time: 12:00 PM
    8. Location: If assigning to a place landing page it must match exactly to what is saved in Localist
    9. Address, City, State: Only necessary if  not  connecting to a place landing page
    10. Event Website
    11. Room
    12. Keywords
    13. Tags
    14. Photo URL: must be hosted on your end
    15. Ticket URL
    16. Cost: $40 or free
    17. Hashtag: do not include a #
    18. Facebook URL: this is for the event page in Facebook
    19. Group: If assigning to a group landing page it must match exactly to what is saved in Localist
    20. Allows Reviews: Enter 1/y/yes/true
    21. Visibility: Enter Hidden or Logged In
    22. Featured Tabs: Enter the name of the Featured Tab, or if you don’t have any custom tabs just enter Featured Events, which is the default tab.
    23. Sponsored: Enter 1/y/yes/true
    24. Venue Page Only: Enter 1/y/yes/true
    25. Exclude From Trending: Enter 1/y/yes/true
    26. Event Types: Must match exactly to what is saved in Localist
    27. Departments: Must match exactly to what is saved in Localist

Note: If you have added custom fields or other filter groups to your platform then headers + columns will automatically be included in the template. If you are using a pre-existing file, just add a column with the custom field, etc., as the title.

Note: If rich text is included, it will be imported and displayed as plain text in Localist.


Importing a CSV Feed

1. In your admin dashboard, navigate to Events > Feeds

2. Select +Add Feed

3. Description Fields

  • Name: This should be used as a general description for the feed.
  • Feed URL: This is where you enter the URL to the CSV file.
  • Skip Pending: By default,  all  events in the feed will be automatically posted. Uncheck this option to send  all  events to the pending queue for additional approval.
  • Taxonomy Overrides: These drop downs will match your platform’s filters. Selecting from the drop downs will apply the filter to  every  event in the feed.
  • ShowAdvanced Options
    • Username / Password
    • Match Instances: If selected, event  instances  that have been added to Localist, but are no longer present in the feed, will be removed. Here’s a breakdown:
      • If checked: Event A on Oct 1 is imported —> Upon next import Event A is now listed for Oct 2 and Oct 1 is no longer present in the feed —> The live event in Localist is updated from Oct 1 to Oct 2
      • If  not  checked: Event A on Oct 1 is imported —> Upon next import Event A is now listed for Oct 2 and Oct 1 is no longer present in the feed —> The live event in Localist is updated to now have two instances – both Oct 1 and Oct 2Essentially, this functionality is only applied to  instances  of events that are still in the feed. If an entire event is remove from the feed then Localist will not make any updates or deletions and the event will stay in the last-imported state unless manually modified.

Note: Upon saving, the feed will initially import once. After the initial import, the feed will import once a day and overnight. Changes will not be reflected in Localist until the nightly import.


IMPORTANT FEED IMPORT DETAILS

Feed Data Takes Precedent

1. Data imported by a feed into Localist will always take precedent over data that has been added or updated in the Localist event. Only the following 3 details can be locked and cut off from further updating:

  • Name
  • Description
  • Event Place

2. All other details that are brought in via a feed must be changed at the feed source. If it is changed in any way in Localist then the changes will only stick until the next feed import, at which time it will revert back to the data in the feed.

  • Exception: If a piece of data is not provided by the feed then any changes or additions in Localist will stick even after the next import. For example, if the feed only provides name/date/time/description/place then anything else, such as a tag or custom field, will remain as updated in Localist.

3. If fields in a feed match fields in Localist then the data must match exactly to what is saved in Localist. It is not possible to assign aliases or alternative spellings. For example, place names must match the place landing pages and filters must match the taxonomy on your platform in order to connect properly.

Deleting a Feed Event

1. Deleted in Localist: If an event has been imported to the calendar then deleted, it will reappear if it is sent back over through the feed. Since feed data takes precedent, if the event is present in the feed then it will be re-added to Localist.

  • Exception: If an event is rejected from the pending queue then it will not re-appear. If the event is deleted while still in the pending queue then it will be re-imported into the queue.

2. Deleted at the feed source: If an event is removed from the feed source, the event in Localist will not be removed. This is because it is impossible for Localist to determine wether the event has been deleted/cancelled or if the event is just not present in the feed. In this case you will need to delete the instance in the feed and in Localist.