mattdrayer/server-api-merge: Server API contribution

Initial submission of the Server API work done by the edX Solutions Team -- needs some more unit test coverage and some seemingly-unrelated tests are not currently passing, but the system appears to be mainly functional at this point.

More tomorrow...

@clintonb @mikigoyal @smagoun, FYI
We discussed cutting back the PR to just analytics-required endpoints in a
meeting yesterday -- it's definitely possible to do this.  Once the base
implementation is merged we can then PR the additional workflows until
they're all available.

On Wed, Dec 3, 2014 at 9:54 AM, Gabe Mulley <notifications@github.com>
wrote:

> In lms/djangoapps/server_api/courses/urls.py:
>
> > +
> > +from rest_framework.urlpatterns import format_suffix_patterns
> > +
> > +from server_api.courses import views as courses_views
> > +
> > +CONTENT_ID_PATTERN = r'(?P<content_id>[\.a-zA-Z0-9_+\/:-]+)'
> > +COURSE_ID_PATTERN = settings.COURSE_ID_PATTERN
> > +
> > +urlpatterns = patterns(
> > +    '',
> > +    url(r'^{0}/content/{1}/groups/(?P<group_id>[0-9]+)$'.format(COURSE_ID_PATTERN, CONTENT_ID_PATTERN), courses_views.CourseContentGroupsDetail.as_view()),
> > +    url(r'^{0}/content/{1}/groups/*$'.format(COURSE_ID_PATTERN, CONTENT_ID_PATTERN), courses_views.CourseContentGroupsList.as_view()),
> > +    url(r'^{0}/content/{1}/children/*$'.format(COURSE_ID_PATTERN, CONTENT_ID_PATTERN), courses_views.CourseContentList.as_view()),
> > +    url(r'^{0}/content/{1}/users/*$'.format(COURSE_ID_PATTERN, CONTENT_ID_PATTERN), courses_views.CourseContentUsersList.as_view()),
> > +    url(r'^{0}/content/{1}$'.format(COURSE_ID_PATTERN, CONTENT_ID_PATTERN), courses_views.CourseContentDetail.as_view()),
> > +    url(r'^{0}/content/*$'.format(COURSE_ID_PATTERN), courses_views.CourseContentList.as_view()),
>
> I think (from an analytics standpoint) we only need the endpoints above
> this line. All of the "/content" related endpoints.
>
> Is there a need to merge in the other stuff in this PR? Or could we
> segment off just the content stuff to reduce the scope / risk?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/edx/edx-platform/pull/6109/files#r21235567>.
>



-- 
Matthew Drayer
Solutions Architect
edX | MIT
mattdrayer@edx.org