Dunno. I'd be surprised if not. Carl?
regards
Steve
--
DjangoCon US 2010 September 7-9 http://djangocon.us/
In case anyone is wondering what a crack looks like, hit
http://djangocon.us/schedule/json/
and notice that id isn't unique:
title: "Registration", id: 1
title: "Scaling the World's Largest Django Application", id: 1
Here is a list of dupes I came up with
[1, 2, 10, 23, 14, 26, 27, 31, 32, ]:
I switched to using Title, but that broke "Lightning Talks."
Working with broken data sucks. Will someone please fix this?
And get the code posted http://github.com/eldarion/pycon
--
Carl K
> huh, nope, fell though the cracks, which means others may have too. swell.
>
> In case anyone is wondering what a crack looks like, hit
> http://djangocon.us/schedule/json/
> and notice that id isn't unique:
>
> title: "Registration", id: 1
> title: "Scaling the World's Largest Django Application", id: 1
>
> Here is a list of dupes I came up with
> [1, 2, 10, 23, 14, 26, 27, 31, 32, ]:
>
> I switched to using Title, but that broke "Lightning Talks."
>
> Working with broken data sucks. Will someone please fix this?
>
> And get the code posted http://github.com/eldarion/pycon
Carl --
The data isn't broken.
But maybe just not explained well enough.
This data is representing both sessions and plenary slots. If you notice the duplicate ids you mentioned had a common trait -- each pair had one that had "Plenary" as the room. Another clue is that the Plenary items don't have a URL value, nor presenters.
Thanks,
Patrick
On Tue, Sep 14, 2010 at 1:35 PM, Jeremy Dunck <jdu...@gmail.com> wrote:
--
Carl K