Active Calendar

Page: Set Up Event Imports

RSS
Event Imports are the tool for transferring event data into your calendar from other event-maintaining systems, including 3.x versions of Active Data Calendar.

Top

Event Imports

Event Publisher allows for you to add events from other calendars using its import feature. The import feature supports adding events from other Active Data Products, iCal (.ics) files, or via specific XML and CSV formats.

The event import are allows you to:
  • Create and manage persistent (dynamic) event imports.
  • Create and view one-time event imports.

Top

Creating new event imports

Follow the instructions below if you would like to add content to your calendar from a file (One-Time Import) or from a data source on the web (Persistent Import).

Event imports can be configured in one of two ways.
  • The first option is a One Time Import. In this method you select a file from your computer or network to upload. This file can be housed on your local machine, or a local network location. A One-Time import is best used for events that will not be changed or managed in another application.
  • The second option is a Persistent Import. In this method a URL is called by the application to trigger a download of events. This option is best used for event that will be changed or managed in another applications outside of Event Publisher.

Top

Create one-time event import

One-time event imports are useful for adding up to 1000 events at a time into the calendar. Follow the steps below to create a One-time Import.

  1. If you have not done so already, click add new import.
  2. Select the One Time Import radio option
  3. Provide a Name for the One-Time Import. This name should quickly identify the import when viewing the list of imports added to the site.
  4. Click the Browse button and locate the event data file to import. Click OK.
  5. Select the appropriate file type option (the file type you are importing)
  6. Choose if all events should be imported using a specific category, or if the file contains the category information.
  7. Choose the event status to be used, this controls if events will require review and approval.

Top

Import Options

Creating a One-time Import allows for you to specify the following options when importing your events:

  • Import File Type
  • Event Default Category
  • Event Status

Top

Import File Type

Event Publisher supports a variety of specific import formats. You will need to specify what type of file you are importing into the calendar.

Select the appropriate file type from the Select Import File Type list:
  • Choose Calendar 3x XML for processing an XML file exported from an Active Data Calendar 3.x series. Please note we require you to be using Active Data Calendar 3.14.5 or greater to use this Import File Type.
  • Choose Event Publisher CSV for processing comma-separated-value files structured for Event Publisher.
  • Choose Event Publisher XML for xml files that have been created using the Event Publisher XML schema.
  • Choose iCal for processing iCal (.ics) files from existing applications into Event Publisher.

Top

Event Default Category

When working with most import file types a category will be supplied for each event.

This functionality allows for providing a default category in two ways:
  • Apply to all Events:
  • Selecting this option overwrites all provided categories in the import file and replaces them with the selected category.
  • Apply to events with no category:
  • Selecting this option will add the selected category to any events in the import file that do not specify a category.

Top

Event Status

When working with most imports an event status will be supplied for each event. If this value is not provided, the application will default to requiring an administrator to review each event. Choose from the following options.

Choose an option from the Event Status list:
  • Use File Defaults specifies that each event record's "approved" field should be transferred into the calendar's database, thus preserving the event's approval status.
  • Approve All places all imported events into the calendar with a status of approved.
  • Review All places all imported events into the calendar's database, but each one must be approved before it appears on the calendar.
Click Submit to start the import, or click Cancel to return to the Event Imports page without executing the import.

Top

Create persistent event import

Persistent event imports are repeating import jobs that run periodically, on dates and at times that you specify. To set up and run a persistent import

  1. Click Add New Import.
  2. Select the Persistent Import option.
  3. Enter a name for the persistent job into the Import Name box. Once saved, the import appears under this name in the list on the Set Up Event Imports page.
  4. Enter into the Import URL box the location from which the import job retrieves its input file.
  5. Enter polling dates and times:
    • Start Date: The date on which the first import of the series will run
    • End Date: The date on which the last import of the series will run
    • Start Time: The time at which the first run of each day will begin
    • End Time: The time at which the last run of each day will begin
  6. Enter into the Polling Interval box an interval in minutes, which will elapse from the end of one run of import job, until the start of the next run of the same import job.
  7. Select the Active option to make this persistent import run on your specified schedule. Deselecting this option leaves this import in the list, but it does not run until this option is selected again.
  8. Select the appropriate transform file from the list
  9. Choose if all events should be imported using a specific category, or if the file contains the category information.
  10. Choose the event status to be used, this controls if events will require review and approval.

