Getting Started > RSS Feeds
UC Berkeley Calendar Network
RSS, XML, and iCalendar Feeds
Each calendar is provided with three RSS feeds for Today's, This Week's, and This Month's events in the left navigation column. If a value for a calendar filter has been selected, then the RSS feed will include this filter. For example, if the calendar has an "Audience" filter and "Alumni" is selected, then "Today's Events" will include only events taking plan today flagged for an "Alumni" audience.
In addition to the three visible RSS feeds, you may set up other RSS feeds for various time periods and filters. Below is a complete list of the options. You may also apply these same options to the live XML feed (which contains more data) by substituting "live_export" for "rss" and to the live iCalendar feed by substituting "ical" for "rss." Some systems may require a final "/.ics" at the end of the URL in order to recognize the iCalendar feed.
Note to developers: an XML file of the names and short names (used in URL) of network calendars may be generated by accessing: http://events.berkeley.edu/index.php/calendar_list_export.html
- Time Periods
- Today "day"
Example: http://events.berkeley.edu/index.php/rss/sn/SPH/type/day.html
- This Week "week"
Example: http://events.berkeley.edu/index.php/rss/sn/SPH/type/week.html
- This Month "month"
Example: http://events.berkeley.edu/index.php/rss/sn/SPH/type/month.html
- Three months in the past and future "past_future"
Example: http://events.berkeley.edu/index.php/rss/sn/SPH/type/past_future.html
- Past (beginning of calendar range through yesterday) "past"
Example: http://events.berkeley.edu/index.php/rss/sn/SPH/type/past.html
- Future "future"
Example: http://events.berkeley.edu/index.php/rss/sn/SPH/type/future.html
- A range of specified dates "range", "startdate", "enddate"
Example: http://events.berkeley.edu/index.php/rss/sn/SPH/type/range.html?startdate=2007-05-07&enddate=2007-05-09
- Single Filters
- Event Type
Example: http://events.berkeley.edu/index.php/rss/sn/dos/type/day.html?filter=Event%20Type&filtersel=19
- Campus Location
Example: http://events.berkeley.edu/index.php/rss/sn/dos/type/day.html?filter=Campus%20Location&filtersel=1
- Sponsor
Example: http://events.berkeley.edu/index.php/rss/sn/dos/type/day.html?filter=Sponsor&filtersel=2
- Other Sponsor
http://events.berkeley.edu/index.php/rss/sn/JRT/type/future.html?filter=OtherSponsor&filtersel="Public Affairs"
- Target/Open To Audiences
Example: http://events.berkeley.edu/index.php/rss/sn/dos/type/day.html?filter=Target/Open%20To%20Audiences&filtersel=3
- Secondary Event Type (defined by calendar administrator)
Example: http://events.berkeley.edu/index.php/rss/sn/gradiv/type/month.html?filter=Secondary%20Event%20Type&filtersel=67
- Feature Type (defined by calendar administrator)
Example: http://events.berkeley.edu/index.php/rss/sn/dos/type/day.html?filter=Feature%20Type&filtersel=895
- Multiple Filters
Example:http://events.berkeley.edu/index.php/rss/sn/dos/type/week.html?filter1=Event%20Type&filtersel1=20&filter2=Campus%20Location&filtersel2=96&filter3=Sponsor&filtersel3=180&filter4=Target/Open To Audiences&filtersel4=3&filter5=Secondary%20Event%20Type&filtersel5=965&filter6=Feature%20Type&filtersel6=65
- Multiple values per filter will be treated with an "or"
Example: http://events.berkeley.edu/index.php/rss/sn/JRT/type/day.html?filter1=Secondary%20Event%20Type&filtersel1=123&filter2=Secondary%20Event%20Type&filtersel2=456
- Limit number of events (recommended with "future" time period) "limitRSS"
- Example: http://events.berkeley.edu/index.php/rss/sn/SPH/type/future.html?limitRSS=5
- Recurrence
- By default recurrences will be limited to one per feed.
- To include all recurrences for the time period, specify "recur=yes"
- Example: http://events.berkeley.edu/index.php/rss/sn/SPH/type/future.html?limitRSS=5&recur=yes
- To limit recurrences to one per feed and skip in-progress events after start date, specify "recur=start"
- Example: http://events.berkeley.edu/index.php/rss/sn/SPH/type/future.html?limitRSS=5&recur=start
- Note: the iCalendar feed (ical) does not provide recurrences, since these are handled by the RRULES for each event.
- By Event ID
- Get all the recurrences of a particular event :
http://events.berkeley.edu/index.php/rss/sn/pubaff/?event_ID=2604
- Limit the recurrences using a time frame:
http://events.berkeley.edu/index.php/rss/sn/pubaff/type/week/?event_ID=2604
- Limit to the first recurrence:
http://events.berkeley.edu/index.php/rss/sn/pubaff/?event_ID=2604&recur=no
- Note: iCalendar by event ID does not require the calendar parameter:
- http://events.berkeley.edu/index.php/ical/?event_ID=4224
or
- http://events.berkeley.edu/index.php/ical/event_ID/4224/.ics
- Decimal Numeric
(live_export only)
- Normally, special characters 128-159 will be converted to decimal numeric e.g., em-dash will be exported as — rather than — (Windows cp1252 code point). If you want to omit this conversion step, use the "dn=no" parameter.
- Example: http://events.berkeley.edu/index.php/live_export/sn/pubaff/type/day/?dn=no
- Optional performers node (RSS only)
- If specificed, the names of speakers/performers will be concatenated with comma separators to a "performers" node in the RSS feed only.
- http://events.berkeley.edu/index.php/rss/sn/pubaff/type/week/?performer=yes
- Optional sortdate node (RSS only)
- If specificed, the recurrence date will be added as a "sortdate" node in the RSS feed only.
- http://events.berkeley.edu/index.php/rss/sn/pubaff/type/week/?sortdate=yes
- Optional admission info nodes (live_export only)
- If specificed, the admission related nodes will be included in the live_export only.
- http://events.berkeley.edu/index.php/live_export/sn/pubaff/type/week/?admission=yes
- Optional Archived Event data
- If specificed, the archived events will be pre-pended to rss and live_export feeds
- http://events.berkeley.edu/index.php/live_export/sn/pubaff/type/past/?archive=yes
Notes for Drupal 6 Developers using RSS feeds:
1) Follow the simple instructions here to reverse the sort order from DESC to ASC
http://drupal.org/node/108581#comment-945500
(this is a hack to the Aggregator.module, perhaps will be a configuration setting in the next update).
2) Events items are Cached so they load quickly if something new is posted it will likely occur out of order it's important to go into
Drupal Admin: Content Management -> Feed Aggregator -> List
http://WEBSITE.berkeley.edu/[your login]/content/aggregator/list
then click "Remove Items" in the feed list. Now the list on the front page is blank.
then go to http://WEBSITE.berkeley.edu/cron.php
and it will repopulate from Events.Berkeley.Edu in the proper order.
See sample events feeds on the front pages of two Drupal sites on campus:
http://arf.berkeley.edu
http://nemeacenter.berkeley.edu