Hi Alex, You're correct. A recurring event will only show up as a single record in the events/search results, with the next instance of the event used for the ID and time fields. In most cases that's what a user will expect to see, especially if it is combined with the recur_string (e.g. "repeats daily until April 21, 2011").
You can see an example of how Eventful.com displays those dates here: http://eventful.com/sandiego/events?q=musical&c=performing_arts The first date displayed will depend on the date range provided; you can see that above by choosing "Pick your dates" from the Date dropdown, or in the API by specifying a "date=June 2011" parameter. >From the API, if you want to see a list of instances for the given event, you >can use the /events/get method and specify "include=instances". XML feeds are similar, but configurable to provide you with instances for each event in-line. We can talk with you off-list to see if that's something you'll want in your feed. Cheers, ~chris On Apr 14, 2011, at 2:37 PM, Alex Matulich wrote: > This brings up a question I've been meaning to ask. Chris, you say > there's been a change below. Does this mean that an event having the > "recurrence" flag set will appear only once unless include=instances > is included in the query string? > > Also, how does this affect the XML feed? I see recurring events > occasionally in our test feed. Are these events repeated in the feed > for each date they recur, or do I have to keep track of these and > create copies of them myself in my own database? > > -Alex >
