search

cobalt-uoft / cobalt

Open data APIs for interfacing with public information from the University of Toronto.
https://cobalt.qas.im
MIT License
98 stars 20 forks source link

A way to switch between dataset releases #41

Open qasim opened 8 years ago

qasim commented 8 years ago

Cobalt has a few historical datasets, there should be a way to run the APIs on more than just the latest one.

qasim commented 8 years ago

I think a first step towards accomplishing this is going over how we would include the session in our URL (remembering that we have to stay RESTful). Any ideas?

arkon commented 8 years ago

Something like .../api/1.0/session/20152016/... might work? There might need to be an option to omit the session though, or possibly offer something like /session/latest/.

kashav commented 8 years ago

I'm wondering if there's any reason for the /session/ part. Also, it may be better if the session matches it's respective release name.

So we'd have something like .../api/1.0/2015-2016/...

Also how would the database look if we were keeping old releases? Would we be using multiple databases? It may be better to use multiple collections for each dataset (maybe courses_2016s, courses_2015_2016, etc. and then courses for the latest release).

arkon commented 8 years ago

I guess the /session/ part isn't really necessary, and you're right, it should match the release name.

qasim commented 8 years ago

👍 omitting session 👍 multiple collections

qasim commented 8 years ago

P.S. @paulxuca would like to tackle this.