Re: General development issues and questions
Chris Radcliff <chris@...
2006-11-08 22:19:21 GMT
Nextcat looks like a pretty cool site; we're always glad to get
performers more involved. When are you planning to add Eventful
integration? Is there a preview of that anywhere? I'd love to see
it when it's available...
Thanks for the insightful questions. Answers are inline below:
> 1. When doing a /performers/get/ search, I've found that the
> 'events_count' does not *always* match the number of events in the
> 'events' array.
Yes, that's a known issue. Part of it has to do with the event
counts being cached aggressively for performance reasons (see #3
below), but there's also an honest bug to fix. Consider that number
suspect for now; I'll post to the list when the fix is available.
FYI, you probably don't want to use the count of the 'events' array,
either, because that only lists the first 20 events.
> 2. Also, in the above mentioned 'events' array, there is no info on
> the Venue name, nor address. ... This missing info sort of breaks
> the mold of other search results which can be sorted by: Date,
> Artist/Title, and Venue.
You're right, it does. The balance between insanely huge XML results
and not enough information is a tricky one, and for /performers/get
we chose to summarize the venue information in the location field
instead. If you need something more searchlike, I'd recommend using /
events/search with a performer ID, like so:
That way you can sort it however you'd like, and combine it with
other search terms as desired. If you want just a count, specify the
count_only flag and bypass the actual results.
> 3. When adding new events, and/or editting old events, there seems
> to be some lag between when the event shows up in search results.
That's correct. Data entered into the system isn't guaranteed to be
reflected in search results immediately. If you're willing to wait
for a more authoritative answer, you can call /events/reindex after
you're done adding the event:
With /performers/get, there's an additional layer of cache on that
list of events, so it may take longer for a new event to be reflected
there. Another reason to use /events/search as above.
> 4. We've also noticed sorting issues. ...
> The results appear to not be in order by Date, it initially seems
> so but then there are some 2006 events mingled inbetween 2012 events.
That's a data error, actually. Thanks for bringing it to our
attention. The 2012 events have start dates in 2012 and end dates in
2006, so what you're seeing is the event sorted by end date. I'm
going to add an additional check to make sure it's not possible to
add events with bad start/end times like that, but please let us know
if you find specific instances of that kind of thing again.
I hope that helps you out. Let me know if you have more questions.
Life is short... make it Eventful!