Top

Import File Types

Event Publisher supports a variety of specific import formats. You will need to specify what type of file you are importing into the calendar.

  • Choose Calendar 3x XML for processing an XML file exported from an Active Data Calendar. Please note, we require that the export be created from the administrative area of Active Data Calendar version 3.14.5 or greater.
  • Choose Event Publisher CSV for processing comma-separated-value files structured for Event Publisher.
  • Choose Event Publisher XML for processing xml files from existing applications into Event Publisher
  • Choose iCal for processing iCal (.ics) files from existing applications into Event Publisher

Event Default Category

When working with most import file types a category will be supplied for each event.

This functionality allows for providing a default category in two ways:
  • Apply to all Events:
  • Selecting this option overwrites all provided categories in the import file and replaces them with the selected category.
  • Apply to events with no category:
  • Selecting this option will add the selected category to any events in the import file that do not specify a category.

Top

Event Status

When working with most imports an event status will be supplied for each event. If this value is not provided, the application will default to requiring an administrator to review each event. Choose from the following options.

Choose an option from the Event Status list:
  • Choose an option from the Event Status list:
    • Use File Defaults specifies that each event record's "approved" field should be transferred into the calendar's database, thus preserving the event's approval status.
    • Approve All places all imported events into the calendar with a status of approved.
    • Review All places all imported events into the calendar's database, but each one must be approved before it appears on the calendar.
  • Click Submit to place the import into your list, or click Cancel to return to the Event Imports page without placing the import into the list.

Top

Import File Types

Event Publisher supports a variety of specific import formats. You will need to specify what type of file you are importing into the calendar.

  • Choose Calendar 3x XML for processing an XML file exported from an Active Data Calendar in the 3.x series, or another application set up to export data in appropriately structured XML.
  • Choose Event Publisher CSV for processing comma-separated-value files structured for Event Publisher.
  • Choose Event Publisher XML for processing xml files from existing applications into Event Publisher
  • Choose iCal for processing iCal (.ics) files from existing applications into Event Publisher

Top

Calendar 3.X XML

Transform Calendar 3x XML: When working with this transform, you must generate your file from the administrative area in Active Data Calendar 3.X.


Top

CSV / Excel Import (Comma Separated Value)

Event Publisher CSV: When working with this transform, the csv that is provided to the import must be a comma separated value (.csv) file with the columns formatted accordingly. The required format for the comma separated value (.csv) file is as follows:

  • external-id
  • local-start-date-time
  • local-end-date-time
  • all-day
  • name
  • summary
  • description
  • keywords
  • contact-name
  • contact-phone
  • contact-email
  • private
  • highlighted
  • status
  • last-modified-by
  • last-modified-on
  • taxonomy
  • facility-name
  • facility-address1
  • facility-address2
  • facility-city
  • facility-state
  • facility-zip-code
  • facility-county
  • facility-country
  • facility-phone
  • hide-end

Top

Sample Import File

You can download a sample import file here: Click to download the Sample Import

Additionally, the file has unique requirements for acceptable values for each column, which have been identified below:
  • external-id: A unique value for each event, it must be a 32 digit number formatted like so : 12345678-1234-1234-1234-12345678
    • NOTE:If you use a GUID that is currently in use, meaning it is assigned to a previously submitted and/or approved event, the application overwrites the existing event with the content in your import file.
    • Example: 7FB3B88E-161C-4980-BE58-DFF140C02549
  • local-start-date-time: The Starting Date and time (if applicable) for an event, it must be formatted like so: MM/DD/YYYY HH:MMAM or MM/DD/YYYY HH:MMPM or MM/DD/YYYY (For all day events only).
    • Example: 8/25/2013 5:30PM or 8/25/2013 5:30AM or 8/25/2013

  • local-end-date-time: The Ending Date and time (if applicable) for an event, it must be formatted like so: MM/DD/YYYY HH:MMAM or MM/DD/YYYY HH:MMPM or MM/DD/YYYY (For all day events only).
    • Example: 8/25/2013 5:30PM or 8/25/2013 5:30AM or 8/25/2013
  • all-day: If the event should not display a starting time and end time you can indicate the event as an all day event, it must be formatted like so: Y or N
    • Example: N
  • Name: The title of the event to be shown in all views, this is an alpha-numeric plain text field, Event Publisher does not support HTML, alt codes, etc, in the event name.
    • Example: MY SAMPLE EVENT
  • Summary: The summary of the event to be shown in list views and sharing, this is an alpha-numeric plain text field. This field is limited to 250 characters, any excess characters in this field will be ignored by the import. Event Publisher does not support HTML, alt codes, etc, in the event summary.
    • Example: THIS IS MY SAMPLE EVENT SUMMARY
  • Description: The text to be shown in the event in the details view. This is an html enabled field, this field is limited to 1000 characters.
    • Example: THIS IS MY SAMPLE EVENT DESCRIPTION TEXT
  • Keywords: Keywords are used to link events together that do not share categories. They will be presented in the event details view, and searchable in the event search area. Keywords should be separated by commas. Event Publisher does not support HTML, alt codes, etc, in keywords.
    • Example: Test Keyword,KeywordNumber2
  • contact-name: The text to be shown in event list views, and event details views. This is the name of the person to contact with any inquires related to that event. This field is limited to 250 characters, any excess characters in this field will be ignored by the import. Event Publisher does not support HTML, alt codes, etc, in the event contact name.
    • Example: Greg Oppenheimer
  • contact-phone: The text to be shown in event list views, and event details views. This is the phone number of the person to contact with any inquires related to that event. This field is limited to 50 characters, any excess characters in this field will be ignored by the import. Event Publisher does not support HTML, alt codes, etc, in the event contact name.
    • Example: 570-333-3333
  • contact-email: The text to be shown in event list views, and event details views. This is the email adress of the person to contact with any inquires related to that event. This field is limited to 50 characters, any excess characters in this field will be ignored by the import. Event Publisher does not support HTML, alt codes, etc, in the event contact name.
    • Example: goppenheimer@activedatax.com
  • private: A status indication to determine if the event is public or private. Private events in Event Publisher are events that require a username and password to be viewed. This field is limited to 1 character. Event Publisher requires one of two options, “Y”, or “N”
    • Example: N
  • Highlighted: A status indication to determine if the event found be highlighted. Highlighted events are prominently displayed in the featured event area. **Note: You must also supply an image with an event for it to be displayed in the highlighted events area. This field is limited to 1 character. Event Publisher requires one of two options, “Y”, or “N”
    • Example: N
  • Status: A status indication to determine if the event requires review prior to being posted to the live calendar site. This field is limited to 1 character. Event Publisher requires one of two options, “A”, or “P”. Inputting “approved” will approve the event. Inputting “pending” will place the event in a pending status requiring review.
    • Example: A
  • last-modified-by: A text field, to be associated with the event, to provide a value or name to whom uploaded the file. By Default, the application will use a numerated value representing a user in the calendar system. No Value is required to upload a file.
    • Example: AE13177B-068D-4C6B-9DC0-1E1607F940A9
  • last-modified-on:
    • Example: 8/5/2013 5:30AM
  • taxonomy
    • Note: Multiple taxonomy sets are delimited by a semi-colon (‘;’) and multiple levels in a set are delimited by a single bar (‘|’).
    • Example: SOCKS|SOCCER|RED;SOCKS|SOCCER|BLUE;
  • facility-name: A text field, that denotes the name of the location where an event will be occurring. NOTE: If the import uses a facility that is not presently in the calendar database, it will add the facility to the “Locations” menu. This will occur for any calendar site that has a location scope value of, “Site” or “Both”.
    • Example: The Main Office
  • facility-address1: A text field, that denotes the first line of the address for the location where an event will be occurring. NOTE: If the import uses a facility that is not presently in the calendar database, it will add the facility to the “Locations” menu. This will occur for any calendar site that has a location scope value of, “Site” or “Both”.
    • Example: 190 Brodhead Road
  • facility-address2: A text field, that denotes the second line of the address for the location where an event will be occurring. NOTE: If the import uses a facility that is not presently in the calendar database, it will add the facility to the “Locations” menu. This will occur for any calendar site that has a location scope value of, “Site” or “Both”.
    • Example: Suite 300
  • facility-city: A text field, that denotes the city of the address for the location where an event will be occurring. NOTE: If the import uses a facility that is not presently in the calendar database, it will add the facility to the “Locations” menu. This will occur for any calendar site that has a location scope value of, “Site” or “Both”.
    • Example: Bethlehem
  • facility-state: A text field, that denotes the state of the address for the location where an event will be occurring. NOTE: If the import uses a facility that is not presently in the calendar database, it will add the facility to the “Locations” menu. This will occur for any calendar site that has a location scope value of, “Site” or “Both”.
    • Example: PA
  • facility-zip-code: A text field, that denotes the 5 digit zip code of the address for the location where an event will be occurring. NOTE: If the import uses a facility that is not presently in the calendar database, it will add the facility to the “Locations” menu. This will occur for any calendar site that has a location scope value of, “Site” or “Both”.
    • Example: 18017
  • facility-county: A text field, that denotes the county of the address for the location where an event will be occurring. NOTE: If the import uses a facility that is not presently in the calendar database, it will add the facility to the “Locations” menu. This will occur for any calendar site that has a location scope value of, “Site” or “Both”.
    • Example: Lehigh
  • facility-country: A text field, that denotes the country of the address for the location where an event will be occurring. NOTE: If the import uses a facility that is not presently in the calendar database, it will add the facility to the “Locations” menu. This will occur for any calendar site that has a location scope value of, “Site” or “Both”.
    • Example: USA
  • facility-phone: A text field, that denotes the contact phone number of the address for the location where an event will be occurring. NOTE: If the import uses a facility that is not presently in the calendar database, it will add the facility to the “Locations” menu. This will occur for any calendar site that has a location scope value of, “Site” or “Both”.
    • Example: 555-555-5555
  • hide-end: A text field, that indicates if the event should or should not display the end time on the front end views (list, summary, and event details view). Acceptable values include "y" or "n".
    • Example: N

