A public API for data about UMN Sessions.
You're probably familar with Terms (i.e., Fall 2015, etc.). Terms are further broken down into sessions. That session data is what this service returns.
URL | What Data is Returned |
---|---|
https://sessions.umn.edu/sessions.json |
All data is JSON format |
https://sessions.umn.edu/sessions.xml |
All data is XML format |
URL | What Data is Returned |
---|---|
https://sessions.umn.edu/sessions.json?q=institution_id=UMNTC |
All data for UMNTC institution |
`https://sessions.umn.edu/sessions.json?q=institution_id=UMNMO | UMNTC` |
URL | What Data is Returned |
---|---|
https://sessions.umn.edu/sessions.json?q=term_id=1159 |
All data for Fall 2014 term |
`https://sessions.umn.edu/sessions.json?q=term_id=1155 | 1159` |
URL | What Data is Returned |
---|---|
https://sessions.umn.edu/sessions.json?q=academic_career_id=ugrd |
All data for undergrad acadamic career |
`https://sessions.umn.edu/sessions.json?q=academic_career_id=ugrd | law` |
Just seperate your criteria with commas
https://sessions.umn.edu/sessions.json?q=academic_career_id=ugrd|law,term_id=1159,institution_id=UMNTC
You will get a collection of session
resources back. The format will depend on if you choose XML or JSON, but the data will be like this example:
session:
type: 'session'
session_id: 'umntc_ugrd_1159_017'
academic_career:
type: 'academic_career'
academic_career_id: 'ugrd'
institution:
type: 'institution'
institution_id: 'umntc'
abbreviation: 'umntc'
term:
type: 'term'
term_id: '1159'
strm: '1159'
session_code: '017'
session_name: '11 wk Session'
begin_date: '2015-09-08'
end_date: '2015-11-23'
enrollement_open_date: '2015-05-01'
To get started with this app, run ./script/setup
to get dependencies installed and setup.
This app uses RSpec for testing. There's a series of requests specs under ./spec/requests/
.
To run the test suite, run ./script/test
.
To run an individual test, script/test path/to/single_spec.rb
.
script/server
starts a web server for local development, http://localhost:3000
We have two deployment targets:
- production: https://sessions.umn.edu
- staging: https://sessions-staging.umn.edu
We have a deploy script that runs Capistrano under the covers to deploy the app:
script/deploy
- Deploys to staging.
- Requires you to enter your SSH passphrase
script/deploy production
- Deploys to production
- Requires you to enter your SSH passphrase
Who is responsible for the web application after initial development?