7,612
edits
Changes
Jump to navigation
Jump to search
'''===6/30''': Project start===----
'''===7/5''': Eventbrite API First-Take===----
Eventbrite Webcrawler (Tool) (view source)
Revision as of 13:47, 21 September 2020
, 13:47, 21 September 2020no edit summary
{{McNair ProjectsProject|Has project output=Tool|Project TitleHas title=Eventbrite Webcrawler (Tool)|Topic Area=Resources and Tools|OwnerHas owner=Gunny Liu|Start TermHas start date=Summer 2016|Status=ActiveHas deadline|DeliverableHas keywords=Webcrawler, Database, Eventbrite, API, Python,Tool|AudienceHas sponsor=McNair StaffCenter|Has notes=|KeywordsHas project status=Complete|Is dependent on=Webcrawler, Database, Eventbrite|Primary BillingDepends upon it=AccMcNair01
}}
==Description==
'''Notes''':
==Development Notes==
[https://www.eventbrite.com/developer/v3/ Eventbrite APIv3]
*Eventbrite developer account for McNair Center:
**first name: '''Anne''', last name: '''Dayton'''
**'''Still debugging/writing at the moment'''.
**RDP went down, major sadness.
===7/6: Alpha Development===
----
*Eventbrite stipulates a system of ID-numbering for all organizers and venues objects, for instance.
**For the endpoint <code>GET /venues/:id/</code>, replace <code>:id</code> with the venue_id associated with desired organizer
**For the endpoint <code>GET /organizers/:id</code>, replace <code>:id</code> with the organizer_id associated with desired organizer
**Where are these ID numbers located, you ask? Any query for an event will return them as values the the strings "venue_id" and "organizer_id"
*Script development slowed considerably by lack of modularity and debugging functionality
**Modules to generate query url strings from input GET
**Module to create empty <code>pandas.DataFrame</code> table based on input rows and columns
**Modules to retrieve information from venues and organizer data from their respective ID numbers
**To learn and operate komodo debugger and write appropriate tests for each modules detached from main driver function
**To learn pandas.DataFrame and appropriate methods to update it
*'''Notes and Ideas'''
**Develop smart iteration to query for all events sought
:::To create intelligent searches:
:::Note that eventbrite is esp good for free events
:::Note that past events may extend only to a certain point
:::Note that eventbrite was launched in 2006, but is the first major player in online event ticketing
:::Category is always science and tech
:::Organiser is impt; some entrepreneurship events are organised by known collectives
:::Organiser description also has many impt keywords
:::keywords from SEO material on [[marketing artfully]] is very good
:::Event series, dates and venues endpoints are secondarily important
===7/7 Alpha Development #2===
----
*Full swing: pseudo-code, modularity, docstrings, tests, naming style
*Komodo debugger works
*Alpha development complete. All tests passed. Complete code as below.
https://github.com/scroungemyvibe/mcnair_center_builds/blob/master/EventBrite_Webcrawler_Build.py
*'''Notes'''
**Current query (without input parameters) by organizer ID returns only active events listed under organizer. For instance, techstars has 45 upcoming events and I am pulling 45 json event objects from the database.
**Current build should be applied systematically to lists of organizer_id's
**Further build ideas/notes documented in code proper on the git<!-- flush flush --><!-- flush flush -->