Top

Event Publisher XML

Event Publisher XML: This format is best used when you create a persistent import of data into Event Publisher from an existing application. When working with this transform, you must use the following node structure in the file:



    <events>
      <event>
        <id/>
        <name/>
        <summary/>
        <description/>
        <keywords/>
        <local-start-date-time/>
        <local-end-date-time/>
        <highlighted/>
        <private/>
        <hide-end/>
        <status/>
        <external-id/>
        <external-series-id/>
        <route/>
        <contact/>
        <name/>
        <phone/>
        <extension/>
        <email/>
        <last-modified-on/>
        <last-modified-by/>
        <categories>
          <category>
            <name/>
            <global/>
          </category>
        </categories>
        <locations>
          <location>
            <name/>
            <address1/>
            <address2/>
            <city/>
            <state/>
            <zipcode/>
            <latitude/>
            <longitude/>
            <country/>
            <county/>
            <phone/>
            <global/>
          </location>
        </locations>
        <images>
          <image>
            <ul/>
            <id/>
            <name/>
            <data/>
          </image>
        </images>
        <attachments>
          <attachment>
            <id/>
            <name/>
            <data/>
          </attachment>
        </attachments>
        <custom-data/>
      </event>
    </events>
  


Top

XML Fields

The following list outlines the details for each XML node available.

  • events: The opening node for the XML file.
  • event: The opening node for a single event or series of events.
  • id: The system identifier for the event,
  • name: The title of the event, up to 255 characters.
  • summary: The plain text short description for an event, up to 250 characters.
  • description: The HTML description for an event, an unlimited number of categories.
  • keywords: Comma delimited phrases that can be used to associate like words together, up to 4000 characters.
  • local-start-date-time: MM/DD/YYYY HH:NN AM/PM
  • local-end-date-time: MM/DD/YYYY HH:NN AM/PM
  • highlighted: The status indicator to highlight an event, use Y or N, leaving this blank defaults to N.
  • private: The status indicator to make an event private, use Y or N, leaving this blank defaults to N.
  • hide-end: The status indicator to not display the end date or time for an event, use Y or N, leaving this blank defaults to N.
  • status: The state assigned to an event, approved events will be added for display on the calendar, all other statuses will be not be visible on the front use, approved, pending, denied, saved, deleted.
  • external-id: The identity assigned to an event from an external system.
  • external-series-id: The identity assigned to an event from an external system that links it to multiple "related" events. /li>
    • Please note: series events that have been imported can not be edited as a series from the Events Dashboard
  • route: The URL extension used to navigate directly to an event, up to 100 alphanumeric characters.
  • contact: The node for all event contact information.
    • name: The first and last name of the contact, up to 255 characters.
    • phone: The phone number of the contact, up to 100 characters.
    • extension: The extension number of the contact, up to 100 characters.
    • email: The email address of the contact, up to 255 characters.
  • last-modified-on: MM/DD/YYYY HH:NN AM/PM of the last modification of the event.
  • last-modified-by:
  • categories: The node for all event category or categories information.
    • category: The node for a single category.
      • category name: The text name of the category, up to 255 characters.
      • global: Indication if the category is a global or site level category, Y or N, blank assumes N.
  • locations: The node for all event location(s) information.
    • location: The node for a single location.
      • name: The text name of the location, up to 255 characters.
      • address 1: The first line of the street address, up to 100 characters.
      • address 2: The second line of the street address, up to 100 characters.
      • city: The city of the street address, up to 100 characters.
      • state: The city of the street address, up to 100 characters.
      • zipcode: The zipcode of the street address, up to 100 characters.
      • latitude: The latitude of the street address, in Float Format.
      • longitude: The longitude of the street address, in Float Format.
      • country: The country of the street address, up to 255 characters.
      • county: The county of the street address, up to 255 characters.
      • phone: The phone number of the location, up to 100 characters.
      • global: Indication if the location is a global or site level category, Y or N, blank assumes N.
  • images: The node for all images added to an event.
    • Image: The node for a single image.
      • id:Identity of the image.
      • name:File name of the image, up to 255 characters.
      • data:Base 64 encoded image binary.
  • attachments: The node for all attachments added to an event.
    • attachment: The node for a single attachment.
      • id:Identity of the attachment.
      • name:File name of the attachment, up to 255 characters.
      • data:Base 64 encoded attachment binary.
  • CustomData: The node for all event extras (Custom Fields).
    • ID#: The Identity of the Custom Field, visible in the Advanced Setup area of Event Extras.


