    /**
     * @class Ext.ensible.cal.EventMappings
     * @extends Object
     * A simple object that provides the field definitions for
     * {@link Ext.ensible.cal.EventRecord EventRecord}s so that they can be easily overridden.
     *
     * There are several ways of overriding the default Event record mappings to customize how
     * Ext records are mapped to your back-end data model. If you only need to change a handful
     * of field properties you can directly modify the EventMappings object as needed and then
     * reconfigure it. The simplest approach is to only override specific field attributes:
     *
    var M = Ext.ensible.cal.EventMappings;
    M.Title.mapping = 'evt_title';
    M.Title.name = 'EventTitle';
    Ext.ensible.cal.EventRecord.reconfigure();

     *
     * You can alternately override an entire field definition using object-literal syntax, or
     * provide your own custom field definitions (as in the following example). Note that if you do
     * this, you MUST include a complete field definition, including the type attribute
     * if the field is not the default type of string.
     *
    // Add a new field that does not exist in the default EventMappings:
    Ext.ensible.cal.EventMappings.Timestamp = {
        name: 'Timestamp',
        mapping: 'timestamp',
        type: 'date'
    };
    Ext.ensible.cal.EventRecord.reconfigure();

     *
     * If you are overriding a significant number of field definitions it may be more convenient
     * to simply redefine the entire EventMappings object from scratch. The following example
     * redefines the same fields that exist in the standard EventRecord object but the names and
     * mappings have all been customized. Note that the name of each field definition object
     * (e.g., 'EventId') should NOT be changed for the default EventMappings fields as it
     * is the key used to access the field data programmatically.
     *
    Ext.ensible.cal.EventMappings = {
        EventId:     {name: 'ID', mapping:'evt_id', type:'int'},
        CalendarId:  {name: 'CalID', mapping: 'cal_id', type: 'int'},
        Title:       {name: 'EvtTitle', mapping: 'evt_title'},
        StartDate:   {name: 'StartDt', mapping: 'start_dt', type: 'date', dateFormat: 'c'},
        EndDate:     {name: 'EndDt', mapping: 'end_dt', type: 'date', dateFormat: 'c'},
        RRule:       {name: 'RecurRule', mapping: 'recur_rule'},
        Location:    {name: 'Location', mapping: 'location'},
        Notes:       {name: 'Desc', mapping: 'full_desc'},
        Url:         {name: 'LinkUrl', mapping: 'link_url'},
        IsAllDay:    {name: 'AllDay', mapping: 'all_day', type: 'boolean'},
        Reminder:    {name: 'Reminder', mapping: 'reminder'},

        // We can also add some new fields that do not exist in the standard EventRecord:
        CreatedBy:   {name: 'CreatedBy', mapping: 'created_by'},
        IsPrivate:   {name: 'Private', mapping:'private', type:'boolean'}
    };
    // Don't forget to reconfigure!
    Ext.ensible.cal.EventRecord.reconfigure();

     *
     * NOTE: Any record reconfiguration you want to perform must be done PRIOR to
     * initializing your data store, otherwise the changes will not be reflected in the store's records.
     *
     * Another important note is that if you alter the default mapping for EventId, make sure to add
     * that mapping as the idProperty of your data reader, otherwise it won't recognize how to
     * access the data correctly and will treat existing records as phantoms. Here's an easy way to make sure
     * your mapping is always valid:
     *
    var reader = new Ext.data.JsonReader({
        totalProperty: 'total',
        successProperty: 'success',
        root: 'data',
        messageProperty: 'message',

        // read the id property generically, regardless of the mapping:
        idProperty: Ext.ensible.cal.EventMappings.EventId.mapping  || 'id',

        // this is also a handy way to configure your reader's fields generically:
        fields: Ext.ensible.cal.EventRecord.prototype.fields.getRange()
    });

     */
    Ext.ensible.cal.EventMappings = {
        EventId:     {name: 'EventId', mapping:'id', type:'int'},
        CalendarId:  {name: 'CalendarId', mapping: 'cid', type: 'int'},
        Title:       {name: 'Title', mapping: 'title', type: 'string'},
        StartDate:   {name: 'StartDate', mapping: 'start', type: 'date', dateFormat: 'c'},
        EndDate:     {name: 'EndDate', mapping: 'end', type: 'date', dateFormat: 'c'},
        RRule:       {name: 'RecurRule', mapping: 'recur_rule'}, // not currently used
        Location:    {name: 'Location', mapping: 'loc', type: 'string'},
        Notes:       {name: 'Notes', mapping: 'notes', type: 'string'},
        Url:         {name: 'Url', mapping: 'url', type: 'string'},
        IsAllDay:    {name: 'IsAllDay', mapping: 'ad', type: 'boolean'},
        Reminder:    {name: 'Reminder', mapping: 'rem', type: 'string'}
    };