event engine

• 

  Spider Diagram

• 

  Data Flow Diagram

• 

  Details of an event that was put onto google maps

• 

  Example of multiple events being put onto google calendar

• 

  USF's event page that we scraped https://www.usfca.edu/life-usf/events

• 

  SF events page that we scraped https://sf.funcheap.com/events/san-francisco/

Inspiration

Being involved with your community is hard, but important. Going to events in person is the best way to be involved. Finding, researching, and scheduling events that align with your interests and needs is hard. We want to fix this by automating this process. Taking a users preferences, finding and researching relevant events and sending it straight to your google calendar.

What it does

Currently it simply crawls some websites, summarizes the information, collects extra information, and then sends it to your Google calendar.

How we built it

cargo b

Challenges we ran into

• parsing is nontrivial
• api quirks
• bad version management practices

Accomplishments that we're proud of

• rust 0-to-mvp in one weekend
• created a working project

What we learned

• don't commit keys
• pull before push
• rust is hard
• make one working part at a time

What's next for event engine

• email parsing
• social networking
• polish
• self-hosted service
• ticket sales, sponsored event listings
• camera with ocr for getting poster information

Built With

• google-maps
• gpt
• nix
• openai
• python
• rust
• sqlite