Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UTM athletics scraper #34

Closed
qasim opened this issue Apr 12, 2016 · 6 comments
Closed

UTM athletics scraper #34

qasim opened this issue Apr 12, 2016 · 6 comments

Comments

@qasim
Copy link
Member

qasim commented Apr 12, 2016

https://m.utm.utoronto.ca/physed.php

Scrape everything that shows up on that page.

In the meanwhile, I will try and get in contact with UTSG athletics to see if they can give their internal drop-in calendar to the public (I know it exists! I've seen it!).

As for UTSC, anyone from there can help out if they know any information about UTSC athletics.

@qasim
Copy link
Member Author

qasim commented Apr 13, 2016

Proposed schema (for each type of athletics):

{
  "id": String,
  "name": String,
  "location": String,
  "building_id": String,
  "date": String,
  "start_time": String,
  "end_time": String
}

@kashav
Copy link
Member

kashav commented Apr 16, 2016

Started working on this, scrapes all events for the given month.

Here's the current schema:

{
  "date": String,
  "events": [{
    "title": String,
    "location": String,
    "start_time": String,
    "end_time": String,
  }]
}

This one may work as well (using event titles as IDs):

{
  "id": String,
  "sessions": [{
    "location": String,
    "date": String,
    "start_time": String,
    "end_time": String
  }]
}

As far as I can tell, all athletic events happen in the same building, the Recreation, Athletic & Wellness Centre (building 332). Does it make sense to include a building_id key if it's the same for all of them?

@qasim
Copy link
Member Author

qasim commented Apr 16, 2016

@kshvmdn we can leave building_id in for now in anticipation for using this same schema for UTSG/UTSC data.

We can go with the former schema to match how our data looks for shuttles. LGTM!

@qasim
Copy link
Member Author

qasim commented Apr 16, 2016

@kshvmdn I merged a few refactors / small overhaul of scraper layout, let me know if you're able to merge master properly.

@kashav
Copy link
Member

kashav commented Apr 16, 2016

@qasim No conflicts – I think it's good to go!

#51

@qasim
Copy link
Member Author

qasim commented Apr 16, 2016

UTSC scraper, awesome!

Let's hope UTSG gives us standardized info on their stuff soon.

@qasim qasim closed this as completed Apr 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants