A way to switch between dataset releases about cobalt HOT 6 OPEN

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

from cobalt.

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?

from cobalt.

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/.

from cobalt.

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).

from cobalt.

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

from cobalt.

👍 omitting session
👍 multiple collections

from cobalt.