[an error occurred while processing this directive]
[an error occurred while processing this directive]K-State's central website provides a way to publish university event information as part of a university calendar as well as on the K-State homepage.
Publishing your events to the central calendar has several advantages:
To add your information to a calendar, the easiest option is to submit the calendar event form with your event information. Additionally, you can submit questions, events, or multiple events to calendar@ksu.edu
However, if you have more than an occasional event, it is better to set up your own calendar. To create a calendar, two files are required:
For these examples, assume that you are providing files for a department with a department code of dept and have chosen to call your calendar events.
The calendar data file is named events.caldata, and it is stored in the department's web space directory, /usr/local/data/www/dept.
The format of the calendar data file is a single HTML definition list:
<dl>
<dt>date1
<dd>description of the event
<dt>date2
<dd>description of the event
</dl>
Several formats are acceptable for the date field:
April 30, 2008 | This is the normal format. |
April 30 | A missing year defaults to the last year specified. |
apr 30, 2008 | Only 3 chars, case insensitive, of strings used. |
Sunday, April 30, 2008 | Day-of-week string is ignored; it doesn't matter even if the day of week is wrong. |
Sunday April 30 2008 | Commas and blanks are equivalent |
April 1, 2008 -- May 2, 2008 | Any two dates separated by '--' are a range. The event is duplicated for each date in the range, inclusive. |
Other notes about the calendar data file:
<dl>
<dt>date
<dd>description of the first event on this date
<dd>description of the second event on this date
The difficult part of creating a calendar file isn't the mechanics of getting the data into the proper HTML format. Instead, the emphasis is on wording the events in a clear, concise, and useful format.
The template file will be provided for you when you're ready for production. The template, named events-template.html
contains the HTML code that surrounds the events. It uses the K-State calendar template which includes a visual calendar at the top.
This templates is only used when the calendar is viewed as its own calendar. When the calendar events are put into the university calendar, then the university calendar's template file is used.
To get your calendar added to the list of calendars, and possibly included in the University Calendar, contact webmaster@k-state.edu.
Suppose your department code is dept, and you are creating a calendar file named events. In the simplest case, you need to create two files: a calendar data file and a template file.
Here is an example calendar data file:
<dl>
<dt> January 1, 2008
<dd> Happy New Year!
<dt> January 16, 2008
<dd> Classes begin.
<dl>
For additional examples, see the existing calendars, most of which are in
/usr/local/data/www/calendar
There can be multiple files that are all put together into one event database.
All files of the form events*.caldata
are read.
For example, files named events-fall1996.caldata
,
events-regular.caldata
,
events-special.caldata
,
would all be processed together.
These calendar files must all be in the same directory, typically
/usr/local/data/www/dept
.