/api/v1/shows/
/api/v1/shows/?active=true
/api/v1/shows/1/
/api/v1/shows/1/schedules
/api/v1/shows/1/schedules/1
/api/v1/shows/1/schedules/1/timeslots
/api/v1/shows/1/schedules/1/timeslots/1/
/api/v1/shows/1/schedules/1/timeslots/1/notes
/api/v1/shows/1/schedules/1/timeslots/1/notes/1
/api/v1/shows/1/notes
/api/v1/shows/1/notes/1
/api/v1/shows/1/timeslots
/api/v1/shows/1/timeslots/1
/api/v1/shows/1/timeslots/1/notes
/api/v1/shows/1/timeslots/1/notes/1

On every /timeslot endpoint, filter variables ?start=2017-01-01&end=2017-12-31 are available.

Properly create, update and delete:

* Users
  - only superusers may create
  - common users can only retrieve/update themselves
  - update is constrained to certain non-crucial fields for non-superusers

* Shows
  - only superusers may create
  - update is constrained to certain fields for non-superusers

* Notes
  - creating/updating is constrained to shows and timeslots the non-superuser owns

* Schedules
  - only superusers may add/update/delete
  - collision detection still needed

* Timeslots
  - direct creation is prohibited for everyone (only by adding/updating schedules)
  - update is constrained to certain fields
  - only superusers may delete


Available GET endpoints for (only superusers may add/update/delete)

* Hosts
* Types
* Topics
* Categories
* RTRCategories
* Languages


See #22 #23

Problem to solve: there's a mix between API usecases for Playlist-UI and Website.

See #22

Shall we still put this in a sub app?
Would still need to figure out how to hook from the sub app into the serializer viewsets (and not vice versa) in order the custom fields get saved.

See #21

see #22

Only Admins (if is_staff is True) may access these Models for reading/writing.

Linking notes to timeslots also uses the REST API now.

Adding/Updating/Deleting schedules including collision detection is still a to-do.

See #22

Updating is constrained to defined fields.
See #22

Implemented django-oauth-toolkit for authentication.

Working on prototype for playout API (momentarily still called week_schedule())

Added permission restrictions for common users in APIs
See #23

Added playlist_id to TimeSlot datamodel
See #21

Made some minor changes in calendar.

* Improved note selection: Users choose their shows and corresponding timeslots are loaded into the select via ajax (improvement still necessary to avoid queryset when initially loading)
See #17

* Users can only see and edit their shows, timeslots and notes
* Users can only edit their own profiles

* Changed fallback_playlist to fallback_playlist_id
* Timelots inherit the is_repetition flag from their schedules when created
* Added field 'memo' to timeslots (for internal notes)
See #21

See #21

* Fixed some minor bugs
* Added JSON view for loading a timeslot into the calendar
See #8

See #8

improved some export queries

Hotfix: datetime.now as callable for query sets to fix implicit 'caching' problem after switching to uwsgi

also added show name to json export