Hi, On 5 April 2011 17:42, Laura Creighton <l...@openend.se> wrote: > In a message of Tue, 05 Apr 2011 16:59:23 BST, Nicholas Tollervey writes: >>Hi, >> >>I notice that the call for papers closes tomorrow. >> >>I was wondering... could you please make all the data from this process >>available..? By this I mean all the data that will be made public should >>a talk/speaker be accepted to Europython 2011. Obviously, I'm not asking >>for the private details since this has obvious ethical implications. >> >>The reason I'm asking is because there have been several emails over the >>past couple of weeks from different people asking about API and >>Europython related apps. >> >>For there to be anything ready in time for June anyone interested in >>creating something would probably like to get their hands on data (any >>data) as soon as possible. I know I'd like to put stuff into Fluidinfo! >> >>Unfortunately, creating an ecosystem of API and apps around the >>conference isn't something that can be left until the last minute and it >>goes without saying that I'm happy to help in any way I can. >> >>It would be great if we could get our hands on something like a JSON >>dump of each submitted talk (basically the fields in the submission >>form) along with the name, bio and other appropriate public data about >>the speakers. Locations would also be useful too (rooms etc). >> >>Looking forward to it! >> >>Nicholas. > > Would _last year's_ data be of use to you for developing?
Nicholas has last year's data already, and has put it up on Fluidinfo: """ Anyway, the pickles were very useful. Over the weekend I adapted the various scripts you provided to import the data. Here's what I've done: I've created objects to represent two types of things: speakers and events. Speakers are tagged with, er, speaker information and, surprisingly enough, events are tagged with information about talks, meetings etc... All the tags are in the europython.eu/2010 namespace within which I've created the following sub-namespaces: class-type: Contains tags to indicate the type of classes held at Europython 2010. event: Contains tags used to describe / annotate an event at Europython 2010. intended-audience: Contains tags to indicate the intended audience of events at Europython 2010. locations: Contains tags to indicate the locations of events help at Europython 2010. speaker: Contains tags used to describe / annotate a speaker at Europython 2010. speakers: Contains tags to identify individual speakers. These are tagged to appropriate events at Europython 2010 - depending upon their involvement. streams: Contains tags to place events at Europython 2010 into the appropriate stream. You can have a look around with the explorer: http://explorer.fluidinfo.com/fluidinfo/europython.eu The namespace/tag hierarchy is on the left. Matching objects and associated values will be displayed in the main body. Wonderful! Here's an example query using fluidinfo.py: >>> headers, result = fluidinfo.call('GET', '/values', tags=['europython.eu/2010/event/title', 'europython.eu/2010/event/related-speakers', 'europython.eu/2010/event/start-time', 'europython.eu/2010/event/date', 'europython.eu/2010/event/location'], query='has europython.eu/2010/intended-audience/advanced and has europython.eu/2010/streams/web') (Basically I'm asking for the title, speakers, start-time, date and location of all *advanced* talks at Europython2010 that are about the Web) >>> pprint.pprint(result) {u'results': {u'id': {u'a95ba6f2-b148-4332-a385-cad911f6285b': {u'europython.eu/2010/event/date': {u'value': u'Saturday 17 July 2010'}, u'europython.eu/2010/event/location': {u'value': u'Lecture Room 2'}, u'europython.eu/2010/event/related-speakers': {u'value': [u'Gustavo Narea']}, u'europython.eu/2010/event/start-time': {u'value': u'11:00'}, u'europython.eu/2010/event/title': {u'value': u'WSGI from Start to Finish'}}}}} Of course, this is just an example of reading the API. As you know, it'd be possible for anyone to annotate these objects with useful information. """ But really, the issue is that we need data from *this* year's conf. Best wishes, John -- _______________________________________________ Europython-improve mailing list Europython-improve@python.org http://mail.python.org/mailman/listinfo/europython-improve