Top

Importing Custom Fields

When using the Event Publisher XML import you can import data to existing custom fields or define custom fields that need to be added to a calendar site.

  • If your system administrator has configured your custom fields, please proceed to the "Adding Data for Custom Fields" section below.

You can define new custom fields by using the "variables" node. This node needs to be added below the "events" node and before the first "event" node.
The following types of fields can be added:
  • Single Line: Text
  • MultiLine: Text
  • Yes/No Feild
  • Single Selection: Multiple Choice
  • Multiple Selection: Multiple Choice

The following sample import defines custom fields to be added, and supplies data for custom fields for events.
<events>
    <variables>
        <custom-fields>
            <field textmode="SingleLine" type="Text" identity="id2ab3700e9cfd4d7dae9bdcb2f6bf875c" name="Custom SingleLine Text Field"/>
            <field textmode="MultiLine" type="Text" identity="id2ab3700e9cfd4d7dae9bdcb2f6bf875c" name="Custom MultiLine Text Field"/>
            <field type="YesNo" identity="id3d035f0174404f0eb075d1bcf1512516" name="Custom YesNo Field"/>
            <field type="MultipleChoice" identity="id84c55ab3695d40fb981baab23423e6d0" name="Custom Single Choice Field" selectionmode="Single">
                <option>One</option>
                <option>Two</option>
                <option>Three</option>
            </field>
            <field type="MultipleChoice" identity="idd93506761ac74694843b13681cf24a0a" name="Custom Multiple Choice Field" selectionmode="Multiple">
                <option>Red</option>
                <option>Green</option>
                <option>Blue</option>
            </field>
        </custom-fields>
    </variables>
    <event>
        <localstartdatetime>20150326T07:00:00</localstartdatetime>
        <localenddatetime>20150326T08:00:00</localenddatetime>
        <name>Green event and custom text</name>
        <summary>Event to test custom event fields</summary>
        <description>Event to test custom event fields</description>
        <route>eventtotestcustomeventfields</route>
        <customdata>
            <id2ab3700e9cfd4d7dae9bdcb2f6bf875c>Custom field text</id2ab3700e9cfd4d7dae9bdcb2f6bf875c>
            <idd93506761ac74694843b13681cf24a0a>Green</idd93506761ac74694843b13681cf24a0a>
        </customdata>
    </event>
</events>
    

Top

Defining Variables

The "variables" node is used to define custom fields.



The following structure should be used to define variables:
<events>
    <variables>
        <custom-fields>
            <field \>
        </custom-fields>
    </variables>
    <event \>
</events>

Top

Fields

When defining a custom field the "field type" attribute or "text-mode" attribute must be supplied.



These attributes determine if the custom field is a text field, mutliple choice field, or yes / no field.
The following definitions are accepted.
    <field text-mode="SingleLine" type="" identity="" name="" max-length="100"/>
    <field text-mode="MultiLine" type="" identity="" name="" max-length="100"/>
    <field type="YesNo" identity="" name=""/>
    <field type="MultipleChoice" identity="" name="" selection-mode="">
    <field type="MultipleChoice" identity="" name="" selection-mode="">

Top

Identities

When defining a custom field the "identity" of a custom field must be supplied. This is a GUID that will uniquely identify the custom field in the calendar site.



This field supports up to 34 alphanumeric characters, with no spaces or special characters.
    <field text-mode="" type="" identity="id2ab3700e9cfd4d7dae9bdcb2f6bf875c" name=""/>

Top

Name

When defining a custom field the "name" attribute is required. This will display on the event details view, and create an event screen.


Top

Defining Text Fields

The following example displays the format and content required to define a text field.

<variables>
    <custom-fields>
        <field text-mode="SingleLine" type="Text" identity="id2ab3700e9cfd4d7dae9bdcb2f6bf875c" name="Custom SingleLine Text Field" max-length="100"/>
        <field text-mode="MultiLine" type="Text" identity="id2ab3700e9cfd4d7dae9bdcb2f6bf875c" name="Custom MultiLine Text Field" max-length="100"/>
    </custom-fields>
</variables>

Single vs. Multi Line Text Fields
  • SingleLine: Allows for the creation of a text field that does not support paragraph or line breaks. The information will be displayed as a continuous block of text.
  • MultiLine: Allows for the creation of a text field which supports paragraph and line breaks.

Maximum Length
  • Setting the value in the max-length attribute define the maximum number of characters that can be used for a particular custom field.
  • If this attribute is omitted from your import the default value of 100 characters will be applied.

Top

Defining Multiple Choice Fields

The following example displays the format and content required to define a multiple choice field.

  
<field type="MultipleChoice" identity="id84c55ab3695d40fb981baab23423e6d0" name="Custom Single Choice Field" selection-mode="Single">
    <option>One</option>
    <option>Two</option>
    <option>Three</option>
/<field>
<field type="MultipleChoice" identity="idd93506761ac74694843b13681cf24a0a" name="Custom Multiple Choice Field" selection-mode="Multiple">
    <option>Red</option>
    <option>Green</option>
    <option>Blue</option>
</field>

Selection Mode
  • Single: Allows for the selection of a single item from the list of options.
  • Multiple: Allows for the selection of more than one item from the list of options.

Options
  • When creating multiple choice fields via the import, you must supply the list of avaiable selections. Each individual selection is refered to as an Option.

Top

Defining Yes/No Fields

The following example displays the format and content required to define a Yes/No field.

<variables>
    <custom-fields>
       <field type="YesNo" identity="id3d035f0174404f0eb075d1bcf1512516" name="Custom YesNo Field"/> 
    </custom-fields>
</variables>

Top

Adding Data for Custom Fields

When importing data into custom fields you will provide your data for each custom field using the fields Identity. The following structure is required:

<Custom Data>
    <ID>Data you wish to import goes here</id>
</Custom Data>
    

The following Sample illustrates how custom fields are defined for an event.
<event>
    <local-start-date-time>2015-03-26T07:00:00</local-start-date-time>
    <local-end-date-time>2015-03-26T08:00:00</local-end-date-time>
    <name>Green event and custom text</name>
    <summary>Event to test custom event fields</summary>
    <description>Event to test custom event fields</description>
    <route>event-to-test-custom-event-fields</route>
    <custom-data>
        <id2ab3700e9cfd4d7dae9bdcb2f6bf875c>Custom field text</id2ab3700e9cfd4d7dae9bdcb2f6bf875c>
        <idd93506761ac74694843b13681cf24a0a>Green</idd93506761ac74694843b13681cf24a0a>
    </custom-data>
</event>
    



Top

iCal Import

When importing an iCal file, commonly availble from Outlook or Google Calendar, the following attributes of the file are supported.

    BEGIN:VCALENDAR
    METHOD:PUBLISH
    VERSION:2.0
    BEGIN:VTIMEZONE
    TZID:Eastern Standard Time
    BEGIN:STANDARD
    DTSTART:16010101T020000
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0500
    RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
    END:STANDARD
    BEGIN:DAYLIGHT
    DTSTART:16010101T020000
    TZOFFSETFROM:-0500
    TZOFFSETTO:-0400
    RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
    END:DAYLIGHT
    END:VTIMEZONE
    BEGIN:VEVENT
    DESCRIPTION:
    SUMMARY:
    DTSTART;TZID=Eastern Standard Time:20150727T150000
    DTEND;TZID=Eastern Standard Time:20150727T173000
    RECURRENCE-ID;TZID=Eastern Standard Time:20150723T000000
    END:VEVENT
    END:VEVENT
    END:VCALENDAR
  

Top

Required Fields

In order for an event to be imported using the iCal file format by Event Publisher each event must contain information in the following attributes:

  • DESCRIPTION:
  • SUMMARY:
  • DTSTART;
  • DTEND;

If your iCal file does not import, it is likely that the file does have values specifed for each of the required fields for the event. Commonly, an event created with only a name will only contain the "Summary" attribute. Each event must have both a summary and description to be imported. Additionally, Event Publisher iCal import does not currently support the import of locations assgined to events.

Top

View Import History

View import history allows you to access detailed information about the events that are contained in a particular import. You can access the following information:

  • Import Start: The date and time that the import service started
  • Import End: The date and time that the import service completed
  • Events Accepted / Rejected: The number of events accepted or rejected by the import service. NOTE: "Accepted Events" will be shown on the left, and "Rejected Events" will be shown on the right.
  • Messages: A text description related to the success or failure of the import
  • Details: A link that will shown detailed information for each event in the import.

To view the history of an event import that is already in your list:
  1. Locate the import in the list, and click on the dropdown box on the right side of the row.
  2. Select "View Import History" From the dropdown menu.
  3. A table will open below the list of imports where you can view information about that import.

Top

Modify existing event import

To change the parameters in an event import that is already in your list:

  1. Locate the import in the list, and click on the dropdown box on the right side of the row.
  2. Select "Edit" From the dropdown menu.
  3. Click Submit to save your changes and return to the list of persistent imports, or click Cancel to discard any changes and return to the list of imports.

Top

Delete existing event import

To remove an event import that is already in your list:

  1. Locate the import in the list, and click on the dropdown box on the right side of the row.
  2. Select "Delete" From the dropdown menu.
  3. Click Okay to remove the import and all of its events, or click Cancel to discard any changes and return to the list of imports.

Top

Purge

This feature will force the permenant deletion of all events added by a specific import. Use this feature when a large number of events need to be removed that were previously imported. To remove all events for a specific import:

Important Note:Once initiated, a purge can not be undone, the events will be permenantly removed from the calendar.
  1. Locate the import in the list, and click on the dropdown box on the right side of the row.
  2. Select "Purge Events" From the dropdown menu.
  3. Click Ok to remove the import and all of its events, or click Cancel to discard any changes and return to the list of imports.

Top

Other available functions

Refresh: Click this icon or link on the list page to reload the list of defined persistent event imports from the calendar' database.